90 karma · joined July 9, 2010
The burden of proof, in my mind, is the one making the claim.
I've always thought that governance and legislation had a lot of parallels with code. It truly is not the size of the codebase that is the problem, it's the complexity underlying it. We can understand a program if everything is laid out common-sensically.
Maybe it wouldn't be a stretch to say that it goes the same for government.
I can't stand reading all these whiny diatribes. Ask all your fellow non-STEM friends and you'll see how much they'd rather be in your position.
You should emulate Bill Gates instead of Steve Jobs...
You should emulate Wozniak instead of Jobs...
Who cares?? I would be proud to emulate any of these great men.
I teach chess to this 12 year old Chinese boy. He clearly has zero interest in progressing his game. And yet, his mother is there, always pushing him senselessly into a vocation he will be, at best, mediocre. Their time (and money) would be better spent on finding something that the kid really enjoys.
1. It's not about the language, it's about the work environment. C#/.NET is just a tool, like Ruby, Scala, Clojure, etc. It's not the cause of your misery.
Your work environment sounds like what's causing your misery. Get out of there, find a startup, find a problem that you'd love solving. Even though you use .NET in that new project, your life will be 10x better. In the end, it's not the technology that is causing you strife, it's the environment you're using it in.
2. Work for yourself. You say you get a lot of interest from people you've worked with before. Why don't you start your own consulting business... do business your way.