digitallimit0

Are there any other hard and fast rules I should be aware of?

I was just reading up on the Graph API Facebook uses and its pattern is just api.test.com/1234/students. There seems to be very little standardization. The tutorial I'm reading right now wants me to pass the id in as a parameter. Weird.

In terms of a RESTful web service, is an object's id supposed to be passed in as a parameter in a GET request, or be a part of the core URI, e.g. api.test.com/teacher/1234 would retrieve the teacher of id=1234 or api.test.com/students/1234 would retrieve that teacher's students.

Is api.test.com/teacher?id=1234 more kosher?

Huh, the back button worked perfectly for me in Chrome, OS X Lion.

My experience has been exactly the same as yours. My current career and company that I'm entirely excited be a part of never had me write code once during the interview process. I graduated an accredited college with a high GPA and had programmed in a student position for 4 years, at a startup for a couple months and a contract-to-hire governmental position for 1 month. Not the craziest experience, but I think it's silly to be so cynical to assume I can't write a simple fizzbuzz program after all of that.

For the Lanyrd team: when exactly are you caching the data? Is the expectation that I browse the events I'm going to attend in advance while logged into the app and you dump all viewed events into localStorage? As well, on first visit to the site I imagine you have some sort of if-storage-is-empty-and-logged-in dump to get the site scripting and design in there, and then just feed off of that afterward?

I'd love to hear more of the technical side as I'm just getting into HTML5 but I haven't sunk my teeth into some of the crazier aspects outside of playing with canvas and familiarizing myself with JavaScript and its associated libraries.

In Chrome, Windows 7 the CSS3 circles in the background shift around when you highlight anything or expand one of those info boxes.

The thing is, those aren't fair comparisons. Software engineers are in exceedingly high demand at this stage. This is just a reaction to that demand. In addition, software engineering is a very flexible field. You can engineer under or tangentially to almost any position or field and be a part of what makes those things interesting. Assembly line worker and street sweeper are not so similarly blessed.

Yeah, that confused my balls.

If you can't build a little house for your little dude and have him drive a little car to his little job, it's not comparable to the Lego brand. There's a sort of imaginative vicarity at play. This toy is far more abstract.

I would really like to see specifically Computer Science majors versus the rest of these majors, mostly because Math is not nearly as employable in comparison and is probably dragging down the numbers.

I'd like to see this because of how disparate my experience was when applying for jobs as compared to anyone in any other field, I being a recent CS graduate.

Basically, I can apply for 4 jobs and get 3 interviews and 2 offers. I can turn around from unemployed to gainfully working in an easy month. It's crazy, and I feel like there should be some numbers somewhere that show that.

Yeah, by being a "PHP developer" rather than say, a Zend developer, he was making that right-hammer-for-the-job argument back in the original article long before ircmaxell got around to implying anything else. I think there's a lot of agreement here that got lost in "simple isn't always better!"

His last bit on the latter part of the manifesto "I like simple, readable code" seems pretty unnecessary. I doubt the original article's author would argue against good coding practices like abstraction layers. And really, the example he provides doesn't even stand against "simple" or "readable". Abstracted code is exactly that.

cloud could could cloud

Love the list. Favorited that for future-use with spicing up my life.

It's not the shoe that's solving your problem, though. The trick is to run on your forefoot and roll back to your heel. That's it. That said, it's true that the key difference in the average running shoe and the Vibram line is the lack of heel-cushioning, which as a result encourages correct running, but I felt it pertinent to clear that up.

tl;dr run with an impact front-to-back, toe-to-heel.

It is honestly baffling to me that DICE has not addressed the "need to press the jump button to get over curbs and small rocks" issue since even their very first game, an issue ironically even more prevalent now with the added details afforded by advancing hardware. I do appreciate the leaps (hah) they've made with their vaulting system, but it too has its own frustrations.

Almost all of this reminds me of OkCupid.