14 ms·

Heh, you've basically avoided fully answering this question twice, possibly because it wasn't properly phrased. Let me give it one more shot. What was _your_ r

by ZoF 13y ago

Heh, you've basically avoided fully answering this question twice, possibly because it wasn't properly phrased. Let me give it one more shot. What was _your_ reasoning for losing a job over a completely semantic argument? Did the illogicality of it all really irk you so much that you couldn't stand to change it? What do you mean by saying that you couldn't 'comprehend' why variables should be written in UK English? It seems pretty clear that they should be in UK English because that's what you were told to write them in... at your job... If this happened as described then I would have loved to be a coworker watching this hilariously petty feud unfold.

buro9 13y ago
> What was _your_ reasoning for losing a job over a completely semantic argument? I wanted a reasonable work environment that was delivering product to the customers, for the business. The work in question was 20k lines and involved the whole stack. As it bled into web page stuff that actually had calls to browser open "dialog" commands, no find and replace was going to safely work to now make it comply with the clarification on the coding standards (UK English var names). We would spend weeks changing it and re-testing, weeks in which we were not delivering it. I felt we were no longer working for either the customer or business, when we were willing to hold back an improvement that would immediately create revenue, for a petty argument. It wasn't the first time I'd seen this architect do that to others, but I never thought it would happen to me so long as the product was good, the code was good, deadlines were met. I was no longer convinced it was possible to create work that wouldn't fall foul of some rule or other. And the architect had managed to position himself on the org structure outside of a chain of command, so there was no-one to appeal to. There are too many good jobs, and good companies, that want to ship product to their customers and build a great business to even consider staying somewhere that doesn't. It was a very easy decision.
- ZoF 13y ago
  Wow, yeah, seems like it was. I still would like to see someone that ridiculous operate... Sounds like the most incompetent architect/engineer I have ever heard of. Sorry for the snark fellow human.

by ZoF 13y ago

buro9 13y ago

> What was _your_ reasoning for losing a job over a completely semantic argument? I wanted a reasonable work environment that was delivering product to the customers, for the business. The work in question was 20k lines and involved the whole stack. As it bled into web page stuff that actually had calls to browser open "dialog" commands, no find and replace was going to safely work to now make it comply with the clarification on the coding standards (UK English var names). We would spend weeks changing it and re-testing, weeks in which we were not delivering it. I felt we were no longer working for either the customer or business, when we were willing to hold back an improvement that would immediately create revenue, for a petty argument. It wasn't the first time I'd seen this architect do that to others, but I never thought it would happen to me so long as the product was good, the code was good, deadlines were met. I was no longer convinced it was possible to create work that wouldn't fall foul of some rule or other. And the architect had managed to position himself on the org structure outside of a chain of command, so there was no-one to appeal to. There are too many good jobs, and good companies, that want to ship product to their customers and build a great business to even consider staying somewhere that doesn't. It was a very easy decision.

ZoF 13y ago
Wow, yeah, seems like it was. I still would like to see someone that ridiculous operate... Sounds like the most incompetent architect/engineer I have ever heard of. Sorry for the snark fellow human.