skysight-inc/HackerNews huggingface dataset:
This article, as is typical around here, addresses a very small part of the industry. Here's a view from a different part; the part where a project has a lifecycle of a decade or so.

I used to work for a software consultancy that had been acquired by a US defence company (second tier). Over the previous 15 years, the software consultancy had elevated their QA to the point that bugs in the delivered product were literally unknown. Nobody ever saw any in the delivered product, over a decade. Every requirement could be traced to the design that would meet it, to the code that implemented it, to the test that verified it. The test documentation was beautiful, and anyone could (and did) execute a complete set of tests, writing their own personal signature on every confirmation of test success. The signed test specs were scanned before being sealed in an envelope against the customer ever choosing to inspect. QA had (and did) veto over requirements, design, and tests.

We were working with two other major, globally known defence names, and the customer had learned through experience that when something went wrong, come to us last. Sometimes, the customer came to us to ask us to work out which of the other companies involved had screwed up (because sometimes, the other companies were themselves unable to work it out). Once, they sued one of the other names for incompetency and gave us their work because we knew how to fix it better than they did, because our interface tests highlighted everything that their software didn't do in accordance with the spec.

We could replay any test, at any version, at any time, and compare the results now with the signed results then from the sealed envelope. The time savings we had because we got things right the first time, by doing it properly, was immense.

Where this is going is that this was priceless. We had the customer's absolute trust, based on experience. Nobody ever found a bug in our delivered software (I'm not saying there weren't any; I'm saying that our QA was thorough enough that the customer was never going to do anything with it that we hadn't tested already). Code coverage, all warnings on, static analysis, valgrind, cross-platform compilation and testing, we did everything. Customers outright told us that we were worth paying extra because of the peace of mind and the reduced risk, so they paid us more and we spent less doing it.

QA is time and money. The better your QA, the more time you will have and the more money you will make.
"none of those will happen because there are too many people making too much money from the current paradigm"

Portugal

Colorado/Washington/Alaska

In the UK they have returned to prescribing heroin to drug addicts

In New Zealand there is new law around novel drugs that will make them legally available in shops if they can be proved safe

It is happening.
Since Apple seems forever stuck on an ancient Bash version (due to GPL 3, I believe), I keep hoping they switch to Fish (or a home built solution, à la Swift, which could be interesting) with every OS release.
I've been using fish for a while, but generally don't go crazy customizing my shell. What makes it less configurable? It'd be helpful to know what pitfalls to avoid.
Ever been in a meeting where there is food at the back of the room but no one is eating it? But then one person stands up to go get a donut an then everyone realizes it is ok and follows suit.

According the Ezra Klein, that it the reason CEO vs. worker pay has increased since the mid 90's. Helped, according to him, by Reagan tax cuts. I beg to differ on his reasoning.

1) While the moves are more erratic in the last 20 years, the degree of change is no that different... from 1975-1995 it was around +300%; from 1995-2015 is was around +300%... suggesting that the trend goes back further than his article accounts for with respect to the Reagan tax cuts.

2) Klein's argument is quite specious in my view... stating "it just wasn't done" without supporting evidence just doesn't cut it.

One could just as easily argue that this "phenomenon" is correlated to the Clinton administration's repeal of the Glass-Steagal Act, or the Nixon administration's unilateral renege on the Bretton-Woods arrangement through the closing of the Fed's gold window. In any case, it is unfortunate that a talented writer and researcher like Ezra Klein spends his talents shilling to support a political narrative. I'm not a republican or democrat, just someone who wants to read good and truthful information.
It'd be like putting a tiny solar panel on your retail consumer grade router, one that degrades very rapidly over time, and generates electricity at a higher cost than to simply buy it (from industrial grade dedicated solar parks), in a world where you can send energy as easily as sending email, or for that matter, bitcoin.

