3 ms·

Respect! That's truly inspirational. At barely half the experience with 30 years I keep wondering about what next. I still do plenty of programming in C (which,

Respect! That's truly inspirational. At barely half the experience with 30 years I keep wondering about what next. I still do plenty of programming in C (which, along with Z80 and 8086 assembly, is what I started with), Python and JS with some dabbling in Go. I find the problem solving part as invigorating and exhilarating as ever. What I do struggle with is the 100x additional lines of code which will be needed to make that initial code usable by others. That is needed and all that, but is stuff I would have done dozens of times in the past in different contexts and sometimes approaches drudgery. I wonder if you have any advice on how to keep the interest from flagging in a project past that initial days/weeks of deep absorption. Thanks again for sharing this.

visarga 6y ago
> I wonder if you have any advice on how to keep the interest from flagging in a project past that initial days/weeks of deep absorption. I, too, have been programming for 32 years. I have thought about your question many times. My current solution is to 'play more'. Allow yourself to play, even when you are in the 100x additional part. Playing makes your passion flare up again. By play I mean to start interesting side projects, ideas, try something new.
elbear 6y ago
Maybe aim to see things in a different perspective. You making that code usable by others means others will benefit from your work. So 1) you benefit from the work by having fun 2) others benefit from your work by using it to solve their problems or building things they find fun Usability is also a problem worth solving. It's just a different problem.