skysight-inc/HackerNews huggingface dataset:
I am a robot is a good question is whether they are willing to pay enough to make the juice worth the squeeze in a few days ago and I kept meaning to take it to the post office is located in the city of the time and a half is leaving for an archeological dig in the Outer Banks and other things that I have been sent by God to bring social skills to the neckbeards of Reddit email this morning and the fumes were still really strong and it sounds like you to know if you want to get together and send an emissary to travel to Rome to ask that the Vatican support our plans to retake the town where I grew up in the numbers until next week and I just woke up at the end of the quarter when annual bonuses were disbursed the same time as a result of the time and a half is leaving for an...
One issue with how developers are hired these days, is many large companies are hiring largely for classical knowledge (aka, memorizing: Algorithms, DS) and mathematical ability. Try interviewing at MS, big G or Amazon and you will see what I mean.

These developers are great as code monkeys, but a lot of them don't have any idea what their code contributes to, or even how their business makes money. I attended a hackathon with a number of Amazon employees, and one of my distinct memories was a Principal Engineer who didn't even know what "publicly traded" meant and was sure that Bezos owned 100% of the company.

A potential solution to this issue, is to hire engineers with more diverse skillsets. Deep understanding of mathematics and classical algorithms is fantastic for software performance, and low level details.

On the other hand, at a tech company - your software is literally your revenue stream. You are hiring people who don't understand your business - to build and grow your business.

Maybe hire some developers with strong business skills, and a good understanding of the economy and your market - and put them on a team with more traditional engineers. In doing so, you get someone with the big picture, and someone with the details working together and might not even need another PM.

Just my thoughts.
Compiling nginx would be a lot easier if they would stop hard coding so many things in the makefile. Enabling libc hardening (aslr, pie, full relro for example) requires manually editing generated files before compiling and overriding his ldflags, cflags, etc. I have reported this multiple times but Maxim didn't agree with me that this is a priority.
The best way to get regulated drugs is through the darknet. If take the time to do your research, and spend the coin to get lab tests, you can pretty much guarantee that every dose will be medical grade. Far safer than a street dealer.

The two best starting places are reddit.com/r/darknetmarkets and reddit.com/r/dnmavengers

Prioritize research and place limited trust in reviews, especially on-market reviews.
The subtitled versions of his speeches certainly shed new light on the guy. You realize how powerful (and potentially dangerous) charisma can be.
previous discussion

https://news.ycombinator.com/item?id=11023720
Looks really cool! I can see why you don't use it every day though :)
Elementary Java Components, 1.22 released
Smallest Federated Wiki's format is very similar:

https://github.com/WardCunningham/Smallest-Federated-Wiki/bl...
previous discussion

https://news.ycombinator.com/item?id=11021665
Firebase *was* down
Pfft, why should I feel guilty about openly advocating everyone use LSD anymore than advocating everyone learn how to drive knowing automobile accidents kills some huge number of people?
I think like most people in leadership positions at big companies, they can coast along on the success of the big company but they think it's all them. See also nfl coaches. When I was at google, she was such an ass to people. Many were glad to see her leave. I wish more leaders had humility about their success. She's got her 300 million, she'll be okay, but I doubt she will get an improved character out of this.
The intel compiler update 1 (16.1) was released in late 2015. It is available to download to all who have a license or are beginning a new evaluation.

For matrices of size 4000x4000 there was significant benefit for blocking the loops - please check the table again. This benefit continues as matrices continue to get larger. I specifically used two different size matrices as examples so that the reader could see that blocking is not a panacea or cure all. So as you point out for the smaller case there was no benefit - I wanted the reader to see that, so I included both data sets. The value of block size varies depending on the matrix size and the cache size of the system you are running on. When the data sets or number of iterations you are running on is relatively small (compared to cache size) the blocking will not provide benefit; don't blindly apply it. The matrix multiply was selected for pedagogical purposes - it is easy to illustrate and easy to explain. I was limited to article length - see the link to the article on finite difference methods for more on value of blocking. If you are really interested in blocking for matrix multiply there many other good articles that go into this in much more detail (and the fastest ones do block into submatrices and perform additional optimizations). (Please note the optimal blocking may be rectangular non square blocks - I did not code the general case.)
That sounds like a good idea, until you realize that developers with a strong grasp of coding AND business are rather rare. If you're a growing business, it's hard enough to find enough really good devs as it is, and now you want to add in another, orthogonal skill set? Good luck with that.
This is honestly an excellent essay, and you if you jumped straight to the comments, take my word for it; its worth the long-form read. Robin is a noted intellectual historian and he draws a great deal on that in this essay in particular.
Assuming force being applied along the axis of the spine, and that it continues, you would experience tunnel vision, lightheadedness, loss of consciousness, and eventual death. People can't really handle more than 5g on that axis without a special g suit.

