Showing posts with label python. Show all posts
Showing posts with label python. Show all posts

Thursday, February 10, 2011

New Website

It can be difficult to keep your programming teeth sharp while studying in law school, but I've done just that. I'm happy to say that after learning a host of technologies (see previous post), my new website is largely complete.

The result is Resumé Launchpad. I got the idea for the website while applying to law firms during the end of my first year of law school. It's a tedious process. There are widely published databases containing the firm names, human resources representative names, and email addresses. So the process normally involves building a generic cover letter, copying and pasting the appropriate information into the cover letter, and blasting the email off.

When you first start, you try to customize the cover letter to each firm. It wouldn't be uncommon for me to spend a good twenty to forty minutes per cover letter. But after doing a dozen of these and receiving only form rejection letters, you begin to realize that quantity is more important that quality. Then you literally just modify the name of the firm and recipient and send the email blindly hoping for the best.

I ran into problems. I tried tracking everything in excel, but on several occasions I sent the my application to the same person twice. Worse than that, sometimes I would copy & paste incorrectly and get the firm's name, the recipient's name, or their gender wrong. After sending nearly a hundred cover letters like this, my programming instincts got the better of me and I decided to automate the process.

So I put together a database of legal employers from widely available sources (all legit). Then I wrote a python program which was kind of like a mail-merge on steroids; it could send hundreds of customized emails to various recipients stored in a local database.

Finally, the day of reckoning came. I put together my cover letter, resumé, and other attachments and let my program do its thing. I sent about three hundred emails in a couple of minutes. What would have taken me hours and days took only seconds.

It was successful. I got a number of interviews at some very prestigious firms. At the time, I didn't see it as a product, but more as a tool to make life easier for me. The idea to build a general-purpose web interface to my program started percolating.

The rest is programming history. I learned how to put together a modern complex site and two weeks ago I launched it to the world.

So if you're an attorney, law student, paralegal, or legal secretary and you're looking for legal work, check out www.resumelaunchpad.com.


Saturday, November 20, 2010

Websites....

I consider myself a pretty competent programmer. I can pick up a new language / programming environment in a day and hammer out a cool prototype within three or four days. So when I had an idea for a website, I jumped right in.

Let me start of at the end... the website works! It's in private beta right now and I hope to release it to all in a month.

But it's been a long hard slog; far more work than I imagined. The last website I built was circa 2001. It was really advanced for its time: simple javascript and flash animations! Now, in this Web 2.0 world, "simple" anything won't cut it. It's not just that javascript has changed and flash has been dropped. Today, the list of technologies to choose from to build a site is staggering.

But even if you don't want to learn everything, say you just want to learn enough to put something decent together; well you're still in for a steep learning curve. Here's the list of mandatory technologies I've had to either know or learn to jump into the Web 2.0 world:
  • Advanced Javascript - learning object oriented programming the javascript way is definitely something new. It isn't bad, there's a lot to like about javascript, just different.
  • HTML - Remember the days when tags like "center" and "table" were your friend? Forget it, you're just using div and span now.
  • CSS - I hate CSS. It isn't a programming language at all. It's fine for colors and sizes. But once you use it to do layout, your headaches will begin. It's an art more than a science and nothing feels deterministic:
    Do you use the "top" or "margin-top" attribute? Who knows, try both.
    Why do we have both inline and inline-block? Because we can.
    Unfortunately, CSS is the only thing out there that does what you want. You just have to swallow it.
  • python - Admittedly, I was already pretty well versed in python (i luv python). If you don't want python, you're going to have to learn PHP or one of the other web-programming languages.
And those are just the languages you'll need to learn. The fun really begins when you include all the libraries:
  • jQuery - Very cool, I must admit. But for the uninitiated, it's totally different from anything you've done before.
  • jQuery Plugins - There's a jQuery plugin for everything. Great. Unfortunately, its a new API you have to learn to do anything.
  • Django - The web-backend. Cool technology but pretty massive and you have to learn quite a bit of it to do anything. Oh, did I mention that to use Django you have to learn its own special html-markup language too? It can easily take a day of tutorials to get familiar with the system. I've been working with it for a month now and I've only started becoming comfortable.
  • Google App Engine - It isn't necessary to learn google app engine. But they're a ridiculously cheap web-hosting solution... actually, for most cases it's totally free. But they do things so totally different, that there is a nice learning curve. To start with, there is no file system. Enjoy.
And perhaps I forgot the biggest pain: compatibility between different browsers. Just when you think you put the final touches on your beautiful site, you check it out on a different browser and it looks like crap. I'm not a Microsoft-hater, but this experience has definitely left a sour taste in my mouth for IE and I haven't even tried the mobile browsers.

Moral of the story is that making a website is pretty complicated involving nearly a dozen technologies. But websites are the future (ahem, present) and it feels pretty gratifying being able to put a real-life site online.