the reality actually is, you DO need depth in order to close lucrative enterprise contracts.

but startups will use anything. you use early money/traction to fund the deeper features. that's saas/startup 101.

anyhow, saas just means the second "s" matters more. maybe software gets cheaper (that's actually an unproven hypothesis), but service encompasses many dimensions. the most lucrative contracts won't be eaten by fly-by-the-night operations almost by definition. any startup that knows the words 'vendor risk' will tell you.

Everyone knows that many things that are not directly beneficial to society would go unfunded because humans optimize for what’s around them, and things that are self-interested.

There isn’t even alignment. One person wants to fund science, the other wants to fund high speed rail, the other wants farm subsidies, one wants social security and the other wants the military. Government balances all of that together. Of course people will make value judgements about their pet interests and declare the other aspects to be better funded separately.

more providers are making refresh-tokens single shot. this means that if someone refreshes your token for you, your own auth will break as you will not be eligible to refresh the token, at which point you could reconnect the app and void the old (stolen) session.

time-limiting and single-purposing the tokens are not cure-alls, but they do certainly offer enhanced security by limiting the amount and scope of damage.

IAM roles/workload identity.

Even time-limited or signed JWT, though has a separate issues.

Maybe you'll say 'those are both just text values passed like an apikey' though api keys don't frequently rotate/time limited, which is an important security feature.

norway and alberta take fundamentally different approaches to how they see the government and taxation. don't blame the federal government by saying individuals paying income tax somehow exempts the province from smart financial stewardship.

Interestingly, I hear a lot of people talk about LTSC, but few talking about their positive experiences. Is this the "I'm moving to Canada," of operating systems?

the downside is no anonymity. The upside is, no astroturf, no bots, no nothing. Or maybe not 'none' but 'greatly reduced'.

That's actually a community I might be enthused about participating in. Sort of like HN, where a lot of people use their real names. The problem is how you bootstrap it. People need a good carrot to embrace the stick.

What a disaster. I don't really know anyone who is voluntarily buying Teslas when there are so many other viable options in an increasingly crowded marketplace.

Even EMs and TPMs are assigning people based on their previous experience, which generally boils down to "i've seen this task before and I know what's involved," "this task is small, and I know what's involved," or "this task is too big and needs to be understood better."

I'm not saying that can't be done, but taking a large task that hasn't been broken down needs, you guessed it, a powerful agent. that's your senior engineer who can figure out the rote parts, the medium parts, and the thorny parts.

the goal isn't to have an engineer do that. we should still be throwing powerful agents at a problem, they should just be delegating the work more efficiently.

throwing either an engineer or an agent at any unexplored work means you just have to delegate the most experienced resource to, or suffer the consequences.

The links on the NAS page are also really good. nice share!

I love drinking craft beer. but when a single craft beer reaches up to $15 a beer, there's only so much I will partake, especially if I can have a $1 coors at home (which imo is still an expertly made product).

similarly, canned vodka sodas or malt bevages (like whiteclaw) easily hit the $10-$15/can mark at establishments. it's no wonder people don't want to drink out.

just add a new git remote and push. less so for issues and and pulls, but at least your dev team/ci doesn't end up blocked.