Author: Andrew Montalenti

There’s a great post on why to use C++ instead of GObject/C over at BMP CodeBlog, the blog for developers of beep media player (my preferred MP3 player on Linux). I have to agree with most of what the author says. Using GObject/C is quite cumbersome, I’m almost surprised so many GTK+ developers do it. Especially considering the fact that C++ doesn’t incur overhead unless it has to, nicely expressed here:

The ultimate feature is that all of these are optional. We incur no overhead when we do not use a language feature (with the exception of… exceptions). In fact, cxx_conversion is currently in perfectly valid C++ and uses none of the features or C++ libraries mentioned above yet. The C++ language follows the philosophy of ‘pay for you use’ (better rephrased as ‘don’t pay for what you don’t use’). As it is right now, cxx_conversion is no less (or more) CPU or memory efficient than its C original.

GTKMM keeps getting more and more mature, so now that I’m finally learning C++ properly, I think moving over to GTKMM will be quite nice for a future project that needs a cross-platform UI.

I just wrote a ~1000 word e-mail in a web-based mail client. When I clicked “send” it told me my session had timed out.

And then the e-mail was gone.

This is why I _hate_ web applications. I am so depressed.

I recently installed X.Org 7 with Exa, Composite and the famed xcompmgr on my Linux desktop. This didn’t enable any fancy special effects for my lowly built-in via video chipset. However, it did finally do away with “rip and tear” on my desktop. That is, when I drag a window over another one, it just smoothly glides across. When I switch workspace, it’s instant — I don’t see as much “widget redrawing.”

More and more advances are going to inevitably lead to Linux “eye candy.” Here’s a great post on Slashdot regarding good versus bad eye candy.

Here’s a great example: pull-down menus in Mac OS X vs the same in Windows XP. On the Mac, pulldowns appear instantly, and fade away once something is selected; this is correct behaviour, as you asked for a menu – there should be no delay. Fading away is fine because the selection has been made, and you have moved on. In XP, the menus fade up, and vanish instantly – totally backwards. That is bad eye candy.

You know, I never thought about that, but I always turned off menu fading on Windows XP because I could “feel” the delay, even on my Nvidia card on my desktop. I never realized how much more sense it would make to display the menu instantly, and fade it away upon selection.

I hope this conservative approach is taken by Linux devs as they implement eye candy. Functional and beautiful, please.

So, this is a personal gripe of mine.

In the last, oh, two years or so, it has become increasingly cool to be hip to technology, and, more importantly perhaps, to engage in rampant punditry on the cultural effects of two companies in particular: Google and Apple.

In my school newspaper, Washington Square News, you will find the Opinions editor writing nearly-weekly columns on technology topics. But, what you’ll find, is that Google and Apple get more mentions then basically any other technology company out there. iPods, apparently, changed our culture in shattering ways, because now, instead of people talking to each other on the subway, they listen to their music collection. And web search and web e-mail (which existed before Google, and will exist in various new forms from now onward) is apparently so darn cool when the logo is rainbow colored, but not when its name rhymes with a parting phrase in Spanish.

Don’t get me wrong: if I consider myself a technology afficionado, then Google and Apple technologies are pretty highly rated, in my book. But can we just get over this obsession? I am speaking mainly to that strange cloud known as “the technology press,” but even to all these new technocratic snobs who spend all day talking about their Flikr albums, podcasts and “Web 2.0” calendaring.

Listen, I’ve been around a long time, and others have been along longer. Can we recognize computer products for what they have become? Commodotized fads, just like basically all other products. Technology makes a statement. Some people use GMail and iPods. These people are cool. Other people, like me, prefer no MP3 player, because I think what’s said in New York City is much more valuable than listening to my music.

And guess what? I still have my e-mail collection on a real, rich client, because I think the one I use is more powerful than Gmail will ever be.

Frankly, if you’re going to comment on culture, take a step outside of the Google/Apple obsession. Talk about things that matter. You’re obsessing over the moves of multi-billion dollar publicly traded companies. Companies that have to make a profit, and come up with a bottom line. Your obsession with them only exists because they want it to exist, because their marketers are smart cookies, and you are their pawns.

Just realize that there are lots of important things to talk about, and web-based e-mail and MP3 players just doesn’t make any reasonable list.

Can I also do what a lot of these technology pundits do, and snag up my own law? Here it is, Andrew’s Law: if you aren’t a coder or engineer, you can’t waste all your time commenting on software or technology products. There, that law being in effect, 90% of the web’s blogs should crawl to a dead halt.

You know you’re in UNIX zen when you are looking at pictures for an apartment you are interested in, and you think to yourself, “Man, I’d really just like to download all 8 photos of this apartment at once.” So you realize they end in numbers 1-8, and you open up a terminal and write:

