From a few months ago:<p><a href="https://news.ycombinator.com/item?id=20985875" rel="nofollow">https://news.ycombinator.com/item?id=20985875</a>
Wow, that's hugely impressive for a 1-man operation. You're like a song that you hear on the radio with solid guitar, vocals, drums, etc. and it turns out it's all 1 guy by himself who recorded and mixed those elements together. It may be possible, but it's definitely not common.<p>Also, to any VC's reading this, this guy will spend $1 better, leaner and farther than any team you can name, and he's already demonstrated he has the chops w/this project.<p>Finally, thanks for sharing this. This is the kind of quality post that 100% justifies the time I spend on HN.
This is the most informative article that I read today. No hype, no story, just a plain list of engineering choices, some explanations, and a very useful list of tools.
This gives the confidence to move forward. You made a break through for me. The point you made about over engineering. I found out resently that beautify is in simplicity, and you grow when you have to grow. Not day 1.day 1 is about day 1. But I was stuck at the over engineering bit, in the name of making things simple.<p>Thank you for this great article I will be waiting for your future blog posts.
Who the hell would consider this stack to be boring? There's so many moving parts for a single person operation, seems pretty insane to me that anyone would consider this boring.
A great inspiration for aspiring tech-entrepeneurs, for which the "VC-hockeystick-picthdeck-series-x"-cirkus sounds like a nightmare.<p>Easily my favorite post this week.<p>Thank you very much for sharing this.
This is a very useful service. I often search for podcasts on random topics that I want to know more about. Imagine if the web was such that you subscribed to certain pages and only consumed those. Weird.
Why not use more managed services like a managed DB and some PaaS for the backend services and workers?<p>I imagine that would be both cheaper and less overhead (in ansible yaml) ect.
> On ListenNotes.com, most web pages are half server-side rendered (Django template) and half client-side rendered (React). The server-side rendered part provides a boilerplate of a web page, and the client-side rendered part is basically an interactive web app.<p>Imagine now every time you change sever side you need to make sure you don't break client side. These dependencies are a big tech debt.<p>How come not using docker there is less overhead? Not using docker I need to worry way much than using it. Like do I need to install anything? Versions works? How do I reproduce my env if my machine breaks?.... You'd need to write docs and keep them in sync.