10 ms·
This article very clearly describes the anxiety I felt as I melded into the workforce a few lifetimes ago. Not to say that I could have possibly articulated wh
by enobrev 12y ago
This article very clearly describes the anxiety I felt as I melded into the workforce a few lifetimes ago. Not to say that I could have possibly articulated why I felt such a need to get away from the employers of the day, but one can reminisce...
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.
- ende 12y agoI am so sorry you has to work in DOS :(
- enobrev 12y agoI didn't mind it back then. Considering the servers and workstations were completely dedicated to a single application, managing them was very straightforward. What was far worse, was teaching incredibly impatient traders - with hundreds of thousands on the line at any given moment - how to use a mouse, as more recent versions of our software became their initial introduction to Windows.
- Natsu 12y agoI worked with DOS as recently as 6 years ago. It's actually not all that bad, assuming you've got them on a network. We had a Novell server and they all mounted a network share on that at boot. From there, backups (and restores) were just a simple xcopy script. I ran a script to create 'flag' files to trigger the backup on reboot and the machines were shut down every night, so it was quite simple to manage. 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.
- marktangotango 12y agoHow did one do network programming in dos? Did it have a tcp/ip stack and winsock.h funtions or equivalent? And threading? Did you use Djgpp? I've always wondered about that. Edit: browsed the DJGPP website and found answers, there are libs available.
- Jedd 12y agowinsock may have come a bit later ;) Read up on the Wollongong TCP stack - very much an MS-DOS stack that I have mixed memories (some fond, some horrendous) of.