skysight-inc/HackerNews huggingface dataset:
I agree, minus the ride-sharing part, which will have a very minor share, in numbers compared to taxis and similar. Car is still a necessity in the eyes of an average (first world) human and our individuality will not let us share them.
Everyone is usually being monitored when around children of strangers; we just usually do so with human eyes instead of cameras. Babysitting is an exception, but why should it be?
Always interesting to note that:

"I believe marriage is between a man and a woman. I am not in favor of gay marriage."

is exactly what Obama "believed" in 2008.
Kasich Parody Website Announces Putin as Trump’s Running Mate
Note that these were the votes against the original CISA bill, NOT the bill that passed yesterday. Those votes were:

Nay - Sen. Michael Crapo [R]
Nay - Sen. Michael Enzi [R]
Nay - Sen. Charles “Chuck” Grassley [R]
Nay - Sen. John McCain [R]
Nay - Sen. Jefferson “Jeff” Sessions [R]
Nay - Sen. Richard Shelby [R]
Nay - Sen. John Boozman [R]
Nay - Sen. Richard Burr [R]
Nay - Sen. Jeff Flake [R]
Nay - Sen. Jerry Moran [R]
Nay - Sen. Robert “Rob” Portman [R]
Nay - Sen. Patrick “Pat” Toomey [R]
Nay - Sen. David Vitter [R]
Nay - Sen. John Thune [R]
Nay - Sen. Bill Cassidy [R]
Nay - Sen. James Risch [R]
Nay - Sen. Tim Scott [R]
Not Voting - Sen. Marco Rubio [R]
Nay - Sen. Rand Paul [R]
Nay - Sen. Mike Lee [R]
Nay - Sen. Tom Cotton [R]
Nay - Sen. Steve Daines [R]
Nay - Sen. Deb Fischer [R]
Nay - Sen. Ted Cruz [R]
Nay - Sen. Dan Sullivan [R]
Nay - Sen. Joni Ernst [R]
Nay - Sen. Benjamin Sasse [R]

Nay - Sen. Jeff Merkley [D]
Nay - Sen. Joe Manchin III [D]
Nay - Sen. Jon Tester [D]
Nay - Sen. Claire McCaskill [D]
Not Voting - Sen. Barbara Boxer [D]
Nay - Sen. Ron Wyden [D]
Nay - Sen. Edward “Ed” Markey [D]
Nay - Sen. Bernard “Bernie” Sanders [I]

Source: https://www.govtrack.us/congress/votes/114-2015/s339
That's honest. :) I agree it will be around a while thanks to all the incumbent code. It's why I push for efforts to automatically deal with its issues at least for legacy code. Astree Analyzer, Softbound + CETS, CHERI processor, and CompCert compiler are all top examples of that. Links below. Enjoy. :)

http://www.absint.com/astree/index.htm

http://www.cs.rutgers.edu/~santosh.nagarakatte/softbound/

https://www.cl.cam.ac.uk/research/security/ctsrd/pdfs/201503...

http://compcert.inria.fr/
The reason tuition increases is that we have tuition. If public institutions were tuition free, this wouldn't be an issue. And yes, we have the money; we already spend the equivalent of total tuition on other things. We just haven't decided to spend the money on tuition, instead of on some of those other things. We have the choice.
newer version of android stop being relevant after 4.4

down vote all you want, but there's no security or functionality after that. only silly animations and insane bright color schemes.
There are a few unfortunate truths here:

1. The TSA is invasive security theater operated on the principle that the most effective placebos are those with tangible side effects, namely body scanners and palpable tension at ultra-vulnerable (targets in and of themselves) security checkpoints.

2. The TSA is a country-scale jobs program for poor, unskilled, and unemployable people who might otherwise join disruptive political groups that promise more resource redistribution.

I think the first two points are reasonable if not explicitly provable, but my third point goes off the reservation a bit:

