If it allows to kick out code faster to meet whatever specs/acceptance criteria laid out before me, fine. The hell do I care if the code is good or bad. If it works, it works. My company doesn’t give af about me. I’m just a number. No matter how many “we are family” speeches they give. Or try to push the “we are all a team and will win”….we aren’t all a team. Why should I care more than “does it work”. As long as profits go up, the company is happy. They don’t care how good or pretty my code is.
Tell me again how you’ve never become the subject matter expert on something simply because you were around when it was built.
Or had to overhaul a project due to a “post-live” requirements change a year later.
I write “good enough” code for me, so I don’t want to take a can opener to my head when I inevitably get asked to change things later.
It also lets me be lazier, as 9 times out of 10 I can get most of my code from a previous project and I already know it front to back. I get to fuck about and still get complex stuff out fast enough to argue for a raise.
Been the sme and completely architected and implemented the entire middleware server farm for my last company. First in ibm after taking it over from someone else that started it, just a here you go takeover. Then moving from an ibm shop to oracle, cause the vp wanted a gold star and wouldn’t listen to anyone. I left when they were moving to red hat when the next vp came in and wanted their gold star. Little over 400 servers. Been there done that.
If it allows to kick out code faster to meet whatever specs/acceptance criteria laid out before me, fine. The hell do I care if the code is good or bad. If it works, it works. My company doesn’t give af about me. I’m just a number. No matter how many “we are family” speeches they give. Or try to push the “we are all a team and will win”….we aren’t all a team. Why should I care more than “does it work”. As long as profits go up, the company is happy. They don’t care how good or pretty my code is.
Tell me again how you’ve never become the subject matter expert on something simply because you were around when it was built.
Or had to overhaul a project due to a “post-live” requirements change a year later.
I write “good enough” code for me, so I don’t want to take a can opener to my head when I inevitably get asked to change things later.
It also lets me be lazier, as 9 times out of 10 I can get most of my code from a previous project and I already know it front to back. I get to fuck about and still get complex stuff out fast enough to argue for a raise.
Been the sme and completely architected and implemented the entire middleware server farm for my last company. First in ibm after taking it over from someone else that started it, just a here you go takeover. Then moving from an ibm shop to oracle, cause the vp wanted a gold star and wouldn’t listen to anyone. I left when they were moving to red hat when the next vp came in and wanted their gold star. Little over 400 servers. Been there done that.