It's ridiculous. I'm curious about the bigger picture because they have a stellar team, backing, board and bank account right now.
Multiple Vulnerabilities in Openlitespeed [Lower volume before visiting link]
No, my bash is mostly the default that Debian provides (only semi-relevant option I have enabled is globstar, which is just the recursive globbing). I guess I didn't mean that zsh wasn't that much better, just that I didn't think it was that much better.

I may switch to zsh eventually, but I just switched shells and I don't really want to do it again very soon.
CppCon2014: Hyrum Wright "Large-Scale Refactoring  Google" (2014)
And that's not even black and white. Cheating rampant among ants: http://www.science20.com/news_releases/ant_life_isnt_a_commu...
It's funny when you contrast it to web applications. It just shows the layers and layers of bad, inefficient abstractions we've built over the years. For example, re-drawing when resizing the Slack chat window can take up to a second. In that time I could have rendered the Deus Ex scene at 1080p at the highest settings 60+ times.
I'm sorry, but I can't take someone seriously who is inisiting on naming Deus Ex HR as Deus Ex 3.

It just smacks of pedantry, which diminishes your entire point.

So few games ever hit a 90, deus ex HR was amazing. Sorry it didn't take the direction you wanted.
Facebook: Fair and Balanced
And I just threw out 50mph as a "cheaper" number.

You really think people would trade the ability to completely focus on something else during their commute (autopilot) for the ability to go faster but have to focus on the road?
Animal rights extremists threaten primate research by harassing scientists
> Within the post, in fact, I wrote that these tips apply to other CMSs and other development-related jobs you outsource.

Exactly, your article isn't about working with Wordpress "experts" and does not really touch on this topic. If it were, I would expect to read about specific issues you have come across when dealing with external Wordpress developers or even freelance PHP developers and how you've mitigated them.

My argument is that the headline contextually has little to do with the generic tips you are giving. It just seems like you are generating content for the sake of content and the search engines. Which is fine, but not really productive for a site like this.
Found this URL while scanning AnonOps IRC. Seems they are currently looking for & attempting to take advantage of vulnerable systems.
I'm now wondering how it would be if we just gave up on the whole thing and stole the Windows WaitForMultipleObjects() semantics.
We are basically agreeing. The point is not that you cannot automate pacman, but rather that other package managers automate for you, which is bound to be a virtue for some people. I personally never found the "integrated" rollback in dnf/yum particulary useful, but I've heard of enough people who used it to accept that it is a desired feature. Same goes for "dnf config-manager" for managing repositories with one command.

As far as pinning goes, however, I disagree: if you mark a package as IgnorePkg it does not get updated. You could use either naming conventions or splitting the repos up to track different repos for different packages, but it starts looking like an antipattern to me (i.e. the way you would have firefox track jessie while you are on wheezy would be by setting up your own repo only for firefox, a bit of an hassle). It's fine if you are the packager, it's a bit cumbersome if you want a stable debian box with a fresher version of django and nginx.

After all the road map for pacman 5.0 proposes hooks and a better handling of optdepends. Both can be already automated via scripts, but both would be nice to have out of the box.
The drivability and safety of the vehicles is impressive, given the aesthetic constraints. I grew up around motorcycle and car drag racing, and I know how squirrelly such vehicles can get!

I raced as a kid myself, but quit after one try at racing my dad's bike. It was full-race B-modified Kawasaki Z1, capable of 155mph in the quarter mile. It would start to shimmy around 130mph. Scared the crap out of me! He was mad that I didn't have the guts to just hang on and ride it through.
This article focuses on a single failed case, the actual worst case scenario. And though it is true cases like this exist, it is a tiny part of the story of Drug Court. It gives no credit to Drug Court's immense success. I have personally met dozens if not hundreds of addicts that came into recovery only through drug court, and have achieved long term recovery, and have become productive members of society.

