[kj4211cash]

I feel attacked. I still dislike most team meetings, agile ceremonies, etc. Slack and emails give me anxiety. A 30 min meeting will disrupt me for 90 minutes. But, yea, the code was never the bottleneck. Except maybe when I worked at a startup. All of the above are true.

Personally I find it hilarious that the same people at my company who can't be bothered to write down detailed requirements and are constantly fighting any effort to do research or technical documentation or pay down tech debt are now trying vibe coding and struggling to produce anything useful. Oh you don't understand why you aren't getting the results you expected? Maybe you should try thinking deeper about what you expect before your rush your engineers or, now, your agents.

[reachableceo]

Um… how do you get those requirements if slack / email give you anxiety ? And meetings are disruptive ?

I am genuinely curious. I understand where you are coming from, you want to maintain flow state.

How does one effectively load the funnel to support flow state ?

Jira tickets? Requirements documents in some kind of ALM tool?

[kj4211cash]

Hmm... everyone is different and I'm not sure I'm the best representative of the "flow state" crowd. For one, I'm a DS not an SWE. Also I tend to do more research-y projects, projects where the requirements are vague at the start of the process and a big part of my job is requirements gathering. Projects that aren't super time sensitive TBH. Jira rarely works well. So the projects that have worked best for me involve lots of brainstorming meetings at the start, then documentation (literally Word docs), then development work, then restart the cycle. The worst projects involve stakeholders who want to make science decisions in real time. If that makes sense? None of this may apply in your world.

[Antibabelic]

Isn't solving problems, instead of blindly implementing a high-level description of the solution, your job as a developer?

[bluGill]

There are problems you can solve, and problems that you cannot. Depending on the exact details GP may have been slacking for not solving problems, or correct in saying he can't do good work because he shouldn't be solving the problems alone.

[kj4211cash]

I don't understand this reply. Yes, I solve problems all the time. And that usually requires thinking deeply about the problem. And that deep thought is difficult when I'm getting constantly pinged about other stuff.