Live data from Hacker News

The architecture behind a one-person tech startup

anthonynsimon.com

321–330 of 334 posts

Re: The architecture behind a one-person tech startup

#321
post #318

Earlier quoted context omitted.

Source? Every source I've seen says that MM is derived from the Roman numeral M, meaning thousand.

Wouldn't that make MM 2,000, the same way II is 2 and XX is 20?

It would be if it was interpreted as an actual Roman number. But in this case it's treated as M x M.

The actual Roman version of a million is an M with a bar over it, where the bar means x1000. But that's not an ordinary character, so wouldn't work for this purpose.

Re: The architecture behind a one-person tech startup

#322
post #293

Earlier quoted context omitted.

It only takes two things – curiosity and time. When you are working on a project, if you hit the edge of your current knowledge / skills, push just a little bit further when it’s something that interests you instead of just aiming to hit the basic requirements / lean on other people. This minor effort compounds over time; do it for twenty years and you’ll be an expert in multiple disciplines and also an expert in how…

Actually I think it takes a third thing: need At least in my experience I can read about different architectures all day and sort of understand them, but I only really "get" it once I find a non-toy problem I need to solve and attempt to apply the knowledge. Then you see how it really works and form hard skills which stay with you.

Absolutely this. Wanna learn French? Go to France and live there for a year. Wanna be good at spinning up infrastructure with Terraform? Take an infrastructure job at a company that uses terraform - a start-up if possible, so you get to solve all of the problems. I wanted to learn Terraform and Kubernetes for years, and no amount of books or online courses really helped. Taking a job at a start-up fixed it. In fact, our stack is spookily similar to the one OP posted, Which is validation and also admiration because this person did it solo.

Re: The architecture behind a one-person tech startup

#323
post #207

Earlier quoted context omitted.

a few to get you started: - https://github.com/vercel/nextjs-subscription-payments - https://bedrock.mxstbr.com/

Any personal experience with Supabase? Looks cool

Used supabase on a few side projects. Overall had a great experience with it. Would recommend.

Re: The architecture behind a one-person tech startup

#324

Earlier quoted context omitted.

I don't have to maintain state on GCP persistent disks. I can blow away a server without warning, and I'll only lose a few seconds of data. True, I have to maintain state on S3, but there's not much work involved in that. If I was maintaining my own database server, I have to manage upgrades, backups, and the complexity of running an additional server. With Litestream, I don't have to manage upgrades because nothing…

SQLite is really great. By using it, you don't have to install and maintain another service, and you don't have to think about things like network security. From that point of view, that's clearly simpler. But it also introduces a few challenges. It's not as easy to connect to your database remotely to inspect it, with something like SequelPro for MySQL. It's not possible to create an index or drop a column without b…

yeah, this is the more sane approach. Just use Google's replication/durability, and export to S3 when you want/need to change vendors. In this case, you wouldn't even need lightstream. Just SQLite.

Re: The architecture behind a one-person tech startup

#325

How do you start learning this breadth of software engineering? I consider myself good in the python / django space, but where do I start with learning these infrastructure technologies? I find that I use them once or twice periodically, and then don't touch them for so long, so I forget much of what I have learned.

work on an infrastructure team. This is standard cloud infrastructure -- the networking (cloudflare/ingress LBs), k8s, terraform, CI/CD etc etc

Re: The architecture behind a one-person tech startup

#327
post #293

Earlier quoted context omitted.

Actually I think it takes a third thing: need At least in my experience I can read about different architectures all day and sort of understand them, but I only really "get" it once I find a non-toy problem I need to solve and attempt to apply the knowledge. Then you see how it really works and form hard skills which stay with you.

Absolutely this. Wanna learn French? Go to France and live there for a year. Wanna be good at spinning up infrastructure with Terraform? Take an infrastructure job at a company that uses terraform - a start-up if possible, so you get to solve all of the problems. I wanted to learn Terraform and Kubernetes for years, and no amount of books or online courses really helped. Taking a job at a start-up fixed it. In fact,…

> Wanna learn French? Go to France and live there for a year.

I actually did that but only for 9 months, my french isn't that good...

Re: The architecture behind a one-person tech startup

#328
post #134

Earlier quoted context omitted.

Work somewhere where you're the big fish in a small pond. You're forced to wear a bunch of different hats and learn multiple tools across multiple business functions.

Also, sometimes, a great way to burn out quickly. . .

Definitely. There's a sweet spot, where you're the go-to guy, and you leverage that for work-life balance (because no one else can do what you do), but it also means you're leaned on a lot to move things along. It definitely requires some fortitude and ability to manage time and expectations (and stick up for yourself).

Re: The architecture behind a one-person tech startup

#329
In the beginning my startup only had 2 people. A designer (my friend) and me (a developer).

For our frontend we used Webflow. My friend was able to create the entire marketting site, and all the app UI's without needing help from me. Webflow is an awesome tool for that sort of thing.

For the backend, I built a simple Node/Express API and hosted via Heroku.

To this day, everything is still running fine and the API is processing roughly 200 million requests a month. The total cost to host that on heroku is $50/mo.

You can definitely have a simple stack but have it be highly scaleable!

Re: The architecture behind a one-person tech startup

#330

Earlier quoted context omitted.

I mean IPO’d with one employee - the founder

I suspect IPO would be impossible with one 'person'. You'd have other people on payroll: Lawyers and accountants at the very least. If you're paying millions of dollars to professionals anyway at a certain point it would more sense to hire the people directly, right?

Maybe not. Conceivably, everyone could be on payroll as contractors except the founder.
Post reply on HN