News for hackers. Stuff that matters.
Re:The Art of Not Working at Work by enobrev on Tuesday November 04, 2014 @06:27PM (#8559689)
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.

Re:The Art of Not Working at Work by ChuckMcM on Tuesday November 04, 2014 @11:24PM (#8560506)
Some folks aspire to the minimum amount of work and the maximum amount of pay. And they are shocked when they get laid off after a decade of that, that nobody wants to hire them. Like you I really enjoy the work so if I'm not getting the work I need at work I'm doing various things outside of work. (lately it is designing a 3D printer) I'm not sure when I realized that time doing nothing was just getting closer to dead with nothing to show for it, but once I had internalized that, idling wasn't really an option any more.
Re:The Art of Not Working at Work by dba7dba on Wednesday November 05, 2014 @01:41AM (#8560764)
"Some folks aspire to the minimum amount of work and the maximum amount of pay. And they are shocked when they get laid off after a decade of that, that nobody wants to hire them."

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.

Re:The Art of Not Working at Work by BillyMaize on Wednesday November 05, 2014 @09:24AM (#8561823)
Exactly the position I am in now. After a couple of years I am looking to move on but I am finding that no one needs the experience I have. Everything I have done for my current company is desktop development and the vast majority of the nearby jobs are web development. Companies these days don't want to hire anyone who can't hit the ground running so it's a rough situation. Better to get out now than many years from now though.
Re:The Art of Not Working at Work by dba7dba on Thursday November 06, 2014 @01:47AM (#8566048)
I think this article may be of some interest to you.

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?

Re:The Art of Not Working at Work by VLM on Wednesday November 05, 2014 @09:28AM (#8561847)
"Hence I believe you should be extra vigilant about stagnating skill set when working at a company for more than just a few years."

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.

Re:The Art of Not Working at Work by marktangotango on Wednesday November 05, 2014 @11:41AM (#8562663)
Interesting, can you talk about how this came about in your situation?
Re:The Art of Not Working at Work by GFischer on Wednesday November 05, 2014 @01:01PM (#8563154)
What, you're saying my 6+ years' experience in FORTE 4GL won't be relevant in the outside world???!! :)

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.

Re:The Art of Not Working at Work by 127001brewer on Wednesday November 05, 2014 @11:44AM (#8562680)
*...time doing nothing was just getting closer to dead with nothing to show for it..."

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.

Re:The Art of Not Working at Work by ChuckMcM on Wednesday November 05, 2014 @11:52AM (#8562720)
You make an excellent point. I tend to think of it as "What would you do if you knew you were going to be dead in 6 months" but that tends to skew toward the 'fun' side of things rather than the 'meaningful' side.
Re:The Art of Not Working at Work by nraynaud on Wednesday November 05, 2014 @02:45AM (#8560874)
I'm heavily depressed and don't work at the moment, my shrink think that taking a job where I wouldn't care and just do my stuff and go back home would be good for my brain. There might be something good about the life of the people who don't care about their job actually. I'm not one of them.
Re:The Art of Not Working at Work by gallamine on Wednesday November 05, 2014 @08:40AM (#8561682)
I tried sending you an email to both email addresses I could find. Both bounced. If you ever need to talk, I'm here: gall amine at google's email service.
Re:The Art of Not Working at Work by nraynaud on Wednesday November 05, 2014 @09:20AM (#8561813)
that's very nice, thanks. I fixed my profile.

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.

Re:The Art of Not Working at Work by protonfish on Wednesday November 05, 2014 @11:03AM (#8562405)
I have found that when I have people at home that need me - a significant other and kids - work is an afterthought. Maybe what you really need is a girlfriend.
Re:The Art of Not Working at Work by mrec on Wednesday November 05, 2014 @12:26PM (#8562924)
Yes, finding one of those is a piece of cake when you're heavily depressed and unemployed.
Re:The Art of Not Working at Work by protonfish on Wednesday November 05, 2014 @12:58PM (#8563126)
I didn't say it was easy. Though I find it's more common for people to miss opportunities for love due to unreasonable expectations of others. There are overweight girls and single mothers out there that need love, if your pathetic, depressed and unemployed self doesn't think you are too good for them.
Re:The Art of Not Working at Work by AznHisoka on Wednesday November 05, 2014 @01:35PM (#8563370)
"if your pathetic, depressed and unemployed self doesn't think you are too good for them"

You didn't need to include 'pathetic, depressed and unemployed' in that sentence.

Re:The Art of Not Working at Work by agumonkey on Wednesday November 05, 2014 @12:04PM (#8562796)
I concur. I used to be all about passions, that was before my existential needs shifted to family, home and sharing life.
Re:The Art of Not Working at Work by nraynaud on Wednesday November 05, 2014 @12:51PM (#8563084)
I do have one.
Re:The Art of Not Working at Work by xorcist on Wednesday November 05, 2014 @04:39AM (#8561091)
Interesting. I share some of your experience, but our conslusions differ somewhat. The absolutely most frustrating thing with being a freelancer is that all the time see what the customer needs to succeed, but it's impossble to change. Sometimes because there is not budget, sometimes because you are contracted by the wrong department, and sometimes just because of change aversion.
Re:The Art of Not Working at Work by ende on Tuesday November 04, 2014 @08:45PM (#8560117)
I am so sorry you has to work in DOS :(
Re:The Art of Not Working at Work by enobrev on Tuesday November 04, 2014 @08:55PM (#8560154)
I 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.
Re:The Art of Not Working at Work by Natsu on Wednesday November 05, 2014 @12:20AM (#8560617)
I 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.

Re:The Art of Not Working at Work by marktangotango on Wednesday November 05, 2014 @05:55AM (#8561278)
How 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.

Re:The Art of Not Working at Work by pjc50 on Wednesday November 05, 2014 @06:23AM (#8561346)
You didn't, mostly.

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

Re:The Art of Not Working at Work by Natsu on Wednesday November 05, 2014 @03:23PM (#8564051)
We didn't do anything like network programming where I worked. We just copied files on and off of network shares with batch files or such and let the Novell drivers handle the network.

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.

Re:The Art of Not Working at Work by Jedd on Wednesday November 05, 2014 @06:16AM (#8561322)
winsock 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.