upvote
I agree that it's an opportunity to "do it the old way", as a way to preserve the skill. I actually would like to do that regularly, like half a day every week or something.

But I find it difficult to motivate it from the "productivity" angle. Like if I work for a day without an LLM today, it feels like I could go skiing instead, and the LLM will do what I would have done today in 10min tomorrow...

reply
Seriously, if the LLM was down and a dev submitted 10 PRs, I think it would raise some good/bad curiosity from the team with where things stands today.
reply
I have couple dozen branches in flight at any time. A snow day is the perfect opportunity to catch up and get those pushed.
reply
I'd be busy yelling at my Mac and trying to get things down with 3.8b-27b, but I'd still be getting things done.
reply
And the LLMs of 5 years from now will do what current LLMs do in a day in 1 minute.
reply
just want to remind HN that it was as little as a year when I mentioned I used LLMs to do all my coding, totally hands off and people here found it a curiosity. One year later and its madness to even contemplate coding manually.

Im not complaining Im just pointing out how quickly the overton window is shifting.

reply
It's not the overton window, it's the capabilities of the models that have changed significantly in 1 year.
reply
I disagree. For me I had already been using hands off ocding for about 2 years by that point.
reply
> For me

Obviously that's not the case for everybody. 3 years ago, LLMs were very far from producing the quality of code I wanted in my domain.

reply
Hey will you share your workflow and how you get LLMs to build correct things for you (or inspite of you)?
reply
If you’re using the latest models( Opus/Fable/Astra/ maybe Sol) and the default harness, along with a little guidance against the worst tendencies like over-writing tests, you really shouldn’t be getting the wrong things built. Like a coworker, you can’t throw it blind into a monster codebase without some guidance, but otherwise the latest models genuinely just work TM.
reply
Testing, testing, and more testing. In the project I'm working on right now, about 2/3 of the code is in one way or another related to testing. As a human coder, I'd never spend that much time on building test harnesses, automating regressions, writing unit tests, etc, but it's cheap when you can have a robot do it.
reply
So you assume code written by the agent canno be trusted? But how comes you are trusting the tests?
reply
At my work we still have a QA dept that runs the manual test suites before each release. We have also automated almost all of those manual tests and they gate every merge to mainline.

Things are still found but normally it is a new test case or an edge condition we don’t have an automated test for. The ever growing e2e suite has reduced the amount of regressions pretty drastically.

EDIT: I forgot to note that automated e2e tests were always the answer to improving quality. AI has just made it cheap to have several layers of test coverage.

reply
To start, you make it a rule that every test must pass with the fix being tested, and it must fail if the fix is missing.
reply
You of course use another AI to test your tests, have you been living under a rock? /s
reply
How are these /s posts even allowed? You contributed nothing to the conversation other than noise.
reply
thanks for the insight throwaway
reply
> One year later and its madness to even contemplate coding manually...

Seriously, why do people assume that what they feel should be how everyone else should be feeling?

reply
I think it's called Normative Cognition or something.

Like: I'm normal, and I do X. Therefore other normal people will also do X. It's the basis for in-group/out-group. We're all normal and they are not. (for some definition of normal).

reply
How are you handling all the errors that are hidden in code you can not understand?
reply
More LLM, duh
reply
You give it time....the same way Technical debt is code you chose not to clean up....your Vibe Debt for code you never understood in the first place... will come through.
reply
I dont think so man, it havent really had any issues that Ive noticed
reply
Have you asked the people downstream of your bot’s work?
reply
deleted
reply
I heard: This I/O 7/1 ARM loan is so cheap let's buy more house.
reply
I am sure it’s all so good that these incidents should not take more than 5 minutes to resolve. Don’t get me wrong, I am one of the people who would look at you suspiciously a year ago and only in the last year “saw the light”. You were ahead. But that doesn’t mean that at some point you will not overshoot. What we witness today we haven’t witnessed in some time. People also made horrible software but they enriched it with hole plugging hacks that made it run, mostly. AI may build better software but who is plugging the holes. At least today no one. In 1 or 5 years maybe AI. In the meantime, we need to plug some holes and they are not as easy to spot when we are not the ones who left them there.
reply
Madness? I didn't think we'd gone that far...
reply
So either I am mad or you are all mad, time will tell
reply
"Overton window"? It's just developers being obtuse, short-sighted and slow.

