> I know people who don't even type search queries or URLs into a browser, they just tell the phone what they want to find and open whatever shows up in a search result.
I don't know exactly what you are talking about here, but if I wanted to find a restaurant that is local I definitely just type 'Miguels' into the browser and then it searches google for 'Miguels' automatically and it know's my location so the first result is going to be their website and phone number and I can load the website for the menu or just call if I know what my family wants.
However even then, I'd rather have an app for them where I can enter in the items I want to order. I've noticed apps tend to be more responsive. Maybe it's just the coding paradigm that the applications tend to load all of the content already and the actions I take in the app are just changing what is displayed, but on a website they make every 'action' trigger an API call that requires a response before it moves on to the next page? This makes a big difference when my connection isn't great.
I also find it easier to swap between active apps instead of between tabs of a browser. If I want to check on the status of the order or whatnot, it's easier to swap to the app and have that refresh then it is to click the 'tab' button of the browser and find the correct tab the order was placed in.
This is pretty much what I meant. Even if the browser is what comes up, the fact is the user isn't interacting with the browser as a browser. They're interacting with their phone through an app (voice => search). They don't understand website URLs, or what search engines are doing. That makes it harder for them to return (engagement metrics!) than tapping the icon on their phone that opens up directly to the app.
It's also why so many websites try to offer push notifications or, back when it seemed like Apple wouldn't cripple it, the "add to home screen" or whatever CTA was that would set the website as an icon. Anything that gives the user a fast path back to engaging without having to deal with interacting with the browser itself is what PMs and marketing want.
I recently took a trip to Hawaii, particularly Maui. I've never been before, but I hit the weather lottery and got to experience the Kona low system that raked the island with copious rain. Anyway... What I found, in the areas that we were staying, was that there were a lot of food trucks that looked to have great coffee, poke, food in general. But with the weather it was unclear if the food truck was 1) accessible 2) open due to other weather issues.
What I found was that none of these food trucks (and even some relatively nice restaurants) had operational web pages. One had a domain but, for some apparent reason, they posted the menu to <some-random-name>.azurewebsites.net. And that page just... Didn't work. The rest got even worse. Most had listings on Google Maps, but the hours and availability did not reflect reality. We went to a coffee food truck that wasn't there, even though the day before they had commented on a review. Then we had others that had a link to an Instagram page of which some claimed to house their "current" hours and location, yet we tried going to two of them and both weren't open.
It's 2026. If you have your business on Google Maps you should be able to update hours and availability quickly. But beyond that it costs almost nothing to host a simple availability page on a representative domain. And even if you don't want to deal with the responsibility of a domain, there are multitudes of other options. Now, I'm guessing that this isn't the norm for most of these vendors, at least I hope. But we weren't there during the worst of the rain, we hit the second low that went through in our timing. So while it was a significant amount of rain and some of the more treacherous switchback roads were closed - I'm talking about food trucks that were off of very accessible main roads & highways. My SO reached out via IG to about a half dozen vendors and only one responded 2 days later.
Clearly tech and simple services like availability and location that is easy to update is not accessible (or known) for these types of businesses. But it definitely does not require an app (nor should it). Having these simple "status" sites would have made the friction the weather caused significantly less than what we experienced. I don't want an app when I'm trying to find out if a restaurant is open. I, personally, don't find apps any more responsive. In many cases a lot of web sites are littered with far too many components that are not required. I've been doing a lot with Datastar and FastAPI recently and some of the tools I've thrown together (that handle hundreds of MB of data in-browser) load instantly and are blazing fast. So much so that I've been asked how I "did that". It's amazing how fast a web app can be when it's not pulling data from 27 different sources and loading who knows what for JS.
NYC rent being unaffordable is due to legislation that keeps apartments off of the market due to not being financially viable to repair to habitable standards in addition to legislation overly empowering local groups to block new construction.
> It's sufficient to have a process that satisfies the letter of the law
No.
Let's take an example of 401ks.
Any company that has a 401k has to pass non-discrimination testing to ensure their plan doesn't favor highly compensated employees over non-highly compensated employees. This is done through Actual Deferral Percentage and Actual Contribution Percentage tests. Just doing these tests can be very costly.
If you don't want to do these tests, then you can follow a 'safe harbor' action where the company automatically contributes x% for everyone. If the plan executes the 'safe harbor' action, then they automatically pass the two tests above.
However, if they don't follow through that plan they may still not have violated the nondiscrimination policies if they end up passing those two tests.
So to bring it back to the circumstance here, because Cox was not following their own processes which would have afforded them safe harbor they do not get the benefit of being automatically protected from the action. Then the court goes to see if Cox was sufficiently involved in the violating actions in order to be liable, and the court found that Cox was not.
So going back to the line...:
> It's sufficient to have a process that satisfies the letter of the law, but you can simply not follow through and enforce it.
Not at all. Because it was not enforced, Cox lost the safe harbor protections and had to defend themselves.
With 401ks and financial instruments in general, it's cut-and-dry: there's either a payment, or there isn't, and there's a whole accountancy industry that supports that.
With DMCA claims, it's an adversarial accusation with inherent unreliability built into the collection mechanism, usually submitted by third parties. The process doesn't lend itself to the same kind of auditability and accountability as securities and investments.
> I guess it was a mix of enjoying the attention, pitying weaker students, and wanting to reward "participation".
It probably wasn't intentional, just 'I have x minutes a day with the students to teach them the day's lesson. I have more than x minutes worth of content to convey. If you willingly spend more time with me, you may get information that was lower in importance and was missed during the day's classes.'
> But Baumol's argument, which you introduced to the conversation, is that outcome and process cannot actually be distinguished
How is that Baumol's argument? How is 'outcome' vs 'process' relevant to his argument at all?
'Cost disease' is just the foundational truth that the cost of the output from industries with stagnant productivity will increase due to the fact that the workers in that industry can be more valuable in other industries, reducing the number of relative workers in the stagnant industry.
If you want to make the output from a stagnant industry available to a broader spectrum of the population then you have to improve the productivity of that industry.
I think he means that when you go to watch the symphony orchestra, you are going to watch a bunch of people sitting with their instruments, manually playing them.
There is no way to separate this process from the product of the process.
You're not buying the sound of the music. You can just stream that. As far as that is the product, it has already been automated and scaled so millions of people can hear it at once, whenever they feel like it.
You're buying the sound AND the people sitting in their formal clothes manually moving their strings over a violin, with painstaking accuracy developed through years of manual practice.
You couldn't make a robot do it, for example. You could maybe make a robot play a violin, but that again isn't what the product is.
The product is tied to an expectation of what it is that does not allow for it to be done more effectively.
By contrast manufacturing processes are not tied to this expectation. If I buy a loaf of bread, I don't care whether the wheat was manually harvested or harvested by a huge machine.
The musical performance example is just one example. The general problem of services being resistant to increased productivity, however, is not restricted to this somewhat unique case. That's why I pointed to medical advice and education: when I need a medical consult or personalized tutoring, I don't specifically care if I have to lock down irreplaceable moments of another human being's life in order receive them.
It's misguided to focus on one special case of the cost disease problem where human by definition must provide the services, when most of the time this is not the case.
Yes, backups are great but a 'dumb robot' or a 'mistaken junior' shouldn't have access to prod.
And a sleep-deprived senior? Even then. They shouldn't have access to destructive effects on prod.
Maybe the senior can get broader access in a time-limited scope if senior management temporarily escalates the developers access to address a pressing production issue, but at that point the person addressing the issue shouldn't be fighting to stay awake nor lulled into a false sense of security as during day to day operations.
Otherwise it's only the release pipeline that should have permissions to take destructive actions on production and those actions should be released as part of a peer reviewed set of changes through the pipeline.
But smart robots like Claude should and will have access to production. There has to be something figured out on how to make sure operation remains smooth. The argument of don't do that will not be a viable position to hold long term. Keeping a human in the loop is not necessary.
>We've literally done it without robots, smart or dumb, for years.
And we've written extremely buggy and insecure C code for decades too. That doesn't mean that we should keep doing that. AI can much faster troubleshoot and resolve production issues than humans. Putting humans in the loop will cause for longer downtime and more revenue loss.
> AI can much faster troubleshoot and resolve production issues than humans
Can, yes, with proper guardrails. The problem is that it seems like every team is learning this the hard way. It'd be great to have a magical robot that could magically solve all our problems without the risk of it wrecking everything. But most teams aren't there yet and to suggest that it's THE way to go without the nuances of "btw it could delete your prod db" is irresponsible at best.
When people talk about backups they typically mean located somewhere else. If one terraform command can take out the db and the backups then those backups aren't really separate. It's like using RAID as a backup. Sure it may help, but there are cases where you can lose everything.
Nobody, not even a "smart robot" should have unfettered read-write production access without guardrails. Read-only? Sure - that's a totally different story.
Read-write production access without even the equivalent of "sudo" is just insane and asking for trouble.
> Top management has insane levels of compensation as a strategy by ownership to alight management's interests with their own, by turning them into owners. If there is going to be a management layer at all, for example the proposed "A-suite", then their compensation will balloon for exactly the same reasons.
That is not correct.
Owner's don't align top management's interests with the owner's interests by giving them 'insane levels of compensation', they do it by giving the managements compensation in the form of shares of the company. It's not the volume of the compensation that aligns their interests, it's the type. Otherwise the 'top management' could just invest in the competitor and torpedo their own company making multiples of the original cash compensation as clients leave for the competitor.
If anything, a high base pay would be a dis-incentive to perform well, because increased wealth (a) reduces the marginal utility of additional compensation, and (b) makes the CEO less vulnerable to going down with the ship. The same goes for "golden parachutes".
IMO, if incentivizing good performance was really the goal, then companies would hire CEOs who are not already wealthy, pay them only enough base salary that they accept the job and can focus on it without worrying about paying bills, and compensate them mainly using illiquid, very long-dated stock options, which become worth a fortune if and only if the company is still around and profitable far into the future. It turns out that this is basically how founders are compensated, and it's a wonder that shareholders allow public-traded companies to be run in any other way.
Sure, if you want to spell it out. It is equity compensation, because they want the management to be owners of the same assets that they hold. Once that's settled though, the question is: how much equity? Well, it needs to be a large number. Owning $500 worth of stock doesn't make them a capitalist -- it just makes them a person with $500 worth of stock.
> I can bet you a hefty sum that Alameda will never go without electrical contractors.
You *really* don't understand the issue then because no one is saying that there will be 0 electrical contractors.
Electrical contractors will continue to exist because demand will continue to exist, but the wait time to get the work done will increase due to not enough electrical contractors.
Or the work will be left undone because the owner doesn't have enough money to pay the few electrical contractors that remain.
Or the work will occur but will avoid all regulations because the cost of complying relative to the odds of being caught don't justify paying it.
I understand why businesses would want to maximize work done in an area - I hope you're self-aware enough to realize this.
The tension you may be blind to, is that society wants to maximize safety in an area - and any work done should be in service to that goal, and not an end unto itself. We shouldn't blindly maximize for work done in an area, we have to make sure the result is safe: this introduces rules and regulations, and the time and monetary costs tag along.
No two people will agree where the balance is, but generally there's regional culture. Hell, Texas allows home-owners to do their own electrical work - does that "drive business away" since some people won't pay for small DIY fixes in TX? I can't say I've ever heard that argued, but I hear it deployed a lot in response to regulations.
Many states are littered with work environments criss-crossed by extension cords because if it plugs in it doesn't need a permit, forklifts moving IBC totes because that's cheaper than the permitting it would take to install real process equipment and be regulated differently. Rain and snow covered parking and work areas that should have structures over them but can't due to the realities of environmental calculations and permitting.
Every time someone trips on a cord and smashes their face, gets mashed by a forklift, slips and falls on ice and can't work for 6mo, you personally, along with everyone else who's fetish for bureaucracy has driven up the cost of "better solutions" that would've prevented that has a little bit of that blood on their hands.
I'm not saying to just let anyone do a 3ph 480v panel swap and connect that shit to the utility. But at this point that might be better than letting you people continue to run things your way.
It's like saying that a ball-and-chain thing is not going to entirely prevent you from walking, so you're not denied the ability to walk. While technically correct, this conclusion misses a few important related consequences.
> But companies prefer to put in that effort and annoy their users so they can have that tracking.
This is making the assumption that the company has already paid the significant legal fees to see if they need the banner or not. Or ignoring the companies that think it is easier to add the banner than pay a law firm to review it's data usage.
It's like 'Hey, I make T-shirts. I want to sell them to anyone who visits my website. Do I need a cookie banner? I don't know. I do collect personal information to facilitate the transaction. I do retain the information for refund purposes. I do log IP addresses. Is this covered without a banner? Am I 'safer' to just make a banner saying we are saving their data and using it? I can't afford a lawyer to review everything we do, but I can afford a developer to make a banner like they did on other sites. Even if they implement it incorrectly, I think it's worth the cost to have the banner because I probably won't be liable if I attempted to follow the law. And maybe I'm wrong there because again, I have no idea what the letter of the law requires. I just make t-shirts and want to sell them.'
Tossing up a banner doesn't really help. You're required to allow users to opt out of anything that's not essential to the service being requested by the user. So regardless of whether you're going to have a banner or not, you have to identify what's essential. And once you've done that, you could stop there and not have anything non-essential.
I don't know exactly what you are talking about here, but if I wanted to find a restaurant that is local I definitely just type 'Miguels' into the browser and then it searches google for 'Miguels' automatically and it know's my location so the first result is going to be their website and phone number and I can load the website for the menu or just call if I know what my family wants.
However even then, I'd rather have an app for them where I can enter in the items I want to order. I've noticed apps tend to be more responsive. Maybe it's just the coding paradigm that the applications tend to load all of the content already and the actions I take in the app are just changing what is displayed, but on a website they make every 'action' trigger an API call that requires a response before it moves on to the next page? This makes a big difference when my connection isn't great.
I also find it easier to swap between active apps instead of between tabs of a browser. If I want to check on the status of the order or whatnot, it's easier to swap to the app and have that refresh then it is to click the 'tab' button of the browser and find the correct tab the order was placed in.
reply