In theory that should be the right framing, in practice having the information means nothing if there is no reasonable action you can take from there.
In the case of Visa and MasterCard, Amex or JCB or Diners' terms aren't better or more competitive, your only real option is to give up on credit cards altogether.
A lot of otherwise sensible concepts have little weight when you have a cartel or straight duopolies/monopolies.
Not "really", but real consent is an incredibly high bar IMHO.
Even in very favorable situations it's a grey zone: For instance does someone _really_ consent to every single term in their 20 pages employment contract when they quit a miserable job to move to the only place offering them something decent that will help them get out of the ghetto ?
> convincing a (product) manager that it was their idea
The standard antidote to this is giving praises to managers even as that's not their idea and they did nothing.
That creates a situation where people are paid to basically not intervene nor block people, which is weird on paper, but makes a lot of sense in an organization.
Moving search to the chat interface has some other advantages, like better control on the context and output. Paradoxally it took the AI turn for Google to understand e.g. that I want query based language detection. Or whether I want fuzzy search or very specific things.
But that's beside the point IMHO. We could have had AI _and_ search, combined in a cleaner way. We wanted search to improve for so long, it didn't have to be throwing the baby with the bath water.
> there's no learning curve.
This really drives home how search is different for everyone. It took me a while to find ways to get the results I want the way I want.
> Earlier this year, a small site called HouseFresh, which is dedicated to reviewing air purifiers, published a blog post that really crystallized what was happening with Google and these smaller sites. HouseFresh managing editor Gisele Navarro titled the post “How Google is killing independent sites like ours,” and she had receipts.
I can’t speak to the quality of HouseFresh (I’ve never been in the market for air purifiers), but 99.9% of these “review blog” sites are low quality and exist not to help readers find good products, but to gain referral revenue through clicks.
So for these sites, I’m not sorry that “Google is killing them” (and I’d argue it’s LLMs that are killing them, not Google singlehandedly).
Their methodology seems ok, but clicking through their pages and looking around, their comparison method is all over the place.
* In many posts they lament if a device doesn't have an app with it (???).
* They have reviewed only 2 Honeywell brand filters. Even though they are in the same ballpark of cost, area, size, and performance. Why not more of this brand? And I had to use google to search their site.
* If I search their site for "Honeywell", I see one smaller unit, not the other unit they reviewed, and then at the very top "how to fix the top problems with Honeywell air purifiers".
* How are they able to provide such expert advice on how to fix Honeywell products, if they don't seem to review them? Unsure, if they didn't remove the Honeywell review pages I'd have more confidence
* They admit on that same FAQ page Honeywell is a huge manufacturer. Where are they on their site, and why does it seem all those pages were removed? I checked waybackmachine, and those pages used to exist. Maybe they did a sitewide purge of other brands?
* The latest I could find for any article referencing Honeywell was in Dec 2025, when the purge of Honeywell review pages began.
Yes, I have Honeywell purifiers which is why I picked that brand to search on their site, as I have familiarity. They represented the capabilities of the purifier accurately.
But it seems to have near identical, in some areas better, performance than the ones getting recommended on their site.
I tried the same kind of search on a niche I'm more familiar with (mirrorless cameras), and the LLM results are pretty mid compared to the tradional results.
I would have expected a site like DPReview to rank pretty high, but it's only the 5th LLM result, which is about the bottom of the 2nd scroll page on my screen.
Of course it's the first in the "organic" result (way way below in the page, about the 4th screen of scroll down to me)
But the AI has just been trained on these sites (or uses search to find them) so you are just getting recommended the same product that would have paid these sites the most commission...
I use to use these types of sites all the time. Not because I trusted their recommendations, but to even learn what the popular products in a category are.
How I just tell an llm what I am interested in buying and it gives me recommendations.
We've already seen an attack on transfusion blood storage.
I wouldn't minimize the impact of the ones on supermaket freezers either. It was technically dumb and somewhat laughable, but we're talking food. The affected chains had stores in very rural areas with elder people living in remote places, these supermakets would be the only purveyor of long conservation food.
I'd argue we're already there, albeit at small scale yet.
Preportioned meals that are hot and ready at the push of a button is a godsend for people with disabilities and/or entering older age. Someone buying a few dozen of those can be set for weeks, longer if they also continue cooking simple dishes from time to time when they feel good. This helps tremendously to keep them independent and self sufficient.
Someone coming once every month to the supermaket to restock, only to be told there's only fresh and canned food available must feel devastated IMHO.
Those people can eat raw veggies other raw ingredients until the store fridges are re-stocked. And there are also plenty of just-add-water ready meals that don't need any refrigeration. No ones survival depends on frozen food.
Not all things that are done are actually needed. Eggs survive for weeks without refrigeration too if you don't destroy their natural protective layer for example.
Just because vegetables are sitting out there in the open doesn't mean it shouldn't be stored in cool places before it reaches the supermarket. And last time I checked people valued eating safe meat and being treated with pristine medicine.
I was actually thinking more about canned and dry foods, which have a shelf life in years.
But most baked goods, fresh produce and fruit will be OK for a few days or weeks, some things even longer. And if they do spoil, it will be pretty obvious and not really dangerous. Dairy and especially raw meat are the things that can go toxic pretty quickly.
The main caveat would be to not care too much about hardware: if you're on a classic desktop or standard laptop setup it should be fine. Basically, if you could move to macos, you could move to linux as well.
If instead you're spending your life on a Surface Pro or a Z13, or some other alternative form factor, linux is probably not for you yet. It runs, but touch support and QOL for tablet mode is subpar at best.
I agree with this. Touch support is quite awkward, stylus support is especially worse since stylus is considered an absolutely positioned mouse than a type of touch. I'm using a Lenovo Ideapad 5, and the main reason why I have yet to switch fully (I have CachyOS on an external SSD) is due to the pen support and also shitty OneNote support (I'm supposed to use a browser??)
Another angle on this: most ATMs were running windows a decade or two ago (I'd assume most still do, but not sure).
You'd see occasional crash screens, but given the sheer number of machines out in the wild, having only a few crash once in a blue moon speaks amply to the reliability of the thing.
There is a growing problem with something called ATM Jackpotting often with this old Windows installed software:
"The FDIC OIG is alerting banks about an increase in a type of fraud known as “ATM Jackpotting.” ATM Jackpotting involves criminal actors accessing ATMs and placing malware software on the system, enabling them to illegally dispense cash from the bank’s cash supply. The process is often run by sophisticated and organized crime rings at both the physical location (accessing machine and hard drive) and operating in foreign jurisdictions (transmitting malware codes).
The FBI estimates 700 instances of ATM Jackpotting and losses totaling more than $20 million in 2025."
Yeah I remember seeing an ATM that was showing a Windows screen five or ten years ago. Based on having seen some screens on the ATM before it must have gone live in... 1993 at the latest.
An ATM has at most a number pad with a few extra keys and some keys at the left and right of the screen or a touchscreen with a few buttons. That is rather simple compared to a full multi user system with actual multiple users and multiple apps.
An ATM is actually simpler than a fruit machine. The latter has more reasons to refuse a payout!
DevOps'issue IMHO is developing software and dealing with the ops side are two fundamentally different propositions, and require two different life styles.
Doing ops also means entering the on-call rotations, being in the war room when a data center goes under and being on the hook when a DDOS brings down the service.
Very few people want that in their life, money be damned. Same way in an ideal world devs should also participate in customer support, but very few could really do it or handle that for years.
>DevOps'issue IMHO is developing software and dealing with the ops side are two fundamentally different propositions
That's why they have to be the same team. Your dev team needs to: 1. understand how to write code that can be debugged and recovered in a crisis, 2. learn to write code that doesn't cause the crisis in the first place, 3. have the motivation to do so because they will be the ones paged.
Anything else produces are far worse experience for everyone involved, especially customers.
The problem I've seen with DevOps is that some fief-builder sets up a "DevOps Organization", which is literally the opposite of what DevOps means.
These are all good point, that I think aren't really related to having devs do operations.
Having engineers understand what makes a service resilient and easy to manage, as well as giving them incentives to produce high quality code doesn't require them to do SRE. In particular, being close enough to the SRE team, getting inputs when building the feature, detailed feedback and requests on live services, and the blame when shit hits the fan, are a more scalable way of doing it IMHO.
>Having engineers understand what makes a service resilient and easy to manage,
I don't believe engineers can understand this without experiencing it. A counter argument might be "football coaches don't need to have played", but the counter to that is "players need to have played". Why would being on call make you a better player? Personally, I think being the person watching the dashboards, in realtime, scraping the logs, in real time, watching how the contagion happens, in real time, gives insights that a next-day post mortem just doesn't. There are things I've learned only from hearing something on the conference call and then asking someone about it in chat. Watching a presentation on "Why 99% of people fell of our new bike" isn't nearly as useful as riding the fucking bike.
I've been on teams (briefly) where the ops team having an absolutely shit 48 hours was simply not on the dev teams radar, because they had more important things to worry about. That of course meant that when devs needed, e.g. a new host to try something, ops just dragged their feet, sometimes for months. Perhaps I've only seen dysfunctional companies in this regard. Or perhaps teams are made of humans, and splitting dev and ops is guaranteed to fail for any organization of more than 20 people? Like, sure, a startup of ten highly motivated people - maybe that works. Never done that myself: we've always run our own shit at the startups I've run/worked. Once that startup is 50 people, I think you're destined to fail with separate dev and ops.
Been paid for this over 40 years now. Done startups and FAANGs. But yes, the rewards better be fucking worth it, and the shifts better be reasonable.
So like, I'm not certain you're wrong. I don't think you can be wrong here. It's about what you're willing to do. Personally, I've done both ways, and if I started a company, I'd only hire people willing to support their shit with a pager. I'm not sure that matters for all businesses, but I'm not interested in starting, e.g. a mom-and-pop web hosting site for local businesses. If the service matters, devs are on call. So maybe I'm self selecting by the expected $ return.
> Perhaps I've only seen dysfunctional companies in this regard. Or perhaps teams are made of humans, and splitting dev and ops is guaranteed to fail for any organization of more than 20 people?
TBH I haven't seen a company that does it efficiently in a way that could be reproduced elsewhere.
The best DevOps experience I had was in a 5 people team. The worse was in a 100ish dev org where each team was supposed to deal with their own ops, but it actually meant that the same 5 people would be running from team to team to fix the mess each team's DevOps were building. Except these firefighters had to context switch each time, so they'd mess it in their own specific way.
I don't think there's a silver bullet, I now tend to go to companies that have dedicated ops teams, but balance it with engineers having enough respect for that job and not wanting to cross the infra team.
A system crashing during a weekend and having the infra guys on-call is a serious issue that won't just end with a report.
Any developer who doesn't at least *understand* the ops side of the fence and has never spent time actually *doing* it, will make bad decisions along the way from an ops perspective. These are bad developers.
I see a stark difference between understanding how it works and doing it in a professional manner.
For instance I probably have a decent understanding of what our CS team deals with, the tools they use, the volume and overall content of the customer feedback and requests that are coming to us. But I don't sit at a CS desk every day for a few hours and process the tickets of the service I'm running.
You should at least be able to step in and do that job, however, if necessary. That's different than that being the most efficient use of your time, but it's something every good developer should be *capable* of doing.
Understanding anything is not binary, and evolves over time. Feeling like you understand something and then having at least some continuous hands-on experience are incomparable levels.
At the end, its just another part of your skillset with the general aim being the best / most experienced engineer to deliver best designed software for customer/company needs. There is no real seniority without being fully-versed in roughly everything that makes software stable and maintainable and delivering it. One cannot be had without the other.
Last team I was on was repsonsible for supporting and maintaining their product, with help from the SRE team. It means after-hours support for issues and (maybe) releases but I think this was the right way. You became the backstop and support resource for things like data center outages and DDOS attacks that were largely the responsiblity of the (much smaller than many places) SRE team. We also put devs very closely behind front-line customer facing staff where it made sense (ex: reporting & analytics - yes, platform - probably not). It made the devs better and they might try and deny it but I think most of them actually appreciated it. #YMMV
The issue I was facing in a previous life was the turnover. We had data scientists, DBA and many specialized roles stay pretty long, where devops moved away at about twice the rate, and work life balance was mentionned in many exit interviews.
I agree with you that it's extremely formative, and having devs involved basically from start to end of the service surface gives a lot of flexibility. The downside being that it requires a ton of different skills as well, and while people learn, many won't get comfortable with it even after months.
This makes it specially tough when people get called at 3 in the morning to deal with an emergency while they've already spent half the night sleep deprived from their kid puking all night. The worst part being that while people could understand wanting to skip turn one or two times, engineers with small kids will have enough going in their lives that most on-call instances land at a time they're busy dealing with more important matters.
> being in the war room when a data center goes under
When doesn't this involve devs? If you have ops separate and isolated from the development effort, a devs representation will have to get involved at some point.
Imagine managing a gitlab instances. You're doing it for years and have a stable environment. If one of the instance gets hammered by external traffic or one of your data center dies, will you call the gitlab devs to deal with it ?
Depending on the size of the deployment. (Not sure what you mean with "one of your data center" though) If it's just you, you deal with it. If you're running a bigger deployment, you likely have GitLab devs internally that will be reachable. Even bigger - you're likely to have access to upstream devs in the ultimate tier even with self hosting.
> DevOps'issue IMHO is developing software and dealing with the ops side are two fundamentally different propositions, and require two different life styles. Doing ops also means entering the on-call rotations, being in the war room when a data center goes under and being on the hook when a DDOS brings down the service.
That's exactly the issue that DevOps aims to solve, though. When you have developers who have no ownership or responsibility once the software is running on production, it becomes a "throw it over the fence" situation, and devs don't care about the operational side.
Logging? Who needs that, if there's a bug report I'll reproduce it on my local machine (and if I can't, CLOSE-WONTFIX!) Performance monitoring? That's an ops problem, tell 'em to buy better hardware. Application crashes? Works on my machine, probably a bug in the server config; ops problem. Tell them to set up a scheduled restart every hour.
You still need dedicated operations staff who deal with the overall system health and design, but yes, a developer needs to be involved when a DDOS brings down the service, because how should the system behave under heavy traffic? Can it serve up cached read-only pages? Did someone find a very CPU-intensive public endpoint that is being exploited and needs to be fixed? Only your developers can answer this question, not the ops team.
That's an org issue. For a given service dozens of roles will be involved, if devs are needed to do every single of them to care and be invested, there is a problem.
> [...] Only your developers can answer this question, not the ops team.
Yes. Those are questions that need an answer before a service is released, and the ops team need the veto power + sufficient means to escalate recurring issues in ways that will hurt the dev teams enough to make them care.
In theory that should be the right framing, in practice having the information means nothing if there is no reasonable action you can take from there.
In the case of Visa and MasterCard, Amex or JCB or Diners' terms aren't better or more competitive, your only real option is to give up on credit cards altogether.
A lot of otherwise sensible concepts have little weight when you have a cartel or straight duopolies/monopolies.
reply