It was obvious in 2023 and it is obvious now yet we still have people in denial even today. These people need AI to take over the world and threatening them with eternal suffering before they will change their minds even a bit.

reply
May I ask why you care so much? Some people like hand-coding, they are free to do whatever they want, stop being so weirdly angry and controlling about what people do/how they do it.
reply
"It was obvious then, and it is obvious now: I am always right, I can predict the future, whoever disagrees with me is wrong"
reply
Don't forget the "it is inevitable" and "people who disagree with me will be punished and humiliated"
reply
[flagged]
reply
Yes, but my company does not pay me every 5 years. I don't know about you, but if I wait 5 years, I won't get a salary in the meantime.

If I wait until tomorrow, though, my company won't see the difference.

reply
Sure, but depending on what your job is it can make the work feel even more meaningless than it was prior to LLMs.

All the work most people are doing it just going to be Ctrl+A deleted and replaced with someone else's LLM slop using Opus 8 in an afternoon.

All the shit people are building right now just feel ephemeral, like its going to float away on a breeze.

reply
Well it's getting philosophical. Even before AI, I would argue that the vast majority of software was meaningless. Actually the most successful software on Earth is hurting society and the environment, in exchange for profit for a few humans.

I don't know any software engineer who can say "if I was not doing what I do, society would get a little worse".

reply
The folk keeping Wikipedia running?
reply
Maybe not part of the "vast majority"? The idea of "the vast majority" is that it's not "everybody".
reply
Of course not. I was responding to your second paragraph.
reply
Oh, I see. Well I don't know any software engineer who works at Wikipedia :-).
reply
I console myself that while the products we make are useless and probably even harmful the activity itself just represents the world Geist familiarizing itself with computation and its possibilities and thus growing richer in the process.

In the worst case.. sometimes you learn what's best by experiencing what's not.

reply
[dead]
reply
sad.
reply
Well it's not just software engineers. The majority of people in developed countries work in offices. And when you work in an office, it's highly likely that your work is not fundamentally useful.
reply
> And when you work in an office, it's highly likely that your work is not fundamentally useful.

This seems wildly inaccurate.

reply
Well, for some definition of useful of course. If you find it wildly inaccurate, maybe you don't have the definition that matches :-).
reply
You might be right in the end, but the middle of a massive outage probably at least somewhat exacerbated by LLMs, being debugged by (presumably) human software engineers is kind of a weird time to make this point
reply
Like to burn billions of tokens? For sure!
reply
Which is the way it should be if we were to share the fruits of our labour more evenly in society. Of course in practice the lions share of the product gains go to the capital class and the while they suck the surplus employees and the remaining workers have to carry the burden of supporting the ones now sidelined.
reply
Snow day / skiing? Since this has affected our customers, and they're asking us for help, it means I was up all last night.

Ironically, I also had a change window last night to make some configuration changes to improve site reliability. It was a little challenging to get customer approval for both the cost & downtime for this. Let's just say... this will be a much more fun conversation to have next week, and for the account manager to have. "Yes, we'e proactively improved your reliablity, and here's why you were very smart to approve it and pay for it."

reply
Once you use a cheat code like “how do you turn this on?” It’s really difficult to finish the game without it.
reply
it feels like I could go skiing instead, and the LLM will do what I would have done today in 10min tomorrow...

You sound self-employed.

reply
Or during that day where the LLM is down and I pretend to work, I feel like I am wasting my time for no reason.
reply
No, and that's also not necessary. We are reliant on our systems. The correct response is to harden our systems, not to foster some illusion of independence.

