jwingy

I like mayo but pretty much all shelf mayo is made with oils that are bad for you. Even some brands which claim to use olive oil primarily use another oil with olive oil further down the ingredient list.

I wonder how Facebook would feel if all the open source software they currently use incorporated the same license. I bet it would deter them from enjoying much of the code they built their business on. This stance seems pretty antithetical to the goal and spirit of open source software and I really hope it's not the beginning of other companies following suit and 'poisoning' the well of other open source projects.

I wonder how Facebook would feel if all the open source software they currently use incorporated the same license. I bet it would deter them from enjoying much of the code they built their business on. This stance seems pretty antithetical to the goal and spirit of open source software and I really hope it's not the beginning of other companies following suit and 'poisoning' the well.

I don't understand the value of this over simply building a mini ITX system for cheaper and equal/greater performance? The only advantage this has is being able stay portable with the external GPU but $500 just for a dock is insane.

There's some decent questions here, but also too many "how to" questions that most people won't bother memorizing since they take 2 seconds to google.

This reeks of forcing a parent's goals and ideals onto their children which in the situations I've seen tend to never end that well. Encouraging them to do what their genuinely interested in I think would probably lead to much happier lives.

A significant impediment is handling peak usage power. Maybe solar can provide most of our energy needs, but for those times where peak power is needed, it's probably more sensible to take a more balanced/mixed approach.

*edit looks like the article has a convenient link to another article talking about this exact problem:

http://www.vox.com/2016/2/12/10970858/flattening-duck-curve-...

Whether "millennial hipster game developers" are actually lazy or not seems to be besides the point. Hasn't it already been consistently proven that working more than 45 hours is much less productive than a steady 40-45 hour work week? What's the actual business justification for that besides massaging egos or trying to enforce some masochistic culture?

Wow never knew. That's a pretty huge barrier that more people should know about.....

There's also the swagger spec:

http://swagger.io/

CALM and CRDTs are interesting stuff.

That being said, I feel like the author is confusing a bit the specific implementations of modern APIs vs the concept of an API which I see as simply some (somewhat standardized) interface to a system which you don't own. Those seem like two different problem domains to me, but perhaps I'm arguing over a different definition of APIs than from what the author is talking about....

I find it curious how people who are as smart and technical as programmers are, can come up with testing/interview methodologies that so clearly deviate from the actual day to day activities of what that position will probably require.

There's definitely value in asking a candidate questions face to face as there are times when problems need to be discussed, but clearly there's a non-trivial segment of the programmer population that has trouble performing under this type of atypical situation.

Why not also have a sort of "written test" portion of an interview where the candidate doesn't have to stress out about performing in front of people they don't know? It would certainly help reduce the flagging of false negatives.

EDIT: by "written test" I mean something like a test where the questions are on a piece of paper or text file, and the interviewee just answers it on there, without another human sitting there and staring at them. The interviewee can always be asked to explain his/her answers afterwards.

You missed another benefit towards API first development: it makes it much easier to get a head start on mobile development as you can reuse many of your endpoints for common operations.

I think you're mostly on the point, but unless you have serious inside knowledge, I don't know if you can really assume PRISM is about national security and not about other nefarious purposes.

New York, NY - Brooklyn Museum - Front-end Developer (Full-time):

We’re looking for a creative individual to help us in a key role working with a small team on our website, mobile, and in-gallery interactives. We’re searching for someone who’s adept at the full stack and looks at legacy code with love while finding creative yet sustainable workarounds to make us more nimble and responsive.

In addition to maintaining our existing CMS, you’d be working on a variety of web and in-gallery projects related to art, community, visitor experience and open access. Recent in-gallery kiosks maximize webkit's CSS3 and JavaScript capabilities to deliver the best visitor experience possible with web technologies. Previous projects included Split Second: Indian Paintings, an online experiment and in-gallery installation exploring visitors’ split-second reactions to our Indian paintings collection; and GO, a Brooklyn-wide open studio event where artists opened their doors so community members decide who would be featured in a group exhibition at the Brooklyn Museum.

Skills checklist:

- Deep understanding of user experience and interaction design.

- Solid working knowledge of object-oriented programming principles, PHP, JavaScript, and relevant frameworks like MooTools and jQuery.

- Solid understanding of browser quirks and web standards up to and including HTML5

- Working knowledge of Photoshop

- Familiarity with version control, e.g. SVN, Git

This is a fun, friendly, and fast-paced environment and we keep the commitment to a 35 hour week. To apply send your resume, cover letter and salary requirements to [email protected].

I did a startup then got out for precisely the same reasons the author states.

You won't always be young, but a startup at any age is always possible. Since money will never be able to buy time (though I'd love to see a time machine or a reversal of aging), I chose the former. I don't regret doing a startup, but I'm happy where I'm at today. Getting my head out of the rat race has been one of the best decision I've ever made.

On a related note, does anyone have some informed opinions on the best type of business entity (e.g. LLC vs S-Corp vs C-Corp, etc.) to set up for a consulting business such as this?

It's an article focused on Singapore. Exec hasn't launched in Singapore yet afaik.

Maybe I'm not understanding it correctly, but on the point about "it's ok to block", does that mean Go will continue to serve other requests normally, but at the point of the blocking code, it automatically has a "callback" to the next command? (effectively saving the programmer the pain of having to write code in callback fashion)

Having no prior experience with Go, I found the rest of the article informative!

The worst part about an article like this is someone will take this seriously and believe this is the path towards "success".

Well, sometimes saying you're profitable is important to the topic at hand, and sometimes it's not. If it is and you gloss over the details, people will find it less helpful, and I personally have less confidence the author knows what they're talking about. Everyone has their filters and this is part of mine since there's so much bullshit out there. If you want to call that pedantry go ahead. No sweat off my back.

The disagreements in just these small sample of comments is a little bit of an example that people don't always have the same idea of what 'profit' means no matter how well defined you think it is in the lexicon. The alternative is to always take what people say at face value, but then that can be a little bit reckless as well.

This is definitely not a useless article. If you've ever read an article or blog post where someone is talking about how they built their business and said something about being profitable at some x point in time, then they proceed to NOT describe what they exactly mean, then I just end up disregarding the whole thing because I can't take what they say at face value. I'm glad someone spoke up about this because it should (hopefully) mean higher quality articles in the future.

Working longer hours also seems to be counter-productive over the long run:

http://news.ycombinator.com/item?id=3707101

It's kinda funny, because I often think this way but in the opposite direction. How the hell does one build a socket anyways? (Yes I will go and google this now so save your lmgtfy links :))

As someone who was taught the 'traditional' way of mathematics, can someone give a few pointers of de-programming myself from the traditional way that I was taught? (Although maybe it won't be so hard since I feel like I've forgotten quite a bit)

Someone already recommended this for calculus which looks pretty promising: http://www.gutenberg.org/files/33283/33283-pdf.pdf

It's also much quicker to parse through text than to wait for someone to say it, even if they are a fast speaker.

I would say the persistence needed to make something does make it hard. I understand what you're saying, but I don't think you can say it makes it any less difficult to ship something.

I had been doing my own research recently on 2d frameworks and engines to use, and while I don't have any experience with the following, they do seem to have a fair amount of respect within the game dev communities:

https://love2d.org/ http://www.sfml-dev.org/