skysight-inc/HackerNews huggingface dataset:
When it comes to topographic maps of Kashmir the USSR maps have been cheaper (and outdated). The indian government keeps their maps secret.
Self-driving cars and shipping containers
that might explain the shell but the article also says that the snails organs are also reversed so it couldn't mate with righty snails.
An Interactive Guide to Early Retirement
I was too young on my career at the time to know how much agile was trivial and obvious when it appeared, it sounds more like a Columbus' egg but I'd appreciate if anyone can give me sources on how obvious agile was before the manifesto was released.
Talk about a ton of effort that would quickly be obsolete.
> From my (possibly flawed) understanding, because USB-C switches modes to carry something like DisplayPort, for example, you can't also carry a USB-C signal at the same time

A USB-C connector has one USB 2.0 pair, four high-speed differential pairs, and two sideband wires. For USB 2.0 you need only the USB 2.0 pair, for USB 3.1 you need the USB 2.0 pair and two of the high-speed differential pairs.

For DisplayPort, you need two or four of the differential pairs, plus the two sideband wires. If you're using two of the differential pairs for DisplayPort, you can use the full USB 3.1 at the same time; if you're using four of the differential pairs for DisplayPort, you still have USB 2.0 left.

The same applies to other alternate modes. As long as they need at most two of the differential pairs, you have USB 3.1, otherwise you have USB 2.0. And power delivery has its own set of wires, so it's also always available.

(The exception is the 3.5mm plug adapter alternate mode, where everything except analog audio and slow charging is unavailable.)
Finally, I thought I was alone in this. I ended up replacing the icon with one that a designer posted online, but on a Mac, I still see the ugly icon when I Cmd-tab between apps. If anyone has a solution for this, I'm all ears.
At least on windows and mac it is really easy to replace it with another icon as well.

Probably would have to redo it with each update but still easier than compiling from scratch.
For those interested in finding maps, the book's author has published https://www.sovietmaps.com/resources
"The problem with any methodology is they tend to lead people to stop thinking about the context they are operating in."

Sometimes (quite often actually) that is precisely what we need. It would be quite bothersome to feel the need to explain the reasoning behind every decision and put everything you're doing in context. How about actually doing any work? Pick a methodology that fits your context, work according to the methodology and regularly evaluate the fit between the context and your methodology.

Ofcourse, don't overdo methodology, but don't overdo not-methodology either. Try to find a balance that works. Don't let the means become the goal.
I have worked with Amelia. Few quick comments:

- understanding intent is tricky in general (not just Amelia). Typical approach is to ask for annotated data from chat logs. Most companies don’t have this, so in our case we had a bunch of people (~10) enter a form as if they were asking the question, and used that as a baseline to train the intent recognition classifier.

- distinguished 3 possibilities in chat outcomes:

1. Intent understood and handled
2. Intent understood and redirected to the correct agent
3. Intent not understood

In our case we had +90% for the first 2 combined after about 1-2 months, with handled rate (1) increasing as processes were ported. (Figures will depend on how varied your processes are)

Time involvement varies. In hindsight it’s probably best to sit someone currently handling those chats down with the team and work rapidly through the implementation. Depending on your back end systems (and processes/bureaucracy) the integration with the back end can take up more time than expected
This only works in certain kinds of projects. I often work on projects where you need to spend months figuring out some technologies and see what works best. For a while we tried to deliver "shippable" updates every 3 weeks but this just created a lot of work creating artificial prototypes without any real benefit so we gave up.

If you work on some web site where the tech is well understood then shipping something every 2 weeks probably works.
> "shippable"

It's less vague, more value, and barely more work to replace "shippable" with built (no scare quotes), packaged (no scare quotes) and demoed. The first two can be automated. The third is a matter of getting the right people to show up for a quick meeting. If that's too hard, you can just post a changelog including screenshots, animated gifs, etc. if needed.

