3 ms·
> Instead, I've found that real-world tasks that require me to do something new are where I most improve, and most enjoy improving, my programming skills. I li
by ChrisMarshallNY 5y ago
> Instead, I've found that real-world tasks that require me to do something new are where I most improve, and most enjoy improving, my programming skills.
I liked this, but then they went on about automating their workflow (which is a great application of skills. They are correct).
It's just that I don't have a workflow that really benefits from automation. Whenever I introduce scripting and automation, I usually end up with concrete galoshes[0], and nothing is really gained. My automation is generally a run of SwiftLint, before compiling. I also automate Jazzy doc building. Other than that, I tend to be pretty manual, even for large projects, with repeated releases.
What I do, is ship often, and write Swift every day. I've been writing Swift every day for the last few years. I probably passed the "10,000 hours" mark, at least a couple of years ago. My GH ID Activity Graph[1] is solid green, and it's not "gamed," like so many people do with theirs.
I just write a lot of code; every single day.
I also like to ship stuff. That means actually doing what is necessary to move it out into the world. Push it out of the nest, so to speak. Lots of "boring" stuff, involved with that.
But I have found, that if you do it all the time, it basically becomes "muscle memory." When folks look at the code I write, they assume that I'm a slow, plodding programmer, because of all the structure and code docs.
Nothing could be farther from the truth. I write a lot of really high-Quality code; very quickly.
It's just habit.
[0] https://littlegreenviper.com/miscellany/concrete-galoshes/ https://littlegreenviper.com/miscellany/concrete-galoshes/
[1] https://github.com/ChrisMarshallNY#github-stuff https://github.com/ChrisMarshallNY#github-stuff