News for hackers. Stuff that matters.
Re:Why you should, and shouldn’t, join a startup by mkozlows on Tuesday August 14, 2018 @05:00PM (#17761847)
There are a lot of things that you simply can't learn by yourself, though. The practicalities of doing things on a team, at scale, are just out of scope for personal side projects.
Re:Why you should, and shouldn’t, join a startup by meesles on Tuesday August 14, 2018 @05:12PM (#17761938)
Agreed. The more I grow, the more I realize it is unrealistic to develop skills in scaling architecture, massive-scale software, etc. with only your own projects.

You either need to contribute to large projects, find large projects to hire you, or push for scaling patterns which may be out-of-scope for your current job.

This is actually something I've been thinking about lately: how can I train/practice these meaningful skills without the risk of damaging a reputation or losing sensitive data in real systems?

Re:Why you should, and shouldn’t, join a startup by strikelaserclaw on Tuesday August 14, 2018 @05:20PM (#17762015)
This is a real problem in trying to learn how to scale systems. I love learning about scaling but I've never personally worked on high volume applications, there's only so much you can do by reading stuff or watching tutorials or emulating high volume in your side projects. There's so many x-factors that come into play that you can only learn on the job.
Re:Why you should, and shouldn’t, join a startup by wolco on Tuesday August 14, 2018 @08:45PM (#17763086)
Using services like loader.io I could simulate high traffic. That opened up a new world. I was able to test different configurations under stress to find the setup that performed the best for a specific application. Highly recommend stress or load testing.