4 ms·
I don't think it should be any different for coding. I probably wasn't too clear in my question. I spend a lot of time designing and putting together systems, b
by nekopa 14y ago
I don't think it should be any different for coding. I probably wasn't too clear in my question. I spend a lot of time designing and putting together systems, but I just don't write code any more. As in actually opening up an editor and just plain writing code. Like a writer, shouldn't I be able to code whatever pops into my head too? For example, sit down and write a small program that will maybe take a bunch of employee schedules (in xml) and find openings and or conflicts in the schedules.
- Benferhat 14y agoIt just doesn't work that way.. I've spent entire days trying to get a feature to work perfectly, often winding up with fewer lines of code than I started with. Were I to judge such progress by lines of code, an achievement would be transformed into a failure. That's why I suggest going by TODO-list entries. Those are concrete things that you know need to get done. You can even score them in terms of anticipated difficulty, then try to reach a certain number of points per day/week. Think of yourself more as an editor than an author. An editor might spend a lot of time re-factoring, looking up syntax, trying to make things flow better, asking people for advice, etc. Amassing words and lines isn't your goal.