Check it out: OOCSS and Basscss (Modular CSS toolkit based on OOCSS principles)

My ex-colleague Eric de Kock posted a link to the Basscss site on LinkedIn and I made a note to check it out when I use it on my next web project.  As a “back-end” developer, I’m aware of OOD principles, but not of OOCSS principles.  Turns out it’s been around for a while.

Back in the days when I worked with Eric’s team the designers would send us HTML and CSS that we had to use as close to what they gave us as possible (seeing that time we used controls we didn’t always have control over the generated HTML).  Whenever we had to make changes to the provided HTML we had to run it by them first.  Wendy Robb was especially good at creating awesome CSS and HTML and taught me a lot about this “other” world.  Reading through some of these OOCSS principles I remember some of our conversations fondly.  Good times 🙂

So, back to Basscss – this looks like something that even I (as non HTML and CSS guru) can use to follow the OOCSS principles and not paint myself into a CSS corner.  Looking forward to using it 🙂


Check it out: A JavaScript introduction for new programmers

Skez on SharePoint sent me a link to JavaScript For Cats the other day.  It’s a pretty cool and fun introduction to JavaScript.  I like the examples (even though I have two dogs) and the general tone of the article.

Check it out: How to fail at ORM

I read this blog post titled How to fail at ORM.  Sometimes hearing what you should do to fail tells you exactly what you should do in order to succeed. 

I haven’t used ORMs but usually people don’t seem overly excited to use them.  I can’t comment out of experience, but this post sounds like some good reasonable advice. 

Using an ORM sounds like committing to a relationship.  As in any relationship, when committing to it, do it well, be in it for the long haul, play off each other’s strengths and keep your eyes wide open – after all, love conquers all 🙂