macintosh

How to get my job (2006 edition)

Dave Farquhar Personal , , , , , , , , , ,

It seems like every year or two, somebody asks me how to get my job. Given the way the last year or so has gone, I can’t believe anyone’s asking me that question, but it’s been coming back up again. I’ve made some mistakes in my career–obviously–but since I’m still in the field, I must have done a few things right too.

I guess it makes sense to trace my career and see what I would do differently.1984: Yes, it all started when I was 10. I’d wanted a computer for as long as I could remember, and that year, Mom and Dad finally bought one. I spent as much time messing with that old Commodore as I could. And when I wasn’t messing with that Commodore, I was reading about it. It was an obsession. It bordered on unhealthy. Or maybe it was unhealthy.

In high school, if you’d offered me a choice between a date with the best-looking girl in the school or a new Amiga 1200 or 3000, I might very well have taken the computer. Sure, I was interested in girls, but the computer wouldn’t break up with me, right?

I bring this up for one reason: If you’re wanting to get into the field for money, find something else to do. Go into sales or something. If you don’t absolutely love this stuff, you won’t last, so there’s no point in wasting your time.

1994: I started my career in sales. When polite company isn’t around, I say I whored myself out for a large consumer electronics chain. That might be a bit more accurate. In a way it was a good move. A lot of IT people my age started their careers the way I did. It’s better than fast food, at least in regards that IT recruiters use it as a scouting ground. Work there and do well, and it’s just a matter of time before recruiters will want to talk to you.

What I did right: I started filling in for the store’s technician, who frequently had problems showing up for work.

What I’d do differently: First, I’d find out who the best salesperson was, and really learn how to sell. I’ve worked with IT management people who couldn’t figure out how to make their computer play solitaire, but they know a little bit about selling, so their jobs are safe, even though they had no qualifications.

The other thing I’d do differently is to get A+ certification. It’s not strictly necessary to get a better job, but it opens more doors. A lot of jobs require A+ certification just because some idiot in HR (and yes, most of them are idiots) decided it’s a good idea.

1995: I caught a break because I knew both Macintosh and IBM hardware, I knew OS/2, and I had connections at the journalism school at the University of Missouri. A professor mentioned the job opening to me and handed me a phone number. After class I called the number. The guy on the other end asked me what I knew how to do. I told him, he told me he’d pay me $7 an hour, and asked when I could start.

It was supposed to be a temporary gig. But it turned out I knew how to do a lot more than just the grunt work that needed to be done, so they found money to keep me. And when I was about to graduate, they offered me a full-time job.

What I did right: I showed up for work, I did everything they asked me to do, and whenever somebody else was sick and they asked me to try to fill in, I filled in and actually managed to do a decent job.

What I’d do differently: It wasn’t a bad gig, until Yoko Ono came along. Actually she was from Pittsburgh and she was Scottish-American. But the relationship interfered with the job and the job interfered with the relationship. And when something went wrong with one, it messed up the other too. I’d have done well to learn how to separate the two. That’s a lot to ask of someone who’s 23. Now I’m 31 and don’t know how now either. Neither does my 40-year-old boss.

1998: I moved to St. Louis to take another job in IT. This was also the year I re-discovered God and religion. This was a dream job, working for my church. I took a demotion and a pay cut to do it. Of course I didn’t know until I’d already quit my other job that it was a demotion.

I’ll get off track if I talk about it much more than that, so let’s just talk about what went right and wrong.

What I did right: I racked up a lot of impressive statistics and I learned how to do everything they asked me to do. I usually wasn’t happy about it, but I always did as well or better than the person who replaced me. The guy I replaced was a legend and I don’t think anyone would have been able to replace him adequately.

What I did wrong: I shouldn’t have taken the demotion. Not at 23. If you’re married and have kids, I can see taking a demotion so you can work better hours to spend more time with your family. When you’re 23 and single, you can’t waste time climbing a ladder you already climbed once. A banker in Columbia offered me a job as a systems administrator when he found out I knew OS/2. I should have taken it and called St. Louis and told them I wasn’t coming.

This job really went downhill as another relationship was coming to an end too. No need to re-hash that.

