skysight-inc/HackerNews huggingface dataset:
> the liberal idea that all humans are equal

This is a misconception and not what the alluded revolutionary idea is quoted by in the declaration of human rights. All humans are created equal, and I'm sure that modifier was put in not by accident, even though I couldn't explain the difference.

Point in case, one conclusion seems to be that humans are precisely not equal to each other, everybody's worth is equally indeterminate. Edit: I am biased to say this because human worth is specifically mentioned in this context in the German Grundgesetz (foundation of the law) where it's called Wuerde (dignity) and encompasses more than the capitalist idea of material value.
Documentation has a cost, and a risk. It must be maintained when the code changes, if not one deceives future developers and increase the chance of bugs. Ideally the code itself should be documentation enough; keep code comments for complex parts of the code which are not obvious -- these comments then stand-out because they are rare.

The only place where you should document the obvious is in the public API, so I'd say the existing team are probably on the right path. Sorry :-)
Why is management getting involved?

The PO should try to balance this with feature impementation and the team + SM should make it clear when it's needed. This seems to work fine in an environment based on collaboration between PO,SM and dev team, but will probably fail in an adversarial one.
This is beautiful:

The deeper the hustle the deeper the pain
I wish I could play the Violin
The thought of you is driving me insane

Go to http://villanellebot.tumblr.com/post/148629267135/so-many-th... for the entire poem, and https://avoision.com/2015/08/26/villanelle-bot-poems-in-the-... to learn how it was done.
It seems to me obvious that it is rich people who own shares and property. Therefore if total income from capital grows faster than total income from labour, the gap between rich and poor will grow.

But I have to admit I don't really understand theory behind the opposite view. In particular, the article says "the data shows changes in the savings rate are likely to offset most of the effects of an increase in capital share of national income".

Is this saying that poor people will save more as capital returns grow, and this mostly compensates poor people for the relatively slow growth in wages?
Then all interrupts need to be prepared for it and check for it anyways. Crucially, the code path that does the check might also get interrupted, even multiple times. No synchronization is possible, and even if it was, it'd be slower than simply saving the registers.

So what do you suggest could be done?
Sprints are meant to be based on the previous sprints velocity, so any commitment should get smaller and smaller until you can do it without forcing it.
The UK carried out a strike against one of its citizens in Syria, so they most certainly do use armed drones.

https://www.theguardian.com/uk-news/2015/sep/07/uk-forces-ai...

It was a US-built drone, but it was a British mission with British pilots.
I like how Scrum promotes transparency and trains each individual to become self-managed (or at least getting better at it). But it often feels like it's being hyped up, with many people getting obsessed over its practices/rituals.

Estimating work is a nice idea, but using 'story points' for it just feels like a bad API decision - I have never seen a new Scrum team member (including me) getting it at 1st try.

And maybe it's just me, but having a full time, dedicated Scrum Master, who serves solely as a facilitator (without having any actual role in product delivery) is a nightmare, especially for teams that are used to Scrum practices.
You, because the moment you leave you become that-guy-who-we-can-safely-blame.

Mostly joking but plenty of places do work like that.
The vacuum isn't empty. Virtual particles are constantly popping in and annihalating nanoseconds later with their antipairs. They affect light.
Please explain why it is misleading.
> I see no reason why a daily status update over the general channel on slack doesn't serve the same purpose as a standup meeting.

I haven't used slack in anger. When you need help, how do you tell the difference between a teammate being busy, unavailable, or just too distracted to respond? Part of the point of the in-person standup is to remove ambiguities about this at least once a day.
Same here:

http://news.delta.com/730-am-et-update-outage-affects-depart...

A power outage in Atlanta, which began at approximately 2:30 a.m. ET, has impacted Delta computer systems and operations worldwide, resulting in flight delays

