skysight-inc/HackerNews huggingface dataset:
I don't know, currently they don't make pencils and paper illegal to own unless you have an engineering or architecture degree. And you can even legally use those tools to draw buildings and work out math formulas. You just can't represent the final work as an engineer in specific contexts.

The software equivalent would be that you can't sign off on code for a safety critical system without proper credentials. Now that doesn't mean you can't write such code, just like the guy swinging the hammer and striking a nail doesn't need to be an engineer.
How about we call them human beings instead of trying to create a label and separate them from the rest of society.
Why Product Managers Are Not Mini CEO’s
Well, if not pilots, what about private EMTs? Averaging minimum wage or 1-2% above, usually working 24 hour shifts, often without meal breaks, responding to 911 calls. They're a little less FYIGM.
There's a third factor - collectivist vs individualist culture.
Older iPhones have exploits that allow bypassing some or all of the protections. It's likely exploits will be found or have been found against current (iPhone 7) hardware given the economic incentives. Nonetheless, I am not aware of any out in the wild.

As for android phones, afaik you're pretty boned.
>Cramming may get a candidate a job. But they won’t succeed at the job if they don’t have the skills and experience needed.

This is a fallacy, you'll encounter things that you are not "qualified" to do on the job all the time, not to mention that if you are applying for an engineering job, or any other job that effectively requires you to solve problems; then learning new things, performing studies and research and finding a solution to the problem is your job description.

If the role is such that a candidate can have 100% of the experience and knowledge needed to perform that role during it's entire lifetime than that role is effectively the burger flipping of the tech world.
This role is also the easiest to automate since apparently all the answers and knowledge needed to fulfil are known.
I wouldn't call those faults. What you call sleazy lawyers the software profession call those cowboy coders working in advertising, finance, or comp sec.

They are just those outside the mainstream. The fact that those sleazy lawyers win cases should show they perform a valuable service from the ambulance chasers to the corporate defenders.
The craziest thing is they have two F1 teams.
I don't mind the login security, but it logs you out after only a couple of minutes of inactivity, clearing the page. Can anyone do anything tax related without spending a few minutes looking at papers or a spreadsheet?
“Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety” - Ben Franklin
I've never done anything explicitly illegal in the context of programming, but some opportunities which fall in the gray area of legality are just too tempting to pass upon.

I did consulting in reverse-engineering and provided documentation and tool too exploit certain vulnerabilities. Provided that I never used those tool myself for profit, the liability falls onto my clients, considering that I also signed a contract explicitly stating that.

The reason why I loved doing this work so much is because it was highly challenging, considerably more complicated than any software engineering job I ever had before. And more importantly I was extremely good at it, and more often than not I discovered something which no one ever did before. It felt like a mix of software development and scientific research.

Unfortunately when it comes to reverse-engineering, there are not many strictly "white hat" applications for it, besides pentesting and security audit. And naturally I missed building things and creating something which would actually make people's lives better.
So, LIDAR is best solution for an autonomous vehicle when it is not moving?
Thanks, that's helpful! And you can email me at <my HN username> at gmail.com.

I'm also curious if there are any ways to quantify, mathematically, the changes over time. There's the simple sum of the squares of the changes distance to get a sense of the "kinetic energy" of the system, but I'm wondering if there are some more clever analyses, especially something that can quantify localized changes versus global changes.

Edit: so are you running a separate word2vec thing for each year's dataset? If so, how to you map between them, because the orientation the word2vec mapping generates will be random, and I worry that trying to rotate the mappings to some common axis could obscure some of the data.
Some previous discussion of the story:

https://news.ycombinator.com/item?id=14218560 - theguardian.com, 25 comments

https://news.ycombinator.com/item?id=14218789 - fortune.com, 8 comments

Also submitted yesterday, but ignored:
https://news.ycombinator.com/item?id=14212662
Just because the current legal framework supports wage theft does not make it right. We can do better.
Your business is the database. Models matter.

Anyone who wants "database neutrality" (least useful common denominator), vs leveraging the awesomeness of pgsql, mssql, oracle, should just use flat files. Or mysql.
I don't think the main advantage of this is switching databases. It's switching mindset.

Lots of developers think database first, then build on top of that. That's good for simple crud apps. Creating/updating/deleting stuff is what databases are good at.

For complicated apps you should think domain or business problem first. Model your domain, make it good for reasoning about your business issues, and then afterwords think about persisting that to a database.

You domain is your application core, database persistence is a technical issue outside of that core. You write an adapter to persist that domain to whatever database you want. It just so happens this means you can write many adapters for any database to persist your domain to it. Utilizing whatever advanced features your database has to speed things up in that database adapter.
When I read sentences like this:
"We steadfastly refuse to be purveyors of cheap, plastic, mass-produced, craptastic speakers made on an assembly line in China that contribute nothing of value to the lives of our customers or the town we call home."