3. The TSA-friendly luggage locks are one of many overt acts of submission that the members of the public undertake in order to travel with speed; there is no incentive for the locks to actually work or be secure, as their primary purpose is to symbolize obeisance. I imagine this may be the case because the TSA-friendly luggage locks are jokes to begin with, as anyone with a common file, rudimentary lockpicking skill, or bolt cutter could pop them open in mere moments... not to mention the misbegotten troglodytes who actually have the master keys and help themselves whenever it suits them.
Steve McConnell has this example in sin #5 of his 10 deadly sins of estimation...

http://www.ewh.ieee.org/r5/central_texas/austin_cs/presentat...
Pinterest replaced 10k lines of Java with 1k lines of Elixir
Projects timelines are like naked shorts in the stock market. You have a capped upside but unlimited downside - things can never be done faster than instantly but they can take literally forever (i.e. just never get finished).
you make it sound like the numbers are out of thin air.. but your link says:

Baseline budgeting uses current spending levels as the "baseline" for establishing future funding requirements and assumes future budgets will equal the current budget times the inflation rate times the population growth rate.

Sounds reasonable to me.
There aren't really many decent small phones. I have a first-gen Moto E, and it's about as big I as I'd like, but the new versions are larger. Same with the Moto X. The best current options seem to be the Sony Xperia Zx Compact series. Everything else small is also very low-end, with bad screens, too-small storage and old software.
Another way of wording this: a list of people to consider re-electing. :)
Before You Send That “Helpful” Email to Someone Who Is Unemployed
There are a lot of apps that do this.

http://www.igeeksblog.com/iphone-apps-to-use-iphone-as-webca...

https://play.google.com/store/apps/details?id=com.pas.webcam...
Using half as many servers as before. More info on the blog:

https://engineering.pinterest.com/blog/introducing-new-open-...
Your main point is correct — no general-purpose writing system has ever been pictographic, not even Egyptian hieroglyphs. But all of your supporting points are wrong.

Egyptian hieroglyphs were in use for about 3600 years, and as other commenters pointed out, Egypt stopped using them because they were conquered by Rome, which then imposed Christianity — which banned a different kind of "icon", killing the hieroglyphs as a side effect. Also, far from being "icons" in the UI sense, Egyptian hieroglyphs were primarily phonetic, although they did have ideographic components — less so than Chinese characters (which are logographic, but only about 4% of them are pictograms) but more so than the Latin alphabet.

The Latin alphabet, which is a modified subset of the Egyptian hieroglyphs (via the proto-Sinaitic and Phoenician abjads and the Greek, Etruscan, and Old Italic alphabets) has been in use for 2100 years, about 1500 years less than the hieroglyphs.

If we're still using the Latin alphabet around AD 3400, your argument from observed adoption that alphabets work better than pictograms would make sense — if hieroglyphs were pictograms, which they mostly aren't.

Every invention of writing except the khipu started out pictographic: Chinese characters (which have been in use since the Shang dynasty a bit over 3000 years ago, contrary to what you seem to think), Sumerian cuneiform, Mayan hieroglyphs, and Egyptian hieroglyphs all have clear pictographic origins. But all of them developed phonetic components in order to expand the range of language that could be written, and those phonetic components came to dominate the script almost immediately, to the point that none of them have an identifiable pictographic-only period in archaeology. In fact, as the numerical nature of the decoded khipus and much of the early Sumerian tablets suggests, logograms for abstract concepts such as numbers may have been in use as early as pictograms or even earlier. So, the actual history supports your idea that systems relying entirely on pictograms have very limited applicability, even though it has nothing in common with the history you imagined supported that idea.

On the gripping hand, maybe computers are not the same medium as clay tablets and printed paper, and so maybe past experience is not entirely applicable.
You start by saying they give all the details. Now you say that it didn't give the information.

Do you at least agree that the article doesn't explain what the quoted 87% increase means in a way the readership is going to understand? Can you explain what that 87% increase means?

The article had almost no relevance to this thread; it was dumped here as yet more pill-shaming bollocks; it targets a group who already have to put up with a lot of bullshit; and it's disappointing to see that kind of behaviour defended.

