process is not a factor

It’s just a basic engineering problem. When you have more than one person working on the team they will end up making changes in the same file, use the same function, or in another object using another object in a critical way. And things are going break unless they are disciplined in their approach. I think this is a problem that basically generally people haven’t got a clue how to share code. That’s what we had there. A usual thing was that someone would stand up and go, “Okay, who’s changed such and such?” with, you know, “You Muppet” going unsaid.

I joined a local software house and I was there for five years. For three of those years I was stuck in the basement doing VB (and I didn’t like VB). I wasn’t getting too well with one of my leaders, with looking for feedback and not getting it basically, with the usual result. The environment was very bad for my health, my eyesight, my optician recommended I get out of there. So I taught myself Java, because I realised it was quite heavily in demand in the industry and the software house had hardly any Java coders. And then I told some people that I’d learnt Java. Apparently there were abou