Oh wow, I did "someone who keeps saying slurs" and there really is no filter:

https://translate.kagi.com/?from=en&to=someone+who+keeps+say...

e: Converting back from output like this to LinkedIn Speak also returns some... illuminating results about the underlying models.

I’m struck by the fact that when other people say ‘faggot,’ it catches me off guard, and it takes me a second to evaluate what to do about it. (Is it a joke? Do they know I’m gay? What’s the appropriate response??)

But when an LLM generates it, it is immediately hilarious.

That's because LLMs are also gay.

Definitely not all contractors, my company at the very least used to have a contract with ICE and isn’t listed.

The same reason we give beginner math students addition and subtraction problems, not Fermat’s last theorem?

There has to be a base of knowledge available before the student can even comprehend many/most open research questions, let alone begin to solve them. And if they were understandable to a beginner, then I’d posit the LLM models available today would also be capable of doing meaningful work.

12/32 SR71s were lost in the 33 years they were flying. 11/200 MD-11s have been hull-lost from 1988-2025. Not to mention that passenger/cargo planes will put on a lot more flight hours than the SR71s did in a given year.

I don't have any nim experience (sorry!) but I'm also exploring SDL3 with odin. I was able to get a naive battleship clone up and working very quickly, pretty neat. Next step is the new SDL3 GPU API.

I haven't looked into Odin that much but I hear it's swell, so maybe I should!

The headers A-L are links to the problem PDFs if you want to see.

The college I went to explicitly billed itself as for teaching, and most of our professors were just that. They might do research with the upperclassmen, but their priority was teaching.

That is, until we got a new president who set a new strategic goal for being a top research school and adjusted all hiring and tenure standards for that.

Are there many people involved in follow the sun support or SRE roles there? I know my company only has an engineering presence in Aus and Japan because of the large coverage gap between the US west coast and the EU. Seems like low wages + native English* could be a nice win for companies.

* For some definitions of native. I've had to work as a translator for a Kiwi and an American, both native English speakers.

> Seems like low wages + native English* could be a nice win for companies.

It's not always native English. It's always at least proficient enough, but a good chunk of the workers in the tech sector speak English as a second language. NZ has very diverse population.

I know that aws has a few reliability engineers in Wellington, but that’s just to support their aus servers. There really isn’t that many foreign companies outsourcing support to NZ.

It's a slightly weird one, but Octopus Energy (UK) have setup a new utility in NZ and it also covers off-hours support.

I've found the same effect when I ask the LLM to do the thinking for me. If I say "rewrite this function to use a list comprehension", I don't retain anything. It's akin to looking at Stack Overflow and copying the first result, or going through a tutorial that tells you what to write without ever explaining it.

The real power I've found is using it as a tutor for my specific situation. "How do list comprehensions work in Python?" "When would I use a list comprehension?" "What are the performance implications?" Being able to see the answers to these with reference to the code on my screen and in my brain is incredibly useful. It's far easier to relate to the business logic I care about than class Foo and method Bar.

Regarding retention, LLMs still doesn't hold a candle to properly studying the problem with (well-written) documentation or educational materials. The responsiveness however makes it a close second for overall utility.

ETA: This is regarding coding problems specifically. I've found LLMs fall apart pretty fast on other fields. I was poking at some astrophysics stuff and the answers were nonsensical from the jump.

> It's akin to looking at Stack Overflow and copying the first result, or going through a tutorial that tells you what to write without ever explaining it.

But if you're not digesting the why of the technique vis a vis the how of what is being done, then not only are you gaining nothing but a check mark in a todo list item's box, but you're quite likely introducing bugs into your code.

I used SO yesterday (from a general DDG search) to help me learn how to process JSON with python. I built up my test script from imports to processing a string to processing a file to dump'ing it to processing specific elements to iterating through it a couple of different ways.

Along the way, I made some mistakes, which were very helpful in leveling-up my python skills. At the end, not only did my script work, but I had gained a level of skill at my craft for a very specific use-case.

There are no shortcuts to up-leveling oneself, my friend, not in any endeavor, but especially not in programming, which may well be the most difficult job on the planet, given its ubiquity and overall lack of quality.

Confirmed by the White House here: https://ustr.gov/issue-areas/reciprocal-tariff-calculations.

Thanks! This is an interesting read.