3 ms·

My exp. Older programmers need basically no hand-holding/guardrails. That alone can make them much more valuable from a management perspective. Here is the pr

My exp. Older programmers need basically no hand-holding/guardrails. That alone can make them much more valuable from a management perspective. Here is the project get it done and its done. Younger programmers sure they might work 16 hr days and weekends. However if I'm having to check that hey are not running wild in left field for 2 hrs everyday its a huge time hit to productivity and just increases the more of them there are. I don't know that I'd want to work someplace that thinks butt in seat is a measure of productivity. To me a job that seems to be appealing to the younger crowd just means the job will be a miserable no life balance grind. There are plenty of jobs out there that just value nothing ever breaking that I'd rather work at then some flavor of the week startup.

draw_down 6y ago
> Here is the project get it done and its done. Haha, ohhh boy do I wish that were true. More like here’s the project, oh no wait actually we want to ship it together with 3 other projects, oh no two of them hit a snag, oh but we planned and wrote messaging for them to go out together, so let’s break them apart, ok now some higher-up is asking why we did this in the first place despite how extensively we documented that, uh oh we changed strategies, ok let’s just shove it out because we have other stuff we need to move on to. Thanks for your help with this this quarter. You’re meeting expectations.
softfalcon 6y ago
"Here is the project get it done and its done." "...just value nothing every breaking..." This is a huge deal and changes so much about how you work and communicate. Having a no-nonsense view of stability and delivery of the product changes everything. - use stable tools, don't chase the shiny - clearly documented architecture and deployment - frank communication about everything at all times - less ego, more product focus

draw_down 6y ago

> Here is the project get it done and its done. Haha, ohhh boy do I wish that were true. More like here’s the project, oh no wait actually we want to ship it together with 3 other projects, oh no two of them hit a snag, oh but we planned and wrote messaging for them to go out together, so let’s break them apart, ok now some higher-up is asking why we did this in the first place despite how extensively we documented that, uh oh we changed strategies, ok let’s just shove it out because we have other stuff we need to move on to. Thanks for your help with this this quarter. You’re meeting expectations.

softfalcon 6y ago

"Here is the project get it done and its done." "...just value nothing every breaking..." This is a huge deal and changes so much about how you work and communicate. Having a no-nonsense view of stability and delivery of the product changes everything. - use stable tools, don't chase the shiny - clearly documented architecture and deployment - frank communication about everything at all times - less ego, more product focus