hirsin

The space is rife with folks asking big questions like "if I give an agent money to invest, I don't owe taxes on it because the agent did it, right?"

I do enjoy asking people what they mean when they say they want to build an agent-native platform, because that work is rarely what they actually want to do.

As someone with a vested interest/being/been many of the parties you mention... Do you think support for "federated login via OIDC" would _not_ fall under the SSO tax?

Who do you think would host the "federated login" system that would replace the major authentication companies?

You can already stand up a SAML or OIDC provider using OSS and run the IdP for your company. I have many customers that do! And you bet we still charge them for SSO, and that they're every six months asking how bad the migration to a "big auth company" would be.

While I generally agree for general human living, I've seen impressive "digital hoarder" success using AI because it changes the dimensions of reasonableness.

Imagine your hoarder scenario except that the hoarder has unlimited storage space and a team of librarian/warehouse workers to go find and fetch the items needed for the wall hanging task.

It's implicit as a request, not something they literally say (usually).

Namely - I put near zero effort into this response, and deciding if it's correct is on you. -> I'm asking you to read it and figure out if it's correct because I couldn't be bothered to do so

Re: Topologies I found it resulted in a lot of reorgs founded on the seeming belief that Conway's law is both immediate and retroactive - if we change the teams and what they own, their features and code will similarly now become cleanly organized.

It's a shame because the underlying message of not overloading teams with extremely broad feature areas is good, and was exactly what we needed.

They mean the apartment building hallways and elevators. As in, if you summed the square footage of all the apartments on a floor, you'd get a number greater than the actual dimensions of the floor, because the common areas are counted multiple times.

Yep, the issue is that recalculating DSCR doesn't happen on the right timescale to incentivize reducing rents, instead incentivizing keeping vacancies open and using a pro forma DSCR.

The banks know this is a structural issue, but are likewise incentivized to keep "strong assets" on their balance sheet, rather than a bunch of troubled assets bound for default.

The claim isn't that they can keep this up forever, it just needs to last another quarter, every quarter.

The shell game is both parties knowing that the cups are all empty but still playing because it's better for them both to do so.

This comes across strongly any time you hear management talking about "fungibility of engineers". Everyone is a full stack everything engineer, and AI makes that even easier for them to trick themselves into believing.

If anything, I feel like AI has made domain expertise more important, not less, as the "confidently wrong" error case for agents has no one able to sanity check it. At least before AI a human would dip their toe in the water and usually realize that having no idea what they were doing, and not even being able to understand what the comments mean, was a sign that they need to go find someone more experienced to help.

Look, it wasn't _my_ request that made the server fall over, it must have been one of the other several thousand thoughtless scrapers running on the website that caused it to die.

Not quite. At least the one I found is some trickle down economics myth.

The one op is referencing is more like the dollar is used to pay off the waitstaff, who pay their rent to the landlord, who pay their over due taxes, so that the government can issue a refund to the cafe owner. The dollar ends up back in the hands of the cafe owner, who puts it back down on the table with all the debts paid off.

It definitely looks like the old tale come true - at Microsoft people would warn against using Google because then Google could figure out what we're working on, since it was pretty easy to tell where a query was coming from.

Sounded far fetched back then, and on the face of it illegal, but now it's just common sense I imagine.

That's the success case. In the failure case you have emboldened, pressured teams jumping in to make a "quick fix" or "that feature we needed" in a codebase for a team they've never heard of, and leaders cheering it on in the name of progress.

Not every company is going to see those boundaries and stakeholders as features, and they'll be under pressure to "mitigate those blockers to execution". That's where the cognitive debt skyrockets.