Every time I'm working with more than two people, there's always this one guy in the team who doesn't know how to format his code properly or simply doesn't care. Don't get me wrong, I understand that sometimes you don't have to carefully comment every single line, align columns etc. but I believe coding is an art and as an art it has to follow certain conventions. I'm going to share some of them with you. These are the set of rules that I always follow when writing code that I'm going to post publicly or commit to repository for other people to use.
The only thing that is keeping me with Macbooks and Apple in general is not that their products are so great, durable and fun to use, it's the competition that is made of crap and there's no real alternative to them. I mean - come on, Windows 8? Linux on desktop? These are definitely NOT the pinnacle of usability and productiveness for web developer. I could build a Hackintosh but they work horribly most of the time. So I'm stuck with a MacBook.
Don't get me wrong - MBPs were great when I first got one. I had a lot of adventures with it, I dropped it, replaced lots of parts inside, it has scratches, it's dirty but until I screwed up a screw (pun!) during one of many fixes, it was the best laptop ever.
Now I have a new MBP, mid-2012, non-retina model. It's made of crap. Seriously, it's fragile like shit, I actually cracked the front glass just by simply tapping the case lightly with my elbow. And now I've discovered that bottom part has a small dent. A dent! It didn't even fall yet, what's going to happen when I accidentaly drop it, I'm going to end up with $1500 paperweight?
This situation is more than annoying for me. I'm too careless for such a pricey toy that's so easy to break. Yet, I cannot use any other OS, simply because they suck (yeah, yeah, I know, 2014 will definitely be linux on desktop year and Windows is actually useful when you get used to shoving a knife through your eyesocket every time you have to deal with it).
Maybe I should've became a farmer.
Do not use a "debugger". A debugger is like doing a full-body scan on a sick person. You do not get any specific useful information, and you find a whole lot of information that doesn't help and is just confusing.Learn Ruby The Hard Way
To be honest I have no idea why Zed Shaw is endorsing this book as it's 1) confusing, 2) have errors and mistakes in code due to it being translated from Python to Ruby and 3) is sometimes simply wrong about stuff. Oh, and it doesn't cover even most rudimentary metaprogramming.
Ruby isn't cool any more. Yeah, you heard me. It's not cool to write Ruby code any more. All the cool people moved on to slinging Scala and Node.js years ago. Our project isn't cool, it's just a bunch of boring old Ruby code. Personally, I'm thrilled that Ruby is now mature enough that the community no longer needs to bother with the pretense of being the coolest kid on the block. That means the rest of us who just like to Get Shit Done can roll up our sleeves and focus on the mission of building stuff with our peers rather than frantically running around trying to suss out the next shiny thing.Jeff Atwood