I'm always amazed how much subtle racism seems to be acceptable when it comes to talking about China.

This sentence contains so many hidden assumptions, e.g. "product from china == crap" and "person in our home town earning money == good, person in china earning money == bad".
Artist writes about his style being copied and featured in the NYT
> same investment in learning materials

Don't you need to go to law school to become a lawyer in most places? That's a lot of money. You can learn to be a programmer using a cheap laptop and public library WiFi.
All I see here is excuses. A good software engineer has to be able to communicate freely and be confident and decisive in what they say. Asking a question like this expresses all of these things, and being an experienced interviewer also allows you to notice when its a little forced (when a person is very introverted), or when they are making stuff up (thats why you ask more specific follow up questions) etc.

I see more people having the skills but not being able to tell the story or communicate in a meaningful way. Seems to be a huge deal with software engineers, the communication piece is just disregarded in most cases. Thats when you end up with engineers who are locked away in their own rooms and not put in contact with any external stakeholders.
There are different kinds of "college towns" in the US.

Boston is a big college town because it has several of the nation's most important/prestigious institutions of higher education—but it's also a distinctive and vibrant city in its own right, with a unique history, culture, built environment. New York is similar.

But many of the state universities and land grant universities, especially in the West, put the state's largest and most important school in a small and otherwise unremarkable town. Norman, Oklahoma, has a population of 110k and the University of Oklahoma, which has enrollment of 30k. Lawrence, Kansas, has a population of 87k and the University of Kansas, which has enrollment of 28k. West Lafayette, Indiana, has a population of 29k and Purdue University, which has enrollment of 40k. Bloomington, Indiana, has a population of 84k and the main campus of Indiana University, which has enrollment of 49k.

These are all nice little towns, but they are all relatively small towns with small enconomies, and there's just a limited number of college graduates they can absorb. They usually have local political cultures strongly influenced by the college and very different than the small and rural communities that surround them.

Plus, lots of American communities can seem very generic. Many Americans towns are less than a century old, with only a few generations of traditions and history, and surrounded by similar communities with a similar size, culture, environment, and history.
Our Site:1 speakers are lovingly handcrafted. We make them one at a time, to our customer's desired spec, using their preferred tonewoods, choice of hardware, as well as other unique customizations.

...

The only way to meet their demands would have been to mass-produce huge volumes of speakers featuring no customizations.

How is Amazon even possibly a good place to sell this kind of an item? People overwhelmingly go to Amazon for the cheapest items that are the types of products that are sold at massive scale.

So if you can't by virtue of your business model sell 100,000 SKUs delivered two day prime, then it seems like Amazon would be a terrible place to try and sell.

I mean it looks like they make a fantastic product for a specific subset of audiophiles: ones that don't want a system to dominate their home. However they don't need Amazon's market to get to the scale they claim to want to reach.
This is a pretty good article that could satisfy the headline: https://johncarlosbaez.wordpress.com/2016/06/29/large-counta...
I tend to agree. The article resonated with my experiences for the most part, but some lines felt out of place, such as:

> Taking one of them would have set me back in my career since I would not have the skills I would have needed to do the job well.

There's a massive disparity in most jobs between experience demanded for, and (potential) experience on offer to be gained from, the particular role.