After touting the worst case scenario and ignoring the success, this article puts a little missive in there about how doctors (those mostly with no personal experience in addiction or recovery) prefer opioid maintenance. This is but another marketing message for Suboxone, in the massive PR campaign underway to create an alternative to drug-free recovery through long term addiction to a pharmaceutical product. In the recovery community, Suboxone is referred to as Drug Replacement Therapy (DRT) because that is what it is, switching street dope for dope that comes from your doctor. It gets you high enough to avoid withdrawal, but not so high that you can't move boxes or burgers in an entry-level job. If you do try to get off the Subs, you will experience withdrawal that makes heroin withdrawal look like a walk in the park on a sunny day with a sno-cone and a puppy. This article also fails to mention the suicide rate of people on Suboxone. While I have no hard data on that (ONLY because it has never been studied), I can tell you it happens. It's happened to people I've known. It happens because so long as they are addicted to dope, doctor prescribed or otherwise, the deeply traumatized individual who is an addict remains traumatized. They will never experience the true freedom, healing and wholeness that comes only through deep self-examination and a conversion process of equal or greater magnitude, that leads to self- and social integration. DRT only treats the most visible symptoms of addiction, and does nothing to treat the underlying cause.

While I know not everyone succeeds as a result of drug court, on balance, it is a net positive. Some people need to be re-arrested 2 or 3 times before it takes. And some die. This is an unfortunate reality of addiction. And opioid maintenance IS addiction. It really is up to the individual to work through their trauma, and find the needed support to exist and find a reason to continue living. That cannot be imposed by law, coercion, or prescription.

Bottom line though, research the history of Heroin in the United States. A hundred or so years ago, heroin was touted as the solution for morphine addicts. It was the Drug Replacement Therapy of that time. We have been down this road before and we know where it leads.
I definitely recommend fish to every newcomer to Unix. It has sane defaults, colorful output, and so many features that work out of the box.

That said, there is a long-standing issue regarding inline environment variables.[1] Briefly speaking, fish does not recognize the `NAME=value command` form. So you should use `env` to work around this. This may not be a deal breaker, but I'm a bit annoyed, and migrated to zsh.

I would call zsh the opposite to fish. It has insane defaults, is highly customizable, and has so many features that are initially disabled. After hours of configuring it, I loved it.[2] Since then whenever I set up a new Unix machine zsh has been the first thing to install.

So, I would recommend zsh for the people who are used to Unix. If not, or you don't bother to customize it, there's always fish. There is no place for bash.

[1] https://github.com/fish-shell/fish-shell/issues/438

[2] https://github.com/barosl/baroslized-settings/blob/master/.z...
>meaning each request must take substantially less than 10 ms

Correction, each request would need to have less than 10ms of CPU time - the instances support concurrency.

My web frontend, by design, does very little - any CPU heavy operations are done by other systems using the task queue. Writing it in golang has helped as well, wouldn't get that performance from python.

Write a simple Hello world example in golang and get it to do some mathematical calculations to simulate "work", I think you'll be surprised at how many requests a second you can squeeze out of a single instance.
Indeed. Very frequently "getting it out the door" can mean enough money to hire a great developer vs just a good one. There are salespeople whose over-promising causes more harm than good, but it's not black and white.
North Carolina sues FCC for right to block municipal broadband
Open Letter to Mark Zuckerberg Regarding Internet.org [pdf]
Thanks for the good word (I'm the author). I 100% agree about setting the right culture / the difficulty of managing the transition.

It takes a ton of work to establish the right infrastructure + culture. Specifically for the reason you mentioned: a lot of folks see QA in black and white.

It's doubly hard when you're growing fast.
Open Source Robotics Foundation Prepares for DRC Finals and Beyond
I personally liked the "not really benefits" section :)
> In the UK they have returned to prescribing heroin to drug addicts

Do you have a cite for that please?

Here's the current English guidance for Drug misuse, opioid detoxification.

http://www.nice.org.uk/guidance/cg52

