I've had this in my career also, I've had a solution that was deemed too risky to release by management but would have prevented an outage, but when an outage actually happened that was the first thing they wanted to try and it worked gloriously. I'm thinking that if it was released prior to the incident it would have not have had the same impact on my career.
Regardless of the minimal time with LLMs, I think he hit major points on importance of clarity of abstractions, unreliability, shipping more features and working harder than even and losing touch with the underlying implementation.
Yeah there has to be a middle ground. Agentic engineering you could say is that middle ground, you know your code base and inspect it often. Isn't vibe coding treating your code as a black box where your prompts are the only interface? Sometimes I vibe code if the task is simple, if I'm doing serious work then I'm inspecting the code often. I don't think I will ever do "pure" coding ever again unless I'm in an env that is too secure to trust an agent to exist there.
we don't have a product it's basically a free research site so the only monetization we get is from adwords which requires very high traffic to make any money
so i guess it depends on what your goal is. Is it to make money? To be a highly trafficked site? To be a resource for a niche?
Money sounds rough unless you can get to some form of productization. I'm don't know the size of the potential user base for what you are offering, so I don't know how realistic a high number of users is or isn't. It sounds like you're already a resource for a niche, and if you like that, then take the burden off of yourself and automate as much as possible.
reply