Mikko Puonti wrote: My practical experience is that it is perfectly fine to work with 2-3 programmers without any coding conventions, reviews or other good practices. You can produce "good enough" code fast enough (=economically). There must be something wrong with the way I code. I’m huge on standards, when I find a better method; I do a code freeze and modify the entire app to fit into that standard (I know what your thinking and yes this has caused problems, but if it ends up improving the code then oh well). It’s the only advantage of being a one man show. Mikko Puonti wrote: If important lead programmer leaves company - your software development is stopped for next 6 month (good salary negotation tactic ). Not where I work, they know I'm leaving. No one has shown any interest in learning how to administrate my application. Their loss… Besides the app is mine, I wrote it at home on my time with my IDEs. hehe Mikko Puonti wrote: Eventually when there was something like 100+ DLLs in system you really needed to start thinking practical consequences from your development strategy. When you started to integrate components together, you needed to look inside components Sounds like a potential for HUGE code bloat. As the soul developer where I am its easy to keep things together. It’s just a real pain when I run into a design question as there is no one to bounce ideas off of. Mikko Puonti wrote: I think that I could shepherd maybe 5-6 average programmers without official, forced and standardised pratices. What ever happened to self discipline? I’m mean is it that rare now a days that people just try their hardest to produce the highest quality product they can? Nobodies’ perfect but forced? Standards yes! ------------------------------- DEBUGGING : Removing the needles from the haystack.
