News for hackers. Stuff that matters.

gerfficiency

Re:From Python to Numpy on Tuesday January 10, 2017 @09:43AM (#13365089)
I really appreciated the problem vectorization chapter. New approaches require new thinking and this is often forgotten when teaching new concepts.
Re:How Cheese Curls Were Invented on Tuesday November 15, 2016 @08:08AM (#12957633)
I've read some interesting facts I didn't know, but how about how unhealthy they are?
Re:The DevOps Handbook on Monday October 03, 2016 @09:03AM (#12627115)
I wish it was possible to take the DORA DevOps X-ray Assessmnent for free, before deciding on whether to buy or not to buy the book.
Re:Spotify in Talks to Buy SoundCloud on Thursday September 29, 2016 @08:29AM (#12604716)
How would they monetize it?
Re:Partnership on AI on Thursday September 29, 2016 @05:38AM (#12604164)
Nice. I'm sure the NSA wants in on this partnership as well!
Re:Show HN: Vectr – Free Online Vector Graphics Editor on Thursday September 15, 2016 @09:45AM (#12506036)
Finally, Vectr is out of Beta. Nick, the CEO of Vectr will answer any questions.
Re:Tesla is suing oil industry exec for impersonating Elon Musk on Thursday September 15, 2016 @05:22AM (#12504546)
For impersonating Elon Musk... to get confidential information.
Microsoft has a document (KB257757) strongly recommending you not try to use Office server-side. They have some recommendations on what other things you could do instead.
Re:Excuse me, your code is bleeding on Thursday September 08, 2016 @02:31PM (#12455800)
Putting the TLDR here because it's really good, and the minimum that one should take from your great article:

The takeaway here is that not all third party code will jive with your app’s intentions. Not all developers take security precautions. Not all libraries on NPM are worthy of being a part of your application. The moment your own code becomes the minority shareholder in the repo and you’re depending more other developers around the world to keep your company afloat than you are yourself, you better make sure you have vetted the code upon which you’re depending. If the head of dev-ops tells you you can’t use a library, trust her judgement before resorting to Millennial cynicism.

On our own projects and experimental R&D efforts, let’s have at it and make bleeding edge code that changes every day. In a professional environment on code that will be used in production in E-Commerce scenarios, though, for the sake of all that is sane in the world, let it bake. Let the community vet it for us! We need to build sites on stacks that don’t implement breaking-changes every week simply because the primary contributor had a stylistic change of heart. We need to use libraries and frameworks that recognize exploits and take extra security measures. Customers trust us with their personal information, credit card numbers, photos and media. We owe it to them to give a shit.