I really must disagree. The age profile in IT is changing, we have to expect to be working a lot longer than our parents did, and inevitably this means more career opportunity for those who choose to stay in the industry
As to my own experience, I made the leap (for the second time - the first time was a mistake) in my late 30s and never looked back. And being (say) a development manager can be a very rewarding job: teams of any size do take some organising (do it right and they'll even thank you for it!), people need support in their career development, and it takes someone who cares about technology to make the decisions to invest in things like testing, to sell the big refactorings and so on.
To put my age in context, I had always been a developer, but by then I was in my third industry (aerospace, tools, finance). Now at 44 I'm leaving behind a big budget team in a big enterprise to become an IT Director in a small but growing company. Smaller budget but bigger scope, and the chance for the first time to have peers and a manager that aren't in IT, which makes for a very different challenge indeed. To someone who is always learning, dispensability is something to pursue!
He may also have been referring to the practice of "tunelling through POST" requests that would be much more appropriately done as GET (SOAP for example makes this too easy), thereby negating caches and the like.
I have done the opposite, moving addressing parameters from payloads to URLs. If your payload is (for example) XML, this is much more space efficient and you get informative URLs as a nice byproduct.
Some banks require you activate your card by phone, giving some further security details. It's not proof against identity theft but the potential thief would need access to more than just your mail.
Even in Jolly Old England the government has "crown immunity" from prosecution in certain areas. Even where those protections don't apply, they can try to hide behind a public interest argument.
In many contexts - mine being a large trading system for which I'm dev manager - scope screep isn't even a problem to be mitigated. Our job is to please our clients by delivering maximum business value, and it's inefficient (and even unreasonable) to demand perfect requirements before any work gets done. Change management for me is simply about having the tools to know exactly what I'm releasing and the confidence that changes have been tested adequately, not about constantly pushing back on change.
I planned to buy one after seeing a colleague's. Then my main (power-hungry, noisy and Windows-based) HP Pavilion laptop had a disk crash and I decided it was time for a Macbook. My ex-programmer-but now-nurse wife fell in love with the Asus (the 4GB Linux version for £219) and we came home with both. We're both delighted, don't feel stiffed at all, and it's likely that neither will ever go back to Windows, at home at least not for home use. I've learned also to appreciate form factor and usability over raw speed (not that the Mac is lacking in that department).
Now if someone call tell us how best to do cross-platform video chat with both machines and our Windows-based friends we'd be over the moon!
Slashdot Mirror
I really must disagree. The age profile in IT is changing, we have to expect to be working a lot longer than our parents did, and inevitably this means more career opportunity for those who choose to stay in the industry
As to my own experience, I made the leap (for the second time - the first time was a mistake) in my late 30s and never looked back. And being (say) a development manager can be a very rewarding job: teams of any size do take some organising (do it right and they'll even thank you for it!), people need support in their career development, and it takes someone who cares about technology to make the decisions to invest in things like testing, to sell the big refactorings and so on.
To put my age in context, I had always been a developer, but by then I was in my third industry (aerospace, tools, finance). Now at 44 I'm leaving behind a big budget team in a big enterprise to become an IT Director in a small but growing company. Smaller budget but bigger scope, and the chance for the first time to have peers and a manager that aren't in IT, which makes for a very different challenge indeed. To someone who is always learning, dispensability is something to pursue!
He may also have been referring to the practice of "tunelling through POST" requests that would be much more appropriately done as GET (SOAP for example makes this too easy), thereby negating caches and the like. I have done the opposite, moving addressing parameters from payloads to URLs. If your payload is (for example) XML, this is much more space efficient and you get informative URLs as a nice byproduct.
DEFINATELY: mis-spelling of "definitely"; usually means "maybe"
Some banks require you activate your card by phone, giving some further security details. It's not proof against identity theft but the potential thief would need access to more than just your mail.
Even in Jolly Old England the government has "crown immunity" from prosecution in certain areas. Even where those protections don't apply, they can try to hide behind a public interest argument.
In many contexts - mine being a large trading system for which I'm dev manager - scope screep isn't even a problem to be mitigated. Our job is to please our clients by delivering maximum business value, and it's inefficient (and even unreasonable) to demand perfect requirements before any work gets done. Change management for me is simply about having the tools to know exactly what I'm releasing and the confidence that changes have been tested adequately, not about constantly pushing back on change.
I planned to buy one after seeing a colleague's. Then my main (power-hungry, noisy and Windows-based) HP Pavilion laptop had a disk crash and I decided it was time for a Macbook. My ex-programmer-but now-nurse wife fell in love with the Asus (the 4GB Linux version for £219) and we came home with both. We're both delighted, don't feel stiffed at all, and it's likely that neither will ever go back to Windows, at home at least not for home use. I've learned also to appreciate form factor and usability over raw speed (not that the Mac is lacking in that department). Now if someone call tell us how best to do cross-platform video chat with both machines and our Windows-based friends we'd be over the moon!