The original study is irresponsibly presented and poorly reported and I have no problem pointing that out.
I was joking. You are entirely entitled to give your perspective and advertise your services as long as you are transparent about it, which you were. No apologies or explanations needed.
It's more likely someone will naively create a gui wrapper app that does it for them.
Look, I get how it's an amusing and poignant metaphor for what a bad idea key escrow is, but we all know that (unlike strong encryption) dinky luggage locks never provided any meaningful security in the first place. I pulled one apart with my hands once when I lost the key. You definitely don't need bolt cutters.

The outrage at this "spectacular failure" feels a little insincere. You want to convince me the government can't keep sensitive data secure, the OPM hack is closer to the mark.
There are a lot of people building their own projects, as well as volunteering time to official campaign projects. https://coders.forsanders.com/
Usually the difference is about 30% by character count, but you can write the kana smaller before the text is too small to read.
More on Github: https://github.com/Mindtribe/Leash-Debugger

I'm all for design aesthetics, but even with my reading glasses, the link underlining was so subtle I googled the github because the content caused such cognitive dissonance...it seemed like there should be more, but the post seemed empty.

Shades of white may be high art, but it's not a good web scheme. Show off what's worth showing off. It's a great idea.
I'd like to see Immutable.js & Ramda collaborate, more on this here https://github.com/ramda/ramda/issues/1367.

// For example, something like this (which was taken from the github link above):

var plainPeople = [{name: "DALE"}, {name: "AmY"}];

var immutablePeople = immutable.fromJS(plainPeople);

R.map(lowerCaseName, plainPeople) // [{name: "dale"}, {name: "amy"}]

R.map(lowerCaseName, immutablePeople)) // immutable.List([immutable.Map({name: "dale"}), immutable.Map({name: "amy"})])
Completely agree with this - last week I was writing a query with one of our junior developers. Rewriting to use a couple of with clauses with very descriptive names immediately made the intention clear. The with clause is really the clean code enabler for my SQL.
Apple Pencil Controlled Christmas Tree Bowling with SceneKit
The GP's point is that if you care about charging as your highest of priorities, then you can do it.

Personally I think that's a silly priority. You don't need to own a car in the city anyway. Unless maybe if you have very small kids that need special car seats. That makes taxiing/carsharing annoying.
There's lot of women who are more comfortable socializing with men and have hobbies or think about topics that might have once been considered "tom-boyish" that aren't considered so now (thankfully) and they can find a lot of common ground to converse with men.
Out of interest what sort of competition was there back when I worked for British Telecom they only had promotion (boards) every 18 months and had around 550/600 apply for less than 20 roles and that was for MPG 1 to MPG 2.

MPG1 is the entry level grade BTW
Zeno's Paradox. The solution is that a series can converge.
The article is really cool even though it is a little bit simplistic in my view (and experience). I've also made this comment on the article by the way.
The first problem is that rarely steps are independent from each other. I haven't seen hard data on this (and if they have hard data, they should look at it) but my guess is that if one step fell behind schedule, there's an higher probability for the next step to fall behind schedule. That's because the reason a step is behind schedule is not purely random but depends on the internal element of the project (it is harder than usual, using new tech, a person is overloaded and always late...) and all this problem will not magically disappear in the next steps.
The second issue is that project are not so simple as a sequence of task. They usually have tasks in parallel,with different dependencies and sync point. Accounting for time variations on each step quickly become a total mess.
All together now: "Comcast Sucks"
There's also feature creep, which is a pretty big problem in a lot of less organised companies and organisations. The original design may well be a six page website with mostly static content, but the final version could just as easily be a web app with a built in help/support/ticket/chat system, member accounts and live updating from a third party API. One two week estimate easily becomes a six months one.

Or it's delayed because of more and more edge cases being found and someone not wanting to be consistent about them. If the first, third, ninth, sixty second and hundredth items in a loop have to all act differently for seemingly random reasons, that adds a lot of time to the development.

It unfortunately doesn't matter how good your estimate is if the company/client tosses out the orignal spec at the first possible opportunity.

But for well managed projects, yeah, it's a good writeup.
Indeed, but it's the illegal rentals which have made AirBnB successful and led to its giant valuation. There were legal rental sites before AirBnB, but none rose to such heights. AirBnB got rich by flaunting the laws on most of their listings.
Older article, but his stance is basically the same today