I made one other mistake. I won’t elaborate on it. But if you see upper management doing something unethical, LEAVE.

2005: Mercenary time. My first contract was with a very large and very nearly bankrupt cable company. The work wasn’t nearly as interesting or challenging as my previous job, and my coworkers were at either extreme: Some were among the very best people I’d ever worked with, and some of them were just overgrown high school bullies. But it was work, and the pay was fair, which was nice after working for seven years at anywhere from $15,000-$20,000 less than I was worth. Making a double mortgage payment and still having more money left over at the end of the month than I’d had a year before was very nice.

What I did right: I came in, learned quickly, took things seriously, was very professional and very effective.

What I did wrong: I didn’t press in. I did what I was asked, and that was it. That’s what a hired gun does. And the result was I was treated like a hired gun. As soon as the money got tough, I was the first one out the door.

I had coworkers who didn’t want me to learn more about the system. Since they didn’t want to show me, I should have found another way to learn it. And I should have loosened up.

2006: I won’t tell you who I’m working for now, other than to say it’s someone you’ve definitely heard of.

This time, I made an effort to go to lunch with my coworkers. I didn’t do that at the cable company because I was trying to save money. I’d gone without enough money for a couple of months and was deathly afraid of having to do it again. I’m still a tightwad and everyone knows it, but I’m willing to spend $7 to bond with my coworkers once a week. The theory is it’s a lot harder to show the door to someone you like than to someone you barely know.

The other thing I did this time was to steal some responsibility. I volunteer for everything. Sometimes they end up giving it to someone else anyway. But I’m always willing. When people give me some of their old responsibilities, I take them, and I figure out how to do them faster and smarter. After about two months, now my boss is surprised when I do something his way.

My path isn’t the only path. There are two previous bosses I wouldn’t hesitate to work for again. One is a retired U.S. Marine. He went into the Marine Corps as a technician, fixing teletype machines. When teletypes became less important, he moved on to computers. When he retired, he kept on working for the military as a contractor.

Most of my coworkers today took a similar path. Some enjoyed very long careers as defense contractors after their military days came to an end.

That seems to me to be a good route to take if you don’t have a lot of connections. And the upside to the military approach is that you know your job won’t be outsourced to India. That’s a real danger and that danger is going to get a lot bigger before it gets any smaller.

The other previous boss has a degree in psychology. He started working with computers because he found them interesting. I don’t know how he got started in the field, but during the time I worked for him, he was the epitome of connections. He knew everybody, and whenever something goofy came up, he knew how to get in touch with them to get the answer. The result? He’s every bit as entrenched as a tenured professor would be. The difference is there’s no question as to whether that’s a good thing.

Microsoft buys and then discontinues Linux/Unix antivirus products

Dave Farquhar Servers and Networking , , , , ,

First GeCAD, now Sybari.

Microsoft has been buying smaller anti-virus firms and discontinuing their Linux and Unix product lines.

Trust, schmust. When your god is Big Business, that means Big Business can do no wrong, so when you’re the U.S. government, you let companies like Microsoft do whatever they want. The problem is that Unix antivirus products are extremely useful, especially in Microsoft shops. Unix viruses are rare, and the heterogenous nature of Unix–never knowing much about the underlying hardware, binary incompatibilities between various dialects even when running on the same hardware, and never knowing for certain which libraries are installed–creates a hostile environment for viruses anyway.

So what good is a Unix server that detects viruses that can’t survive in Unix anyway? It makes a great buffer between the hostile world and the soft and chewy Windows boxes inside corporate firewalls, that’s what.

I love to put Unix boxes in between the world and mail servers that may be running Windows. Just set it up to relay mail to your Exchange or Domino server, but have it scan the mail first. Better yet, have it running on weird hardware. A slightly elderly Macintosh or Alpha or Sun box works great. Since the Intel x86 instruction set is the most common, most buffer overflows use it. While non-x86 processors aren’t immune to buffer overflows, an overflow using x86 instructions will appear to be gibberish and it won’t run. It’s like telling me a lie in Japanese. You won’t fool me with the lie, because I don’t speak Japanese, so I won’t understand a word you’re saying.