We can of course do that privately, for just the heck of it, but it's not the right response for anything at societal level. We simply need to work harder for more of these 9s

reply
What's wrong with failover? I don't use anything from Anthropic except their API. So when Claude is having issues, I switch to GLM 5.3 or something, doesn't take more than a few seconds.

I realise people on the monthly plans can't do it as easily. But I would say that as far as possible, having a plan B is the foundation of resilience.

reply
I think that's the 6 '9's problem. If you have something with 99% uptime, how much more are you willing to pay for 99.9% uptime, then 99.99% uptime. It's risk vs cost. Many places in the US do the same thing with things like say snow removal. Instead of having expensive systems ready to go for the 1-2 days of year of snow, you just shut things down for a day and slow down a little.

That doesn't work for all systems, and not for all businesses, but I would say the mass majority can 'suffer' 24 hours without email or an LLM without everything going up in flames.

reply
It's not only a 9's thing. If you can set yourself up to easily switch between providers, you also put yourself in a better bargaining position.

That's not always easy to do, but with something like inference providers it is, so why not kill two birds with one stone?

reply
Not hard on monthly plans either. I have ant, OpenAI and cursor (mostly for grok and gemiii). Taxonomy of model steps, each has a pre-tuned failover from a different plan and I just need to flip a switch when a lab goes down. Switch isn’t really required but occasional enough that I want eyes on and the system is only for my personal usage so outage until switch is acceptable…

Another reason to have good Evals…

reply
Failovers are nice, something that all reliable systems will provide, and, most notably, exactly the opposite of "just adjust".
reply
You’re not wrong, but some companies swing real hard at the biggest players assuming they won’t all be down at the same time. My work has hard dependencies on 365 and Cloud Entra and only allows Claude company wide. Today is going to be a snow day since we couldn’t get into anything yesterday but we could at least get projects done using connections Claude had into various platforms that cached the data in 365.
reply
Did scheduled jobs failed loudly or stalled? My sessions just stalled and I did not know the outage until I send the followups.
reply
One part of hardening our (company, economic) system is not collapsing when our (technological) system isn't working right.
reply
Reading the site guidelines, so I can be Claude-like and properly adjust my answer:

> Comments should get more thoughtful and substantive, not less, as a topic gets more divisive.

You are also a system. And, if you, as a system, don't run with Claude, you're not sufficiently hardened. People have made all sorts of helpful suggestions, like de-risking with multiple providers or just getting yourself a better Mac to run a local model.

The idea that: "No, no, we must have Claude, b/c it's the same as having a pen and paper!" is woefully naive. It's hard to attack the supply chain of pen and paper if you have a few extra reams and a few extra sticks. It's pretty easy for our geopolitical enemies to attack computers located far away from you, especially those systems are designed like fragile Rube Goldberg machines; furthermore, if we build an entire society (a system) to be productive only when we have LLMs, our issue isn't "insufficient-hardening". It's that the design is wrong.

reply
There is always something that you can do that isn’t gated by the api. It isn’t critical path for literally everything. Go organize your expense reports or something.
reply
What do you think I use to organize my expense reports? If there’s something substantial you can do entirely without tokens that’s probably an opportunity for additional automation. But please have failover across multiple labs!
reply
What do you think got ya here?
reply
>> If there’s something substantial you can do entirely without tokens that’s probably an opportunity for additional automation.

Well, I just finished a meeting where we diagrammed out how change authority is to be structured as we split one group into two, which teams will retain what authorities. Zero claude involvement. Ten people in a room. Whiteboard and markers with a "scribe" taking notes. I am now editing old SOPs to reflect the decisions made in the meeting ... not something we would trust to claude or any other AI.

reply
Learned helplessness on full display here
reply
>harden our systems, not to foster some illusion of independence.

Let me know when the tech industry workers stop doing this and gains some solidarity, and I'll join you in that sentiment.

