hmmm.
The question is about the process though, not the tool chain. If the only problem I had at work was wrestling with the tool chain, then I'd actually rate both about the same, since each environment still involves a bit of fiddling to get things running smoothly (except for MS VSS, which I just want to replace entirely...).
The problems at work which I face are more along the lines of rickcarson's observations (except that the anally retentive code "quality" is "enforced" here by peer review only, not a code lint...). We have much more basic problems, such as, insistence on a waterfall approach to everything, no test-driven programming (and no budget or interest in building a unit/regression test suite), no control of requirements and no structure in determining them. To some degree our customer even designs and dictates the solution (?! disaster !).
At home, I can control the development process, adopt rigorous test cases and do peer programming via IRC and email. I can use the (radical?) idea of use-cases and some UML documentation instead of trying to retro-fit 1970s "structured analysis/design" methods and documentation to an OO project... This is basic stuff that has little to do with the tool chain, and more to do with being in a huge, inflexible, beaurocratic monolithic dinosaur company. |
java.net RSS Feeds
