adeaver

This took me a bit as well but there is a small bit that is editable, but I agree that it isn't clearly defined, especially when it's only a few characters and not an entire line.

Hint: Phone functions

But then you are paying for the hosting and dealing with the maintenance. At that point is's easier to switch back to Dropbox. (IMHO)

That's interesting. I have yet to have any issues with D3 working in IE8 and above. Don't really care about anything below that but so long as it support SVG I would imagine it works.

And I've also found HighCharts extremely limiting. I ended up having to break things in HighCharts to meet some requirements. Granted that's a project problem not a HC problem, but D3 made much more sense for me.

To each their own :)

They actually shouldn't, assuming I'm understanding you properly. class should never describe the content but should instead be generic. So rather that class="big_red_text" it should be class="alert_text" or something

Like others have said, if your boss is calling you at 7PM to do a worksheet for a meeting the next day, one he has likely know about for a while, then worrying about your work/life balance is the least of your problems.

As it's not so much the occasional 'Crap, we need X stat!' that is a problem, it's the constant assumption that your boss can call on you any time and _expect_ you will comply.

That's just a shitty boss. Regardless of their title.

Odds are no, I won't do anything to the code. Why? Because for one, it would likely take a bit of time to 'make it decent' and secondly, by the time I've been informed that Project X will be talked about the interviewer has already looked at it.

If I change it at that point then I'm either being disingenuous or taking away the aspect he wanted to talk about.

All that said, if I put my github url on the resume then it's fair game to _talk about_. My point is (same as the articles) using it as a filter is generally a bad idea.

Except in a live coding exercise most people are trying to be efficient or 'to it right' and paying attention to what they are doing and how.

I realize this is anecdotal, but 95% of the public code in my git repo is stuff I did as fun. I didn't care about being right, or care about memory issues or being thread safe or anything other than 'I wonder if...'

In that instance, and I suspect a lot of other people public where they aren't contributing to something using the repo code as a talking point is counter-productive.

Why did I do it that way? Because I wanted to see what would happen.

Except he's doing it because there is (to him) an impression that the original software isn't being maintained. So instead of letting a beloved piece of software disappear he cloned it and released it to the world.

The presumption that he's trying to destroy the original developers livelihood is naive at best.