Until then, I pretty much need to bolster myself on the idea that one day I will need to switch frameworks, IDE's, and even OS's themselves. I'm the ones guiding the tools, not vice versa.

>We simply need to work harder for more of these 9s

The only 100% thing I will guarantee is that these tools will align to the incentives of their leadership over time, not the customers using it. add 10 9's if you want, that just guarantees that humanity is the weakest link.

reply
>No, and that's also not necessary. We are reliant on our systems. The correct response is to harden our systems, not to foster some illusion of independence.

I'm not sure if this is your intent, but this paragraph reads like satire given current real world events.

The systems you mention in your second sentence are failing at the "right response" you mention in your third, which dictates that contrary to your first sentence alternative action is necessary.

You cannot harden systems you have no control over. Societal level assurances require law and goverment regulation and enforcement. It is juvenile to pretend otherwise. If we were talking about government services, then as a taxpayer you would have some avenue to enact change.

Your only option when dealing with private companies is to try and become anti-fragile as much as possible at a personal level or at the level of your own company.

reply
Is there not a single SaaS, cloud company or similar that your org depends on? No AWS, no Cloudflare, all internal mail servers, no Docusign, no outside inference, nothing of that sort?
reply
And a 4th option where you have more than one AI provider
reply
And the 5th option where you are your own AI provider.
reply
Finally having time to vacuum clean the office
reply
Is it not worth getting a Roomba-type device?
reply
Those things are also still pretty loud. And if you have a large shared office space, it might take hours for it to finish.

At our office we have a cleaning crew and when they come by to vacuum during office hours, everyone in our section takes a 5 minute coffee break and then it's done when we get back.

reply
You can schedule the roomba to run at 2am.
reply
Then at 2:30am it gets stuck as it eats a loose power cable.
reply
Might not be a roomba-friendly setup. Tall doorsteps, multiple levels, lots of opportunities to get trapped on a carpet etc.
reply
They’re getting really good. In a few years no one will be hand vacuuming anymore.
reply
Satire, I assume.

Our house has three carpeted steps between levels. Is there a Roomba that can clean those steps whilst cleaning the rooms on each of the levels? Or do I need one per step and the levels?

a) I’m not lazy enough to buy a Roomba. If I was, I definitely would be too lazy to nanny it around the house, lifting it up the three steps. b) When I am feeling lazy I hire a cleaner, who uses their own hand vacuum cleaner.

reply
Yes, I'm being facetious. I do wonder how far the analogy goes; is your willingness to apply effort a virtue that will atrophy? Will the satisfaction of applying yourself wane? Will the very real challenges to robot vacuuming (the steps) just be ignored long term, with the resulting loss of quality, or will we simply accept the new higher costs of cleaning floors? Will this all feel like a boon to productivity, or will the atrophied willingness to apply oneself cloud our judgement?

Time will tell.

reply
It is but they don’t replace a good manual clean.
reply
In this context, the metaphor is almost too thick.
reply
Cleaning is therapeutic.
reply
They need Azure to be up....
reply
deleted
reply
Why bother? You do a little bit of work, fine, but when Claude returns all that work will be done in an instant anyway, so unless you really need results right now, just wait.
reply
I can't imagine a construction worker saying, power is out, gotta find a way to be productive, I guess instead of the paint sprayer, nail gun and circular saw, we'll just find other ways to be productive with our hands. The same might apply to law, medicine, etc. I think we're almost there with software.
reply
I understand what you’re trying yo day, but my family ran a construction company for generations (until my father retired) and they had contingencies for every adverse scenario to stay on schedule: Generators, battery-operated tools, hand-operated tools, heaters for pretty much anything you can think of for extreme cold, wind coverings, etc. I don’t remember them ever stopping work except for a trade union strike.

I’m pretty sure doctors don’t abandon their patients during a blackout either, or even a war for that matter.

Mature professions have procedures and backup procedures for pretty much every non-catastrophic situation.

