Kilenaitor

Having bugs is not the same as being non-deterministic.

I get the point that the compiler is not some pure, perfect transformation of the high-level code to the low level code, but it is a deterministic one, no?

Same! Would love any resources. I'm interested more in making models run vs making the models themselves :)

+1 Leap takes a second to get used to but I love it so much. Even if you don't get to the precise character you want, you can get so close enough that normal motion commands get you the rest of the way.

I do change the bindings, tho. I have 's' leap forwards and 'S' leap backwards.

Neither teachers nor nurses only work 40 hours and no overtime. :')

Definitely something that requires social/interpersonal skills though will be the thing that winds up being AI immune. Humans are social creatures so I assume there will always be some need for it.

I'm Christian, so slightly different context going in, but I also found it profound. I've been to other churches and cathedrals (including the Vatican!) and they feel sterile by comparison. Stepping inside to the sight of a towering forest of stone and dazzling light is truly breathtaking. It made me genuinely emotional.

It's nothing like I've ever seen before so I'm surprised by the comments at the end of the article that make it seem like its originality has waned over the years. You can feel the conviction and passion that have been poured into it for over a century.

I can't wait to visit it again. I really love it.

Sure. I guess caveat I haven't used Mosh in a while, so maybe things have changed.

Mosh paints the screen, meaning no native scrollback. You have to use a multiplexer like tmux to get it. But ET has native scrollback. This is the biggest one for me.

Couple years ago I was on a more limited network that constrained usage of UDP which Mosh uses. ET uses TCP.

Mosh buffers inputs locally first which gives it the appearance of low latency but that illusion breaks when there are network issues. I prefer ET, even tho it can appear slower, since network issues are more obvious and I can troubleshoot them. But on a good connection, they're indistinguishable to me.

Those are three. There may be more. Honestly they are probably still more or less interchangeable for most. No reason to switch if you love Mosh.

To elaborate with some context: large sites do this to avoid hammering a small site if posts containing the link go viral.

Like imagine the thumbnail were fetched every time a link appeared in someone's Facebook/Twitter feed. That could be tens of millions of hits easy.

Also has a way better headline heh

God. Thank you.

> But the last fucking thing I want to do is delegate all the code writing to someone or something else

I talked about this a few days ago with coworkers and I phrased it almost exactly this way. I want to be an IC. I want to do the work. Becoming a manager-of-one to funnel all my work through would deprive me of genuinely my greatest joy in life.

I'm envious you managed a few good decades. I'm almost eight years into what has been my dream profession and to see indications it's going to morph from writing code into telling a robot to write code is just so demoralizing. I could have done this for decades. I wanted to do this for decades.

The individual scientists' rights to publish uncensored papers??

The firing is not motivated by the ratio. It's not a handcuff saying you must find x% of the workforce to fire.

It's setting a bar that when evaluated on a curve a certain percentage of your employees wind up being below that bar. You derive the ratio from how aggressive you expect your bar to be.

But no one is saying you need to fire people. They're saying they expect a certain amount of lower performers and if they don't see it, they want to know reason. But it also only manifests at much higher populations than an individual team. Totally possible a small enough team has everyone >= meeting expectations.

I enjoyed this post since this is exactly my approach to improvements: imagine the magic want solution, find the deltas between it and current state, code the deltas.

At work I often get tapped to work with folks who struggle with "Better Engineering" ideas (codebase improvements with an eye towards increased productivity). Usually it's just people being unable to come up with any improvements.

I always prompt them: 1. "Is this the best codebase you've ever worked in?" and 2. "If you were to rewrite this from scratch, would it look exactly like this?".

It's amusing how often those two questions trigger a light bulb moment. I of course follow up to ensure their ideas are actually good and grounded (no "let's convert the monolith to microservices") but it does wonders for inspiration.