3 ms·
I think you’ll find with any skill you learn, early growth comes quickly, and then takes much more time/effort for smaller gains. To feel like you’re taking bi
by al_borland 3y ago
I think you’ll find with any skill you learn, early growth comes quickly, and then takes much more time/effort for smaller gains.
To feel like you’re taking big leaps each day after reaching a level of maturity you’d likely need to be learning new things, which you’d likely pick up quickly and feel like you’re making a lot of progress, but you’d be sacrificing depth for breadth, if you’re way of finding new things is picking up a new language each week or making the same type of projects which don’t introduce new concepts.
At some point you just need to start making things. Let people use those things and get feedback, they’ll let you know what your blind spots are. Even something as simple and thinking about designing for an end user instead of just yourself will make you think a lot differently about your program. The first thing I really did on my own was a collection of scripts to help me at work. They helped me, but couldn’t really help anyone else. Eventually I started thinking about others and it got a lot better. I made a GUI front end so people could consume it easier, made settings so it could be customized, figured out how to compile it to distribute it to them without dependencies, started actually handling errors, testing edge cases, and fixing little bugs that I would simply avoid running into when it was just me. The whole thing became much more robust. That project, and a couple others, led me out of the sys admin space and over to being a software engineer.
If know one can use, or wants to use, what you’re writing… what’s the point? Thinking about building for people really helped me out when I was getting started.