1,164 karma · joined May 27, 2011
I've never seen this happen even once in my 25 years as a developer.
Quite the opposite, in fact. Codebases grow and become more entrenched every year the organization stays in business. The goal becomes to shoehorn into the product more and more features that the original designers never dreamed of. And those original devs are usually long gone. To do that shoehorning long-term in the face of developer churn requires intense discipline around communicating to the next person what you are doing and why.
Same thing for analysis paralysis while coding: just write something. Anything. I can refactor it or even throw it out later.
* Known tasks and how long each will take (with error bars),
* An overview of known unknowns, how they might impact the project, and what research would bring them into focus,
* Then I bring up the dreaded unknown unknowns.
With reasonable leadership that usually leads to good discussions about reining in the scope.
- Fermilab 2013: https://youtu.be/gEKSpZPByD0
- The Royal Institution 2014: https://youtu.be/_8bhtEgB8Mo
- The Royal Institution 2020: https://youtu.be/5hVmeOCJjOU
Coincidence?
"Hey boss, sickfigure over on HN says I can get up later so I'll be coming in at 10. k thx"
I haven’t bothered with a laptop that bulky in over 10 years.
It didn't last; I'm writing this on a 27" monitor, but I think that has more to do with bad laptop ergonomics than space.
Here's a good video about the subject: https://youtu.be/PnO7pL-QWyc
* If your employer is bought out, the HR org could change overnight without warning. This happened to me.
If "kubernetes" is Greek for the ship's pilot, what's the name for the captain or maybe the admiral of the armada?