So, there are a few doctors that have the required special licence needed to prescribe heroin as a treatment for addiction. These special licences are not new, they've existed for a long time. I'm not aware of the numbers of licences going up.

https://www.evidence.nhs.uk/formulary/bnf/current/guidance-o...

Most addicts are not going to get heroin, they're going to get oral meds like suboxone.
Debian uses dash actually, not bash. I rather prefer it that way since dash is strictly POSIX compliant. Takes some of the tediousness out of creating portable shell scripts.
Using `env` is very much a feature, not a bug. It's part of fish's philosophy to use programs rather than builtins wherever possible. It's good practice to use `env` even when using other shells.
I would describe it as the simplest fastest least buggy terminal available that supports tabs and unicode. So I have tabs for each machine and tmux sessions on each of those machines, kind of 2-dimensional. As you'd guess for something with a full name of "unicode-rxvt" the unicode support is bulletproof, perhaps the best out there of all possible terminals although it varies over time.

As simple as possible, and no simpler.

It does nothing that impresses other terminal authors. Other terminal authors seem to prioritize user experience beneath keeping up with the achievements of other terminal authors. So it is completely incapable of 3-d widget animations, or transparent viewing of 3-d accelerated VDPAU movie rendering via transparency, or any number of things that are extremely technically challenging and "desktoppy" and very impressive to other terminal authors but users primarily see as something that makes it slow and crash alot and complicated and distracting.
21 Inc Confirms Plans for Mass Bitcoin Miner Distribution
To both you and exelius, got it. Missed the part about there being a cash incentive not to sue. I thought it was just agreeing with no incentive on your part.
Skara Brae is amazing: it's a very freaky feeling standing in something still recognisable as a home after four thousand years.

But it is in no way a city. The article admits as much, calling it 'one of the best preserved Stone Age villages in Europe'. Even the word 'village' is generous; it's a hamlet.

I guess '34 Lost Settlements' wouldn't have the same snap as a title.
I can't really agree with your premise. Our current situation is pretty broken, and our drug laws and enforcement have not achieved their stated aims.

That said, the legality of alcohol hardly keeps it from causing lots of people very serious problems. "Drugs do them very little harm" is fantasy, though you are quite right that a felony history and time behind bars only makes things worse.
So, this I agree with too, in contrast with my other comment. There are particular industries (engineering, banking, aerospace, defense, for some examples) where it -has- to be correct. These are also the industries where at least the final product should probably be waterfall or spiral, and generally you need formalism all the way down.

The problem comes when people bring lessons learned from that to companies that don't need that level of assurance. Documentation that's never read again is a waste. Spending time to make tests replayable if they'll never be replayed again is a waste. And so forth.

As for bugs being literally unknown, I'm jealous--it'd be nice to claim I ever guided a project to that state. But keep in mind that's different than no bugs period, just means no bugs in what was tested or used.

If you're delivering a product with very specific use cases, flows and a tight scope with strong bumpers around anything unintended, it's pretty straightforward to guarantee all that. But if you're delivering a sandbox product on the internet to a bunch of randoms, much less so.

After all, ten checkboxes on a dialog are 1024 testcases. That's not even accounting for free-entry fields. You'll never cover all combinations of all uses of the whole app interface, ever, period, and equivalences and fuzz testing only get you so far. That's a simple (if slightly fantastic) example for UI testing, but the same basic thing applies to most other kinds of testing. At the end of the day you often have to pick your battles.

So I really disagree on the better is more. There is absolutely a diminishing return. It just so happens that for what -you- were doing, that point of diminishing return is pretty high.
I really, really hate it when people point at a web browser and a modern game engine and then say "Look how sloppy and horrible and inefficient the web is!"

Seriously, just stop for a second and use your head.

First, that game? Probably using precompiled logic--especially as games in the last decade have gotten objectively harder to mod. The browser must deal with any arbitrary code shoved at it, and handle modifications to its scene graph (the DOM) at any time. These modifications may include creating more script code, pulling in networked resources, or any other damn fool thing.

