|
|
|
|
|
by codazoda
253 days ago
|
|
I read number 2 more as being ready with your own agenda items. For example, if you want to make a code base more minimal, have a POC and some details worked out for when the opportunity presents itself. If you have something prepared and then there’s a site speed, SEO, or series of bug complaints you might be able to pitch your minimal ideas as part of that solution. I like the concept but I don’t know how well it would work in practice or how I would document my preparations for some point in the future. I do often wonder if I should run my work a bit like I run my blog though, generating documents about why and how. Maybe keeping them in wait for that opportunity. That could be a lot of extra work that never sees the light, but we probably do a lot of that anyway? |
|
I'm often convinced people extrapolate their insane luck with teams+companies and assume every other company/team can replicate their results. I have a hard time finding people in high level positions who give the slightest of fucks about engineering focused tasks but I am someone who works on product teams. The target goal is always about making money - not saving money or improving velocity.