http://www.theregister.co.uk/2007/01/18/kahn_net_neutrality_...
I'll bet Stairway to Heaven has had at least as many listens. And it's still being listened to, not "viewed", every single day.

Bands like Led Zeppelin were indeed cultural phenomena that transcended their music - they represented a lifestyle and way of thinking that was genuinely exciting to young people of the time (not me personally, well ahead of my time).

I'd guess the underground metal scene of the '90s had a similar feel.
This seems like seeing someone trying to stop genocide in the Congo, and yelling at them because they're not simultaneously trying to stop street violence in Brazil.

There are a lot of problems, they have varying magnitudes, and some people choose to focus on a particular problem. That's okay. It's frustrating how often it seems like feminists are expected to solve every problem in the world simultaneously to legitimize their attempts to solve one problem.
> And since when is that a credible work of historical scholarship, rather than a (not very subtle) apology of British imperialism (England the new Rome)?

Since always. I'm not sure where you're going with this since it's received innumerable accolades and been considered an exemplary classic for hundreds of years. You must be aware that criticism such as you just gave is a minority view, but you didn't present it as such.

D&F is very well sourced, cited, and footnoted from primary and secondary Roman sources. There are criticisms to be made of it, and there are a few things that modern discoveries have shed more light on, but by-and-large reading Decline and Fall gets you a decent grounding.

I'm afraid I did not read at all an apology of British imperialism; if anything, a criticism of it, but I wouldn't go so far as to say that either. Historians still recommend reading Decline and Fall.
All other things being equal I would prefer my ISP to not even have the equipment in place to determine whether I'm downloading from Spotify or Youtube.
The outrage isn't that your luggage can be stolen now. The outrage is that a) the government felt that it needed to invade the privacy of our luggage for security; so they made these master keys (yes, you can pull them apart with your hands, but provided the TSA doesn't regularly go through luggages, a broken lock is a quick way of telling someone's been through your stuff and you can take action appropriately) and b) it's been revealed that these keys can easily be obtained and the government does not care--showing the broader problem of what happens when you compromise privacy for "security".
What implicit trust?

Phrases like If you want something to stay private, don't post it. are bandied about by the general public. Not just by single issue privacy advocates, but by people of all sorts.
This is very true. The best way I have found to combat it is by splitting up the tasks into many smaller pieces. If you have a task that is scheduled to take a month, then it can easily go out to 10 months in the worst case. If you have a task that is scheduled to take a day, it can easily go out to 10 days in the worst case. This allows you to make corrections to your schedule.

There are 2 other important issues. First, you need to update your schedule based on the amount of time tasks are actually taking. If you only have 10 tasks (each taking a month), the error bars can be quite significant. But if you have 200 tasks (each taking a day), the mean completion time will have quite small error bars. So if you keep a rolling average (say over the last 30 tasks), you can have a fairly good estimate for completion time (agile developers will notice that this is "velocity").

The second very important issue is to be completely anal about your definition of "done" and about making sure that the completed tasks actually meet that definition. Your mean completion time will only be useful if you are measuring the time to completion accurately (obviously).

This effect is so powerful that I recommend "same sizing" tasks and planning everything to have a completion time of somewhere between 1 and 2 days.

There is actually one last thing you need to do. Requirements discovery never happens completely before you start development. As you write the code, you discover new things to do. It is obviously important to modify your plan to accommodate that new information. If you don't, you will end up building something that nobody needs. However, the amount of new work seems to be predictable. I made graphs of new work added to projects over a couple of years and it appears that the growth of new requirements is very similar to some of the defect discovery models (for example Littlewood). Just making a graph of new stories/tasks added over time will give you a decent idea, but I have found that a rule of thumb of adding 30% or so (over the whole project) for new requirements seems to work well.
No information on you or your team, barely any info on your company, if you get funding from this post - I've failed at life.
There are unknown unknown in projects, people won't pay you for a full analysis and there is always the option that one library you rely on has a nasty bug you cannot foresee.

