[thegooley]

Looks like it was heavily inspired by this (from ~2010): http://culturedcode.com/status/

And I really like the concept, but I believe that the value of a "status dashboard" is that it's a concise view of what's happening right now. I really don't think that this sort of concept is a good resume replacement it's not a good format for 20+ items.

I'd suggest making it a status dashboard for what you're working on right now, and once things are "completed" they drop off into a bulleted list at the bottom which becomes your "work log" rather than "dashboard" at that point. Make it less overwhelming and I could really see a recruiter or business partner getting some good info from it.

[snowwrestler]

Software company status boards are not uncommon; here's another one from ~2010:

http://www.panic.com/blog/2010/03/the-panic-status-board/

[eps]

I'm partial to visual design and I'm fairly certain CC's dashboard wasn't an inspiration here.

They share inverted palette and a grid layout, but other than that if you set out to design a "cool" looking and functional 2 column table, it'll end up looking as posted project. There are just too few convergence points for this sort of design pattern.

[justindocanto]

OP, theres some things you should definitely consider in here. ^^