SEEKING WORK - Toronto or Remote

Student currently completing my final year at the University of Toronto. Very experienced in web programming, especially Java/GWT, with some personal work in Django and Rails. Multiple years of industry experience. Worked in the past with Google Summer of Code, Rypple, and Salesforce. Big fan of functional programming as well (Lisp and Haskell, mainly)

Relocation might be an option in a few months.

conradbowen at gmail dot com

My Github profile can be found here: http://github.com/cowen

The Future Uses section certainly has a joke-y tone, but if it's an April Fool's Day joke, then NASCAR has given them a huge amount of leeway.

Usage of NASCAR trademarks, hosting videos, and even linking to the video on their homepage.

I'm more inclined to believe that it's real. But I've fallen for more Google April Fool's jokes then I'd care to admit.

Sure, I guess we aren't in a post-PC era. Yet.

I don't even own a tablet of any kind, but the reasons the author gives for dismissing them are extremely short-sighted.

The reason people still use PCs for email, office applications, and graphics applications has absolutely nothing to do with how suited tablets are to those domains, and everything to do with market inertia. It takes time to convert to a new system of doing anything. As more and more people move to tablets, you can expect all of the author's points to change overnight.

There are plenty of office applications for iOS and Android. Off the top of my head, I know that much of the iWork suite and Google Docs both have native apps for their respective OSes, and I wouldn't be surprised in the slightest to find Microsoft Office on WP7. As people start to use these more at home, they'll slowly start to creep into offices as well. I don't know if Photoshop (or anything like it) exists on a mobile OS, but the Photoshop interface seems like it would translate almost perfectly to a touchscreen. Again, as more people start to use it, more offices will start to use it.

Games like World of Warcraft and Skyrim are targeted towards the PCs because that's where the hardcore gamers are. But games like Angry Birds and Cut the Rope are on tablets because that's where everyone else is. But as hardcore gamers move to tablets, game studios will start building their games for mobile OSes. John Carmack has already moved Id in this direction, releasing their latest game on iOS, and it's only a matter of time before others follow suit.

Ergonomics are almost a non-issue. Almost every tablet owner I've ever seen has a stand of some sort or another, and many who do serious work also have a keyboard.

Which brings us to his last point that a tablet with a keyboard is "basically a desktop". This is about as useful as saying that a mobile phone with a bluetooth headset is just a phone. That hasn't stopped bluetooth headsets or mobile phones from selling like crazy, and the same can be said for tablets and keyboards.

I doubt the computer is going to leave wholesale, but I think it's crazy to believe that tablets won't start taking huge chunks out of their market share within just a few short years.

First, let's be clear that the term "brogrammer", tongue-in-cheek or not, is downright misogynistic.

But equally problematic are the common beliefs that spawned the term in the first place; that programmers must always be obsessed with technology above all else, and to appreciate things like sports, fashion, or fast cars is somehow "bad" or "uncommon" for programmers.

There are a whole host of programmers who despise guys like DHH for enjoying fashion and cars. They seem to believe that somehow, those traits detract from his skill or significance as a programmer. That Rails is a "bad" or "fashionable" framework because of those things and is thus to be avoided. This kind of thinking is just plain ridiculous.

The spectrum on programming ranges from a hobby, to a career, even to the lengths of an obsession. But no one should be expected to act like the "norm". A programmer that cares more about the latest Ferrari than the latest web framework is not necessarily an undesirable programmer. They're just a programmer with different interests, and no one should be treating them differently because of that.

>First, let's be clear that the term "brogrammer", tongue-in-cheek or not, is downright misogynistic.

No its not. It's a description of an attitude. When used in a job listing as "looking for brogrammers", then that job listing is sexist. The term itself however is not.

I've never met anyone who refers to himself as a brogrammer. Pretty much all I know about the term is what I get from it's construction and this article.

I take strong issue with the idea that celebrating masculinity is somehow automatically misogynistic. It seems to me that the term has absolutely nothing to do with women.

At the first sentence I was like "..really?" then you were like "DHH ... enjoys fashion" and my head exploded. He dresses like a high school kid.

We must realize that Ed Hardy under button up shirts two sizes too large is considered fashionable by some people. I've never met them, but I'm sure they exist.

I don't know a lick of iOS or Obj-C, but this line is absolutely true:

> The biggest boon to closures, for "regular" programmers, is the dramatic simplification of async code.

Consider the way it's currently done in Java:

    listener.addCallback(new AsyncCallback<ReturnType>(Parameters ..) {
        public void onSuccess(ReturnType returned) {
            System.out.println("Successfully returned!");
        }
    
    
        public void onFailure(Throwable thrown) {
            System.out.println("Unsuccessfully returned!");
        }
    });

This is unbelievably ugly, and yet this is about as easy as it gets in Java. In order to make asynchronous callbacks "easier" you have to instantiate an anonymous class with very precisely named methods.

It's not only wasteful, but the potential for error is huge. Closures could make this much, much simpler.

You also need to do this with closures if you have more than one method.

Possible privacy implications aside, this is awesome.

I am consistently astounded by how advanced AI techniques are becoming.

Echoing rileya, GSoC was the shimmering star on my resume when I applied for my first internship two summers ago.

Mine wasn't at Google, but at a startup that decided to keep me on and just got acquired, so it all worked out pretty well!

If you want to learn the entire Linux ecosystem, I can't recommend Arch enough.

From personal experience, don't try to install Arch on your machine unless you have another internet-capable device in hand. You're going to reach for ArchWiki several times.

Of course, ArchWiki is an incredible resource with great examples, so as long as you have it, the process is mostly painless.

Arch is kind of an intermediate Linux in terms of how much it will rely on your configuration. Not quite Gentoo, but far, far, far away from Ubuntu.

There's also a local installable mirror of the arch wiki. I don't know how often it's updated but if I didn't have multiple machines laying around I'd put this on my arch laptop:

http://www.archlinux.org/packages/community/any/arch-wiki-do...

Sure, they can complain.

But if they're going to, they should just impose more restrictions on using their code. Maybe even a copyleft license.

If you can't take the heat, get out of the kitchen.

If Sony were using my code in their product, I'd be pretty excited and proud to have created something that a huge company would use.

yeah, let's ruin it for everyone because of a few bad Apples.

I find Wikipedia's blackout to be lacking in expedient information, and I see those tweets as evidence.

No where on that first page does it say "SOPA", "PIPA", or anything about censorship. I think the use of bigger, bolder text would've gotten the message across better than the more aesthetically-pleasing splash page they have now. Imagine how much more backlash there'd be if it had a look more inline with that have http://smbc-comics.com

It comes off as an issue that Wikipedia cares about, but doesn't explicitly tell me why I should care about it.