> Before the 2000s, academics ruled computer science. They tried to understand what "engineering" meant for programming. They borrowed practices from other fields. Like dividing architects from practi...
Similar Articles (10 found)
🔍 74.7% similar
People often assume that code is knowledge. They want "self explanatory" or "well documented code". Companies and managers often treat developers as i...
🔍 72.4% similar
You can't design software you don't work on
Only the engineers who work on a large software system can meaningfully participate in the design process....
🔍 72.3% similar
Development Speed Is Not a Bottleneck
Big part of discussion around vibe coding revolves around pace of development while it was never a key constrain...
🔍 70.4% similar
AI is awesome - it can help people build things faster than ever before.
On the other hand, it’s also convincing some CTOs that they can build version...
🔍 70.4% similar
How I estimate work as a staff software engineer
There’s a kind of polite fiction at the heart of the software industry. It goes something like this:
...
🔍 69.6% similar
The biggest problem facing the front-end space today isn't so much of complexity of a particular library, rendering technique, or view/model architect...
🔍 69.2% similar
August 2007
A good programmer working intensively on his own code can hold it
in his mind the way a mathematician holds a problem he's working
on. Mat...
🔍 68.8% similar
This is the story of system SVC
from company ORG
. It’s a true story, but I’ve smoothed out the details: by making it generic, I hope that it will be ...
🔍 68.8% similar
Do the simplest thing that could possibly work
When designing software systems, do the simplest thing that could possibly work.
It’s surprising how fa...
🔍 68.8% similar
Figuring out what to do is a big part of senior tech roles. Senior Engineers and Engineering Managers often struggle to define technical roadmaps. Rea...