When I've sat on the recruiter side of the desk I've always been a bit wary about people who have a superset of the skills required for a job -- they're going to be very bored, very quickly. When I've sat on the other side of the desk I've had trouble verbalising, to the panel, the benefits of considering a candidate who has 70-90% of the skills or experience they're looking for.
I worked on this exact same problem one summer, and it's a much harder problem than I anticipated. The makers of this would probably concur -- I haven't gotten great results, even using their suggested searches (e.g. "entrepreneur brings up Demi Lovato, Tiger Woods, and Pitbull).

There are both tweet-level and account-level signals. But some of those signals can be artificially inflated -- follower counts, favorites, etc. One of the highest signal features I focused on was whether or not you were RT'd or @'d by another influential account. Of course, this is a somewhat-recursive problem which made it difficult to wrangle with.

I eventually got something to work, but it was only possible because I had access to the Twitter firehouse and through the manual weighting of features.
> The lack of empathy in the comments is disconcerting. The post is a bit light on details (though the example given of flying 23 hours back-to-back continental flights is terrible if regular) the post deserves better than: 1. Pilots fly for fun. You made the wrong career move. 2. Capitalism! 3. you're lucky - imagine if you were a warehouse worker.

The majority of the criticism is very legitimate, because the article does a terrible job of actually naming any problems beyond saying "it's bad now". Don't mischaracterize all those posts just so you can step in and be the voice of reason.

> Pay has been stagnant for the vast majority of workers for decades. We should be doing something about it, not dismissing it.

We should be doing something about it! But pay is barely mentioned in the article, and even that seems to be about the short-term effects of competition rather than decades-long pay stagnancy.
A company I worked for basically told me to make the "opt-out of emails" checkbox not work. Which means whether you opt in to our emails or you don't, you get emails anyway. Most people would just assume they left it checked (even if they did uncheck it). Being the lazy person that I am, I just said "oh, that's just less work for me implementing that functionality"

but I'm sure that's technically breaking some anti-spam law
#4 UK(7.4/1000) does have over 3x the rate of new bussness per person than the US (2.28 /1000) which ranks #32 and is mostly behind countries with a stronger social safety net.

http://www.nationmaster.com/country-info/stats/Economy/New-b...

Now, if you mean startups as a specific type of new and arguably lower risk business backed by VC money. That has more to do with VC funding than people willing to take risks.
If only I weren't allergic to dogs :(
I think that says more about the the US-based public services than it does about public services in general.

From a european perspective, public services in the US seem really terrible. Whereas in the UK and Europe, the default mode of transport in large cities is public transit, in every US city I've been to (accepting maybe NY) your only real options are Uber or your own car.
Heh, Outlast humans lifetimes for now.
I don't see this as being humble, I see this as a lack of confidence in their skills and abilities and achievements. These same people, for the same reasons, are adverse to avoid making decisions and second guess their work, which causes delays and communication problems.

Instead of trying to make this into an excuse of being humble, it should be acknowledged as a lack of a certain important trait.
yeah I didn't want to derail the discussion with cryptocurrency, as it is better and requires less cooperation, between partners.

but the problem here is the name on the bank accounts even if you wanted to get to cryptocurrency, you would really want a nominee director on the corporate bank account, but then you have to trust they don't take the money (there are plenty of reputable ones though).

if you had that much in cash already then you could buy mining hardware. set up a solar powered mining farm and get cryptocurrency over the next 6-12 months, then you have the liquidity. if you are interested in national currency and bigger material things, then you will still need to contract w/ a crypto-service so that you could report income, but the crypto-service's funding source would be a deadend for auditors.

There are many reasons to mine at a loss.
You can leverage whatever database feature you want, just a long as you do it in the database adapter/gateway.

I write mine in raw sql normally.
High-Frequency Jump Analysis of the Bitcoin Market
> The overriding rule that makes this architecture work is The Dependency Rule. This rule says that source code dependencies can only point inwards. Nothing in an inner circle can know anything at all about something in an outer circle.

You can get pretty far just worrying about this part.

I tend not to find these acronym names and the diagrams very helpful in terms of actually creating code. Separating concerns, as we all already know, is crucial, as is being careful about where knowledge is located. But I've found that if you buy in to these architecture patterns, you quickly become confused about which part of the pattern a given class or module or area of responsibility falls under. Like, is my `BazFrobber` a Gateway, or a Presenter, or a Controller... ?
It would just have to be written into the terms of your license like current breathalyzer laws are right?
Link-Dump April'17
Floating around infosec Twitter last night:

https://pbs.twimg.com/media/C-cMZg5VoAAcz24.jpg
Speech is a weapon, don't wield it unless you intend to hurt somebody or defend somebody.
Absolutely, however Yves Rossy's wing is rigid (cheating! :) ) and the setup requires diving off from an airplane (or a cliff or tall building) and landing with parachute.

I was just talking about keeping the vertical take-off, vertical landing and just adding extra material flaps between the arms and legs like a wingsuit to extend range and endurance.
It's tough to give a definitive answer because every company is different, but I work at a very small strange shop, 5 devs + 1 manager, maintaining 10-15 custom websites (5 of which are on a single VM) and I have been deploying our new apps in Docker (no K8s). I use each container as a "miniature VM" which runs the entire web app (except the database), blasphemous I know. Compared to putting multiple apps on one box, the Docker method adds some minor complexity, but keeps apps isolated. That was my biggest requirement, to prevent devs from cross-pollinating applications, which happened constantly when everything was on a single server. It was much simpler than setting up Puppet on a bunch of legacy machines. I also considered putting each new app on its own VM, but went with Docker because a lot of our apps hardly get any traffic and would have wasted quite a bit of resources to spin up a VM for each (all our servers are in house).

The pros to Docker so far:
Dependencies: Dockerfile gives a list of explicit system dependencies for each app. This can be done in other ways with package files or config management but this was not being done before and this is an easy catch all to force it for any different type of environment.
Logical Grouping: App environment (Dockerfile + docker-compose.yml) lives alongside codebase in a single git repo
Deployment: Deploy to any box with `git clone myapp && docker-compose up` for testing/dev instances or migrations
Development: We mount the codebase from a host directory into each container, with git hooks to update the codebase, which works well for us (we have no CI)
Plus it's fun!

Cons:
Operational Complexity: Devs/Ops teams probably won't want to learn a new tool. I setup a Rancher instance to provide a GUI which makes things a bit easier to swallow. It has things like a drop in shell, log viewer, performance metrics, etc.
Network complexity: we never needed reverse proxies before, now we do.
Clustering/Orchestration: We don't cluster our containers, but the more we add the more I think we might want to, which would add a whole new layer of complexity to the mix and seems unnecessary for such a small shop.
Security?: lots of unknowns, lack of persistence can be bad for forensics, etc.
Newness: Documentation isn't great, versions change fast, online resources may be outdated.

Like you, I'm sometimes unsure if this is the right choice. Maybe a monolithic server or traditional VMs + Puppet would be easier, simpler, better? In the end, I think Docker just fit with the way I conceptualized my problem so I went for it. You may never get that "definitely good enough" feeling, but if it fits your workflow and keeps your pipeline organized and manageable, then I say go for it.
You don't need services to be fully publicly run. It'd be sufficient for just the required natural monopoly infrastructure to be publicly run, with companies buying access to that infrastructure to actually sell service to consumers.

This doesn't fully address your point. The government might still do that part badly. But it isn't quite as bad as entirely state-owned public services. We don't have any better solution for natural monopoly situations, such as pipes and roads.
Parity Technologies Introduces New Bitcoin Software Written in Rust
Ah, I see. I think my perspective tends to be outside the norm when it comes to things like this, since I learned Rust before learning C++, so the Rust way feels "natural", for lack of a better word. I find myself wishing I could do things the Rust way in C++ far more often than vice-versa.
I take your point, but that story sounds really apocryphal. It's hard to imagine someone refusing wine like that. Why not just say, "No thanks!"?
Fyre Festival in chaos
The author makes the implicit assumption that success in a software interview means success in the workplace, and vice versa. This may be true for some interview processes, but this idea can't be generalized across the industry.
I'm not a career counselor but I do believe there's something out there for everyone. Maybe the 25-year-old waitress is happy in her current job. Maybe it's easy and fun for her, she lives in an exciting place, and she makes enough to get by. Why should she worry about the next forty years down the road if she's happy?

Things don't look good economically for a lot of people in America, and a lot of people get treated unfairly for stupid reasons, but there's no easy solution I'm afraid. You can't guarantee a job for everyone because not everyone necessarily wants a job, or perhaps they may only want a certain kind of job.
No worries, I'm sure the next version of Unicode will have a single glyph that provides a complete introduction to the topic.
I definitely think thats a more realistic example of the things that might happen. It won't be the shady guy on the street corner, it'll be your boss asking you to do just one little thing.
It's been suggested that humans have an innate biological desire to believe in religion. I think from an evolutionary perspective this hypothesis makes sense. Groups of humans inclined to believe in religions must have been selected for at some point in our evolutionary past, considering the great benefits in group morale and cohesion religion offers. A tribe of humans with a shared belief system and a sense of purpose and meaning beyond everyday human existence would be much more likely to survive a harsh winter, than say, a tribe of humans with no such belief system.

Religion isn't going anywhere anytime soon.
Can you prove this? I've also set up DKIM, reverse DNS, and SPF, but Microsoft places mail sent from my AWS box straight into the spam folder. Every other email provider that I've tried has been able to receive my email correctly. Microsoft is the only one asking for a bribe to do so.

I've even tried to contact them by phone and their support forum. On the phone they told me that this is a "feature": all mail goes to spam folder until the client whitelists the sending address. This is false, and on their support forums I was told that my static IP from Amazon "is not eligible for appeasement" or something like that.

When you look at what Microsoft has done with Skype and Windows, it's fairly obvious that they don't care about security. Even so, I find it especially egregious that they are offering a "pay to spam" service while at the same time knowingly blocking legitimate email.
Part of my job is telling clients to abandon the startup mentality. When you have 100 employees, two buildings and a defense contract, you can no longer play fast with regulations. That rep from the japanese air force (hypo) wont forgive a lack of compliance paperwork because you needed room for an arcade.
No, This is not a Circle
Wolf Barth (1942–2016)
Is it accurate to say that Japanese are just used to orderly boarding in general? I haven't visited yet but just watching the amount of order and efficiency at train stations on YouTube is crazy compared to the US.
OSVDB is back and public again. Restored from the dump
Public key cryptography of any sort would also probably help here. PGP keys on their website, Facebook page, annual report?

Blockchain?
Ask HN: What CMS are you using?
Hi HN.

I know many of you probably use static site generators. Question for me to those who use a CMS:

* What's the name (link)?

* Would you recommend it?

* Why yes, why no?

:)