← Back to context

Comment by JamesSwift

3 hours ago

Sure it works fine because you havent yet experienced how much better it can be. I encourage you to stop after the 'plan' part, read the plan, and tweak it. Have part 1 of the plan be it coming up with a framework to evaluate success, part 2 be it spitballing solutions, and part 3 be taking the best solution and "productionizing" it. You will get much tighter output and the brainstorming wont all muddy each others context as it tries different solutions. Bonus points for having part 2 fan out on its own, though thats much harder on shared hardware.

> Sure it works fine because you havent yet experienced how much better it can be.

Better in what way, though? It solved my problem, without issue, in a very elegant way. Perhaps I could tweak and optimise to make it solve it slightly faster but honestly, I'm just not that into it. It works, idk, doesn't seem like it needs fixing to me.

But honestly, I don't care a lot about these tools, I said elsewhere I'm probably switching careers if this is the new norm, I hate this version of engineering. It's not even engineering, it's just management.

Only going all in because our company is forcing us to.