Notice that I didn't say the product should be shipped. That's varies a lot from domain to domain and project to project. Sometimes even feature to feature.
Succinct!

If anyone should know it would be you, so thank you for your verdict.
From BOOKPROMO.NET, Download or Read Chapter of  'The Adventures of Nihu.'
VS Code is my primary editor. I don't really find myself having any issues with resource usage. Of course, I have 16GB of memory on my primary and secondary machines.
This could work, but it relies on highly competent autonomous team members who trust eachother. Often not the case.
Can't talk about this without spoilers. The ending is very good.
I think that's called "Kanban".
This is what I call, development by a dozen managers.

If you have every developer on the team on the look out to do The Right Thing then you be sure that you'll start replacing your decision-making strategies with whimsical fancy.

A collective fiction, or methodology if you will, isn't supposed to replace individual thought with adherence to the all-powerful methodology. I'm suspicious of sales people with a vested interest in the methodology they're selling. A methodology isn't something you can purchase... the collective fiction metaphor is apt: you have to convince people to believe and adopt it.

In my experience a team will adapt a methodology like Agile but the best teams will mold it to the way they do things. Their collective fiction needs to integrate their tribal knowledge, goals, experience, etc. There isn't Agile™ — there's Agile the X way.
Most governments keep their most accurate maps secret, especially maps that include terrain and soil traversability information.
I would take that one step further and say the only deliverable is satisfied customers.
To me the key differentiator in agile approaches is whether it's business-led or developer-led. If developers can decide on what gets done and when, then agile can work quite well, but to me that's just a pipe dream in most cases. Unless a company's sole business is software, and the financial health of a company is strong, developer-led agile is a hard sell for business owners, even if it leads to long term benefits. So what happens instead is business-led agile which in my experience is worse than waterfall, as you get constant demands for poorly defined new features, with tight deadlines as that's being 'agile'.

In other words, agile has just become a stick for companies to beat their developers with. That wasn't the original intention, but I would suggest that's at least part of the reason why management types like the term 'agile' so much.
DOE – Cybersecurity for Energy Delivery Systems (CEDS) Fact Sheets
Even musicians need to understand a little bit SEO ;) Software is indeed eating the world.
Here's the deal:

Skilled, knowledgeable programmers with strong work ethics will produce well-crafted software in a reasonable amount of time.

Unskilled, unfocused developers will take an excessively long time to produce crappy, buggy, unmaintainable software.

That's the starting point. Methodologies will not magically produce above-average results from below-average programmers. But the evangelists of various methodologies never seem to acknowledge that. They claim that if you follow their recipe, you'll get stellar results, and if you didn't, well, then, you didn't follow the recipe correctly.
According to the most recent data from the Department of Transportation, there are 11.3 million motor vehicle accidents a year in America, with 2.4 million people injured in said accidents. 2016 was the deadliest year in almost 10 years, with about 40,000 traffic deaths—up about 2,000 over 2015.

