fab13n

My gut feeling is, this post is 180° wrong. LLMs are the exact opposite of "elite coders", they're perfect StackOverflow users:

* they memorize adapt and write back small-scale patterns very efficiently; * they know widespread libraries inside out, and can learn others in minutes, even if their doc sucks; * they often produce good results, because most of the time we write unoriginal code, which paraphrases something it already has dozens of versions of in their training corpus; * but they're bad at seeing meaningful, non-obvious, simplifying abstractions, we really have to spoon-feed those to them; * they _love_ verbosity, that's literally how they "think"; * they also love repetition: the other term for "repetition" is "patterns", and they're basically excellent pattern matchers.

So, Lisp is enjoyable for your typical LLM-complementary hacker, but not for LLMs. LLMs typically replace the kind of "non-elite" developers who hated Lisp, for remarkably similar reasons.

What I'd love would be an LLM trained to faithfully rephrase a "normal" program into Lisp-ish pseudo-code, that would make reviews faster, more reliable, more enjoyable. But hand-written code is going the way of hand-written machine code; let LLMs have what suits them best, and higher level tools for the more abstract jobs where we're still relevant, and that would be various forms of code reviews.

As for calling "elite" the kind of developer won't understand that development is a team sports, and that the proper tool is the one that fits the team, not their own peculiar quirks, I'm not going to address that, it isn't the keystone of his argument; but a lot could and should be said about that too.

Being the maintainer of such a big open-source application as Chrome used to grant dictatorial power: maintaining a fork represented too much work. It only happened in the most awful situations, such as Oracle acquiring OpenOffice.

But that was before LLM-driven development, I think that now the game has changed, and maybe Google hasn't got the leverage it thinks it has.

Smart move: now that they're an established player, and that they have a few billions of investors' money to spend, they comfort a jurisprudence that stealing IP to train your models is a billion dollar offense.

What a formidable moat against newcomers, definitely worth the price!

> it's questionable whether this is a net benefit for Romania as a whole.

it depends what's most beneficial: having a few percents of very mathematically experts people in maths-heavy professions? Or having everyone somewhat decent at maths, even when it doesn't affect their productivity in their jobs?

I don't have any hard data about this, but instinctively I'd bet on the former: I'd rather have a few hundreds more Sutskevers, than most of the country's bakers know their way around PDE.

The choice is between:

* be completely autonomous from day 1, and progressively increase the number of situations you can drive through;

* or drive through every legal situation from day 1, and increase the % of them handled autonomously.

I believe the 2nd approach, Tesla's, has one key advantage: it collects data about freak situations much faster and more exhaustively. Given how data has become the key resource in AI, that's probably a very strategic asset they've accumulated here.

Also, Waymo's joker (remote operation by humans when the software bails out) is totally replicable by Tesla robotaxis.

the magic power of spreadsheets is that they encourage improvisation, and it probably applies to that one.

you have only one data structure (the 2D table), data types are super-weak, there are no variable names... all of this guarantee a maintenance nightmare, and rightfully scares developers. But it's also a very low barrier to entry. You've got data, you paste them into the grid, and you start toying with them, before having figured anything about them.

That's an amazing superpower, when targeting non-developers, and that's why Excel is the most used programming language over the world, by far: it's probably got an order of magnitude more users than there are trained developers in the world.

If Google succeeds at banning ad blockers from Chromium-based browsers, there's no doubt that Firefox' usage will go back up.

Remote software engineer in the EU here.

Remote has been fantastic, to extend our pool of potential customers/employers. Not working in an open space, not being disturbed by pointless red-tapers and middle managers is a productivity boost. Not losing time and energy in commutes as well.

I can see one serious drawback with pure remote: it's a cumbersome way to mentor junior developpers. In big companies which maintain a balance of junior/senior staff, and try to make the former grow, it's a legitimate issue. In start-ups, which expect you to hit the ground running, and don't have an army of managers to keep busy, remote should be the norm.

That's what better IDEs did to Java codebases indeed: they made layered boilerplates and leaky abstractions somewhat navigable, therefore generations of careless contractors have been able to ship ever nastier messes.

if your test can't tell a smart student apart from a dumb algorithm, the broken part is your test.

can't wait to see what people come up with when they'll start interfacing it with a modern AI.

Got one under Ubuntu 22.04. My only issue is that some transitions are frustratingly slow, much moreso than on my 2014 XPS13:

* Getting out of sleep (deep RAM sleep, not hibernate)

* Handling password/fingerprint authentication once out of sleep

* Wifi rescan frequency

* Occasionally, plugging/unplugging external screens

And I've got no idea why. Once woken up and plugged to whatever I need to use, it's a really good laptop.

there's a problem between Bob and the bureaucracy. whether it's a Bob problem or a bureaucratic problem is left as an exercise to the reader.

However, I'd be thoroughly unsurprised if Bob happened to be on the autism spectrum. And autistic people are counter-intuitive but very easy to handle: force yourself to be extremely explicit, and to stick to first-degree in your exchanges to a point that seems ridiculous (to you). That's it, really.

I've had a bakfiets for 12+ year in France; I did DIY electrification at the time, as that was the only viable alternative then; both kids have been moved around in it since they're born (now my teenager can use our non-cargo e-bike, a RadExpand 5); I've already taxied two (petite) adult women at once in it; I use it as a wheelbarrow under steroids to bring wood pellets from parking spots to my boat's moorings, 7×15kg at a time; it truly replaces a second car, for a tiny fraction of the running expenses.

They were a niche gadget before electrification went mainstream, but today, I really urge you to give it a try by renting one for a couple of days, it makes life more enjoyable in my experience, beyond the money saved.

I prefer companies which are open about the technologies and languages I'm experienced with. That's a huge green flag, that they consider their software engineers as smart people solving hard problems while continuously learning new skills. It also means they listen to their senior technical staff, which consider that learning new bits of stacks is hardly the most complicated thing they expect you to do.

As opposed to companies which consider them as glorified factory workers, who are insufferably hard to manage and monitor.

I'm currently working with RoR, which I'd never used before, and what matters is that I know algorithms, SQL beyond ORM, how to write code which won't be a nightmare to maintain in a couple of years, etc. All those skills are the same in Rails, in Django, in C++.