Any idea of what kind of 'custom-trained' model does builder.io use? Is it some kind of an rnn? they claim to have 100k context window

Are there real world exercises where I could apply these patterns?

ben awad from youtube[1] has a slightly better solution for actual usage: stars/tags

[1] https://www.youtube.com/watch?v=MT6M_sqAuZo

what habit tracking application has worked for you?

I use TickTick to manage my daily tasks, it also comes with a habit tracker and you can even set reminders for your habits, for ex. Workout time, diet check, meditation time, everything is synced to cloud and the free tier has enough features for a normal user. Moreover the pomodoro timer and time tracking features it offers are a plus and it just gets so easy having all these features in a single application.

I recently built a habit contract (a concept mentioned in Atomic Habits) website (https://news.ycombinator.com/item?id=29726228). It's helped me achieve a 116 day streak on Duolingo.

Habinator https://habinator.com

Habinator

Here is a peer-reviewed collection - https://github.com/mre/idiomatic-rust

A Thousand Brains: A New Theory of Intelligence - Jeff Hawkins

If anyone else wants to do this as a learning exercise I found https://www.maizure.org/projects/decoded-gnu-coreutils/ which goes into design and code of most of the utilities from the original coreutils.

netlify has something similar to what you describe - https://app.netlify.com/drop

> a language to communicate within a group of peers while under environmental pressure

what does this mean?

Another difference, that I have found, is that programming is immediately rewarding because it's verifiable. On the other hand, writing is without a feedback mechanism or a very delayed feedback or even subjective feedback, which can be painful and demotivating.

It's one of the reasons I self-published my novel. Of course it may well be it's not good enough and that it would never in a thousand years get picked up by a publisher. But I was certainly not willing to spend months or years even finding out if a publisher wanted it, when I could get it into the hands of readers myself within a few months of finishing writing.

[if you want to maximise the chance of "making it big" traditional publishers are more likely to be able to make that happen, but for my part it's a hobby first and foremost, so that wasn't really a consideration I cared about at the odds of that are extremely poor anyway]

Agree that programming has that aspect. Just knowing that code does what you expected it to do at the technical level is great.

But ultimately when you write code it was done for some purpose so a similar delayed / subjective feedback mechanism is still relevant (i.e. does it solve problems for users? Does it work with real data? Does it scale?)

Interesting, never thought of it like this. Personally I like the no-feeback aspect of writing because I have to find it in myself to keep on writing. Makes it much more rewarding and personal, private, not doing it for the social media likes/brain chemicals. The ultimate form of delayed gratification: never