4 ms·
I haven't worked at the same place, but in the same industry since 2001, doing almost exactly the same work for each place I've been. Having so much domain know
by kgwxd 8y ago
I haven't worked at the same place, but in the same industry since 2001, doing almost exactly the same work for each place I've been. Having so much domain knowledge is extremely useful. I'm not a great developer but it sets me apart, very far apart in my opinion.
The part that sucks is that very few people recognize it and the ones that do are rarely the ones that get to make the calls. The ones that do make the calls think any developer can do what I do. What I've seen happen several times, is the company decides to replace me with outsourced/cheaper development, and after an attempt to reason with them, I stay for a bit to help them move in that direction and then move on to another place. Invariably, they call a year or 2 later looking for help, not because I've planted some obscure code no one can understand but me, but because no other developers have the knowledge to form the necessary follow-up questions to the ever-changing specs handed down from the higher-ups before moving forward. They end up with systems full of incorrect assumptions that fail daily and tie up all the developer time being fixed. Now I can't help them because I'm working for a competitor. It's infuriating. Every company I've ever worked for I've wanted to make the best in the industry, but they've consistently been blinded by short-term goals, driven by unfounded hype to be "progressive", when all they needed to do was a few basic things better than the competition to take the majority of the market. Even when I get far enough to produce numbers to prove that point, they still want to do some wild shit no one is asking for, or they get bought out (because they start growing rapidly) by a venture capitalist company that just wants to do a quick flip.
- cced 8y agoWhy is it that an employer can let a developper go only to need to call them later and ask questions? Do you think this a documentation issue?
- kgwxd 8y agoThe questions aren't usually about things I left behind, though that does come up and documentation could help that. They're usually looking for someone to build out a new integration with a big customer that has to be done right the first time, quickly, or risk loosing the customer to a competitor. Outsorced dev teams with high turnover and little domain knowledge just can't pull that off, a fact many places learn too late.