Posted on

What’s a hobbyist programmer?

New to Visual Studio 2005 is the Express Editions which “ include lightweight, easy-to-use, easy-to-learn tools for hobbyists, enthusiasts, and novices who want to build dynamic Windows applications and Web sites.” In conjunction with Beta 2, they also launched a new website, Coding4Fun. Is it just me or are the people depicted on the websites for Express Editions and Coding4Fun unlike any other programmer, you’ve ever met? Especially Coding4Fun guy: it looks like he has some issues. The VB guy looks confused. Haha. Perfect

They’re selling these as simplified tools for hobbyists and beginners, and that’s fine. That’s a laudable goal. But I can’t figure out why they removed VS add-ins in the Express products. Did they think it would confuse new developers to have add-ins? Is that what the market research is saying? One menu item in the Tools menu is going to deter budding hackers from coding “dynamic Windows applications and Web sites?” When I started with the Beta 1 of C# Express, I was excited about it: a cheap IDE that does just what I want. Then they got rid of add-ins!? WTF?!?! Why?

Here’s what google says a hobbyist is: a person who pursues an activity in their spare time for pleasure. It says nothing of skill level. So why reduce the tool set for the hobbyist? Does the Gus The Hobbyist developer profile specify that he’s a beginner confused by a menu item? What about Isaac the Open-Source-Project Weekend Warrior? 

Did you click the link for Coding4Fun? In case you didn’t, they have a link to an article about starting your own game with DirectX. For hobbyists. Amateurs. Who do it for fun. That’s a bit like an amateur photographer getting a low-end professional camera without a tripod, then explaining to her about setting up those light parachutes for backlighting. If we added this request to the Product Feedback Center, will they listen?

Posted on

Transparency’s other edge

You’re either not a nerd, or you’ve been caught under some shelving, if you’re finding out from me that Visual Studio 2005 Beta 2 has shipped. It’s available for download if you’re one of the privileged few MSDN Universal subscribers, but if you’re one of the unwashed masses of developers, like me, you’ll have to wait for Microsoft to mail you a copy.

Click the first link, it’ll will show you a handy-dandy list on the right about the current build information; click on the Profession Edition link (or just click here), and what do you see in Release History? That’s right: included with VSTS. We have MSDN subscriptions at work: the downloads they offer are VS Standard and VSTS Suite. What I can conclude, and it’s only speculation, is that MS is foisting Team System on us for the Beta, letting us get used to the great, new features, and then coming out with VS 2005 Pro for the real release. Of course, I could be wrong; like Mike Gunderloy surmises, it could be that they’re waiting for SQL Server 2005 beta 3. At any rate, given the recent, justified (IMO) outcry about pricing for Team System, this just makes me feel a little off. Like I just got off the phone with my phone company’s customer service: Angry, but defenseless against the tyranny.

This is the downside of all that transparency that MS is giving us. All the bloggers give us cutting-edge info before the marketing wonks have figured out how to peddle it. When those two messages don’t jive, like they don’t with Team System, how quickly will it be before the blogs start being dismissed with mistrust? Most of the MS bloggers I read don’t really mention it, to be honest, but occasionally the Kool-Aid smells real bad. Guess I should just turn up my BS filter whenever there is a post about the future and quit complaining.

 

Posted on

The Wealthy Blogger

Our eviction two months ago really made me consider buying a place,my financial situation and my future. I’ve since taken steps to be more responsible with my money: sock some away, put some in an RRSP; stuff I always meant to do, and now finally did.

So, when Darren Barefoot pointed out the Wealthy Blogger, my curiosity was piqued. Here’s a blog from a couple of guys trying to be financially independent before they’re 35. Great advice; I’ve already learned a lot. And he’s Canadian: can’t go wrong there. Subscribed.

Posted on

Geeks Rule and MBAs Drool

Eric Sink’s blog is one of the first I started reading way back in the summer of 2003. He’s a good writer, a legendary geek, and a successful entrepeneur. I’ve written before that he’s Joel Spolsky without the attitude, but that’s not quite accurate. I read Joel On Software over the Easter weekend. I couldn’t put it down. His essays are much better in book form. Everytime I read one of Joel’s articles online, I’d think: He’s got some good points, but what an asshole! After reading his book, I don’t think he’s an asshole. Joel’s a smart guy; he knows it but he’s not afraid to whack you over the head with it. Eric is smart and he knows it, but doesn’t whack you over the head with it.

Anyway, he’s had a column at MSDN for the last year and a half called the Business of Software. His latest column, titled the same as this post, is about the importance of listening to geeks in a software company. Actually, if this is the first you’ve heard of the column, read all his columns.

I just finished a similar article from Paul Graham, another guy that will whack you over the head, entitled Why Smart People Have Bad Ideas(in truth, this article’s ideas span a couple of Eric’s columns). He starts off well, but, about 3/4 of the way down, he makes such an absurd assertion about those who can write optimizing compilers that I didn’t want to finish the article.

Yet both Sink and Graham say the same thing: business people aren’t necessary when you’re starting out. Whose article do you prefer?

Here are a couple articles you should read, in the order I give them: 1) Hackers And Painters, 2) Dabblers and Blowhards