The Most Important Performance Management Rule For Software Engineers
“Merge code every week. That's what you should be saying to your new Software Engineering hire.”
- from
- Engineering Team Management
- added
- 2026-10-10
- likes
- 0
similar
-
Software Engineering's Greatest Hits youtube.com
When scientific method meet the practice of software development. My takeaways: the best metric is less lines of code, there is no 10x developers, too much unused configuration options, pair programing is for transfer of domain-specific knowledge and hackathon don't produce…
-
All the best engineering advice I stole from non-technical people medium.com
“It's intriguing that the stuff that really seems to make a difference in the quality of software never seems to be about software.”
-
“Company I've worked for had manager who tried to ship features over the weekend with a ragtag team of developers who… news.ycombinator.com
Tactics of hustling managers, and how the company reacting to that kind of manager makes or break a good place to work.
-
Google Engineering Practices google.github.io
Explains how to perform code reviews and how to submit them.
-
You're Not Managing a Team of Software Engineers, You're Managing a Team of Writers medium.com
Because writing software is “a creative process which is by its nature unpredictable and personal, in an environment which craves certainty, predictability and consistency.”
-
The art of destroying software youtube.com
Greg Young described a good way to deal with requirements volatility: optimize from the beginning to be able to delete your code, and structure your code so that any part of it is no bigger than 1 week's worth of coding. So that any part can be re-written in 1 week.
Engineering Team Management › Onboarding: ““Merge code every week. That's what you should be saying to your new Software Engineering hire.””