RSS is actually one of my favourite uses for the tablet; I built a little service that builds a pdf "newspaper" twice daily and sends it to Google Drive. Very nice to read my feeds on the rM2 instead of a glowing screen
Hi, hyperpaper creator here– sorry it didn't work for you :(
Just curious if there were any problems specifically with the planner, or if it was just the fact that the rM really didn't work for you at all? Always looking to improve it and fill in any gaps in the product.
Also when did you try it? Because I will admit the first version was definitely clunky
The Swedish, rather short-lived but very influential, magazine Pop voted There's a Riot as the best album of all time in 1994. That list had a huge effect on a whole generation of Swedish music fans.
I've been using "pdfcpu optimize" as a post-processing step for dynamically generated pdfs for several years now. Simple, well-documented, and fast. I've been very happy with it
I will add a +1 to your recommendation as well, his blog has been my favourite way to keep up with the AI landscape over the last 18 months. Just the right level of detail and technical depth for me
Yeah, honestly the answer is mainly not having a proper job (I don't have anyone who can tell me how to spend my time) combined with constructive procrastination: I've not been making nearly as much progress on my main projects over the past couple of months because there's been way too much stuff I want to write about.
I can write fast because I've been writing online for so long. Most short posts take about ten minutes, longer form stuff usually takes one or two hours.
I also deliberately lower my standards for blogging - I often skip conclusions, and I'll publish a piece when I'm still not happy with it (provided I've satisfied myself with the fact checking side of things - I won't dash something out if I'm not certain it's true, at least to the best of my ability.)
One thing I'd love to know - how do you balance time spent "building" vs. time spent "researching"?
The writing, I understand - you do it relatively quickly because of a lot of practice. But I feel like just reading up on the AI news every week takes up a significant amount of time - time that can't be spent researching/building things.
Having relevant projects is key. My https://llm.datasette.io projects gives me the ideal playground for trying stuff out - any time a new API model comes out I can spin up a new plugin to for LLM, which is a great way to try the model with limited development time (most API plugins are a few dozen lines of code).
I've managed to balance building vs writing a lot better in the past - I lost that balance in November and December, I'm trying to get it back for January.
Oh that's cool. We've been blogging about AI eng recently, but the project is often "try this idea/tool/library in order to write a blog post about it".
Having some kind of standard "I need to integrate this new thing with an existing codebase" makes a great standard project.
It isn't just React / Non-SPA, even by SSR / HTML standard there are no needless moving graphics, page / section transition. It is simple, accurate and to the point. I like the word people in this thread here to describe it as "artisan".
It really is a page of Art.
If there is only a few thing I could nitpick. Sections or indicator of how long the article is. The Moon is long... very long. And I understand why he want Image on load just to save bandwidth but personally I hate when image only start to load and appear when I scroll close to it.
I hope this will inspire a new generation of people to rethink about Front End.
Frontend dev here. Hats off to Ciechanowski as always. The code is readable and works well, and looks written with love. I wouldn't do it this way, but then again, I wouldn't do this at all. Probably couldn't.
This is an example of frontend as a craft. I am confident it was written with a model M keyboard and his home office is referred to as an atelier.
I've built a custom planner/calendar generator targeting e-ink tablets like the reMarkable, Supernote, and Kindle Scribe. Revenue is highly seasonal, but now consistently over the $500/mo threshold :)
Great podcast and I really enjoyed their MSFT episodes.
I thought their pro-Ballmer angle was interesting at the time too (it was the first long-form defense of his tenure that I had heard), but I wasn't sure how much of that was due to him being a primary source for the podcast's material.
RSS is actually one of my favourite uses for the tablet; I built a little service that builds a pdf "newspaper" twice daily and sends it to Google Drive. Very nice to read my feeds on the rM2 instead of a glowing screen