Lesson: Don't try to take it standing up.
google finance has all that.
Worth a read - The dirty little secrets of transitioning away from Parse https://medium.com/@suniltom/the-dirty-little-secrets-of-tra...
Does anyone know if that works with sites behind a nginx proxy? I have Apache and Nginx and if that works for proxied content.
The link is already shared in the article. Good notes and good read.
And even when it wasn't possible, it was either done through IPMI web UI, through BIOS being able to do it itself off a fat32 file system mounted anywhere (including IPMI fake drives), or a bootable DOS-based CD (which also can be booted via ISO fed to IPMI).

Disclaimer: I run a medium sized dedicated server host. Hi.
Three if you count entropy.
Bourbon and Whiskey Sales Soar at Home and Abroad
Amazon checkout is down
I’ve been using ES6 modules in Ember.js development for two years now. Using Ember CLI is simplified down the dev process extreamly. The whole dev app development is so simple and fun with Ember. I don’t understand why people cry about it, the solution is exist, they should just use it. Thats all.
The inside story of Uber's redesign
Absolutely ridiculous price for something most people don't even know about.
Many developers prefer to work like Navy Seals or Jazz Musicians. It's objectively more empowering, arguably more fun.

Some jobs require an army or a big band, i.e., a lot of coordinated precision - objectively less freedom and autonomy, arguably more tedious.

Beyond some threshold of granularity you will crush morale though.

Do what makes you happy.
"If you're just doing one round of XOR it's pretty easy to break the key"

