181–190 of 524 posts
Earlier quoted context omitted.
You forgot to add "you are an expert software engineer with PhD level architecture insights".
haha..After all "prompt engineering" is the mystic art of magecraft that uses forbidden incantations to summon the souls of special experts and make them possess our computers to do our bidding.
I'm increasingly convinced that there's a killer app waiting for whoever can come up with a UI that makes claude code or codex accessible to the average user. Onboarding my non-software engineer teammates to it has super-charged them and essentially given them all their own personal developer that can automate tasks for them. Managing codebases, etc. is still a hassle though. 90% of the power of Excel was that it was…
Earlier quoted context omitted.
When I quit my day job and started Rails freelancing a big chunk of my work was from companies with "that tech guy" who had built a database in Microsoft Access that was vital to the department's operations. And then either left the company - or the app had started to fall apart under its own weight. I would get called in to rewrite it, using a proper database, documented rules and ensure it stayed scalable - and eve…
But at least you could basically follow their logic. I think what a lot of us are concerned about is that the vibe-coded stuff bloats fast. It's so verbose and all over the place, that picking that thing apart will be a huge job, and relying on an AI to pick apart work that an AI already failed to maintain seem like wishful thinking. It's literally "The AI is failing! Don't worry I'll just use AI to fix the AI!".
What I needed to do was sit with a user (not a manager/the person buying my services) and ask them to show me the different things they did with the software. Then I could write a spec for the actual _feature_ and would only need to look at the existing codebase if they needed data transferring across[1]. I don't see why our new LLM-based future would be any different
[1] Of course this meant I would leave out edge-cases and/or weird quirks of the system - often this was actually a bonus as they were either no longer relevant or worked that way because that was the only way they knew how to do it
Turns out Anthropic is pivoting so fast that they're doing all the 'Claude for X' themselves.
Surely 'Claude for Cheese' is soon.
I'm increasingly convinced that there's a killer app waiting for whoever can come up with a UI that makes claude code or codex accessible to the average user. Onboarding my non-software engineer teammates to it has super-charged them and essentially given them all their own personal developer that can automate tasks for them. Managing codebases, etc. is still a hassle though. 90% of the power of Excel was that it was…
Super early stage but I am really happy to read your comment.
Earlier quoted context omitted.
Same as anything else. It’ll go down sometimes, people will take a break and chat, then it will come back up. Like Slack or GitHub or AWS or whatever. It’s almost always a net positive to wait vs do it yourself.
I think the scenario was more of, if really everyone depends on claude, then better nothing critical(medical software, aviation, traffic controll ..) breaks while claude is offline.
I'm increasingly convinced that there's a killer app waiting for whoever can come up with a UI that makes claude code or codex accessible to the average user. Onboarding my non-software engineer teammates to it has super-charged them and essentially given them all their own personal developer that can automate tasks for them. Managing codebases, etc. is still a hassle though. 90% of the power of Excel was that it was…
> that makes claude code or codex accessible to the average user That's what they aim Claude Cowork at. Every executive/leader I've shown Claude Cowork to has gone from 'what is AI' to 'vibecoding whole apps' in weeks. Then when Claude is down for an hour, they get visibly angry and don't remember how to do anything pre-Claude :) I understand the impulse to provide a UI to manage codebases, etc. But my observation is…