8:40 a.m. ET UPDATE: A Delta ground stop has been lifted and limited departures are resuming following a power outage in Atlanta that impacted Delta computer systems and operations worldwide. Cancellations and delays continue.
It wasn't as highly rated as 'Cloud Atlas' but I particularly loved 'The Bone Clocks'. Something about his vision of a post-apocalyptic future seemed very plausible - and very memorable.
CSS mix-blend-mode is bad for your browsing history
> The use of story points appears to be one of the defining features of Scrum.

Practice and experience may have led to this conclusion, but it will be good to know that the (original, Scrum-defining) Scrum Guide, http://www.scrumguides.org/scrum-guide.html, doesn't even mention nor defines "story points". Obviously, there is planning and estimation involved in Scrum, and story points can be a metric used for "amount of work"... but it's not a defining feature.
It's not a dichotomy.

It's true that there are people who have an "if only people were nice" type of outlook on life, and that is indeed naive. The problem isn't that individual people are nasty, it's that the system is set up in a way that favours negative outcomes for many.

The only way to fix the system is politics, and a necessary condition for getting anything done in politics is for people to care.

That said, I agree with you that less complaining and more actual plans would be great. (And especially if the people who complain would then start supporting plans, even if it means that others call them "bad" words like "commie"...)
AngelList is launching ‘Syndicates’ and its hiring service in India
I know nothing about palaeontology. Can you give an example of unfalsifiable claim of palaeontology?

Yes, classical physics is a simplification, but it is a _falsifiable_ simplification, unlike the utility maximizer.

Note that falsifiability has nothing to do with making experiments.

https://en.m.wikipedia.org/wiki/Falsifiability
It's a long time since I've had to deal with "strict" Scrummers. But I do remember being utterly baffled as to the insistence on user features being ready by the end of a sprint, even for quite complex, technical components.

Why can't we make some sub-component this sprint then the UI bit the next?

I tried various ways of reframing it such that the developer of the UI be the "user" but it didn't wash.
An effective retrospective requires creating a safe environment for sharing ideas and a SM which can foster such an environment.

I am guessing that such an environment is quite rare, hence the percieved lack of utility of the retrospective.

I can speak from experience that this is very hard to do. I expect that I will have to deal with a brewing technical conflict in the team soon and I'm not sure what's the best way to do it.
I've also seen what happens if such coflicts are sweeped under the carpet and it's not nice.
I have been two different org, one use scrum and one use kanban, working in the team apply kanban was feel like a sunny afternoon in a park - you lose the awareness of time, and just want to lay back and work on few things for long time, but suddenly your manager told you there is a timeline, no one knows until your CEO keep ask (yep, a startup).
Stalin was probably undervaluing religious zealotry.
"I have never seen a new Scrum team member (including me) getting it at 1st try." - I've never seen one get an accurate time based estimate either. Even experienced ones.
> React for me has some fundamental problems, like its small surface area(only handling the view), which means it doesn't solve all my problems.

