Now, my opinion is it currently can't think, but it certainly has memory.

However, LLMs don't have memory. That's what I (and others on this thread) responded to, which is unrelated to how my own memory works.

I’ve been fully remote for 17 years and, before that, did short periods of remote work as early as 2003.

The first junior I remember being onboarded remotely (into an irc-mostly, voice call for ultra rare cases job) was me and it worked pretty well.

From about 2010 to 2012 I grew the support team of a database services company from 2 to about 20 people (the 2 at the start was counting me). A lot of the new hires were junior when it came too dabatases, some just junior period, and it worked great too.

There were some in person meetings but the vast majority of onboarding and training happened remotely.

Maybe people invested in office real estate are perhaps biased to get the wrong answer on this one.

If I had time now, I’d write an article titled “is the FT right about the cause of weak junior hiring?”

I don’t have time, but you can apply that saying about headlines to my imaginary article.

But back to your productivity angle: Stephen Wolfram wrote about the productivity benefits (for him) of walking while working: https://writings.stephenwolfram.com/2019/02/seeking-the-prod...

Yes, another layer to cross-check, say, “in kubectl logs I see …” with an actual k8s tool call can help, that is, when the cross-check layer doesn’t lie.

For the time being, IMHO, human validation in key points is the only way to get good results. This is why the tools make experienced people potentially a lot more efficient (they are quick to spot errors/BS) and inexperienced people potentially more dangerous (they’re more prone to trusting the responses, since the tone is usually very professionally sounding).

I would not make a good fact-checker :(

It was also my first “fuzz pedal” because the sound never came out clean :)

So while the video is impressive and I couldn't do something like this myself, I was glad when I saw how bad it ran, as that computer of mine would a little bit more than 30yo today, so to have that beat by a 40yo printer controller would make me think I could have done something to have it run better back then!

Especially important if you want orchestral instruments that sound realistic. Just think of the many ways that a single note can be played by a professional player and multiply that by the range of the instrument.

Edited to add: not orchestral instruments, and also not samples, but this gives an idea of the complexities of capturing the characteristics of an amplifier so that it can be modeled faithfully: https://neuraldsp.com/quad-cortex-updates/introducing-tina (I'm not related and I'm actually a Line6 customer, but I saw this at work in an interview by Rick Beato and though it was super interesting)

Do you remember if that was a recent addition?

Full disclosure: I was quite the newbie back then and most of what I "new" about SQL Server was what the more experienced coworkers told me. This was a very IBM-biased place so I'm not surprised they would have stuck to some old shortcoming, like people who still talk about bad MySQL defaults that have been changed for at least 10 years.

Up until that job (which was my second Actual Formal Job), all my DB experience had been with either dBase (I think III plus or IV) and access, so this was a whole new world with me.

It was through MS SQL Server that a colleague taught me about backups and recovery, after I ran an update in prod but forgot to include the where clause ... :)

In my experience in the late 90s and early 00s, besides Oracle and Sybase, DB/2 and Informix were also regarded as good. Oracle was considered the best though.