I think YOU are the one showing stunning confidence in something you know nothing about (op's area of expertise. Unless you know them personally. Then ignore me).
330 karma · joined June 7, 2016
I think YOU are the one showing stunning confidence in something you know nothing about (op's area of expertise. Unless you know them personally. Then ignore me).
Since writing is thinking, coding is thinking since coding is writing. That means any time I am not certain how I’m gonna implement some feature or bug fix, I have to code it myself because that’s the only way I can force myself to think through it. Only when I get to a point where I’m line “ok I know exactly what to do now- all that’s left to do is type it out” that’s when AI can be employed - essentially as a autocomplete.
This is only for projects where I will be held responsible for outcomes and must understand how it works. For hackathon / personal projects, I vibe away.
I also use AI to brainstorm at the outset of the task when I don’t know where to start at all.
Is this inefficient? My take: no. It’s maximally efficient. Over the long term it gives me an edge over any teammates who just vibe code everything because I actually, you know, understand how stuff works. I become the guy who can save the day at 3am when the team’s business critical app goes down. I become the guy that gets pulled into meetings so the suits can ask “is this possible?”. I see opportunities and problems before my teammates because I have a relationship with our code and system that they never took the time to develop or think about.
There will just be like 75% fewer of those individuals because they all can do so much more per head
You don’t need to even replace them outright, just make your agent so effective that [big tech company] requires fewer VPs and GMs etc.
Modern frontier LLMs are incredibly good at all types of knowledge work - this should be possible with enough elbow grease
I could imagine a harness that 1) reads LLM output 2) uses a research sub-agent to attempt to verify any factual claims 2) rephrase the main agent's output such that it conveys uncertainty if the factual claim cannot be independently verified
I started off as a javacript developer. Then I was a full stack SWE. Then I was an Applied AI Engineer. I think enterprises will have a need for folks with technical expertise to deliver value - often new software - for a long time.
Until an enterprise like capital one can operate without anyone in the organization knowing how any of their technical infrastructure works (never?) I expect I'll be able to find work.
You know how adding ".ai" to your company name / domain name increases your valuation an order of magnitude or whatever?
Well has anyone tried chaining .ai's to their company name...???
For example could x.ai increase their valuation another 5-10x by renaming themselves x.ai.ai?
What about perplexity.ai.ai.ai?
Seems like a low-hanging fruit for increasing valuation / attention on your company, but let me know if I'm missing something.
Level 12: agent superintelligence - single entity doing everything
Level 13: agent superagent, agenting agency agentically, in a loop, recursively, mega agent, agentic agent agent agency super AGI agent
Level 14: A G E N T
Yes, I'm sure by then there will be better models on offer via cloud providers, but idk if I'll even care. I'm not doing science / research or complex mathematical proofs, I just want a model good enough to vibe code personal projects for fun. So I think at that point I'll stop being a OpenAI / Anthropic customer.
Someone needs to be held accountable when things go wrong. Someone needs to be able to explain to the CEO why this or that is impossible.
If you want to have AI generate all the code for your business critical software, fine, but you better make sure you understand it well. Sometimes the fastest path to deep understanding is just coding things out yourself - so be it.
This is why the truly critical software doesn’t get developed much faster when AI tools are introduced. The bottleneck isn’t how fast the code can be created, it’s how fast humans can construct their understanding before they put their careers on the line by deploying it.
Ofc… this doesn’t apply to prototypes, hackathons, POCs, etc. for those “low stakes” projects, vibe code away, if you wish.