The price of solitude is effort. Don't want to share nature with others? Walk a mile and you will filter 99% of humanity. Three miles uphill will filter 99.9%.
My trip to the Grand Canyon was tailored for solitude. We drove hours to get to a trailhead on the North Rim, hiked a a steep trail down, camped (by a hard-to-believe falls/spring), and hiked up and out by moonlight to avoid the heat. I don't mean to sound hardcore - I'm really not - I just like solitude and that's how you get it.
I'm ambivalent about this particular proposal. Exposure to nature creates naturalists. At the same time people ruin nature - the experience of it and it's physical environment. It's a balancing act and I have no idea if this is too much or too little.
I like your idea of coding up your resume - it shows competence and a desire to learn and build. I recently did the same thing.
But there is a first-impression problem. Obviously design skill is not what you are trying to demonstrate, but it's the first thing people see! Some people might read the code (and appreciate it), but even they won't jump right into doing that in the first few seconds.
I'd suggest copying the heck out of a good-looking online resume, and then subtly tweaking it to your taste. Subtly.
I'd also suggest hosting this on it's own. It will look more professional. (Github pages is a slick, free way to go.)
Your question was about whether someone would hire you as a dev. Yes, I suspect they would! Especially if you find an employer that has at least a passing interest in your operations/systems experience. I would look for a software company that works in this area (maybe one of your frequently used vendors?) - they'll eat it up that you know the domain.
It might be time for me to stop worrying about IE8 and embrace `transform`-dependent icons.
I regularly create one-off semantic icons as long as they don't rely on `transform`. That limits it to ones based on a character glyph - (i), (?), (x), etc - strictly orthogonal blocks - (+), (-), etc. - or CSS triangles - mostly arrows (which don't always render great anywho).
I'm always too concerned about the fallback in browsers without `transform`. But really, that's illogical - it's just IE <= 8, and generally don't need to worry about that support anyways. I guess my hangup is that the meaning of the icon gets garbled when it isn't displayed correctly in older browsers, and that seems like it crosses a line. (Thought about the "semantics" of an icon quickly feels like Philosophy 101 and probably means its time to get back to work!)
As others have pointed out, I wouldn't use the pixel-based positioning/widths as this does, but `em`s, `rem`s or `percent`s. Relying on `tranform: scale(x)` would complicate layout flows - for one thing you'd always need to compensate for the scale with `margin`, `padding`, or other pixel-budging.
In the early 2000's I worked in a school system that used a faux-email system where un-sending messages was completely possible. Any user could un-send messages that no recipients had read, which was _great_ as a user. Only sys-admins could un-send read messages. The only time I remember the latter happening was after someone got fired and flamed their way out the door. It was a bit chilling if you did read their messages before all evidence of their outburst erased by the invisible hand of the sys-admins.
IntelliJ is indeed java-centric (and not light-weight), but the front-end coding environment is top-notch. I've tried going back to a light-weight text editor (I'm still a sucker for TextMate) but I always come back to IntelliJ. The code completion for HTML/JS/CSS is phenomenal, and the way it intelligently switches syntax highlighting schemes regardless of filetype cuts down on my numerous, numerous typos (for example, if in app.html you write <div style="foo:bar" the HTML, CSS, and JS components will all be syntax-highlighted appropriately). It's also great for XML.
(I also happen to work on an app with a Java backend so it's a no-brainer, and the company's paying for the software...)
EDIT: Just realized you were referring only to the CE, which I've not used. I'll leave this here as a _non-sequiter_ opinion on the paid version nonetheless.
My trip to the Grand Canyon was tailored for solitude. We drove hours to get to a trailhead on the North Rim, hiked a a steep trail down, camped (by a hard-to-believe falls/spring), and hiked up and out by moonlight to avoid the heat. I don't mean to sound hardcore - I'm really not - I just like solitude and that's how you get it.
I'm ambivalent about this particular proposal. Exposure to nature creates naturalists. At the same time people ruin nature - the experience of it and it's physical environment. It's a balancing act and I have no idea if this is too much or too little.