The economic impact of car accidents is almost as staggering as the numbers of injuries and lives lost. The total economic impact of car crashes is a whopping $871 billion in the U.S. (http://www.thedrive.com/sheetmetal/13792/car-accidents-cause...)

The revenue of the entire restaurant industry is less than that total economic impact ($799 billion http://www.restaurant.org/News-Research/Research/Facts-at-a-...)
Nice one. It always bothered me that code review is talked about as something completely different then any other supervisory/controlling or people managing (in the sense of trying to make people do what you want) work. It is not, it can demotivate people and rob them of any motivation the same way as any other supervisory function done badly can. The most important point would be to distinguish between bad code and "I would have done that slightly differently". The two are not nearly the same.

Through, I dont thing "we" is better then "you". The most maddening for me was when reviewer attempted to take complete control and responsibility over task as if it would not be me who was supposed to do it in the first place. It is not us, it is you telling me what to do and me then doing it (oftentimes regardless of what I think due to time pressure or simply because reviewer has higher status in the company), so lets not lie about it. Speaking about feelings, let people feel like they did work when they did task, don't take it from them.

The impact of this "actually it is our task lets do it my way" on juniors was quite visible - they essentially stopped to think for themselves or stopped to look proud of their work. They became quite passive as if working in a factory, you did not seemed them to make suggestions how to make something better even if they knew the way (based on personal discussion) and shyied away from any dilemma or initiative.
The above seems like a pretty usual time for Full Autonomy; I've only beaten the full game once so far, and it took 7 hours 58 minutes and 10 seconds to beat completely.

I've heard some people can do the whole thing in four hours; I'm far along in my second playthrough right now, we'll see!
The job security comes when you write great code but awful designs and architectures. The resulting objections are more abstract and harder for project managers to really understand. Or they'll understand the objections but not know how to weight their severity.
Airbnb Has Finally Launched an Official API
Depends, of course. If one is original, inventive and noticeably smart with at least an MA degree then the ideal job would be working in an R&D department.

If more of a scientist mindset focus on the research side and if more of an engineer focus on the development side.

I came across an engineering agency awhile back in my city that is kind of a multi-disciplinary (hardware + software + design) group that enables companies that maybe cannot justify a multiple team member R&D department a place they can outsource development of their out their kinds of ideas.

This kind of agency might be most satisfying because of the variety of challenges and industries.
This is an excellent game in its genre! It has some rough spots; if you do the wrong thing at key points, it can take much, much, much longer to complete than it should. It does have an ending, which is great as well. All around, wonderful game.
I work in such environment, it is pretty cool. We have also testers who test things completely independently of developers , so that helps with bugs. Independently means that my biases over what could break and what is important dont affect them.
After using tachyons (http://tachyons.io/) I've gone the complete opposite direction. While tachyons takes it to an extreme, I found having many small classes that (generally) do one thing, then composing those classes in the HTML, is much nicer than giving each element one "semantic" class name and hiding all the complexity in the CSS, with the large file size and many duplicate rules that approach brings.

You are then not scared of changing existing classes, as they are so simple. In fact you rarely have to change them after writing them the first time. Often you can build a whole new component without writing any new CSS.

It works especially well with components, as it's OK if the HTML is "noisy" with many class names, as generally you're not dealing with large chunks of HTML at once.
Early Facebook Employees Regret the Monster They Created
Things like this make me wonder if I just have an extreme lack of... grit, or tolerance for risking other people's lives or something. I mean, the idea of spending an hour and a half a day driving, experimentally, means I break after a few months even if the job is relatively stress free. (now, experimentally, I can ride a lot longer than I can drive, but I'm one of those people who can read while in a moving vehicle.)

I know this is a normal thing that normal people do; I know people who do it, but it is something I personally find incomprehensibly difficult.
I noticed this as well. It's either a bug, or there's a rogue employee secretly siphoning off paperclips and selling them on the black market.
Not exactly what you asked for, but if you can code you can use any integration testing framework for any language and program the browser to fill out fields, click buttons, read HTML content, etc.
Infrastructure like roads tend to not change that regularly and once it's built it's there and won't change for quite a few years. They might be missing newer roads but knowing about a portion of the roads would still be useful for planning movement and logistics even if there might be a newer better route.
Tangentially but related, does anyone know how to convert xbox360 XMV video files back to WMV or better yet MP4?

Asking for a friend...
I've always supposed HN to be growing very petty. This is just further proof. Really? It's an icon. An icon! And we are spending time deliberating on this?

I am now really curious as to the demographics of HN these days. It is clearly not the same place as yesteryear. I'll probably be down voted into oblivion as well but this is the truth. Stop being petty and worry about things that actually matter.
SPOILER:

After "full autonomy" is attained, should it still be producing paperclips? Because mine is no longer producing paperclips, and I can't see any way to proceed other than producing more paperclips.

EDIT: I understand it now. It is working as intended.

EDIT2: Nitpick: in the second (?) stage, there's a stat for "MWs/sec" power consumption... this should just be "MW" - 1 Watt is 1 Joule/second so I don't see what 1 Joule/second/second of power consumption would mean.
For most of human history populations have been very low. ~10 million or fewer people worldwide before city states means land simply was not an issue. There was not enough people to clear and farm all the land for a long time.

The earth has 130 million square km of land. If ~10% makes good farm land that's 1km per person ~(247 acres) which is far to much to farm by hand.

PS: Currently 11% of land is under cultivation, much of that is only viable due to irrigation. But, we also use a lot of land for city's, suburbs, roads, etc that would have been great farm land.
Great by whose definition? I think that GIMPs UX is more than sufficient for what it is. It certainly doesn't "give FOSS GUIs their bad reputation".

It's okay if GIMP's UX doesn't suit your tastes. It suites others just fine.
I've tried this too during a lull in my undergrad studies - it's how I discovered my love for Kobo Abe. Didn't get much further than AB though...
Anyone know about a similar tutorial that's based around Rust?
OK, I was talking about whether or not the language was OO. So I guess we're in agreement then :)
This article makes it pretty clear that if the Kindle doesn't emit light, it's ok. The experiment was done with an iPad. Kindles were designed with this issue in mind, so I think posting the article in this manner is misleading.
Did anyone else start off by thinking that this was some kind of snarky think piece about Jeremy Corbyn? Maybe I'm watching too much news...
I was passively confused with the new icon but the rationale just annoys me.

They want to make it feel like the full VS icon, but with a gap to signify it's not the full experience. They made the icon incomplete because they thinks devs can't tell them apart (and honestly some of the people I talk to can't, maybe they should have used a different name?)

It reeks of some sales guys complaining that devs won't be able to tell it's not the VS they make commissions on, ignoring the fact VS code can make MS money though getting developer mindshare on an MS product again.
There is part of me who is embarrassed to even think about this, because from a certain perspective, the icon is so irrelevant. If I like the program, I will use it, no matter how ugly the icon is.

But having said that, the new icon does look rather weird (and not in a good way), and why did they change the icon in the first place?
LinkedIn is testing autoplaying video ads
Your car isn't the sum total of what you spend on transportation. Every loaf of bread and gallon of milk was also transported a fairly long distance to arrive at your local supermarket. All the Uber stories here would lead you to believe that the initial thrusts for self driving cars will be in transporting humans, but I find it much more likely that the initial rollout of self-driving technology will, instead, be focused on moving stuff.

Truck driver is, IIRC, the largest single job description in the US. That's a huge target market for self-driving technology and a massive societal problem that's looking when so many people are left jobless.
Just leave the $%$@$!@##$ icons alone! I hate it when my status bar changes and I have to look for the icon.

Whenever a company changes icons I see it as a sign of decline. They are out of ideas to make the product better so they just do some busywork and shuffle the UI around.
Increase Your Likes on Facebook
> Or as Bruce Lee put it: Be like water.

So you are saying go with Waterfall?
Well, minicab drivers had all the time in the world to band together and invent something like Uber, and they never did.

Capitalism has plenty of problems, but let's not pretend it doesn't have advantages too.
It's starting to remove some of my braincells atm.
> ...without selling his product for capital...

Maybe I'm missing what you mean somewhere in there, but facebook raised a lot of capital through investment rounds and an IPO.
...down to the heights of houses and types of businesses.
Google street view can't even keep up with this.
It's on github, right?

Isn't the point of open source that someone can fork it, revert the icon, and call it "IconStudio Code" or something?

Why all the fuss?
Imagine if we nationalised Uber.
> Now you expect a solo person to document?

Yes, unless it is single-use code. Otherwise, if the person is only developing for himself, he can choose whether or not to write any documentation, but if he is sensible, he will write something.

It is moot anyway, as he was not supposed to be a solo developer.
Last I remember newer versions of mtr include MPLS labels in their output to help avoid this confusion, but that version wasn’t included in CentOS 6 perhaps even from EPEL.
Based on reference to iDRAC, certainly seems that way. Presumably they 1) don't have a huge amount of hardware (in the sense a commodity hosting provider or cloud provider would) and 2) get a decent deal from Dell.
Personally, I don't usually retain much, ebook or physical book, unless I take notes, and I find ebooks make such note taking a lot easier.
A lot of things make it to the front page here, not because they are profound or inspire great passion, but simply because... well, they're kinda funny! At least, I assume that is the case here.

But yes, the thing that MAKES it amusing is that some non-trivial portion of the readership will debate it seriously.
Well it's branding, and I get the feeling branding is pretty important to the HN crowd.
They'll just ignore them and do what they please, is where I'm going with this.
Enterprise and professionals.

And then there's the large group that pirates the software, but those are potential future customers.
As a network engineer who gets similar reports fairly often, I recommend watching "Tutorial: Troubleshooting with Traceroute" (a.k.a. "A Practical Guide to (Correctly) Troubleshooting with Traceroute"), as recorded at NANOG 62 (there's also an older presentation from NANOG 47, IIRC). It covers the same stuff John's article does and more. A PDF of the slides [1] is also available.

John alluded to this in his "side note" but often (the majority of cases, IME) the TTL will not be decremented inside of the MPLS core so you, as an end user, will have no visibility into it. You'll just see, for example, hop #4 (Los Angeles) then hop #5 (New York City), completely unaware that the IP packet actually passed through (MPLS "P") routers in Phoenix, Denver, Kansas City, Chicago, and Washington, DC, in between.

You'll see the same thing -- although at a different layer -- when Q-in-Q tunneling is in use (assuming L2 protocols are also being tunneled).

N.B.: On common Linux distributions, there are usually several traceroute variants available. They are not all created equal. If a "regular" (UDP) traceroute won't work, you can try using ICMP or even TCP.

[0]: https://youtu.be/a1IaRAVGPEE

[1]: https://www.nanog.org/sites/default/files/tuesday_steenberge...
Not everyone always works on me to crud applications leaving aside SAP and other "miracle" tools :-)
Type System Differences TypeScript (Structural) VS C# and Java (Nominal)
So it's the widget come back ? One for the weather forecast, one for stock exchange informations...
I would take that further and say the only deliverable is profit. Or more VC :)
ask the USA and UK MotorBike and Car industry about the "faddish" methodology the Japanese companies used to hand them their ass
I disagree. I don't care what the motivation was since I believe CSS with cascading styles and global declarations was a failure to begin with.

I've built many sites using both traditional CSS, with standards like BEM and now CSS-in-JS and this is the first time it actually makes sense. I have yet to encounter a case where I miss the old way of writing CSS.

I think applying "consistent styles" is a fallacy. It sounds like something you want but in the end it becomes a nightmare to maintain once you start sharing styles all across your app. What happens is that you overwrite stuff instead of rewriting because you don't know what rewriting a certain style declaration will affect.

My main point however is that there are very few styles that actually make sense sharing between components. I gave one example; colors, but what else? Take stuff like padding and margin for example. It feels like they are something you want to be standardized but usually in big projects they become extremely context dependent and as soon as you need to deviate from the standard it becomes a headache.

The bloat argument is invalid if you use a proper CSS-in-JS lib which compiles the styles to CSS classes.
He retained control of the company (is what I meant).
Solidus: A Protocol for Confidential Transactions on Public Blockchains [pdf]
Just reopen the tab and it will pick up where you left it
Chrome and Safari (including iOS) have native support, which also means mobile browser native support is near universal. For Firefox and IE/edge, the v1 polyfill works really well. I’m optimistic these browsers will soon support it natively but until then it works very well today conditionally loading the polyfill for that percentage of browsers w/o native support.

We do this with Stencil, so far so good: http://stenciljs.com/