The problem with this is the reason LLMs are so good at writing Python/Java/JavaScript is that they've been trained on a metric ton of code in those languages, have seen the good the bad and the ugly and been tuned to the good. A new language would be training from scratch and if we're introducing new paradigms that are 'good for LLMs but bad for humans' means humans will struggle to write good code in it, making the training process harder. Even worse, say you get a year and 500 features into that repo and the LLM starts going rogue - who's gonna debug that?
For example, Claude can fluently generate Bevy code as of the training cutoff date, and there's no way there's enough training data on the web to explain this. There's an agent somewhere in a compile test loop generating Bevy examples.
A custom LLM language could have fine grained fuzzing, mocking, concurrent calling, memoization and other features that allow LLMs to generate and debug synthetic code more effectively.
If that works, there's a pathway to a novel language having higher quality training data than even Python.
I recently had Codex convert an script of mine from bash to a custom, Make inspired language for HPC work (think nextflow, but an actual language). The bash script submitted a bunch of jobs based on some inputs. I wanted this converted to use my pipeline language instead.
I wrote this custom language. It's on Github, but the example code that would have been available would be very limited.
I gave it two inputs -- the original bash script and an example of my pipeline language (unrelated jobs).
The code it gave me was syntactically correct, and was really close to the final version. I didn't have to edit very much to get the code exactly where I wanted it.
This is to say -- if a novel language is somewhat similar to an existing syntax, the LLM will be surprisingly good at writing it.
I worked very hard for the first 5 or 6 years of my career - hit senior dev pretty quick, managed to double my pay moving into consultancy, and back on product dev in a smaller company nowadays.
Honestly? I don't feel a massive need to grow beyond where I am. I earn in the top 5% in my country. I live a comfortable and flexible life. I continue to learn like any dev with a passion for technology does - but i'm not constructing my life around an endless climb. If my role naturally transitions upwardly, great. If I stay where I am, steadily taking on more responsibility,that's also totally fine. The diminishing returns of chasing a CTO title or another arbritrarily large sum of money just doesn't seem worth it.
I run my Jellyfin on a Pi 5 8GB (with a bunch of other homelab stuff) and run an OSMC (Kodi + Jellyfin plugin) on a Pi 3b 2GB with absolutely no issue. OSMC automatically integrates with my TV remote, runs very low power and smooth. I never used any of the Plex stuff that wasn't my media, so I prefer it this way. Less bloat, more customisable.
I met a dude at a Rust meetup a few months ago who was creating an infinite, multiplayer minesweeper game in Rust/WASM you might also find interesting! http://infinitesweeper.online
It definitely is cultural, but I've never viewed it from the perspective of getting straight to business being rude. A bit like in the UK, "weather chat" is a very standard point of conversation at the start of a meeting with people you aren't too familiar with, as a reflexive ice breaker.
For me personally, whilst I understand all the reasoning and logic behind it, it does ultimately come across as fake and unnecessary - everyone knows it's fake and unnecessary, but we ritualistically do it anyway, because the alternative is too jarring "we're here for work, lets do the work, and we're done"
Yep I work with a fair amount of people from India and I can definitely concur anecdotally that this is something my Indian colleagues do more often. It’s a global thing in my experience but definitely more predominant in some cultures than others