Fortunately, there are still antivirus products for Unix and Linux out there. And once Microsoft establishes its antivirus product, it will be more difficult–I hope–for it to simply continue buying antivirus firms and discontinue their products, since now they would be buying off competitors, rather than just attempting to acquire technology that they don’t have the ability to develop internally.

And even if they do buy and discontinue everything, there’s always ClamAV.

The Microsoft Killer

Dave Farquhar Windows , , ,

Yet another story about what’s going to kill Microsoft popped up on Slashdot today. This time it’s cheap solid-state computers running open-source software. I didn’t bother reading it.

Here’s what I think the Microsoft killer will be: Windows.

Say what?Yeah, Windows.

Computers are cheap enough now that the majority of people who want one have one. Even those who can’t afford to buy new can turn to the used market–used 1 GHz systems are now selling in the $100-$150 range without an operating system.

The biggest problem with a computer these days is keeping it running. People throw away VCRs and DVD players because it’s cheaper to buy a new one than to have one repaired. And had I charged fair market value for the last computer repair I did, it probably would have exceeded the cost of a $399 Emachine.

But there’s a problem. When a VCR or DVD player dies, you unplug the old one, plug in the new one, and get on with life. You’re looking at three or four cable connections. It takes most people less than 10 minutes, usually much less. When you go to swap out a computer, you have to worry about all your data and the programs you installed.

Most people don’t know that 99% of their data is in one place, and even fewer people know where that is and how to get to it. These same people are the ones who are most likely to inadvertently end up with their data in weird places.

The result is the cost to replace a computer is much higher, and it’s not necessarily something the majority of people want to undertake themselves.

The result is lost revenue. And an opportunity.

Google, if you’re the one who wants to unseat Microsoft, find a way to help users move their data from one computer to another. Someone else, if you want to beat Google to the punch, find a way to help users move their data and their programs. I know such a program won’t be foolproof, but if it works even 75% of the time, it’ll sell like crazy.

Of course if someone does it and it proves successful, Microsoft will just clone it and assimilate the market.

But if no one does, maybe Steve Jobs will sell a lot more Macs, because this is one task that’s always been easier on a Macintosh.

So there is a benefit to running Windows Server 2003 and XP

Dave Farquhar Servers and Networking , , , , , ,

One of the reasons Windows Server 2003 and XP haven’t caught on in corporate network environments is that Microsoft has yet to demonstrate any real benefit to either one of them over Windows 2000.

Believe it or not, there actually is one benefit. It may or may not be worth the cost of upgrading, but if you’re buying licenses now and installing 2000, this information might convince you it’s worth it to install the current versions instead.The benefit: NTFS compression.

Hang on there Dave, I hear you saying. NTFS compression has been around since 1994, and hard drives are bigger and cheaper now than ever before. So why do I want to mess around with risky data compression?

Well, data compression isn’t fundamentally risky–this site uses data compression, and I’ve got the server logs that prove it works just fine–it just got a bad rap in the early 90s when Microsoft released the disastrous Doublespace with DOS 6.0. And when your I/O bus is slow and your CPU is really fast, data compression actually speeds things up, as people who installed DR DOS on their 386DX-40s with a pokey 8 MHz ISA bus found out in 1991.

So, here’s the rub with NTFS compression when it’s used on Windows Server 2003 with XP clients: the data is transferred from the server to the clients in compressed form.

If budget cuts still have you saddled with a 100 Mb or, worse yet, a 10 Mb network, that data compression will speed things up mightily. It won’t help you move jpegs around your network any faster, but Word and Excel documents sure will zoom around a lot quicker, because those types of documents pack down mightily.

The faster the computers are on both ends, the better this works. But if the server has one or more multi-GHz CPUs, you won’t slow down disk writes a lot. And you can use this strategically. Don’t compress the shares belonging to your graphic artists and web developers, for instance. Their stuff tends not to compress, and if any of them are using Macintoshes, the server will have to decompress it to send it to the Macs anyway.

But for shares that are primarily made up of files created by MS Office, compress away and enjoy your newfound network speed.

