Pieter Levels Makes $600k a Year from Nomad List and Remote OK
91–100 of 147 posts
Re: Pieter Levels Makes $600k a Year from Nomad List and Remote OK
#92I would say that for every Pieter on this planet, there are thousands of failed Pieters. The success of his business niche doesn't have much to do with tech stack or even programming, but rather Instagram style lifestyle businesses.
Aren't this all successful companies? There is a reason why all big companies spend 100s of millions of dollars in marketing every year.
Re: Pieter Levels Makes $600k a Year from Nomad List and Remote OK
#93I don't think this has anything to do with tech stack. React is generally easier to use correctly than plain JavaScript, PostgreSQL is as easy to use as SQLite (and more powerful), Node is as easy to use as PHP (but has more libraries, and you can use TypeScript which makes it easier to write correct code), etc. The only actually simplifying choice seems to be using a single VPS instead of a Kubernetes-based cluster.…
For Pieter its about staying with PHP.
Re: Pieter Levels Makes $600k a Year from Nomad List and Remote OK
#94Re: Pieter Levels Makes $600k a Year from Nomad List and Remote OK
#95Earlier quoted context omitted.
I knew someone would ask. Sorry but I’m not gonna reveal it, don’t want competition. I will say it’s been online for over a decade, information rich, with affiliate lead generation as the main source of income.
If it's the Milliondollarhomepage.com then it isn't quite living up to its legacy ;)
Re: Pieter Levels Makes $600k a Year from Nomad List and Remote OK
#96> sqLite - This is described as being unsuitable for > production by it's makers. I would doubt that is what the creators of SQlite intend one to take away from their documentation: "SQLite works great as the database engine for most low to medium traffic websites (which is to say, most websites). The amount of web traffic that SQLite can handle depends on how heavily the website uses its database. Generally speaking…
HN: "A single server with SQLite is perfect for typical production workloads, it's so robust" Also HN: "Database X can fail in Jepsen tests during partitions, it's unusable" I see HA as a mandatory part of what makes a system production ready...
It's likely the additional overhead worrying about HA is not worth it, not to mention the real possibility of HA just not working properly in actual failure scenarios
Re: Pieter Levels Makes $600k a Year from Nomad List and Remote OK
#97I don’t usually like to toot my own horn, but I make $600k/year off a plain HTML static site that isn’t even coded well, in-line CSS, many pages not responsive, broken links, etc.
I have a site like this as well and it makes about a paltry $40k on a good year. I mostly got lucky because I had some niche domain knowledge for a specific industry that was lacking a web product. I wasted money trying to grow it for some time but I've come to accept even at it's full potential it would probably only make maybe double of what it does now at max. I hope someday though i'll stumble across a $600k a ye…
Re: Pieter Levels Makes $600k a Year from Nomad List and Remote OK
#98> sqLite - This is described as being unsuitable for > production by it's makers. I would doubt that is what the creators of SQlite intend one to take away from their documentation: "SQLite works great as the database engine for most low to medium traffic websites (which is to say, most websites). The amount of web traffic that SQLite can handle depends on how heavily the website uses its database. Generally speaking…
HN: "A single server with SQLite is perfect for typical production workloads, it's so robust" Also HN: "Database X can fail in Jepsen tests during partitions, it's unusable" I see HA as a mandatory part of what makes a system production ready...
Most websites are not Google or Amazon, and gain very little from more 9's past the initial 2~3, which is totally manageable on a single server. Why spend thousands setting up and managing distributed servers if going from 99.0% to 99.999% gains you hundreds? If you need more nines and stronger guarantees than that, absolutely, use distributed solutions, nobody is telling you otherwise.
Jepsen tests are valuable once you have decided to use a distributed solution. They showcase problems that would be extremely hard to track down in production settings but can cause serious problems there. If encountered in practice these problems can cause data corruption or other very strange bugs that would take days if not weeks to track down.
I wouldn't say that a system with failures in Jepsen tests is unusable, every system has bugs, but if a system has these problems on purpose (e.g. to make it look better on benchmarks) and there is no movement to fix these problems then I would definitely steer clear of that system.
Re: Pieter Levels Makes $600k a Year from Nomad List and Remote OK
#99Earlier quoted context omitted.
HN: "A single server with SQLite is perfect for typical production workloads, it's so robust" Also HN: "Database X can fail in Jepsen tests during partitions, it's unusable" I see HA as a mandatory part of what makes a system production ready...
For many websites it's perfectly acceptable to go down for a few hours (or however long it takes you to notice, spin up a new vm/server and restore a backup) should stuff go wrong, which is fairly unlikely if you're just running a few servers. It's likely the additional overhead worrying about HA is not worth it, not to mention the real possibility of HA just not working properly in actual failure scenarios
It seems like his business could at least afford an HA setup on a cloud provider. Moving to any hosted db with backups, updates and redundancy could be worth it.
As for HA failing, it's still less likely than not-HA failing.
Also an HA setup allows for maintenance and upgrades without downtime, which is way better than the very common "we don't upgrade if it's working, because it could break".
Re: Pieter Levels Makes $600k a Year from Nomad List and Remote OK
#100i think this deserves a nitpick. when we say “makes” wrt a person, it means their gross salary/income. here, it refers to revenue. that’s misleading.