There are plenty of rails, they’re just different ones. Like criticizing dear leader or Tiananmen square.

While that’s a good amount of money, it isn’t “fuck you” money. You’re still gonna need a job.

“For cause” at my company is gross malfeasance, not merely performing well below expectations. It’s the employer again putting themselves first: problematic employees are “harder” to get rid of than the status quo of letting them stick around indefinitely. Sucks for everyone else who has to work with them. Every company should cull a small number of people every year.

I actually think a few % a year is healthy (1% feels right to me). I work at a company where we never lay anyone off and it’s led to a bunch of deadweight in the company that make work harder for everyone else. You gotta have some mechanism to let low performers go.

10% is way too high though

The law wouldn’t apply to free games or games that are only accessible via a subscription.

Boy this feels rife with potential loopholes…

“What a great observation! Now why don’t we both kick back with a nice relaxing glass of Coke Zero?”

I’m fine with just cooking him and throwing the meat away

Please, they’re super reliable cars! I haven’t needed to fill the blinker fluid on mine even once since getting it

I think the community is a good size right now. Popular enough that we guarantee getting any content of relevance I care about, but not popular enough to have all the problems you mentioned. I hope the community stays this size and off the radar indefinitely.

Cause it’s a shit post.

“I might have to delay the purchase of my 5th yacht by 2 months!”

Or in my ass?

I don’t think you get 3 seconds with prime Tyson

If VSCode is just hijacking the in-IDE commit UI, is bypassing it as simple as committing from the command line?

It’s small now, but it keeps growing

…the steamship

And all this shit is insured

I do a lot of “disconnected coding,” think scripts that do a long and complicated calculation, triggered manually by a few users, and aren’t online services. In these cases vibe coding is pretty great: if something doesn’t work the first time, I can iterate easily till it does. Very few consequences in getting it wrong other than time. My hand is also very firmly on the wheel and I have a lot of time to think about changes to fix issues or make things better.

Now for an online service with very specific requirements on how it handles inputs and produces outputs, at scale, with security issues, and millions of people using it…yeah I’d be pulling my hair out too if I had to vibe code all that.

He was vibin’ before it was cool

For years, we’ve been warned that the robots are coming for us. Now they’re asking us to come for them.

Some gold quotes in this one