104 karma · joined August 28, 2013
Guess I need to go read how that's implemented now.
If you're using if/else all over the place instead of a branch, what's to stop you from forgetting to remove one when you decide your new work is 'production ready'?
At the easiest level, I'd suggest using branches for new development. Bug fixes, new features, etc. Keep the work small; branches are cheap. Once its reviewed or tested merge it back into the master branch. This way 'in development' and 'complete' are abstracted to a level above code.
Also, imagine your project has 30 developers, or more. Would the strategy of if/else everywhere still work well?
[0]: http://www.iafrikan.com/2014/07/07/beware-the-local-maxima-p...
But what does that mean? Are you looking for actual work towards your company's product? And what does THAT mean? Time spent coding a feature? Research? Professional development? Or are you looking for just time spent at work?
Revised, I spend probably 25 hours at work. Maybe 70% is added value to the company. Maybe half of that is actual coding.
How are you determining your 'I don't achieve much per week'?