The big question: PC or Mac?

Dave Farquhar Macintosh , , , , , , , , ,

I haven’t stirred the pot in a while, so to prove that I am a professional writer after all, I’ll go tackle the most inflammatory question I can imagine, something that makes Bush vs. Kerry look like a game of paddy-cake.

What’s the better computer, a PC or a Macintosh?OS X closely follows the history of the first Macintosh in that the first version showed lots of promise, but had lots of problems, probably shipped too soon, and lacked some important capabilities. But Apple, to its credit, washed its dirty laundry in public, fixing the problems and adding capabilities. And now, OS X has a reputation as something that “just works.” And it has something to back it up with.

Windows XP, well, that joke about 32-bit extensions to a 16-bit graphical interface on top of an 8-bit operating system originally written for 4-bit computers by a 2-bit corporation that can’t stand 1 bit of competition is almost true. Microsoft bought the 8-bit OS from a company that may have stolen it. And while Gary Kildall‘s first operating system was 4-bit, he may have written CP/M from scratch. But I digress.

Unlike Apple, Windows XP tries really hard for backward compatibility. And for all the stink about the things SP2 breaks, I’ll bet you a dollar you can go download the 1981 edition of VisiCalc for MS-DOS and it’ll run just as well on your three-point-whatever gig Pentium 4 running XP as it did on the first IBM PC. And if you can find old copies of WordStar and dBASE II and Turbo Pascal, chances are they’ll run too. Old programs that break are at least as likely to break because of timing problems with CPUs that are almost a thousand times faster than they expect as they are because of Windows. Probably more.

Sure, you’ll find programs that break, but you’ll probably find a thousand that work for every one that breaks. Especially if you limit yourself to titles that aren’t games.

This is a blessing and a curse. The blessing is that software you bought almost a quarter century ago still runs if you need it. If you think that isn’t important, I’ll introduce you to one of my clients who’s still using dBASE II. It sure is important to him. The curse is all that spaghetti code you need to keep those billions and billions of old programs running.

I have a little bit more sympathy for Microsoft when I remember that Windows XP is really OS/2 1.3 with DOS bolted on, and Windows 3.1 and 98 bolted on next door.

Just a little.

When you look at it that way, is it any wonder that sometimes when you plug in your digital camera it acts goofy?

But truth be told, more often than not, your mouse and your digital camera and all your other stuff works, whether you plug it into a Windows box or a Mac. And when it doesn’t work, it’s every bit as infuriating on a Mac as it is on a Windows PC. When Windows has an error code, it spits one out in hexadecimal. The Mac spits out an error code in decimal. I guess that makes the Mac friendlier.

But I guess it doesn’t matter whether I say “deleterious” in English or in Pig Latin. It’s still not going to be a word you’re likely to have heard today, either way. And there’s a decent chance it’ll send you reaching for a dictionary (or Google).

I’ll be frank: I hated OS 9 and OS 8 and everything else that came before it. I tried to get the Mac Toss turned into an official olympic sport. If there are any old Macintoshes in the pond in front of the office building where I used to fix Macintoshes, I know nothing about them.

But Apple knew it was b0rken and threw it away and bought something better. I still think they bought the wrong something better and would have gotten here a lot sooner if they’d bought BeOS, but they bought NeXT and got Steve Jobs back, so here they are.

All things being equal, I’d go with a Mac, if only because it’s got a Unix layer underneath it.

But all things aren’t equal. Macintoshes cost a lot of money. And when you’re 2 percent of the market, you don’t have a lot of software to choose from. I know. I had long love affairs with Amiga and with OS/2 before I threw in the towel and installed Windows. And it wasn’t until 1997 that I actually used Windows as my everyday OS.

When someone hands me a disk, I can read it. When someone tells me I’ve gotta try out this new program, it runs.

On the other hand, there’s virtually no problem with viruses and spyware on the Macintosh. If I want to spy on people or cause enough damage to make the front page of USA Today, I’m going to set my sights on 90+% of the market instead of the Macintosh’s 2%. Being a minority can have its advantages.