One doesn't have to go very far and look for psychological issues when a major source of indeterminism comes from directly the imperfect tooling itself we use.

Sometimes software is compared to construction, except you don't get to start with a perfectly detailed environment to build your software on. Until we have this major source of indeterminism in the tools themselves, pretending to fix issues on the estimation process alone is a fool errand.

I believe a as-400 project can be estimated fairly well now based on previous experiences. But how would you go estimating a project relying on, say, local browser storage? The only way is to go and build it and identify all the pitfalls yourself, and then the browser landscape changes and you get set back all over again.

Just following Safari rules on IOS to obtain a full screen mode sets us back a week on almost every releases. We started before they started messing with stuff, now we include a week of fixes in the schedule for every major IOS update, but we had no chance to predict this when the project started.
Was he fired? I thought he just swapped positions with the CEO of Porsche.
I disagree (Disclaimer: I'm one of the early backers). The current trend in mobile phones is towards more closed systems. Components are glued together, and often it's not often possible for a user to even change a battery. That's what I would call a big monster.

The Fairphone is the first phone to get a 10/10 repairability score from ifixit. Though there could be more components, it's definitely a step in the right direction. The whole point is to a able to use that phone for 4-5 years. If one part breaks (touchscreen, battery), you can replace that part yourself. If a better camera becomes available, I can choose to update just the camera instead of buying a new phone. Cheaper for me as a user and better for the environment.
Did you mean "In the latter case"?
One thing I always wondered: why inclined people couldn't buy the four locks and mechanically reverse engineer them? Could someone not disassemble the lock and see where all the tumblers fit and iterate on a solution until they get it?

I feel that the people that would exploit the 3D key files now floating around the Internet could achieve almost the same thing anyways.

I don't think any sufficiently logical person ever thought that a TSA lock was secure.
This comment, combined with your username, just made me laugh out loud.
Agree about it being more efficient to invest in emission reductions moving forward. I'd still like to see heavy jail sentences for the executives involved (assuming there's some law they actually broke, and all that). As if the forced recalls ever would constituted true "punishment" for those responsible for this crime.
In practice, you can't even have two. That's because the cheap-fast-good rule assumes that you're already close to an optimum, whereas in practice, things are expensive, slow, and bad, for reasons that are unrelated to one another. As a result, a team will lower the requirements, or agree to spend more money, and discover that the project still takes just as long. I've seen this happen over and over.
Guerrilla Grafters – graft fruit bearing branches onto non-fruit bearing trees
Assume he wins and becomes president, what could he do? Judging by the way congress operates right now, not much.
"That misses the entire point of a modular computing device - phone or otherwise."

No it doesn't. One major use of a more modular device is easier repairs. Many devices are difficult to repair to increase support or replacement revenue. A device whose modules are easy to replace is a differentiator and benefit as it let's us just use Google. :)

Of course, the modularity needs to focus on the devices that will break the most often. In mobile, I'd say it's screens, buttons, speakers, mic's, connectors, and maybe batteries.
> 2. The TSA is a country-scale jobs program for poor, unskilled, and unemployable people who might otherwise join disruptive political groups that promise more resource redistribution.

This is a pretty mind blowing perspective.
Carlos Slim: biography of Mexico's richest man penetrates 'cloak of silence'
That sounds like an index to me, and the operation surely indexing.

I mean, if one has a hashmap

hash = {"foo": 1, "bar": 2}

we say hash["foo"] is an indexing operation, and "foo" is an index. Seems the same to me.
From my high horse...or perhaps between it and me.

The engineering that matters at a startup is driven by business concerns. A well organized codebase isn't a product. Best practices revolve around making money or at least surviving.

Industry best practice in the hardware industry is selling hardware. A professional matches a budget and requirements to what can be done and what cannot be. The whole idea of being a professional is getting paid to apply expertise to the specific circumstances and not promote one's trivial values. To put it another way, a professional turns down jobs that violate their non-negotiable values. They don't take money and then impose them on the unwilling.

Experience will give you professional judgement. That will make you better.

Good luck.
wow - that was so similar to my experience.