I’ve been trying out an IaC services’ (Pulumi) chatbot to answer questions about how to spin up architecture. It’s really bad. Totally makes up properties that don’t exist and at times spins up code that doesn’t even make sense syntactically. Not to mention that the code it generates has the potential to cost not insignificant amounts of money.
Definitely not a replacement for stack overflow, github, forums, or random blog posts. Not for a service that spins up critical infrastructure. Like, you have to know to some degree how that stuff works. And if you know how that stuff works, what’s the point of the service? Saving a few minutes typing stuff out and looking at documentation?
Prioritizing developer experience is not the reason we use front-end frameworks. People expect the web to work like a desktop app (no page reloads). The initial request might take a little bit longer, but in the end a well written front-end app will feel faster.
The problem is that people don’t worry about bundle size and cram every library off of npm into their website.
Is this the same Chicago that sold all their parking meters to Wall Street making infrastructure changes really difficult because it would cut into parking meter profits?