If you're doing two rounds, it's even easier!
The original version isn't actually valid POSIX BRE. It's a sed specific meta-character that is specific to sed and won't work anywhere else [1]. It's not part of POSIX BRE (which doesn't cover substations anyway). The zero width positive look behind is common to many more languages than just sed for doing that substitution. There is one version that will work in all of them, s/rump/rump kernel/, but it repeats the first word

[1] http://docstore.mik.ua/orelly/unix/sedawk/appa_02.htm
The gcc compiler does vectorize the code. I wrote that gcc 4.1.2 did not interchange loops automatically (ijk to ikj). Matrix multiply is very easy for a compiler to optimize and it is easy to use to illustrate principles. There may exist some cases where a developer may see the value in interchanging loops that the compiler (intel compiler, llvm, gcc, . . . )doesn't recognize. I pointed out how to see when the compiler does this with the optimization report. If the compiler already does it for you, don't bother with explicitly making the change - save your time for something else.
Geeky (single focus) developers are
- cheaper

- do not get distracted by politics / business

- easier to control / manipulate into lower salaries
I think context is important here. What is the software you are building? Is it highly critical or possibly life threatening, like a stock exchange trading system or a aeroplane control system? Should the developers be given autonomy to speed delivery? Or should more controls be put in place to ensure delivery of the quality, validated product while possibly slowing down the delivery speed.
I just did the same, but the problem is that (I only suspect here without research) the keyboard calls home every so often so your data isn't yours anymore.

I am now searching for a new keyboard...
It's like normal Facebook, which I don't think even the biggest of addicts treat as a synchronous system. The entire structure of the application is for you to post and consume updates at different times.

You're going to have a hard time convincing me that Facebook is synchronous when the entire power of News Feed (and what makes Facebook so much more powerful than Facebook) is its ability to keep you updated without requiring constant real-time attention.
Uber has a new logo. People hate it, but it doesn't matter
Problem is in any large organization the real (and inevitable) choice is "all of the above"

Relevant xkcd: https://xkcd.com/927/

The only way to win is not to play the game.
I converted legacy code to JS using emscripten because the company had severe constraints on the output of the code. In other words they didn't know why their code did what it did. (grin)
The story begins with a new feature request that the "business" thinks is needed while the "developers" think is not. It's really hard to pick sides here without knowing more about the specifics. I've seen situations where developers are completely wrong about the business value of something and I've seen it the other way around.

If the new feature was indeed critical to the business then the boss finds himself in a situation where one of the best developers spends months trying to build some DSL and comes back with nothing. So we can understand the frustration on the business side of things. This is where things started going the wrong way and there's a loss of trust on the ability of the technical team to deliver.

Now obviously the new PM and his buddies (I've seen this before) only make everything worse. "Jira" or "Scrum" or "Agile" wasn't really appreciated by the old team used to doing whatever they wanted to do.

I think the truth here is there has to be some sort of balance. Developers need to balance architecture and refactoring with delivering new stuff. They need to listen and have a dialog with product management about new features. There has to be trust. When there is trust there are less controls. When trust is lost it's almost an unfixable situation especially when you have a combination of a tech team that isn't delivering anything useful (from the business perspective) with management who doesn't understand software development.

Clearly the best situation is trust combined with good management and developers who take ownership and see the big picture. Then useful stuff gets delivered and things like architecture or refactoring get taken care of.
primaryobjects, thank you very much for a great article!! I am one of the developers for Concept Insights and I really enjoyed seeing the technology described by a 3rd party. Please let us know if you have any questions you would like answered.
Uber Rebranding
TL:DР He won't eat anything with taste.

The US system is absurdly safe for people with immune systems. If you are or cook for immune-compromised person - go on - incinerate the food.

Read the data yourself and make informed decision.
> "I've said it before and I'll say it again, we're too damn disorganized to be as evil as you think we are."

That's actually hilarious. Our defense is... our ineptitude!
It turns out that software development is a very immature industry. We simply don't know how to judge successful software projects/developers.

In the face of that immaturity we can try all kinds of things. Personally, I do anarchist development and hope for the best. Others try cargo cult project management. Still others move to highly constrained development methodologies.
Clever but useless.
Cold boot attack does not work on RAM with DDR3+.
Pretty much all new computers are safe.
http://superuser.com/a/464396
This is one of those wishful thinking rants that serves to highlight the rose-colored glasses many developers see the business world through. All good things eventually come to an end, and you need to be ready for the inevitable.

The author described two perfectly good responses for this scenario, and managed to paint them both as the cowards path. Leaving the company, and checking out mentally, letting the people with the responsibility hang themselves with their own rope. The company is bigger than you are, its decisions weigh heavier than yours. Stop with the ego-belief that you know better than it. It's cold comfort to be right, so just get behind management and try to make the new direction work.

I mean, come on, in the grand scheme of things, developers are wizards who never have to be worried about 90% of the things other people in the world have to worry about. These finer qualities of career enjoyment are nice-to-haves, not necessities. There's always good, solid ground to retreat to in case you get routed. Complaints like this remind me of a rich wanker bitching about the valet not putting his seat back the way he left it. Just adjust it yourself and move on with life. Life's too short to get mad about stuff like that.
Ask not what your left or right brain can do for you. Ask what both of them combined can do for your company.
What quests are, how to find one and why it's necessary – Chris Guillebeau
Her Stifled Identity: The Story of One Bangladeshi in India
"WebKit does have a Linux sandbox, but it’s not any good, so it’s (rightly) disabled by default."

I'd love to know more about why, that seems mad in 2016.
Some good points but the argument that software teams will be most performant as a result of autonomy really depends on the team in question.

I worked on a small team with 2 other developers who were both pretty good devs technically. However they treated the business side with almost-contempt and they would estimate even simple changes to take days.

As the most junior member on the team I couldn't really influence them. Interestingly, after about 2/3 months on the job, the business side decided to use me as their initial go-to for dev.
You are very clear. To put in abstract terms: you argue that the education process carry some value which is difficult (or even impossible) to test, making it inherently more valuable than the certification process. I can't say I completely agree with the argument, but I can understand it.

I still think that the tests, if elaborated by entities fully dedicated to them, could grow to be way more advanced than they are today. But even in the case where this growth does not happen, having separate entities dedicated to perform test-only certification could be beneficial.

By the way, if you still read this: suppose you have student A and student B. Student A attended to all classes, did exercises etc. but failed the tests. Student B missed all classes, but passed every test. Do you think student A should be certified? What about student B? Who would you hire?
You're right about what HR should have done, but you're overplaying the significance towards Yahoo's current position.
They don't and they encrypt it, why encrypt something that is read only? So i can only assume that it is writable for configurations.
I am a bit tied up on my other projects and it is a bit of a Twittervision clone of the code to a new project to avoid filling up gmaps the same as the diff tool for Windows and Mac is Araxis Merge onto I am a bit tied up on my other projects and it is a bit of a Twittervision clone...

Not nearly as interesting as some of the others here!
Plenty of other attacks work, such as sniffing memory lines on a running system.
Ebay's product quality is very good but not customer service. I never noticed this before like JS in item description....
This stands as an interesting broad strokes story from a developer's experience at a growing company, but worth keeping in mind it's one specific scenario and one perspective on it.

In the generalizations-from-this-instance part of the essay, watch for two false dichotomies—"developers that care about getting things done fast with little technical debt and hate having PMs" vs "mercenary developers who like doing one small thing at a time without architecting things themselves, don't find fast ways to do things and ps like cars and money instead of hacking".

And "no PMs or process at all" vs "way too much process causing poor development time investment".

The best developers, team leads, PMs, etc know when to introduce new processes and team members and when not to. And, importantly, how to tailor processes to each team member to make them as effective as possible. And they work together collaboratively to solve problems—estimating and discussing features flexibly, not tossing pie in the sky specs and finished products over the fence.

In this instance it sounds like they didn't do a great job of working with existing scrappy developers' potential, but instead supplanted a new framework (eng/PM) they had seen work before, and the blunt hammer of that move destroyed a lot of potential the early team had invested in. It sounds like there was a general communication issue that was crippling the team even before a producer and new hires came in.

I've seen a few teams now grow from no dev process to combinations of issue trackers, estimates, specs etc. Around 14-20 developers it becomes nearly inevitable for someone to take on a high level production role and someone to take point for engineering reliability, whether those are official job titles or not.

Often this period coincides with when early team members move on. It's rad when growing companies find ways to keep those early, scrappy hires with deep historical product knowledge in productive roles as the company grows and shifts priorities from staff-leanness and product-speed to staff-scale and product-predictability. But that's often unfortunately not what happens, and it can be extremely painful for both early team members and those trying to evolve the company. (Growing pains!)
CPU registers aren't as persistent.
Great article, this echoes a lot of my frustrations working in the software world. It doesn't help that I've experienced being on a well-managed software team working on interesting problems--it kinda spoiled me for all those other jobs... :)

Anybody have any advice for escaping this? I want the freedom to work on interesting things in my own way with a minimum of the politics. Ideally a PM would be someone who pushes back on all this micromanagement crap and does everything they can to make the developers' jobs easier. It seems I'm not self-motivated enough to do freelance work or start a start-up, so what other options are there?
I think its easy to judge if a software project was successful (eg. Did we launch? Did we deploy that feature?).

The harder question I suppose is whether it was successful and we've got/maintained a quality codebase.
LOL you should look at how much we pay in the States! http://www.tomsguide.com/us/best-phone-plans,review-2953.htm...

The cheapest of the cheap is $40 without a phone and you get 3gb with crappy service. Most are $90 and $24 a month for your iPhone.
Ah the "lets make the project cooler by adding a DSL so customers can add their own features!" never ever pans out! ;)

