https://amontalenti.com/feed - rss+atom feed
https://amontalenti.com/archive - full archive of posts/essays
https://amontalenti.com/about - info about me
See GitHub PR here: https://github.com/hnpwd/hnpwd.github.io/pull/32
https://amontalenti.com/feed - rss+atom feed
https://amontalenti.com/archive - full archive of posts/essays
https://amontalenti.com/about - info about me
See GitHub PR here: https://github.com/hnpwd/hnpwd.github.io/pull/32
PX is a daily developer tool that helps backend engineers go from working code on a laptop to deployed code in a freshly-built cloud cluster -- all within seconds.
In December, I wrote up a launch blog post:
https://amontalenti.com/2025/12/11/px-launch-overview
We also launched the PX website, https://px.app/, and we wrote up a basic developer quick start guide @ https://px.app/docs/quick-start.html
Prior to PX, I was the founding CTO of Parse.ly, a real-time web analytics startup that grew to be installed on 12,000+ high-traffic sites and had terabytes of daily analytics data flowing through it. PX stems from my experience as a startup CTO who eventually ran large distributed systems on AWS and GCP.
PX is cloud independent, programming language agnostic, and open source friendly. PX is, in short, the backend development tool that I always wished my team could have. We're having a blast building it and we're excited to give back some power to backend developers so they can wield cloud hardware resources with open source tech, rather than locking in to proprietary cloud APIs.
The current version of the CLI is focused on one-off (or batch) workloads on GCP, but on the immediate roadmap: cron-style scheduled jobs; a v1 of our monitoring/debugging/admin dashboard (already looking good in internal builds!); and, formal support for the other 3 clouds (that is: AWS, DigitalOcean, Azure). We also have a lot more documentation to write and a lot more examples to post, but you have to start somewhere! The launch blog post covers some of the history and inspiration.
No format/vendor lock-in and very amenable to living in a git repo. For my note taking that's already game over right there against everything else. I don't want to worry about whatever cursed format OneNote uses is still something I can extract in 2035.
I also like that it's become a defacto standard that LLMs speak. I can tell it to look at the code in this server repo and make me a API_documentation.md and it'll grasp that I want a text based summary of how to use this endpoint
Simple and Universal: A History of Plain Text, and Why It Matters
https://amontalenti.com/2016/06/11/simple-and-universal-a-hi...
You might enjoy it!
The concept of time dilation explored in the article is fascinating. But I think it's possible the author has some wishful thinking about how experience and memory works. Or perhaps is using a plausible formulation as a reverse justification for his own life choices.
Here is how my childhood memories feel to me. Ages 0-14 are like an opaque tunnel, through which my brain and developing body was shot, like a cannonball, in an instant. I have some fragmentary memories of having gone through that tunnel, but they are mere fragment. My 14 year old self, somehow and miraculously, ended up on the other side of that tunnel healthy and of sound mind.
Age 14 is around where something resembling "the recorded video of my early memory" begins. I have clear memory of various episodes from ages 14-18, and this was also a period of intense individual development for me. This was where all my inclinations, passions, and life goals started to come into focus. That turned into full-blown adult individuation in college, where my goal was to pull away entirely from societal/parental expectations and live my own life. In other words: pretty much everything I associate with my adult character had its seed-like start in my age 14-18 period, exactly the period where I was pulling away from my developmental dependence on my parents.
My childhood before then is a blur. That might be a depressing thought for parents -- that this kind of blurred and fragmentary memory of childhood is possible, given that parents often describe this period as one where they are "making family memories" -- but I don't think I'm the only one. Importantly: this doesn’t make early parenting meaningless. Good parenting is ethically and developmentally important even when it doesn’t leave the child with later-retrievable episodic memories. But I don't think the point of parenting is to create said memories. It's to create a healthy child who can develop and individuate on their own in adulthood.
The article talks a lot about childlike wonder, and seeking that in adulthood. I'm all for that. But what's strange is that OP seems to believe the only place to find that childlike wonder is in parenting of your own children. I am sure parenting can be one such way to regain childlike wonder, but surely not the only one. People can reclaim their childlike wonder in sport, art, hobby, play, and travel, among other things. What's more, I know many parents who haven't the slightest bit of childlike wonder when they interact with their children. Or any other children in their family. So I'm not sure it comes as naturally to everyone as OP seems to think it does.
Two adult thinkers on how adult humans spend their time that have interesting thoughts on childlike play are John Cleese and Alan Watts. Cleese discusses it in the context of creativity in his wonderful lecture, summarized here:
https://www.themarginalian.org/2012/04/12/john-cleese-on-cre...
And Watts had this to say about it: "... if you don't have a room in your life for the playful, life's not worth living. 'All work and no play makes Jack a dull boy.' But if the only reason for which Jack plays is that he can work better afterwards, he's not really playing. He's just playing because it's good for him! Well, he's not playing at all! You have to be able to cultivate an attitude to life where you're not trying to get anything out of it. You pick up a pebble on the beach and look at it: beautiful! Don't try and get a sermon out of it."
I really enjoy the ability to get started quickly with a known idea like “make a single user letterboxd clone” with a system prompt that explains my preferred tech stack. From there it’s relatively easy to start going in and being the tastemaker for the project.
I think people being able to build their own bespoke apps is a huge super power. Unfortunately I don’t think the tools today do a good job of teaching you how to think if you aren’t already a software engineer. Sonnet rarely grasps for an abstraction.
Side note: I once wrote about recreating Delicious Library: https://dingyu.me/blog/recreating-delicious-library-in-2025
First, I took photographs of all my physical books simply by photographing the bookshelves such that the book spines were visible.
Then passed the photographs with a prompt akin to, "These are photographs of bookshelves. Create a table of book title and book author based on the spines of the books in these photographed shelves." ChatGPT4’s vision model handled this no problem with pretty high accuracy.
I then vibe-coded a Python program with ChatGPT4 to use the Google Books API (an API key for that is free) to generate a table, and then a CSV, of: book title, book author, and isbn13. Google Books API lets you look up an ISBN based on other metadata like title and author easily.
Finally, I uploaded the enriched CSV into a free account of https://libib.com. This is a free SaaS that creates a digital bookshelf and it can import books en masse if you have their ISBNs. You can see the result of this here for my bookshelf:
https://www.libib.com/u/freenode-fr33n0d3
There are some nice titles in there for HN readers! My admin app for Libib (the one at https://libib.com) is more full-featured than the above public website showcases. It's basically software for running small lending libraries. But, in my case, the “lending library” is just my office’s physical bookshelf.
I also added a Libib collection there that is a sync of my Goodreads history, since I read way more Kindle books than physical books these days. That was a similarly vibe-coded project. But easier since Goodreads can export your book collection, including isbn13, to a file.
As for my actual physical bookshelf, it is more a collection of books I either prefer in print, or that are old, or out-of-print, or pre-digital & never-digitized.
I liked the Libib software so much I end up donating to it every year. I originally discovered it because it is used for Recurse Center’s lending library in the Recurse Center space in Brooklyn, NY (https://recurse.com).
Also, Libib has a Android, iPhoneOS, and iPadOS apps -- these are very basic but they do allow you to add new books simply by scanning their ISBN barcode, which is quite handy when I pick up new items.
I did enjoy reading the OP writeup, it’s a fun idea to vibe-code the actual digital bookshelf app, as well!
It's mostly probably fine if that's the thing most of everybody wants to use and it works well; but also it's very unwise to forget that the point was NEVER to have a deeply centralized thing -- and that idea is BUILT into the very structure of all of it.
"In the 80s and 90s (and before), it was mainly academics working in the public interest, and hobbyist hackers. Think Tim Berners-Lee, Vint Cerf, IETF for web/internet standards, or Dave Winer with RSS. In the 00s onward, it was well-funded corporations and the engineers who worked for them. Think Google. So from the IETF, you have the email protocol standards, with the assumption everyone will run their own servers. But from Google, you get Gmail.
[The web] created a whole new mechanism for user comfort with proprietary fully-hosted software, e.g. Google Docs. This also sidelined many of the efforts to keep user-facing software open source. Such that even among the users who would be most receptive to a push for open protocols and open source software, you have strange compromises like GitHub: a platform that is built atop an open source piece of desktop software (git) and an open source storage format meant to be decentralized (git repo), but which is nonetheless 100% proprietary and centralized (e.g. GitHub.com repo hosting and GitHub Issues)." From: https://news.ycombinator.com/item?id=42760298
-Donald Knuth