But, after living for years with good computers and operating systems that were years or even decades ahead of their time but had no software availability, I run Windows most of the time and exercise caution to keep my system clean. I don’t use Internet Explorer, I keep my virus definitions up to date, I don’t read e-mail from strangers and don’t open unexpected attachments, and I don’t install freeware software unless it’s open source.

And guess what? I don’t have any problems with my computer either.

I know and respect other people who’ve gone the other way. For me, there never was much choice other than PC hardware. I can afford a Macintosh, but that’s money I really need to be putting towards paying off my car and my house sooner, or saving for retirement. Or any number of other things. I’m a legendary tightwad.

Other people may have had their own other reasons for making the same decision.

Open sourcing code doesn’t necessarily mean people will rush to it

Dave Farquhar Retro Computing, Software , , , , , , , , ,
Open sourcing code doesn’t necessarily mean people will rush to it

John C. Dvorak wrote a nice layman’s introduction to open source on PCMag.com. But he makes at least one big false assumption.

Dvorak says he’d love to see old code open sourced. Some examples he sought, such as CP/M, CP/M-86, and GEM, have already been open source for years. Caldera, after buying the intellectual property of the former Digital Research from Novell, released just about everything that wasn’t directly related to DR-DOS, some of it as GPL, and some under other licenses. The results have hardly been earth shattering.

Read more

Go get ’em, SCO!

Dave Farquhar Windows , , , , , , , , , ,

I’m sure you’ve read it 4.3 billion other places already, but Microsoft has been granted a patent on double-clicking.

Well, there’s something you probably have only read a few hundred other places. Apple obviously had people double-clicking more than a year before Microsoft did, seeing as Windows 1.0 was released in November 1985 and the first Macintosh shipped in early 1984. Commodore had Amigans double-clicking by the summer of 1985. So did Atari.

Guess who supplied Atari with its operating system, since Jack Tramiel failed to swindle his way into ownership of the Amiga?

Digital Research, that’s who. DR provided Atari with a version of CP/M-68K, with its GEM GUI running on top of it. Atari marketed the bundle as TOS, for Tramiel OS.

Digital Research got crushed by the Microsoft juggernaut a few years later and eventually sold out to Novell. Novell then attempted to compete head-on with Microsoft (buying up its Utah neighbor, WordPerfect, and part of Borland in the process) and failed spectacularly. Smelling a rat–Novell believed Microsoft sabotaged some of its applications so they would not run under DR-DOS–it then pawned the Digital Research portfolio off on Caldera, a Linux company run by former Novell executives. The catch? Caldera had to turn around and sue Microsoft. Which they did, successfully.

A few more years later, The Santa Cruz Operation, a small Unix firm, wanted out. It sold its Unix-on-Intel business, as well as the rights to the old AT&T Unix (purchased from Novell, ironically) to Caldera, who soon changed its name to The SCO Group to reflect this business.

Yes, this is the same SCO who is now on a legal rampage, suing anything that moves.

Now, whether Novell or SCO is the more rightful owner of the double-click “innovation” is arguable. But such matters never seem to matter to SCO. It’s a frivolous lawsuit, but Darl McBride and Co. have made frivolous and baseless lawsuits into an art form.

Go get ’em, Darl.

The problem with online streaming video

Dave Farquhar net.culture , , , , , ,

I think we may have lost a project at work today: a project to do streaming video. It’s not really our fault; our offering looked just like everyone else’s streaming video.

The problem is that our competition isn’t everyone else’s streaming video.First let’s look at the hurdles. No matter which option you pick, some percentage of your audience is going to have to download or install something. That all but eliminates Real, since I don’t think even Woodward and Bernstein could successfully track down the link to their free player every time.

Windows Media Player is easier, but won’t necessarily run on some older versions of Windows. An overwhelming number of people have Windows XP now, but not everyone does. How many hundreds of millions of copies of Windows 98 did Microsoft sell? Do you think all of those people have thrown them away yet? No. Those people will have to download and install something.

But Media Player will leave some Macintoshes in the cold. Do you want to do that if your target audience might include schools?

QuickTime is the best cross-platform solution, but again, Windows users will have to download and install something.

