Do things that don't scale, and then don't scale
derwiki.medium.com
Do things that don't scale, and then don't scale
1–10 of 216 posts
Re: Do things that don't scale, and then don't scale
#2Interesting perspective about writing a bunch of mini-apps that you aren't concerned with making money on or scaling.
Reminds me a bit of the carpenters I've seen work who spend time building frames/other wood "tools" to help them get the actual work done faster.
The cost of writing software has definitely decreased. And you do have a different and smaller class of problems when you write an ad-hoc app.
Re: Do things that don't scale, and then don't scale
#3Building things for yourself is fun -- I do it. But the original article was written for startup founders, building companies.
Re: Do things that don't scale, and then don't scale
#4I feel like the main takeaway here is that if you want your personal project to last, you should run it on your own server.
Re: Do things that don't scale, and then don't scale
#5Building things for yourself is fun -- I do it. But the original article was written for startup founders, building companies.
Yep, totally — the OG advice was founder-focused. I just couldn’t resist twisting it a bit, because the line itself is too good not to repurpose.
Re: Do things that don't scale, and then don't scale
#6[deleted]
Re: Do things that don't scale, and then don't scale
#7> Then came the weirdness: bursts of Tor traffic, spammy signups
I have a small hobby site - maybe a few hundred real users ever, and a handful of regulars. But the logs and users table are full of brute force and lousy sql injection attempts.
Why does this happen? How is it economical?
Re: Do things that don't scale, and then don't scale
#8> Then came the weirdness: bursts of Tor traffic, spammy signups I have a small hobby site - maybe a few hundred real users ever, and a handful of regulars. But the logs and users table are full of brute force and lousy sql injection attempts. Why does this happen? How is it economical?
They are automated bots, it's economical when it's automated.
Often, they have databases of technologies, see what they come across and try a bunch of things that have worked, or try to look at the version of the software on your server and try just that.
Re: Do things that don't scale, and then don't scale
#9Building things for yourself is fun -- I do it. But the original article was written for startup founders, building companies.
It's also possible to build things to solve your own problems, that might be problems other people have too, which they also try to solve but fail at, which are problems that are painful enough that they would spend on.
They're harder to find in B2C than B2B. Individual problems can sometimes map to B2B.
Re: Do things that don't scale, and then don't scale
#10Interesting perspective about writing a bunch of mini-apps that you aren't concerned with making money on or scaling. Reminds me a bit of the carpenters I've seen work who spend time building frames/other wood "tools" to help them get the actual work done faster. The cost of writing software has definitely decreased. And you do have a different and smaller class of problems when you write an ad-hoc app.
Making tools to make the tools is the real devops.
CI/CD can be as complex and full of pagentry as some people want and it's great when it fits, and premature optimization the rest of the time.