for i in `seq 1 8`; do 
  wget http://www.livinginbaires.com/imgs/departamentos/46-$i.jpg; 
done

And that’s it, you hit enter and vroooooom! You see progress bars fly across your terminal as wget snappily fetches your photos, and suddenly, all eight photos are downloaded, and you get back to work. That’s empowering.

Early in the history of Microsoft, our view was, if you were very smart then you could learn how to manage people, how to do business, how to do marketing.

It turns out that talent isn’t that fungible. Somebody who is great at doing software in many ways is often not the right person to manage people. I think the thing to recognize is these different kinds of ability, and to think through, as you build a team, “How do you get the right mix?”

Although I probably wouldn’t have used the word “fungible” myself, I agree with Bill’s sentiment. Programmers are not developers. And developers are not managers. But, I would add something else to this:

A manager who doesn’t know what it’s like to be a programmer or a developer cannot be a manager of programmers or developers! Management is a special combination of leadership ability and empathy. Your manager needs to be able to stick his neck out for you, because he knows you. And he needs to be able to provide wisdom — not because he’s smarter, or because he’s more mature, but because that’s now his role. Managers are the guys who protect you from everyone not on your team, who make sure you have everything you need to innovate, and who provide wisdom because their job description includes, “must be able to dispense timely wisdom at all the critical moments.”

Management also includes vision. Some software developers become managers and their vision alone leads their team. Where that kind of energy isn’t possible, lots of empathy, planning, and wisdom are necessary.

I gave a talk last Tuesday called “Open Source Development: A Rapid Introduction.”

Here’s the blurb I sent out when I advertised the talk:

Have you wanted to work on open source projects, but just don’t know how to get started? This talk will provide the basics you need to start working on open source software the next time you sit down at your computer.

In particular, this talk will cover:

(1) A brief overview of open source development in the industry and press.

(2) The UNIX development platform. A brief and whimsical overview of the UNIX shell, its surrounding tools, and the power of shell scripting. (Useful to anyone wanting to learn more about UNIX tools.) Learn how to do in a few lines of shell script what you only thought was possible with a big, extravagant hundred- or thousand- line program, and learn why so many of the world’s best hackers hack on a *nix system.

(3) The basics you need in order to hack on open source project: how mailing lists, wikis, bugzillas, source code revision systems all come together to form an organic code management process, and how to get started using those tools and others to learn about a project and what parts need development work done. This will include a brief introduction to CVS.

(4) The last part of the talk will involve actually watching open source development in action. In particular, the speaker will checkout some code from a source repository, make a change to it, create a patchfile from that change, then track down the mailing list or bugzilla related to the project and submit the patch to the maintainer. You will actually get to see open source “in action,” and will want to do it right when you get home!

If you’re a Windows or Mac OS developer who has always wanted to learn more about *nix systems, or if you’re a developer who wants to either take his own project open source or work on existing open source projects, this talk is for you.

Of course, if you’re someone who is just interested in the concept of open source, this talk will give you an inside look at “how things get done” in this community.

This talk was at least partially inspired by Nat Friedman’s blog post, check it out here:

“How to be a Hacker”

The talk was a general success, I think. About 12 people attended. You can see the talk in PDF or ODP formats, and you can also download the patches I wrote specifically for the talk to illustrate “open source development in action.” The patches are pretty stupid, but do illustrate the point, at least. Plus, each of the three patches served one of my own goals (hacking my CPU frequency scaler, fixing a gnome-terminal bug, and hacking galeon “for fun”), so that’s that. I think it’d be cool to give this talk again (maybe a little refined to include less basic UNIX tools and more hacking stuff) at a later date. We’ll see.

To start out at a small software firm, or to go with one of the big guys? I’m wondering myself what the right decision is, what advice I’d give someone.

On the one hand, big guys mean bigger projects, more formally managed projects, and at least from that point of view, harder “software engineering” problems.

Small firms are less formally managed, but you may be pushing some technology to the limit, rather than just providing some service (however essential it might be) to the company. It’s the software that matters, not “the System.” And you’ll probably be working with better coders. (The best coders fill up the small shops, whereas they are just diamonds in the rough at the bigger shops).

In either case, this is turning into one of those things your parents always warned you about. You know, when they say it isn’t about the company, but it’s about you and what you put into it. Just like college was. I honestly could have gotten just as much out of college with a library card and Internet connection, and lots of free time.

Now that I’m moving up to the “real world,” I keep thinking: no matter what I do, it’s gonna be my responsibility to grow my skills and knowledge, and no one else’s.

It’s definitely going to be an interesting year…