I really don't want this to be AI writing because I enjoyed it, but as other commenters have pointed out, the rate of publishing (according to the linked Twitter account) is very rapid. I'm worried that I can't tell.
I'm surprised no one in the comments is mentioning Kotlin. Out of all the languages I've worked with it has been the most enjoyable by far. I agree with the article that there isn't much community but I feel like that's arguably the least important category there. You should definitely give it a shot if you've never tried it before.
I think this sums up my thoughts on the LLM writing "style" pretty well:
> If a student submitted a piece of writing to me that sounded like this—and I was sure they wrote it themselves—I wouldn’t know where to start. I guess I would tell them to stop writing for a while and go read some old novels, or work a crummy job, or backpack around the other side of the world. But that would be bad advice, because I know people who have done all of those things in the hopes of becoming a more interesting person, and it hasn’t worked. So I might ask them instead: “Have you ever considered a career in consulting?”
Code doesn't need subjective intelligence. I think LLMs, as much as I dislike offloading thinking to them, are likely to become a large part of software engineering. I'm hoping that it'll never nail the subjective experience - I read to explore others thoughts, however ungrammatical, broken, or convoluted their prose is. Give me that over a bowl of bland and tasteless slop any day
I have sync to support the amazing devs, and for convenience, and an automatic git-based backup that runs in the background. It's good to double dip sometimes
I'm sick of using React for personal projects so I've been building a lightweight, functional, and minimalistic reactive web framework. Turns out there are a lot of decisions that go into something like this, it truly is an iceberg of complexity. It creates plenty of enjoyable problems to think about though