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.
It's better to host it in your own home. Everyone has an old computer with more storage space than you can ever afford from Dropbox. All you have to pay for is dynamic dns (which is useful in many other ways). "Maintenance" is a bad criticism. Use some stable distro and run apt-get update && apt-get upgrade once every couple of months.
With the sterling reliability of the average residential ISP... For what it is worth, home runing is a viable option for many uses: I do run a server or two at home myself but important things are out in external DCs too.
> Everyone has an old computer with more storage space than you can ever afford from Dropbox
For transfers maybe, but are your really trusting an ancient box of parts long out of warranty with your long term storage?
> "Maintenance" is a bad criticism.
It isn't criticism (as it "this is bad and it is their fault because of how they've designed the product"), it is a perfectly valid concern when considering whether to run a service for yourself or pay someone else to do it for you.
> Use some stable distro and run apt-get update && apt-get upgrade once every couple of months
Remind me never to employ you as a sysadmin! There is (potentially) a lot more to it than that. what about setting up backups, monitoring those backups and testing those backups? What about connectivity: if you home connection goes down of you have a hardware failure while you are mobile who is going to fix it? If there is a fault with your physical line how long is it going to take to get people out to fix that?
You might not find those issues to be relevant to your (storage of and) access to your data, but to some people they are vitally important and need considering.
I'm actually planning to test an OwnCloud install for myself and family & friends, it looks like the feature set covers out needs quite nicely if it works well enough, but I can assure you I'm giving the above things all due consideration and I don't consider it "bad criticism" to do so (for my own data at least: friends and family will be told the service is free to use at their own risk!). I may even suggest we run an instance at work if my experiments with it go well, as we could use such a service but the nature of some of our data means that we can't trust it to 3rd party services.
No one ever said a DIY solution was going to be as reliable as a proprietary service, just that the relatively low risk is worth it for your freedom. I personally would never use Dropbox since they don't open source their technology.
> Everyone has an old computer with more storage space than you can ever afford from Dropbox.
Weird definition of everyone, even in the HN reading crowd. Lot's of twenty-somethings have moved several times in a short amount of time, and tend to ditch the cruft. I know I did.
It's referencing Microsoft back tracking on the XBox One being 'always connected' and calling homebase once every 24 hours. The removed that functionality after a huge backlash o the 'Net
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.
Let me be clear...for my own personal projects and works, D3 is the way to go. It makes the most sense for the crazy ideas I have, and from my limited perspective, just seems to be the best API among all viz libraries.
But in the domain of common chart type that areperfectly serviceable, clear, and customizable...there's not much choice. Google Charts seems like an easy win because hey, it's Google. It'll definitely be around for at least a few years, as it seems to be the dogfood tool for Fusion tables and other Google products.
But other than that, there's not much else that seems to be widely adopted. Raphael is more of a visualization library and seems to be going by the wayside after D3. Highcharts, in this context, seems to be an all-out winner compared to Google Charts, and against most of the D3-chart-wrappers that I've seen so far (Rickshaw, nvd3, etc).
I've heard of it but thought it was for the domain of python development...which is not a downside, per se, but doesn't always fit the project requirements of "here's some data, now throw some javascript on a page and show that data"
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
FYI, big_red_text is presentational (specifies size and color, while saying nothing about what the role or purpose of the text is) while alert is semantic (describes the content, says nothing about presentation).
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.
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.
I occasionally do interviews for my company, and I use Github in the manner that fecak describes.
Before the interview, I will check out your stuff and make sure I have compilers/interpreters for your favorite languages (as best I can identify them). Then I will do a combination of live coding, and talking about repositories that might have caught my eye.
In this kind of situation "Why did I do it that way? Because I wanted to see what would happen" Is a great answer. It leads into a discussion about what happened, and whether or not you would do it again (without waiting half an hour for you to work through a problem of my devising). I could not care less whether the code was good or bad if you can show that you analyzed the experience and learned from it.
Part of writing good code is having written bad code in the past. I get that. I'm a programmer myself.
Now, we do not use Github as a filter (as the article discourages). If you put your Github in your resume, I will use it to make the interview itself a more valuable experience for both of us. If you chose not to put your Github on your resume, then you will get the generic interview, and I might not have your text editor/IDE ready to go.
Sure, but if you were aware that your public git repos would be up for discussion in an interview, you might go back and switch some things up, no? At least a handful of times, I know that the repo that would be discussed was referenced before the interview as an agenda item - "we'll talk about PROJECT A from your GitHub account".
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 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.
The intention doesn't matter, the effect does. We are talking about risks of doing business with developers (which reimplementation is), not about some abstract morals.
That is still different than voting for a party. In proportional representation you would cast your ballot for e.g. The Democratic Party. If they got 54% of the vote, they would get to then appoint 54% of the representation for that district. In this way, a very heavily Tea Party district would still have representation for the democratic minority, just less.
> In proportional representation you would cast your ballot for e.g. The Democratic Party.
You are confusing "proportional representation" (which is a continuous-valued property of many election systems) with "party list proportional" which is a particular election system for achieving a high value of proportional representation.
Notably, Single Transferrable Vote is a system in which people vote for candidates as they do in FPTP elections (except using preference ballots), but which is designed to acheive proportional representation.
I don't have any clocks that need manual changing. Haven't for years. And I rarely know what the date is unless some external stimuli makes me check. It's just not relevant to my daily life.
Your experience is not mine, and mine is not yours. Why is it so offensive that someone has tried to make my life better? Is it just jealousy that they didn't work on one of your problems?
I'm not even really conscious of microwave clocks still being a thing. I guess my microwave probably has a clock, dunno why I'd ever set or use it, though.
I just checked, apparently my stove has a clock, too. It's not set to anything resembling the current time.
Neither of these appliances are things I would ever look at when I want to know what time it is, so I just file them under things that are not clocks.
My clocks no longer require manual changing, and those that do I end up replacing... I haven't been sure when daylights saving time starts/stops for a while now and have been caught off guard when I end up being early at work because my body naturally woke me up at a certain time.
Hint: Phone functions