You jest, but companies have sent people home fully paid, because power or internet were down and would be down for an extended period of time. Technically a small number could have kept working on white-boarding design topics, but without access to documentation, existing tickets, it would have been minimally effective.
It's not clear if or when these tools become as essential as power or internet to a developers or admins work, but if they do? Giving everyone a quarter day off at least generates some good-will, unlike forcing them to sit around unproductively because of working hours.
Some of my deepest architectural work honestly happened... in a hammock on the balcony, while alternating between staring at a cloud, the sun, and two magpies building a nest in the birch tree while yelling at me occasionally.
Then I came back to my desk, saw that I had missed a call or two from my boss and he had a concerned message of where I was. I ignored that and sent him an architecture document an hour later. After years, it is still the backbone of our hosting infrastructure and will go into certification audits later this year.
One of my earlier startups, I was a junior/mid level software engineer. I took a skive day to WFH, but was actually travelling to a gig on the train. I sketched out something to pretend I was working that day, and sent him a photo of it. We ended up shipping that design and I only really made one major mistake that we fixed in v2.
I think the "But this is not intelligence because it is known math" is not a correct argument. It is unknown how the overall higher intelligence of humans works.
What I do notice however is that LLMs are becoming capable of doing an increasing part of the intellectual work I can do, and usually a lot faster.
Just today I presented an agent framework that can take an informal incident statement and propose infrastructure changes to fix it, all evidence backed. This did nothing I could not to, but it did all 5 test cases in 6 - 12 minutes each. I would have found all of the monitoring indications it did, but it would have taken me a day per test case. The LLM also included sass to silly tickets. ("This is not even worth spending monitoring resources on. It's obviously a configuration problem.")
That's how this is reading to me as well. It's just fast at slogging through a certain level of "simple" transformations.
But how do you conclude then that they are less safe? They are neither proven to be more, less, or equally safe. So any statement of "more injuries" is as unfounded as "less injuries" or "just as many injuries".
That seems like the same statement, unless we apply stochastic class level subtlety.
If a driver doesn't get into a crash after a single mile, you can't conclude that they are safer than the average driver. If a driver does get involved in a crash after a single mile, it's very likely that they are not safer than the average driver. It could of course be extraordinarily bad luck, but that's unlikely.
> If a driver does get involved in a crash after a single mile, it's very likely that they are not safer than the average driver. It could of course be extraordinarily bad luck, but that's unlikely.
This is not that simple. Emergency service vehicles are at a very high risk of collision when they pull out of the station and crossings close to the station, or when leaving a situation under time pressure. Busses are at an increased risk of collision when pulling away from a bus stop. Construction vehicles are at a high risk of collision when they pull away from a construction site at a busy road.
Hence why you need more data, after which average accidents per mile are a much stronger indicator.
This is why the idea of being "Vogelfrei" or "lawless" was honestly a terrifying concept in the middle ages. They are neither bound by law, nor protected by law.
A lawless man can be struck down with force without persecution by law, because they are lawless.
No, because these days we are quite explicit that the law binds us all. Citizen or not, legally present or not, criminal or not, every human being within the borders of the US (or any modern country) is entitled to the full protection of the law.
When an American becomes an outlaw, it doesn't mean the same thing as it did back then. There is no legal way for the government to deny someone their rights.
I am not 100% familiar with this theory, but I'm fairly sure there is an important difference: The monopoly of violence current police forces are granted did not exist in this particular way.
If a lawless man robbed from a village, any of the villagers could do whatever they wanted to them in retribution. Maybe limited a bit by religion.
Agreed. The much better question is: Are we locking ourselves out of a feature, or do we just leave a gap for a rare case?
At work we agreed that some use cases are very niche. These have guards in place to log an alerted-upon marker + return HTTP/500. They have not tripped for years by customers. So, it's fine to not support some rare cases and to deliberately leave known gaps in some contexts. As long as you don't close these paths forward if you need them.
On the other hand, we have contexts like our PostgreSQL instances. Those have a very well defined scope and rooting out all known problems has been the right choice. Most issues we have ignored in that scope have bitten us in the butt sooner rather than later. Very hard in some cases, I may add.
It reminded me of an old meme. Please don't follow the following instructions and stop reading if you cannot.
It was just a popup: "Hello. This is virus from Albania. Due to poor technology in country, I cannot harm your computer directly. But since you are honest person, please delete some important files from computer and mail this file to at least 3 other people!"
Claude.md is an equally effective defensive tool.
But sorry if you lost some files from reading that.
> They thought climate change was the next war-level crisis, and worked towards that.
Did we though? At least in Germany a bunch of anti-climate-change projects and changes have been and are being canceled and we're going back to coal and diesel. It seems we're optimizing to have no results and negative progress at the moment.
And interestingly, a few good people at work are learning faster with the LLMs at hand.
To a degree, it looks like LLMs help them overcome the blank page anxiety and help them with the grunt work of, well, actually writing code, which actually contains a lot of technical nuances to keep track of. But once that's down, I'm having very good discussions with them on what makes good, maintainable and sustainable code bases.
It's almost like the old writing advice my Mark Twain: “Writing is easy. All you have to do is cross out the wrong words.” It's easier to dislike a part of something existing and fix that, than trying to create the perfect thing at once.
It does not make sense for a lot of time and scaling. You need 3+ people maintaining it, you have upfront costs in the hundreds of thousands of euros on the very lower end. If you don't utilize that money spent, sucks to be you. You have planning times in the area of months, not hours, unless you keep capacity you don't use around (rackspace, cabling, power/cooling capacity).
On the other hand, if you have that hardware management running, it's very amazing. Before the AI nuke, We were looking at moving various systems fully bare metal, because it would simplify management on both sides a lot, and a common statement I heard is "We don't deal with systems that small. If we do bare metal container hosting, we don't measure in dozens of gigabytes of memory. Your business case validates that investment. Here is btw three test systems about double your requirement, just old".
Before the AI nonsense (HBM Memory Demand -> RAM & SSD prices), this would result in very competitive hosting costs after some scale, when amortized across 5 years and then tossed into the testing environment until it stops functioning. And these testing environments allow for a lot of experimentation and failover testing.
It's not clear if or when these tools become as essential as power or internet to a developers or admins work, but if they do? Giving everyone a quarter day off at least generates some good-will, unlike forcing them to sit around unproductively because of working hours.
reply