I spent the 90s working on office automation projects that always seemed to degenerate into report DSLs. Is nothing new?

The better I get at coding the more I am attracted to avoiding complicated tooling.
"I mean, come on, in the grand scheme of things, developers are wizards who never have to be worried about 90% of the things other people in the world have to worry about."

wat
My question in these cases is always this: what is the percentage of people who don't care/notice compared to those who are sensitive bunch is like 1-10% or even 20 or 30% then it's better just to ignore their sensitivities. It just takes too much time to appease everyone, and that is at best an idealist goal. If you don't like something and it's just you and a handful of people, well maybe just _deal with it_.
The Long Term Relation Between Insurance Apps and Software Testing
Its kind of sad that text and image documents today are so complicated that security vulnerabilities in software that reads them are considered inevitable.
"Note: this feature is currently experimental" and that's a true statement.
That is not CBA so it's not on topic.
Extracting encryption keys on a running system is completely other vector attack and I doubt using registers is much safer than RAM in such case. Might be wrong though. :)
There's always a flip side! My current project has a DSL (not written by me) and it functions superbly.

It does take about a full work day to wrap your head around though :)
Yep. Ember is the best solution out there at the moment. There is a trend, that silently more and more serious dev team switching to Ember. Ember never had hype period. It works and it is really matured. With Ember you can focus to your product and you don't worry any more about tools. I think most of the Ember dev is just smiling when they see these debates, because for us everything work and we ship day by day with a very high level of developer happiness. :)