Wholeheartedly agree. However don't forget those who worked hard but were just got stuck doing something that was ONLY relevant in that organization. Once laid off, they belatedly find out their 'skill' isn't a skill outside of the organization.
Hence I believe you should be extra vigilant about stagnating skill set when working at a company for more than just a few years. A lesson I'm learning now.
http://www.kalzumeus.com/2009/09/05/desktop-aps-versus-web-a...
Also, ever look into trying out micro ISV? You may not get rich but doing doing something like it will help you work on techs that are popular/relevant, not what your managers wants done. Or try working on side projects with free time?
I have some experience in this and some autonomy is vital. If you negotiate something approximating a consultative relationship with your boss, then you're pretty safe.
http://en.wikipedia.org/wiki/Forte_4GL
I wish I was kidding about the FORTE4GL bit, but I do acknowledge the need to stay current, though it's sometimes hard to get the drive to do so.
I realized the same, however I understand and appreciate that others do not share this same view.
The question becomes "What would you do if you were financially independent?" For me, it still would be to create, build, explore, learn, and tinker - basically what I do at, and outside of, work.
In a moment of stupidity I lost the email server that was serving the wildcard email address, so now, I have bouncing email addresses all over the web.
You didn't need to include 'pathetic, depressed and unemployed' in that sentence.
I was able to deploy updates via a similar mechanism. There was a network script called from autoexec.bat. I would make a few changes to have it pull in the new updates from the network, then tell them to reboot at their convenience. So I almost never had to leave my desk to deal with them, except for a restore from backup.
Edit: browsed the DJGPP website and found answers, there are libs available.
In DOS times you only had one core, so there was no particular necessity for multithreading. Network card drivers were available using the NDIS standard: http://www.freedos.org/wiki/index.php/Networking_FreeDOS_-_N...
DOS games tended to roll their own protocol on top of the raw packet drivers. This is why they were often LAN-only. Generally in the DOS era you didn't have Internet; it existed, but wasn't widely deployed.
DJGPP got some use (see the PCGPE as well), but professional game development tended to use Watcom: http://www.openwatcom.org/index.php/Project_History
So you'd download the day's schedule or updates by copying the file off the network and use a few primitive means of coordinating things like using 'flag' files for signaling and then if exists xxx / echo foo > do_bckup.txt type things in your batch files.
It's very primitive, but most things were at least doable and you could always write small programs to extend your scripts if need be.
Back then I was doing on-site tech support for a market-data software company serving the major investment banks of the time (a major partner and competitor to Knight Ridder, DTN, and Reuters for those who might have any idea). My days we very full, supporting DOS-based servers and workstations; In the evenings I spent my hours working on an intranet, which, as I understand, still remains in what's left of the expired once-incredibly-successful company.
Soon after, I was laid off as the company downsized to almost nothing. As I took on a couple jobs from former customer contacts, I found it far too easy to waste time on the clock. I hated it. I hated the water cooler. I hated the extended lunches. Getting paid relatively well for little output was nice in a way, as I had plenty of friends my own age back home who would kill for such a position and wage. But it wasn't for me. I didn't care as much about wasting company resources (though I did care), but I felt it was a complete waste of my own time.
Within a year of being laid off, I went full-time freelance, and within three years I was able to pick my clients. Most of the time, my contacts at my clients' companies were as incredibly intelligent as they were underutilized. At odd hours, we'd get into the nitty gritty of what was really needed for the client to succeed and I was able to propose interesting solutions, not only to offer what was asked, but what would take them further. And my attempts to give credit to said employees usually (not always) seemed to fall upon deaf ears.
As a freelance developer, I was able to continue to pick clients, work on interesting things, meet incredibly interesting people, get the job done, all from my own desk on my own time, and when it was done - move on. Meanwhile, I saw friends and contacts fall into stagnation as they remained underutilized. Some happy, with the stability to support their families and lifestyles. Many, less so.
I'm obviously very lucky as a programmer - someone who can jump into almost any industry, learn as much as possible about their needs, remain busy for as long as the project exists, and then move on. I think that's what drives my interest in software more than anything. Provided I can ask the right questions to the right people, there is never a shortage of interesting things to figure out for a good wage. I don't pity those who don't currently have such an option, as that would undermine the respect I have for them.
But I do firmly believe the closer we get to enabling such a world for those of us who are not so well versed in translating business requirements to tech solutions would be a societal benefit. I certainly don't think everyone should be a business entity unto themselves. But the flattening of the company structure - beyond the walls of the institutions that hold said structures dear - has a good deal of potential for the creative possibilities of the most competent workers therein.