HN user
Just another squirrel trying to get a nut.
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)
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.
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.
We are suppose to vote for people, sadly far too many people vote along party lines regardless of the qualities of the actual people involved.
Never said anything was offensive, I was merely pointing out examples of ways that one could remind themselves to change the batteries.
However if you insist on focusing one a singular viewpoint then I will remove myself from the conversation.
No it doesn't. It simply requires a reminder. On Jan 1, change the batteries. On June 1, change the batteries.
Of if you live in a majority of the US, when you change the clocks, change the batteries.
Neither of these schedules will sneak up on you. If you don't change them and it wakes you, it's your own fault.
Sorry to sound snarky, but it's not _that_ complicated.
Exactly. There is a huge difference in the following two statements:
1. "I hear you about X but we are doing Y anyway."
2. "I hear you about X and understand you viewpoint, however we need to go with Y because..."
I'm okay with #2. #1 will drive me away. And it should. It's disrespectful and basically tells the other person that you have no regard for their opinion and that you only ask to satisfy a rule or expectation. If you are aren't going to have a discussion about why Y is the solution and were going to do it regardless of what anyone else said, then why bother even asking?
You do see the irony in your statement right?
I suggest you examine why they are complaining. Are they being forced to work that many hours because of your process? Might want to rethink that.
Do you have so much work that it can't be done with your current staff in 40 hours/week? Hire more.
Is your management so inept that your employees are forced to work more to keep up? Training will help.
Many people will willingly work extra when they need to (trying to squash that one last bug or trying to squeeze in that new feature) but rail when it's expected and demanded for no legitimate reason.
Because semantic actually means something, it's not a subjective term.
Calling something Semantic UI and comparing it to another library, that more follows the actually meaning of semantic, is silly. Yes you can change the class name but setting up the name as something meaningful, something semantic, such as 'submitButton' lets you redefine it in the CSS.
If I'm building something that multiple clients will use I don't want each client having buttons with class names specific to the client, but something I can modify easily in the CSS to get the look and feel they want.
It's ass backwards.
The average weight loss is supposedly that. Not everyone falls into that range and so long as you are eating enough to live, are enjoying yourself and not starving to death and are getting exercise it's not dangerous.
That said, he (and anyone doing it) should probably check in with the doc just to make sure something internal isn't getting out of whack.
Anecdotal speaking, when I moved from the Southern US to the Northeast I developed allergies that kicked in during late spring.
Someone suggested this and all I can say is that after a few years I don't have the allergy attacks anymore. Not even when I mow the lawn.
Since I stopped taking Claritin or anything like it I can only assume the honey did _something_.
It shows they have passion, drive, dedication and an eagerness to learn from others
No, all it shows is that they wrote some code and put it on a website.
The developer that has just a resume might be just as (or more) skilled that the one that uses github but for whatever reason can't post code up like that. To exclude someone simply because they don't have an active github is foolish.
However did you screen, interview, and hire people before github came along?
Sorry for the diversion, but what is/was it like to be able to ace a test without really studying for it?
Fairly anti-climatic. For someone that it comes easy too there is no real emotion or sense of accomplishment.
It would be like trying to explain the color green to someone that was born blind.
HN rules say to use the original title unless it starts with a number or has the name of the site, etc...
So it's not editorializing, or if it is, the NYTimes is the one doing it.
You aren't looking at the entire picture. Some have trouble in interviews because of learning disabilities and social anxiety but do well in the workplace once they are comfortable with the people.
Add to that the fact that most tech interviews are held in non-real world situations and it's easy to see why some people have problems. Putting a person in a room with a piece of paper with a chunk of code that has a 'hidden' flaw with no access to any other resources isn't real-world.
All of us have access to books, manuals, the code, google, any number of places we can use to help.
And usually these interviews focus on nuances of a language or a programming trick that you only know if you've seen it before or encounter it regularly.
The codebase I'm working on now targets the iPad. If I were to interview with a company and the tech reviewer asked me about an IE specific hack chances are it would take me a while to come up with it. Assuming I've encountered it before.
In the age of the Internet will that actually work though? It would be be that hard to find the names.
Undoubtedly some will see this as a success and use it against writers/devs they don't like in the future. Needs to be nipped in the bud now by reporting this people. These are legitimate threats, not jokes.
Network. Talk to people be it in chat on a social network on the people next to you on the highway. Reach out to people on HN. Search through Linked in and send messages. Search google for dev blogs and email them. Search github for people in your field.
Make connections however you can. That way if something does happen you can reach out to them to see if they know someone or might know someone who knows someone that can help.
Worked for me (and many others) in the past.
Because you are cutting off part of your potential candidate pool and increasing the chance of choosing someone who has no practical experience other than working on OSS projects.
If you can't distinguish the difference between a talented dev and someone who has managed to BS their way into a job I submit that the problem might not be with the developers you are looking at.
The most evocative map for me was the bonus one. I could only color in 2 countries (and 1 is my home country).
Makes me want to explore the world more.
It 'selects' all the section nodes. That's what .only() is for.
Sizzle is one of the engines we are checking out. Is HTML.js better? No idea. Worse? Same answer.
HTML.js is still smaller (a huge factor for me right now) and less 'robust', but that isn't always a bad thing.
For you they must answer those questions. For some (like myself) these are enough. I don't need or want to load all of jQuery unless I'm using more than just DOM selectors and manipulation. The projects I'm working on now all target the latest browsers so I don't care about IE 6/7 or backwards compatibility.
Yes, I could write one myself but this way I don't have to maintain the codebase. Nothing is a 'one size fits all' solution but for some this is a good start.
My point being don't dismiss it just because it doesn't fit your needs right now. It's still worth taking a look at.