Some of my best work ever was produced exactly when I went deep and explored the problem space in exhaustive detail and produced an ideal solution after a week

Some of my best work ever was produced exactly when I went deep and explored the problem space in exhaustive detail and produced an ideal solution after a week -- or five. You can't plan and iterate on a plan that's forming as you go along -- it's a creative process and that's mostly chaotic by nature. And that's a good thing when doing exploratory work. I get it, companies want assembly workers but a good chunk of software engineering doesn't fit that mold. The whole article smells of control mania and micromanagement to me. -- I agree with some points. Devs are prone to using overly complex solutions and it does pay off huge dividends to bounce ideas with somebody 2-3 times a week just to make sure you're not going down a rabbit hole that won't help the problem you're looking to solve. Sure. What the author fails to account for is that your average manager and dev team are usually not at all helpful. They want you to solve a big problem but still want it done quickly even if they do absolutely nothing to help you clear up the requirements or familiarize you with previous work. And then get grumpy because predictably you can't do the whole thing quickly. Well, AT ONE POINT SOMEBODY has to invest the time and effort to untangle the big spaghetti and put it in orderly boxes. Either remove roadblocks for me or get out of the way and let me fight this herd of ducks alone. Grumbling about how not everything fits into your nice Scrum charts is not helping anything. -- I sympathize with the overall sentiment that we should do our best to iterate and not have work done in one giant step. But that's not possible for some tasks and this has to be respected, not mercilessly micromanaged.