OK, so you got it installed. Prepare thyself for thrilling, 15 frame-per-second 160×120 video!

Translation: Video the size of a postage stamp that moves about as fast as your mailman.

Theoretically you can stream bigger and faster video, but it’s going to be jerkier if you do. There’ll be dropped frames, artifacts, and the audio may drop out. And what’s it look like when you send DVD-sized 720×480 video? Well, considering a lot of people run their monitors at 1024×768, it makes letterboxing look good. It’s not full-screen like it is when you pop a DVD into your DVD drive.

And that’s precisely the problem. The competition isn’t other people who stream video. The competition is DVDs. Computers are digital, right? So why does its video look worse than the oldest, most worn-out VHS tape at the video rental place? And why do I have to jump through so many hoops in order to play it? On a DVD, I hit the "menu" button and then I hit "enter" or "play." (Also keep in mind that some people can’t even figure out how to do that. I’m serious. I dated a girl once whose parents couldn’t figure out a DVD player, so they had to get their 15-year-old son to come hit the buttons for them.)

And that, I think, is the reason you still don’t see tons and tons of streaming video on the Web, in spite of the high availability of DSL and cable modems in the United States, the abundance of cheap bandwidth, and the cheapness of the server software (free, in the case of QuickTime, and included with Windows Server in the case of Media Player).

MyDoom/Novarg Gloom

Dave Farquhar Uncategorized, Viruses , , , , ,

Just in case anybody is curious, my employer’s virus scanners filtered roughly 3,000 copies of Novarg (a.k.a. My Doom) during working hours yesteray. If that’s not a record for us, it approaches it. I know we weren’t the only one.I’ve heard Novarg/MyDoom/My Doom called the fastest spreading virus yet. I don’t have statistics on prior viruses with me, but suffice it to say, its impact certainly felt similar to the big names from the past.

Although SCO would like people to believe it was written by a Linux zealot, I’m more inclined to believe it was created by organized crime. Maybe the creators hate SCO, or maybe the anti-SCO DDoS was just an added touch to throw investigators off.

LoveLetter was the first virus outbreak to really have much impact on my professional career, and I noticed something about it. Prior to LoveLetter, I never, ever got spam at work. Not once. After LoveLetter, I started getting lots of it. I don’t believe LoveLetter’s intent was to gather e-mail addresses for spammers, but I do believe that more than one spammer, probably independently, noticed that viruses were a very efficient way to gather a large number of e-mail addresses.

I got spam before LoveLetter, and I saw viruses before LoveLetter. But I started seeing a lot more of both very soon after LoveLetter.

I don’t buy any giant conspiracy to sell anti-virus software, nor do I buy any giant conspiracy against SCO. I do believe in bored people with nothing better to do than to write viruses, and I also believe in people who can profit off their side effects.

I’ve said it once and I’ll say it again. If you run Windows, you must run anti-virus software. You can download Grisoft AVG anti-virus software for free. Don’t open unexpected e-mail attachments, even from people you know. Even if it looks safe. Don’t send unexpected e-mail attachments either–you don’t want anyone to get the idea that’s normal. Quite frankly, in this day and age, there’s no reason to open any piece of e-mail that looks suspicious for any reason. I told someone yesterday that this is war. And I think that’s pretty accurate.

If you’re an intrepid pioneer, there’s something else you can do too, in order to be part of the solution. If you join the Linux revolution, you can pretty much consider that computer immune. Macintoshes are slightly less immune, but certainly much less vulnerable than Windows. Amiga… Well, I haven’t seen the words “Amiga” and “virus” in the same sentence since 1991 or 1992. But one thing is certain: a less homogenous field is less susceptible to things like this.

 

The first PC I ever built

Dave Farquhar Retro Computing , , , , ,

I’ve noticed a disturbing trend lately: Everyone who built his own PC knows everything. Just ask him.
Now, don’t get me wrong: It’s admirable to build your own PC rather than just buying Dell’s special of the week (although some people would be better off just doing exactly that), and it does require at least skill with handling a screwdriver. But it’s not what it used to be. Today, building a PC makes you know something. It no longer makes you an expert.

Read more