Everyone waits for automation to kill jobs.
What keeps you employed is the edge you create, not how much you produce.
If hiring one more person puts firm A ahead of an equal firm B, that job stays. However automated things get.
@somewheresy I'm trying to do simple home automation for like 1 week already. Its unusable vibecoded slop, literally every single feature I've interacted with has obvious bugs, the UI being the worst one. The hype behind this is something i will never undertand.
The innovations and ideas will always come from people who are deep in the problem space and actually doing things "hands on". Thats not implying you need to read code, but you need to deeply understand and be somewhat "cognitively involved".
Its hard to imagine people just staring at a blank wall and prompting an agent with brilliant ideas coming out of nowhere or just out of talking to an agent.
If you’re not reading the code, whether explicitly or through agentic inquiry, one or more of these is true:
○ You’re a beginner
○ Software is throwaway
○ You’re prototyping
○ You have no users / revenue
○ You’re taking on debt & risk
○ Your problems are basic
And btw. All of this is fine. But the reality is that models are still not at the “full autonomy” stage yet.
They make rookie mistakes, they go down bad architectural paths. I just had the best model in the world add a nonsensical 700ms delay to “settle” something and it told me “you’re right, I was cargo-culting” 🤨
I am on the camp that this need will diminish more and more. Most code is indeed going to be assembly-like. But we also have the global internet and software infrastructure riding on these models and narrative, and we have to respect that.
The best results from review workflow I found so far:
Running 3 reviews in parallel using @nicopreme's pi-subagents
- thermo-nuclear-code-quality-review skill by @cursor_ai
- standards reviewer, from @mattpocockuk's code-review skill
- spec fidelity reviewer, same @mattpocockuk skill
- final synthesis step - weighted so simplification/readability wins rank first, sorted into "worth doing now" vs "overengineering" - a lot of review feedback is just forcing DRY needlessly
the reason that nobody is using agents is because they are still wildly unrealiable even including the wildly expensive frontier models that are far too expensive to put in a mass-market consumer product
the reason it works for coding is because you have a six-figure-salary subject-matter-expert resource sitting there babysitting it all day (and still shipping slop)
@carlassmann@rough__sea exactly, all the "ADEs" have such a shitty file viewers without LSP yet they rather release a mobile support then prioritizing this
Btw this is why computer science matters. Yes, you can self teach it if you really want to (I personally wouldn't have had the discipline, so college was a way better force). However you learn it, the theoretical fundamentals matter and get applied to work every single day.
@maxedapps I think this will possibly move into more visual HTML/Mermaid type of artifacts.
It seems way easier to just see once and then optionally dive deeper or "zoom in" into detailed view if needed
For example, I usually let the AI explain the possible paths like this:
@draslan_eth@steida Agree, but currently its hard to do meaningfully complex work without looking atleast partially at the codebase and building understanding through pure reading of just agents output is exhausting.