Category: Software Engineering

I just read 200 undergrad and graduate student resumes

My eyes are killing me.

Why the heck are you cramming so much unimportant information onto your single-sided single-page resume? You make it completely unreadable! Especially when someone (like a hiring manager) is trying to scan through hundreds of scanned pages.

Also, a new tip. Your paper resume will be scanned. It will be OCR’d. If you use tiny text on a background that provides low contrast with your text, no one will call you. EVER.

I found myself starting at the top of the page and letting my eye fall naturally down it. If I couldn’t get enough information to decide if I wanted to actually read it quickly, I just skipped to the next one.

It turns out that a good and specific objective statement is worth more than I ever gave it credit for. It was how I could tell a computer graphics grad student from a business undergrad.

Another question: why do you think anyone cares what high school you went to?

It’s great that you were a summer camp counselor, if I’m hiring a summer camp counselor. But I’m not, and it is just crowding your already crowded resume. Leave it off.

What, you are studying Human/Computer interaction, and you produced a resume that I need an electron microscope to dis cipher?

Sigh…

So, if you found me because you just got e-mail from me to talk about an internship, congratulations! Your resume is legible and clear, or your name begins with a letter from the beginning of the alphabet before my eyes started to glaze over.

Alex Iskold’s tips for startups

36 Startup Tips: From Software Engineering to PR and More – ReadWriteWeb

This is a collection of startup tips covering software engineering, infrastructure, PR, conferences, legal and finance. They describe best practices for an early-stage startup. We hope that you will find these tips useful, but also please remember that they are based on subjective experiences and not all of them will be applicable to your company.

These tips are great for web startups. They are pretty useful for non-web startups as well. I’ve been through the startup mill myself a couple times and I still got some good pointers.

comparing PHP RSS parsers

For a little project I’m working on, I needed to do some RSS parsing. I quickly found lastRSS, magpie and the Pear XML Feed Parsing Library. I wasn’t sure which was the best, so I decided to do a little apples to apples to apples comparison. I created the PHP RSS Comparator to help me figure out which library worked on the most feeds and had the best performance.

My findings so far? Magpie is rock solid, seems to handle nearly every feed I throw at it. When LastRSS handles a feed, it handles it the fastest. The Pear XML Feed Parsing library trips up on the same feeds that break LastRSS, but it is also a lot slower than LastRSS. The cache in LastRSS is effective and a very good idea.

It’s possible that I’m mis-using the Pear or Last RSS libraries, but I basically did the same thing with all three libraries which is to start from their own sample code and then make minimal changes so that they all showed the same results.

I can definitely see why they use magpie for wordpress. It isn’t as fast as LastRSS, but it is close and it handles a lot of feeds that lastRSS does not. The Pear XML Feed Parsing library may be powerful, but it doesn’t work well enough on real-world feeds to make it worthwhile for me.

Dear Radiohead and the rest of the music industry

I applaud you, Radiohead, for doing such a forward-thinking experiment with your distribution for InRainbows. However, you’ve unfortunately made sure that any data you receive from this experiment will be useless. Why? Well, because your website and ordering process are HORRIBLE. I had so many problems getting your website to work that I almost gave up. I’m now concerned that I paid for it at all. I’m scared for the safety of my personal data. Really, it is 2007, get a web designer who knows what they are doing.

Secondly, you also seem to have gone out of your way to make sure that the downloaded tracks themselves are sub-standard. I’d heard that the mp3s you are distributing were at 128 kBps, which would have been ridiculous. I see now that they are at 160 kBps which is just lame. How about 192 kBps or higher? I would have gladly paid $10 for this record at a higher bitrate. Given the bitrate you are distributing it at, I decided only to pay $5. Also, where is the cover art? How about tossing a jpg into the zip file with the album cover? Maybe a text file with some liner notes. Just because you aren’t shipping shiny plastic discs around, it doesn’t mean that all previous ideas with the album were bad.

Hey, here’s an idea. Give the album away for free at 128 kBps, charge a nominal fee ($5-$10) for a 200 kBps or higher bitrate.

How about an optional survey section at the end so that I could have told you this instead of posting it on my blog?

So Trent, and other artists considering following in Radiohead’s footsteps (although they weren’t the first to do this honestly), try downloading the tracks yourself and see how much easier it would be to do something much better for your listeners.

I may just do this with the next Intonarumori album…

I have seen the future and it is Thermo powered

Holy frijoles was that beautiful.

That was absolutely one of coolest demos I have EVER seen. If I wasn’t wedded to C++, I’d switch over %100 to doing ActionScript development right now so that I could use that tool to make my GUIs. Microsoft should be shaking in it’s boots, because from what I’ve seen of the Silverlight tools, they are (silver)light years behind.

I work for Adobe, so I knew about Thermo. I’d seen slide decks on it, I’d discussed it with people. I’d never seen a demo. This went beyond any expectations I might have had. This combined with FlexBuilder3, AIR, Hydra (you knew I had to make a plug for that) and Astro makes an outstanding tool set for building desktop applications connected or not.

C# has been my go-to for doing up quickie applications or doing app prototypes for my personal development. Not for much longer. Especially because I’m on the mac now and being able to do cross-platform development with such an awesome rapid app development toolset is super exciting.

Interesting article on Ruby vs PHP

I’ve been doing PHP for a little while, but I’m always hearing about how much better Ruby on Rails is. Luckily, Derek from CDBaby decided to rewrite his site with Rails and actually decided that PHP was better for some stuff.

7 reasons I switched back to PHP after 2 years on Rails – OReilly Ruby

I spent two years trying to make Rails do something it wasn’t meant to do, then realized my old abandoned language PHP, in my case would do just fine if approached with my new Rails-gained wisdom.

f’ing A! CSS Positioning sux

Every time I try to use CSS for positioning, I hit the wall. Gradually, this wall has been getting further and further, but I still always hit it. First I couldn’t get things to lay out correctly at all. Now I can get them to lay out, but only on three of the four browsers at any one time. Then I read this and it makes me feel better:
jwz – CSS is BS

I have learned or in some cases reconfirmed a few other things about CSS, too:

  • Web designers, and especially blogging web designers, are self-important fuckheads. This might be tolerable if they were right, but by and large theyre also dumbasses.
  • Everybody who fancies themself a CSS expert uses pixel-based layout for everything. Their shining examples of elegance always include boxes that are exactly 400 pixels wide, and that specify font sizes in pixels not even points This is better than auto-flowing auto-sizing table layout… why?
  • Most of the time, these examples look like ass on my screen, presumably because Im not running Windows and dont have the same fonts that they do. Or maybe because theyre all using 50-inch monitors and sit with their noses on the glass, the only way those miniscule fonts could actually look readable to someone.
  • They never measure in “em” units, so that their boxes might have at least some relation to the size of the text inside them.
  • This may or may not be because “em” doesnt work consistently across various browsers.
  • Oh, “em”, a term from the world of physical typesetting, is supposed to be the width of a capital letter M, and used only for horizontal measure; the vertical measures are ascent, descent, leading, and sometimes “ex” height of a lower case “x”. CSS defines “em” as being the height of an M instead making it synonymous with “ascent”, which makes it generally about twice as big as youd expect if you know anything about this stuff. Nice. Thats like redefining “centimeter” because it seemed more convenient at the time. Except sillier, since “em” is an older unit of measure than centimeter is.