3 ms·
"Seek out information greedily" That's the biggest problem for me. I spend so much time *reading* about tech stuff/programming but it rarely sticks until I for
by cassepipe 4y ago
"Seek out information greedily"
That's the biggest problem for me. I spend so much time *reading* about tech
stuff/programming but it rarely sticks until I force myself to write code/work
on project, that's when the knowledge *incorporates*, else I am just a erudite
bag of wind. It really helps to know what you are doing, but it's useless if you
are doing nothing, or scrolling through HN comments :)
- pksebben 4y agothat same problem has gently corralled me into mostly working on projects that are useful to me. Some lisp to make my editor do better things here, a mnemonic keychord database there. It can really help to motivate when you have a deep and intuitive understanding about why you're building x y or z thing. The most recent thing I'm hacking on is a gui to sort through and rank stable diffusion outputs. it's not technically complex or advanced but it'll solve a problem I have so I keep coming back to it.
- cassepipe 4y agoI am all for "a deep and intuitive understanding" of whatever I do" but it tends to be a bit extreme to the point where I don't do anything because I feel it won't perfect the first time, and it never is.
- pksebben 4y agowell, it won't be. Matter of fact, I haven't made a perfect thing yet! Loads upon loads of failures, though. I get prouder of them every time. The way I try to look at it is that it's all practice. Every scrap of code I write is a prototype of a better version.