Really appreciate the graphics, in-between summary elements and the progress bar widget. A bit too much colorful font variants my taste as it leans towards distracting, but hey everybody is different. That was a swell read, thanks for sharing!
As far as "app which helps create overview, reduce overwhelm and taks small steps" - I wonder how many of those are out there? I have written about 3 of those already for various use cases and in different flavors. Using them over a longer period of time, once the chaos subsides or the novelty wears off seems to be hard for me personally.
I'm also curious about ways to provide value with a technical project.
The challenge when exploring this topic: the incentive to stay under the radar. Those succeeding don't have much to gain from sharing details here. Worst case: it could invite competitors into their space.
Communities that thrive on growth (e.g., open-source) tend to share freely, but API businesses, especially ones which are easy to execute, often guard their edge.
A recent finding I had, while not necessarily an API: services which help you 24/7 stream a lenghty video file. YouTube live streams seem to work well for those lofi-types of channels, and there are services which are built to enable autopilot live streams.
That's the reason why I chose to focus on Go instead of Rust after immersing myself in it for a while.
Rust invites you to aim for brevity and crafting smart solutions whenever you can. Don't get me wrong, sometimes this leads to beautiful code. It can be super satisfying to write. But there is only so much fun in reading yet another 10-step iterator method chain which works due some arcane edge case in the middle of it.
I vastly prefer reading dumb and obvious Go code. It's just easier to understand and to work with.
Way out of my depth! However, the stuff I saw the folks from Oxide [1] talk about comes to mind. Hardware stuff with Rust. If you want to look at a specific project, Hubris [2] is a kernel for "deeply-embedded" systems.
I wondered about an adjacent topic recently ("what IS the kernel actually") and found out that a great way to understand it, would be to start with the boot process. Once I felt less lost, I tried to capture my learnings [1]
The text is not edited yet, but as I had the benefit of learning about it with fresh eyes, it should be very approachable (and hopefully accurate enough)
The site was built with Next.js and TailwindCSS in about a day. The size is quite big, because data is baked-in, for that sweet sweet quick interactivity.
"Liked", "watched" and similar annotations are only saved on your local device. "Look, no server ma!"
Hope this helps some of y'all to find one or two interesting JRE episodes you haven't stumbled over yet.
Interesting! Reminds me of James Clear and the way he used blog posts as raw material for his book.
PKM geek-out time: Edw519 has been using HN as a tool for thought. Producing intermediate packets in the form of comments. If those comments were more interlinked, it would be closer to a Zettelkasten.
Whoops, sloppy generalization on my part. You're completely right of course, thanks! I've been focusing on deep learning a lot lately, to the point where AI has become an alias for those exciting new GPU-heavy techniques.
The results are really impressive. At the moment I'm considering spending a low 3-figure amount for a professionally spoken intro for a new podcast. Some of the lines I generated are in my top 5 easily, human speakers don't have a lot of edge for short generic blurbs of text anymore it seems.
Yeah, running anything related to AI involves GPU instances. An alternative is to point people to using Google Colab where you can get access to a GPU for free, but that's not a smooth end user experience for most folks.
https://thehonestsorcerer.substack.com/p/running-on-empty-co... - the hidden world of copper supply
https://www.orcasciences.com/articles/there-has-to-be-a-bett... - thoughts on improving the current titanium production process