An anonymous reader writes: After college I was hired as a Junior .NET Developer (C#) for company X. Five years later I am still at company X, now called a Senior Level and given $120k a year, with a $10k bonus and guaranteed $10k raise come January. The problem begins in that company X doesn't sell software, it sells product — it's an e-commerce company that does not outsource and has it's own small development team. It's not a coding house, and large projects are worked on through ticket systems as if it was simple tech support. Bad habits and poor practices have molded me into a 'right now' developer and not a 'right way' developer, being reactive and solving problems as they come.
After applying for a Senior level position at company Y — which is a coding house that is extremely organized and object/design-oriented — the interview did not go as well as hoped, even with my excellent troubleshooting and problem-solving skills. I got the impression this was due to a lacking in my OOP skill set, which I attribute to not being given proper direction by my superiors, the time to spend iterating design, and my ignorance in the way I was growing as a developer was not how I should. Instead of a potential matching salary, they said they would have to bring me in at $90k, possibly $100k if I aced an interview lab.
Company Y would be able to reign in my cowboy coding skills and help me get on the path of the Jedi.
The question posed to Slashdot readers: Is the gigantic pay cut worth it? Should I remain at X — which is becoming an unbearable work environment — for the pay and spend the rest of my waking hours unlearning what I'd still have to use daily and study/practice every facet of C# and OO principles?