I've occasionally, successfully repurposed React to keep track of my AJAX requests. Just create a (<div/>) component for every type and start/cancel the XHRs via componentDidMount() or componentDidUpdate().
In a past life I was an IT consultant and good organizations do ask this question. Sometimes you have to ask the question like that to get business leaders (or board members) to pay attention to that "new IT spending".
This sounds like more of an issue with technical debt management. I'm much more of a proponent of Kanban, whenever possible, so in this case if a user story requires a refactor or architectural change then that's just fine. Also regular code reviews to eliminate hacking and sanity checking automated tests shouldn't be made optional, they should be actively encouraged by the team leads and dev manager.
The retrospective is also my favorite thing about Scrum (or my favorite Scrum ritual, let's say). As you said, when it works, the team feels the rush of having solved a significant problem together. This is the reason I think it should be done more often, and more thoroughly.
(I'm the author of the post, btw)
Sweden may have the answer to America’s gun problem
How has the fork support improved?
Teletext is still alive in many parts of Europe. The Austrian broadcaster still has a service and they have an online interface for it: http://teletext.orf.at/
I've had people on my team frown at my tweaking.

I'm extremely happy to discuss the reasons I want to change something, but all to often the only counter-argument is "that isn't Scrum". I'm 100% fine with that, but I'm not going to do something if the only reason for it is religion.
AFAIK it's both; for developer the requirement of a company to give all changes back to community means they won't be cheated on by stealing their work, not giving them credits and making business off their work for free. They have to contribute back if they decide to use a developer's work, raising their credit/fame that developer can directly capitalize on.
I can tell you which startups will succeed, without even knowing what…
> You don't, however, have a right to a parking spot

This is debatable. In some countries there is an old tax for all car owners. They take the money specifically "for your right to have a parking spot for your car". But after you pay the tax, surprise, you realize that there is not a single remaining place with free parking in the entire city... by design. So of course, you are obliged to pay again. The car owner is taxed two times for the same service. Cling, mo' fresh money.

The planned scarcity of park spots is also a source of power and a weapon of mass destruction of high quality employments. If you restrict the access and monopolize the park spots, you can force easily the small bussiness in this areas to flee and make the whole neighborhood into recession. A handful of big bussiness that can build its own private parkings (or, even better, are strong enough to convince the local government to build a big parking for them) will quickly take all.
This will likely never happen since it puts the offending company in the position of having to publicly air their internal problems, whether it's a lack of proper power backup, inadequate staff, etc.
While I agree with you in principle, after reading the blog post I can only say it did work out quite well for Oliver. He works on what he likes full time and that's already more than what most of us can say. Would his own enterprise tool have made him richer? Possibly. But he himself says that it didn't have many enterprisey features at the time it was still his hobby project. Pretty sure he didn't reach that conclusion on his own and had someone at RedHat to guide him on the way.

In any case, nothing is stopping him now from starting his own company and consulting practice. It's still his open srouce project. Maybe he just doesn't want to do that and there's nothing wrong with that. You know who else was a genius that didn't want to sell things? Steve Wozniak. He even gave up most of his Apple stock to colleagues who he felt deserved getting it. Then there's Linus Torvalds. For some people, there are stronger motivations for building a product than running a company.
I came up with an example of where problem descriptions were useful.

A more relevant example would be The Mythical Man-Month. In many ways, agile and scrum are iterations on solving that problem: project-based knowledge work is hard to estimate and challenging to scale in certain ways.
Agreed. This is a great lecture that explains the connection:
http://abyss.uoregon.edu/~js/ast122/lectures/lec05.html
+1, but gave it to a someone who was quitting his job and about to take on an entirely new career
I agree, it is often not the best approach. But many situations demand a well defined approach to estimation and although the OP tried to preempt this, he didnt provide an alternative
Six unknown settings of Google Maps
Can you please re-check the link? It seems to be broken, and your user profile lists only the Property Oriented Programming from 2013
I am not who you responded to, but: the registers are always in the same physical location, but internally, they are virtually renamed for efficient reuse and to avoid resource contention. If the CPU knows the stream of assembly instructions to be executed, it can abstract away actual register names and show a larger number of registers than what's physically available.
Things like state decisions are direct but limited.

But decisions like the Roman Catholic Church's policy on contraception has only devastated as many lives as it has because those people choose to believe in the symbol.
I am a SM and a dev and it's not at all a comfortable position to be in, because it's often making demands on my time and there are conflicts of interest (but not as bad as SM/PO or SM/manager).

The SM is major piece of the Scrum puzzle and a lot of practices lose their value if the SM is not paying attention.

This over-reliance on the SM is a minus for Scrum IMO.
> it also means that a well thought-out design won't be immediately copied.

And why is this good for society? Like the last paragraph in the article says, I think I'd much rather pay a smaller fee for functionally the same thing?
If developers talk within their team, they should constantly be aware of what their workmates are doing.

If communication is a problem, having a daily standup just pretends the problem doesn't exist, rather than solve it.
`git push` is in no way simple.
Sub-Microsecond Code Profiling of Google Cloud DataFlow
Delta flights grounded after systems outage
CERN says new particle hopes are dashed
One amendment I always wanted to make was to have a "technical debt dial". You could stick it on the wall next to the scrum board.

The debt dial should be from 0% (spend all the time refactoring) to 100% (spend zero time refactoring, get it out at all costs).

Management should have complete control over the dial. Developers should have control over what kind of refactoring they do (ideally the retro should have a question "what debt/tooling issues caused you the most pain this sprint? and a parallel track for debt/tooling stories").
How exactly does one reproduce this?
What would you think of an article titled "Steam locomotives are coming back from the deads" when someone restore an old locomotive in his garage?
Yes, though zealotry is perhaps the wrong word here - zealots were a Judean movement that rebelled against the Roman Empire and sought to expel it by force of arms; zealots are associated with violence.

Pope's influence has over the recent centuries come over non-violent conviction of followers.

Daesh has lots of zealotry, Catholics less so.
Rare cancer baffles doctors – but not IBM Watson
Nonfiction:Global Brain, Fiction:Robinson Crusoe. A handful of poetry (rumi) and philosophy books over the years too.
Show HN: IO-808, a Web-Based TR-808 Using React, Redux, and the Web Audio API
tell us how you did it, and in exchange we promise not to compete with you for a while

That reasoning definitely hasa role in the history of patents, but I don't think it plays much of a modern role either in patent holders advocacy/lobby efforts or in proponent economists' reasoning. Instead, we have a more "modern" & market oriented rationale:

We promise not to compete with you for a while, and that should give you the incentive to create.

This works equally well as a rationale for copyrights. Either way, neither of these arguments can justify retroactive granting of IP rights of any kind. The value has already been created.
Quiz makers show how to take advantage of interactive content in many ways
if pressure is ramping up and quality down the sprints arent serving their purpose.

One of the few defining characteristics of scrum is that the developers define how much they can achieve, and this estimation is improved over time. If this is not happening there is something else wrong with the culture and Scrum is being used as a scapegoat.
Thanks, exactly the same thing happen to me and I thought the performance characteristic is different.

But if that is true ( Which align with my own experience ) this would really annoy me. SSD or not, it should ALWAYS fill up the memory first.
Nope, it's terrible. Just look at the international comparison: http://www.ipu.org/wmn-e/classif.htm

Unless you think "At least the U.S. is doing better than Kyrgyzstan" is the appropriate response. In that case there's really no convincing you.
I Peeked into My Node_Modules and You Won’t Believe What Happened Next
The very idea of a one-size-fits-all process is unrealistic IMO. Something will always be customised in practice.

Regarding success stories, it might be that process doesn't play such a critical role as long as solid engineering techniques are used and the team is competent.
Yes! Rereading a (good) book you've already read is an excellent learning technique. (Mine was Dune.) Your foreknowledge provides plenty of context, something which is often lacking in more artificial exercises.
Happy 808 day HN!

As an amateur/bedroom music producer I've always been fascinated with the impact and history of the TR-808. While trying to learn the new Web Audio API I attempted to try and recreate a few of the sounds by referencing the Sound on Sound Synth Secrets series and the block diagrams of the 808 itself. It became addicting and once I had most of the sounds done, I figured recreating the interface/functionality was the next logical step.

This is a completely client-side app made with React, Redux, and the Web Audio API where all the sounds are being synthesized by the browser (look mom, no samples!). If anything this was a really intense exercise in learning all of these web technologies and was more fun than I’m personally willing to admit.

Feel free to ask me any questions, and I hope you enjoy it!
https://news.ycombinator.com/item?id=12240253
Profit Birds вывожу 2251 руб Экономическа
The most important feature of NSIS 3.0 is adding support for Windows 10.

NSIS and Inno Setup are great when you want great control of your installation process instead of following the standard Microsoft Installer (MSI) idiosyncrasies which can give non experts a lot of headaches.

It is important to note that NSIS is not transactional like MSIs and is not the official Microsoft supported installation mechanism in [big] organizations.
Teletext is still available here in The Netherlands, the public broadcaster [1] and some of the commercial channels still have teletext pages. If you have an internet connection (which 96% of the households in the Netherlands [2] have) there's absolutely no point in using it as the same (and more) information is available on their websites, but it's still an important source of information for the elders.

[1] http://nos.nl/teletekst

[2] https://www.cbs.nl/en-gb/news/2015/11/9-in-10-people-access-...
Experiments are generally needed to "falsify" claims in physics, chemistry etc. Those are experimental sciences, which can use the scientific method. Mathematics et al can falsify "on paper".

Palaeontology, economics and many other sciences can't do either. Why can you dismiss one out of hand, but not the others?

(I have written this quite obvious point 3-4 times now.)

Edit: Your own wikipedia reference have a link to the "scientific method". You should read it. Well worth the trouble. It is arguable the basis for most everything we know about the world.
Power failure, clearly their back power systems are inadequate. I believe some of Delta's systems are also backed by SABRE which while ancient is generally rock solid (it lives in a nuclear hardened bunker in Tulsa). This problem is in Delta's own systems not SABRE.
I think it has happened to everybody, but I can't reproduce it reliably. It happens to me at random, if I don't reboot the computer for days it will always appear.

You can kill explorer.exe to fix it.
I am glad to see somebody mentioning Jiddu Krishnamurti here.
He is the most underrated and forgotten person, mainly due to his own insistence, but he made a tremendous difference to some lives. I've come across his books almost twenty years ago, I haven't read any of his books in years now, but his teachings(insights he shared, because he wouldn't like to be called a teacher ) are so well ingrained that I am reminded of them every day.

Similar to the OP of this thread, I didn't marry a person who said he finds his teachings dry :), I am now happily married to my spouse for twelve years who humbly says it is too difficult to really understand Jiddu.
Creating advanced coupon campaigns
A new way to support PC users
Indeed, because Derrida, after all, moves culture towards liminal sublimity. By discoursing on the always-becoming nature of the sign, he aided decolonisation of the scientific palimpsest.
Yes, they'll blame him. It won't make sense for the most part, but it'll still happen. Probably largely things like "it only tomelders had worked with us more instead of being 'difficult', we wouldn't be in this mess", even if the 'mess' is precisely what he was advocating people work on before he left...
In my experience, you struggle to move that dial from 100%.
Yeah it's hugely popular here. It's not just the elderly, it's also popular amongst younger people too.

I think it's predictability is it's strength. You get news at 101, sport at 600, weather at 700 and, if you haven't found the button on your remote, the tv schedules at 200.
> Why can't we make some sub-component this sprint then the UI bit the next?

Because that's how you get bad UI. The user-facing design needs to drive the API interface, not the other way around.
NoEstimates: http://ronjeffries.com/xprog/articles/the-noestimates-moveme...
I've seen pressed/depressed button state bug periodically in older versions of Windows (up to XP it seems). Sometimes multiple buttons in taskbar appeared in pressed state (should be one which is active).
Yeah direct mode is "easy" it's a simple driver hack, ATW is kinda well meh, ATW is the oculus term for reprojection which means you don't hit the frame target so you have to resort to reproject existing frames, ATW reduces the judder by a bit but it still generates pretty bad artifacts this isn't something you ever want to use unless you really have too because your hardware can't hit the true 90fps target.
Viewport multicasting and other true load reduce techniques are huge, NVIDIA had a demo with 2 VR headset running of a single GPU (I believe it was one of the newer Pascal Tesla's) and they showed that under worse case scenarios you get about the same load on the GPU as a single headset on a GPU without VPMC and multi-viewport shader pass through and under most circumstances they only were running at 30% additional graphics load because they could stream the entire 3D scene space only one, transform it once, and then do their pixel reduction screen lense transformation to reduce the amount of pixels that need to be calculated and drawn by about half.