Second, that game is only going to run on a narrow selection of hardware. It's not going to run on a machine from ten years ago, probably. It's not going to run on a machine ten years from now, probably.

Third, that game is built to use files and formats specifically made for itself. It's not dealing with old goofy image formats. It's not dealing with potentially malformed XML documents. It's not dealing with any number of things, because those have been trimmed away and pre-verified.

Fourth, that game is never going to have to scale from a multiple-socket workstation all the way down to a handheld phone or shell script.

It's really silly to point at a hyperoptimized purpose-built tool and claim it is somehow massively better than a platform for distributing massively-varied media and documents.

EDIT:

Downvote away--but first, write a purpose-built pipeline for deferred rendering, and then a real-time app in Angular, for example. If you haven't done both of these things, you probably don't know what you're raging about.
You could ask--but you have to understand that small teams thrive from working in the same space as it gives easier collaboration. Also, Hallway and lunch conversations are pretty impactful. But, I think this shouldn't stop you from applying, if you can contribute significantly while working remote, go for it.
Just to add to the first line, it also seems fairly well-commented in the code, at least the couple pieces I've looked at. This is really good for me as I often check the source first and helpful (or any) commenting is quite rare.
Trees, Quil and Random
During my residency, I did some fMRI research and learned a little bit of programming. The structured thinking involved in programming has been a useful skill that I try to maintain.

Plus there's lots of interesting discourse with smart people, which is a rare thing to find on the internet these days.
Ask HN: How “technical” Is a Technical Solutions Engineer Position at Google?
I've been rejected for an SRE position after the on-site step because of one particular interview. The others did succeed according to my recruiter, who offered to contact me again in one year for applying for the same position (I guess this is how these things work); I replied: "Yes, why not?", I've no rush at the moment.

After some weeks another recruiter reached me by email saying that he received my resume from the recruiting team, and asking if I could be interested in applying for a Technical Solutions Engineer position ([1] or [2]). I'm sure he could provide me all the information I need, but I was also looking for an impartial and external point of view, so I'm asking here.

My doubt is that this role may be too distant from a generic system/software engineer position and not particularly inline with my academic degree: a MSc in computer science. I'm maybe wrong but, reading the information reported in the links, it seems to me that ultimately it boils down to a customers support job (especially [1]) and that it may give little to no advantage to one who plans to eventually switch to a different engineering position; I don't know... I'm perceiving this as a "backup offer".

In your opinion, is it worth to take this chance even if I'm interested in other engineering positions? Is my view about this somewhat biased by the rejection?

Thank you so much for your time.

[1]: https://www.google.com/about/careers/search#!t=jo&jid=107445001&
[2]: https://www.google.com/about/careers/search#!t=jo&jid=106825001&
And a second factor:
Apple may be the high-end-only player, but that is not necessarily a disadvantage, as they are still raking in most of the profit of the cellphone market.
> Nobody will pay $1 for electricity to generate <$1 of bitcoin.

Nobody would willingly, deliberately do so. There are plenty of cases of cryptocurrency mining software being installed on unsuspecting users' machines, causing them to spend a large amount of energy generating a tiny amount of Bitcoin/Litecoin/whatever that gets sent to the attackers.

Notably, this has happened to a number of EC2 customers. If you accidentally leak your AWS secret key (by unwisely checking it into version control, or through a buggy deployment process, for example) then more likely than not, you'll very quickly find your account being used to spin up a bunch of expensive GPU instances.
> QA is time and money. The better your QA, the more time you will have and the more money you will make.

Just to caveat again that this is for your part of the industry. That level of detail gets you few benefits if you were Facebook, for example, or a very small startup still doing product validation.

Also to say that "the better your QA the more money you'll make" is a very strong position to take, even in your industry.
get addicted to MUDs. worked for me.