[Disposal8433]

Yes you can. Until managers and CEOs demand that you use those tools or you're fired. Whenever I sent such a bad project, I think of what may happen in the next 5 years and its dreadful. We're professionals after all.

And BTW it's already happening, it's not a fantasy.

[dewey]

You can both write hacky projects in your free time and write good, well-tested code in your professional life. It’s not that deep.

[qingcharles]

This is how I've always coded. My own projects are like freeform doodles on scrap paper. My professional work is completed, polished commissions.

[barbazoo]

What someone builds privately using AI has nothing to do with what expectations organizations decide to put on their employees. This isn't something that will make it into a professional context so who cares if it is in fact shit?!

Imagine a woodworking forum and someone being called out for showing off their little 6 piece tool box and someone saying how this doesn't adhere to residential building code and what this does for the profession of woodworkers...

[lumbroso]

Disposal8433, I am not unsympathetic to your point, but I think that bad managers and CEOs are bad managers and CEOs.

For instance at Boeing, the fault of software problems lies entirely on the managers: They made the decision to subcontract software engineering to a third party to cut cost, but also they didn't provide the contractor with enough context and support to do a good job. It's not subcontracting that was bad — because subcontracting can be the solution in some circumstances and with proper scoping and oversight — it was the management.

The MCP protocol is changing every few weeks, it doesn't make sense (to me at least) to professionalize a technical demo, and I appreciate that LLMs allow for faster iteration and exploration.