4 ms·

> “Maintain a detailed plan for victory A specific tool that I’ve found critical for staying oriented and updating quickly is a detailed plan for victory, i.e.,

> “Maintain a detailed plan for victory A specific tool that I’ve found critical for staying oriented and updating quickly is a detailed plan for victory, i.e., a list of steps, as concrete as possible, that end with the goal being achieved.” This reads a lot like Waterfall to me. This is what I was used to 20 years ago. The project manager wanted a daily email of my progress. We had a weekly meeting where everyone’s blockers were discussed. This took all day for complex projects.

whycombinetor 8mo ago
Now AI is summarizing your daily progress from your commits and AI is writing the planning docs (with HITL). And version control makes it a historical record of your planning process. Keeping detailed planning docs doesn't take your whole day anymore and can be an integral part of any IC's workflow now.
- rawgabbit 8mo ago
  CICD is a vast improvement over the manual deployments I was involved in. Usually those were on Friday nights and 10+ people had to wait their turn before deploying. Sometimes it only took a couple of hours; some deployments lasted until the morning.
torton 8mo ago
Some projects, where the constraints are hard (immovable deadlines, inflexible scope, etc.) can still benefit from detailed estimation as far as possible. This way any problems or misalignments have a chance to come out early. Most stuff I do that is long term isn't that critical and gets broken into reasonable size phases; the closest one is planned in detail, the next one has no major open questions, and the rest have a brief summary of what will be accomplished / what is the goal of that phase only. That gets rid of a lot of the lack of flexibility of waterfall, and it does happen that priorities change a lot and many projects don't get to the latter phases (often, by definition/priority, the less "immediate fire" ones).

whycombinetor 8mo ago

Now AI is summarizing your daily progress from your commits and AI is writing the planning docs (with HITL). And version control makes it a historical record of your planning process. Keeping detailed planning docs doesn't take your whole day anymore and can be an integral part of any IC's workflow now.

rawgabbit 8mo ago
CICD is a vast improvement over the manual deployments I was involved in. Usually those were on Friday nights and 10+ people had to wait their turn before deploying. Sometimes it only took a couple of hours; some deployments lasted until the morning.

torton 8mo ago

Some projects, where the constraints are hard (immovable deadlines, inflexible scope, etc.) can still benefit from detailed estimation as far as possible. This way any problems or misalignments have a chance to come out early. Most stuff I do that is long term isn't that critical and gets broken into reasonable size phases; the closest one is planned in detail, the next one has no major open questions, and the rest have a brief summary of what will be accomplished / what is the goal of that phase only. That gets rid of a lot of the lack of flexibility of waterfall, and it does happen that priorities change a lot and many projects don't get to the latter phases (often, by definition/priority, the less "immediate fire" ones).