Hmmm... I'm not sure how to rate my programming skills - they're certainly there, and I can do a few clever-clever "word games" when needed (YVFC), and I did write NW. Except I never finished that. And the code for my PhD - not huge, about 3k lines of Python, but there the main thing was working out what to make it do. And my current source trees are starting to get quite large - there's about 10k lines of Java in my IDE workspace (OTOH, Java is *verbose*). I guess that what I've got going for me is neither the deep-compsci knowledge nor systems-engineering know-how, but a minor knack for (extremely informal) analysis - well, OK, bringing in some of my domain knowledge - and invention.
In terms of approach: I'm an incremental, get it to work and then keep hacking on it type, but I can do some big-block-coding when needs be. I tend to refactor quite a bit - I can notice when my code's getting shabby and re-design it to be smaller/more elegant/more readable/extensible in the right way. I was never particularly methodical or perfectionistic. I guess this is what lets me get to a certain size of my C code base, and then get horribly bogged down and demotivated. Ho hum.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
In terms of approach: I'm an incremental, get it to work and then keep hacking on it type, but I can do some big-block-coding when needs be. I tend to refactor quite a bit - I can notice when my code's getting shabby and re-design it to be smaller/more elegant/more readable/extensible in the right way. I was never particularly methodical or perfectionistic. I guess this is what lets me get to a certain size of my C code base, and then get horribly bogged down and demotivated. Ho hum.