3 ms·

There's still a huge divide in terms of talent, the vast majority of programming jobs outside silicon valley seem to be working on legacy code that is terribly

There's still a huge divide in terms of talent, the vast majority of programming jobs outside silicon valley seem to be working on legacy code that is terribly architected (think Java apps written in a procedural style, etc) whereas top companies are making full use of more modern approaches and tools. It will be a very long time things even out and programming jobs are similar across the board.

rsynnott 9y ago
> legacy code that is terribly architected (think Java apps written in a procedural style, etc) If anything, the hallmark of legacy Java is excessive object orientation for the sake of it. FactoryFactoryFactories. By comparison, in these more enlightened times, a class method to construct an instance may occasionally be countenanced without the programmer being burnt at the stake.
jameskegel 9y ago
> the vast majority of programming jobs outside silicon valley seem to be working on legacy code that is terribly architected How can you say things like this? The internet is the great equalizer of distances; it does not matter what geographic location you live in, you could be working on anything. On a sidenote, I can't tell if you are trying to be deliberately offensive or if you're someone who's never left SV.
- tormeh 9y ago
  >How can you say things like this? The internet is the great equalizer of distances; it does not matter what geographic location you live in, you could be working on anything. It really is not. Culture matters. If you're from a conservative place, your boss and colleagues are likely to be conservative. It'll be JEE for you until the end of time.
Clubber 9y ago
Generally I don't necessarily think top companies are the ones using the newer stacks, with the exclusion of a few technology companies, but it's more so the newer companies that are. Once a company builds a system, they don't want to spend to build it again. They'll bandaid the hell out of it. As long as it's doing what it's supposed to do. They're like farmers with these old beat to hell tractors. They're ugly and bitchy but they work, why spend $100K on a new one?

rsynnott 9y ago

> legacy code that is terribly architected (think Java apps written in a procedural style, etc) If anything, the hallmark of legacy Java is excessive object orientation for the sake of it. FactoryFactoryFactories. By comparison, in these more enlightened times, a class method to construct an instance may occasionally be countenanced without the programmer being burnt at the stake.

jameskegel 9y ago

> the vast majority of programming jobs outside silicon valley seem to be working on legacy code that is terribly architected How can you say things like this? The internet is the great equalizer of distances; it does not matter what geographic location you live in, you could be working on anything. On a sidenote, I can't tell if you are trying to be deliberately offensive or if you're someone who's never left SV.

tormeh 9y ago
>How can you say things like this? The internet is the great equalizer of distances; it does not matter what geographic location you live in, you could be working on anything. It really is not. Culture matters. If you're from a conservative place, your boss and colleagues are likely to be conservative. It'll be JEE for you until the end of time.

Clubber 9y ago

Generally I don't necessarily think top companies are the ones using the newer stacks, with the exclusion of a few technology companies, but it's more so the newer companies that are. Once a company builds a system, they don't want to spend to build it again. They'll bandaid the hell out of it. As long as it's doing what it's supposed to do. They're like farmers with these old beat to hell tractors. They're ugly and bitchy but they work, why spend $100K on a new one?