Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
metamourge849758dIf you'd cut away the first tile, the title could be "When your work-machine uses Gnome instead of i3".
Memorable2558ddon't forget to ask dumb questions on stack overflow coz someone always cares enough to answer
Starting is the easy part. Following through on the other hand...
I think for most people, the difficult part is being creative enough to find projects to work on.
The best way to learn programming in my opinion is being annoyed that a favorite browser extension doesn't work anymore, and searching "how to create a browser extension". Or Minecraft addon. Or a script to process excel sheets. Or feed your fish with an Arduino.
The language or application are irrelevant, but to stay motivated you have to work on something that's tangible and meaningful to you. Don't code along with a tutorial from start to end, just steal bits and pieces to serve your goals.
Finishing projects isn't even important. You just have to dive in far enough that you gain some persistent knowledge out of it, with every failed toy and shelved alpha you clear up a few mysteries.
ltlian126158dIs there a term for how you avoid learning a new skill because you lack said skill? If there is then I have or am it. Or at least was.
One of the biggest mistakes in my career was how long I spent thinking I didn't know how to program so I couldn't learn it. It looks ridiculous when it's spelled out, but I'm sure it's a common fallacy.