reply
Which begs the question is Software Eng'g/Development a mature profession? We've certainly been trying to especially in the last decade, arguably incentivized by ZIRP and VC money but the last few years?

I'm not just talking about tools either. You mentioned redundancies and contingency plans. Layoffs have stripped workforces to barebones headcounts. How can you have redundancy when one sick man-day reduces your eng'g team by 50%?

reply

  > Which begs the question is Software Eng'g/Development a mature profession?
I think that correct question is "does use of external LLMs and agentic coding make Software Engineering less mature profession?"

For every sense of the word pair "less mature," including, but not limited to, "less responsible for consequences of actions."

reply
No, it's not.
reply
> Generators, battery-operated tools, hand-operated tools, heaters

The equivalent for a dev is laptop, another AI, mobile hotspot and work at a cafe/library.

Microsoft being down is like having a contingency for a tornado.

reply
> Microsoft being down is like having a contingency for a tornado.

I'm probably misreading your point, so, apologies, but I'd still just like to say:

Microsoft is a profit-driven, human-run corporation that mostly offers business infrastructure services. I think contingency planning for Microsoft service failures is almost entirely unlike contingency planning for adverse weather events?

reply
> having a contingency for a tornado.

Sounds like a normal thing to do if you live in Kansas. And perhaps we are all about to start living in the software equivalent of Kansas?

reply
Yes, I believe US hospitals are legally required to maintain and test backup generators in case power goes out.

Of course proof by analogy is silly anyways, my email going down is not nearly as bad as a patient's medical equipment going down.

reply
>Yes, I believe US hospitals are legally required to maintain and test backup generators in case power goes out.

And even that only does so much, it was 45 years ago but my Grandmother had a stroke on the operating table because the power went out and generators didn't kick on until someone could run and manually start them because the autostart failed.

reply
I have seen framing crews leave site when their compressor goes down.

Or maybe more prescient; machine operators going home on a cold day because they can’t get their loader started.

reply
I may be misunderstanding what you wrote, but I think that says more about your imagination than about software. Yes, medics do improvise a lot to keep patients alive when the power is out, or when essential tools or medicines are not available. "Well, the power failed, so did the sustainable backup, let's everyone go home, today's ICU is a writeoff".
reply
Imagine not knowing how to code or write anymore.
reply
I get what you're saying and I would wholeheartedly agree 5-7 years ago but after hearing Our Lord and Savior Claude Code as the solution to all our technical problems with ever increasing fervor and intensity for the last two years, I'm gonna take the cynical route, maybe fence on office chairs, not because my code is compiling, nor my prompt is running, but Claude is down management, what do you want me to do now, actually think?

From what I hear, the project managers are having a hard time sending emails anyway. We'll call it quits, winkwink.

reply
Friendly reminder that Microsoft has been engineering Office 365 for a while so it simply cannot interoperate with a self-hosted e-mail server or a small hosting provider's e-mail platform.

Likewise, Anthropic / Dario has been busy proclaiming why nobody except themselves should be allowed to develop frontier AI, that we need "kill switches" in all AI models, and that we need a pause / slowdown on AI development because of the threat of open source models.

Essentially, they want complete lock in to their platform, so yes, it's very appropriate to ask questions when they can't meet basic 3 9's of reliability.

I was unable to do things beyond basic banking with my bank yesterday (and today) due to this outage. It just involves making changes to a merchant processing account for a nonprofit, but the point is that normal business activity grinds to a halt when it relies on an unreliable provider like this.

reply
Sure, like if your company’s internet is down, you can start sending invoices to customers by paper mail. Just to prove that you’re not reliant on a technology that’s made work more efficient.
reply
tell that to people working in medical fields.
reply
There's also the option where it doesn't affect you at all, because you do not rely on LLMs—or even just do not rely specifically on Claude—at all, and can easily do your job without ever noticing that it's down.
reply
This concept is baffling to people who are terrible at their jobs.
reply
Haha. Like people forgot how to develop before LLMs smh
reply
[dead]
reply