skysight-inc/HackerNews huggingface dataset:
> Scrum is not opinionated about the actual development methodology so claims about how it affects the code that is written are themselves a bad smell IMO.

Scrum is actually part of the problem, IMO. I've seen many teams turn scrum into a hammer and treat all future problems as nails.

Example problem: The foobar story has failed failed for the third sprint in a row.

Likely discussed in retrospective (plausibly good ideas, mind you):

- We need to break down stories more before we estimate them.

- Or we need to stop underestimating foobar stories.

- Or we need to focus on unblocking subtasks related to foobar stories.

Probably unconsidered:

- The foobar code is a mess and needs to be refactored.

- Or the foobar subsystem is too coupled to the Fizzbuzz subsystem.

- Or the need for some developer tools to increase productivity in the foobar ecosystem.

Since scrum is methodology oriented, methodology is the first tool teams reach for when a problem is encountered. And I see this after team leads make it explicitly OK to discuss technical subjects in retrospectives.

I'm not a psychologist, so I can't describe why this phenomenon happens, but I see it regularly.
He wrote some other books about that. Most of the points he gives are pretty reasonable (tech isn't a panacea, tech for its own sake in an professional/educational environment is bad, PowerPoint is the devil (that's actually true)), but I still wouldn't invite him over for dinner.
Interesting! Are there any source listings anywhere? Do they have particular programming tools or methods that help them deal with the complexity? If it's all assembly, I'm surprised this is only happening now.
पीछे से डालोगे क्या || Dehati India Comedy || Hindi Comedy Video
are you assuming the other element is also in the filter? my assumption is your 'deletions' occur only when you know before hand the element already is in the filter. if two elements with the same fingerprints are added to the filter, the finger print is stored two separate times. deletion of any one of them would effectively remove only the single copy thereby not affecting the other (you could be deleting the fingerprint that technically belongs to the other element but it's all the same), so no in this case you do not get false negatives.
Ask HN: Does code documentation increase contributions?
I'm trying to convince a team working on a complex open-source project that they need to document all the code they write.

They have documentation for some public APIs, but most of the code only has an occasional comment. Otherwise, there is no data structure, function, or module documentation. I.e. no explanations what they represent, or do, no member or argument descriptions, and no overall module introductions.

For now I'm trying to focus on a single argument: better code documentation will bring more outside contributors by making it easier for them to figure the code out. The project is corporate-funded, already has a lot of users, and is present in all major Linux distributions and FreeBSD, but sees little outside contributions.

To me the answer seems obvious, but I would like to hear your opinions, if possible see actual data, or at least anecdotal evidence of any effect.

General opinions on the need for most, if not all code being documented are also welcome.

Thank you!
The point you're missing is that a lot of people cannot even attend medical school because their parents are too poor to support a child which could be working an underpaid job at mcd instead. And I'm only taking about cost of living, not tuition.
essentially, yes.
Scrum is the worst possible development methodology, except for all the others.
Look, I don't know. I didn't down you.
Piketty's book was not peer-reviewed, but as it's often the case in all fields you first publish a bunch of peer-reviewed articles on a subject and then you summarize and clarify stuff putting together a book.

So the book itself might not be peer-reviewed, but many of the findings within are
The Indoor-Outdoor IoT
I love this thread. One that hasnt been mentioned and that I've enthusiastically gifted is The Dispossessed by Ursula Le Guin.
Deconstruct Scrum and perhaps something like RUP/DAD (Scrum doesn't tackle the whole lifecycle) into components and understand what the purpose of each component is.

Start from Kanban and add stuff until you get a process that matches the critieria of the organisation.

This requires a lot of skill though, so many teams are stuck with one-size-fits-all tools like Scrum, especially now that it's become a management buzzword. And it does a not too bad job at delivering somehing of passable quality not too late. :)
Describing drawbacks and problems is value added. Theoretical physicists regularly know about problems for decades before solutions are found. Precisely describing the problem can get the intelligent diaspora organized around finding improvements to the situation.
How extreme can material inequality get before it's a problem? Well the Walton family have the same amount of money (wealth) as the bottom 160 million Americans. How much more extreme does it have to get before it doesn't become the issue?

http://www.politifact.com/wisconsin/statements/2013/dec/08/o...
Can you elaborate on both there being 180 registers and the CPU does renaming of them? Surely the RAX register in an X86_64 CPU is always the same physical location no?
Linear transformations and matrices – Essence of linear algebra [video]
Both distributed databases based on erlang (most of which I guess run on erjang anyway) not distributed systems such as boinc.

The OP is talking about the system part

i.e. Not merely using a distributed system such as erlang, couch/mongodb, and pretending you can do distributed systems.
Been that way for at least 2 decades. There's a big company in Atlanta that does all of it but I forget the name.

No source listings that I know of.
That's pretty true - quality of food in HK and SG really is at another level for certain cuisines (though options for decent European food are naturally fewer).

From what I've noticed, Asians seem to be more prepared to queue for a good meal.

Examples above aside, those in London need only to go to Kanadaya by Central St Giles to see queues galore.

Jury's out on whether this is a down to a great desire to experience good food or people being kiasu (fear of missing out)
Your little factoid is an example of the definition of factoid you're describing. But there are other definitions of factoid and I suspect the most common one is along the lines "small tidbit of information".
Also hardware. Likely older and expensive mainframes, which while generally reliable do have a finite lifespan.

I'm guessing a critical hardware problem affecting some central part of their flight dispatching system.
Well, now they will have to be more creative, and the law works both ways, their designs will also be protected. So everyone will have slightly or more different designs, just for the sake of being different.
All else being equal, the size of an economy seems to be proportional to the size of the networks of people and things that make up the economy. For example, countries with larger populations tend to have larger economies, and countries with better communications and transportation infrastructure tend to have larger economies.

It makes sense. The better and more extensive the networks that make up the economy, the easier it is to meet, transact, collaborate, move physical and digital goods back and forth, teach and learn from others, expand markets, compete, etc.

As people and things become more connected physically and digitally, the networks that make up the economy get larger -- by definition.
This kind of tweaking is frowned upon and you will be chastised for doing it.

Yes you can do it (and probably should when you understand the purpose of each Scrummy practice), but don't expect to be praised by Scrummers.
" It took nature some hundreds of millions of years to accumulate so much easily usable energy"

You're thinking in terms of an epoch.. namely our current one.

Energy sources change over time.

Oil is just the latest incarnation.

Nuclear is the next, obvious solution, when fools who don't actually understand it get out of the way.

There is enough known Uranium deposits to power the world for 100's of years and this is assuming: A) ancient, inefficient reactors (we have made so much progress, but not allowed to build newer things, and can do even more), and B) we haven't used any new fancy techniques or explored for more Uranium in 50 years.

Your bit about Oil is a little wrong (we don't know what 1/2 is): we keep finding new deposits. Using new tech (indirect drilling, undersea, deep digging, Oil Sands, more efficient extraction) we keep moving back 'peak Oil' they keep telling us we're supposed to be at. Eventually we will, but something better will be available by then.

We could go Nuclear today and wipe out Co2 emissions and cut energy costs by more than 50%. Probably more.

Fusion is maybe not that far off.

When the Nuclear and Fusion revolution take off - the 'Oil' era will look to people living in that era as 'wood burning' looks to us now - totally arcane, inefficient and 'low power'.
I'm a designer and my experience with small scrum teams has more or less been the same - a lot of the issues are handled by developers who are given some agency to self-manage and who are half-decent at doing so. I've only worked in one environment that was true scrum, and I don't know if it was the process or the organization — but it felt so overly boxed-in.

The last point has been the biggest one for me. Across multiple organizations working in the scrum process I've occasionally felt like just getting some time to talk to developers for future exploratory work is like pulling teeth because the scrum process relies so heavily on tangible tasks. I think that's a time management thing that has to be established with teams ahead of time — like "hey 80% of your week are these tasks, but you have 20% set aside for research/discussion'
a rebours is sick.
The Imperva HTTP/2 Vulnerability Report and NGINX
I would be interested to hear of any cases where in-admissable evidence is deemed admissable for the purposes of finding someone guilty. As a European (currently!) I would not want to allow this to continue.
Agreed, and MitM is arguably a bigger threat than DPI to most people, especially if you use coffee shop wifi, etc.
Social Media Apps You Must See
> The daily standup, IMO, should be only to remove impediments, and if you have none, then a sentence or two will suffice.

100% this. The only thing a synchronous team-wide meeting is useful for is revealing a significant issue and getting a prompt and definite acknowledgement from the team. And then, if it's a priority, some help with the issue. But given the proper tool, even that feature can be made asynchronous.
In my view the only way to handle this is to make constant refactoring part of the work without telling management. If you ask for permission for refactoring you will almost always get a "No".
> It's also not like Piketty's book was peer-reviewed either...

Curious, what is exactly a peer-reviewed book? Could you give me some examples of one?
I don't understand why this has to be a dichotomy? Why cannot you be a caring, empathetic person, while also rationally maximizing efficiency of your actions? There are people like that.

And yes, sometimes empathy is needed to motivate people to take action. For example: http://www.aljazeera.com/indepth/features/2016/08/greece-fis...
Book:

- Information Theory, Inference and Learning Algorithms
Textbook by David J. C. MacKay (free pdf: http://www.inference.phy.cam.ac.uk/itila/)

Other things:

- (the already mentioned http://camdavidsonpilon.github.io/Probabilistic-Programming-...)

- https://github.com/markdregan/Bayesian-Modelling-in-Python (a practical introduction to PyMC3)
That's why it is called "tradeoff between exploration and exploitation". Exploration costs resources too, and has a lower chance of generating rewards in the short term. But without it agents can be stuck in a local minima without being able to "jump" to a better local minima.
I've seen the "you're doing it wrong" argument so many times (I applied it myself a few times).

Scrum is complex and not always possible to follow exactly, so this is to be expected but it makes me wonder, how many successful projects are out there that are following the true Scrum methodology?

My guess is that it's a few more than the classic waterfall but I still seem to see far more failure than success stories.
I didn't find any architectural details on QPX after they've been acquired by Google.

For Haskell I remember reading about Cloud Haskell ( https://haskell-distributed.github.io/ ) which allows you to write Erlang-style systems and Sparkle ( https://github.com/tweag/sparkle ) by Tweag ( http://www.tweag.io/ ) which allows you to use Haskell with Apache Spark. But those are tools and libraries and not complete production systems.

I'd love to read about Haskell or Common Lisp distributed system implementations if you have any pointers!
>>> Scrum is intended to be the straightest line towards measuring your real progress on a project, and not much else

There's slightly more to it than that: it also encodes an assumption that you're working with a single fairly-tightly-integrated group (with synchronisation points at least daily). It's possible that this helps with estimation and scheduling -- it's a lot less clear that it helps get the best outcome in other respects.
How we become goal-less
Using the HTML5 Battery Status API for Advertising
But that is mostly not true, you simply must invest money to replace and upgrade old system. Image similar excuses if airline was running WW2 era planes.
Is Twitter finally about to get bought?
This is actually an argument which is pretty core to Austrian economics. They're dismissive of most traditional aggregate models basically because they think they aren't accurate enough to qualify as scientific. Generally Austrians are sort of dismissed as a cult, but IMO they have a pretty compelling explanation of how the Fed's attempts at price level stabilization helped cause the Great Depression. I'm not an economist or someone who has really studied this, though.
Those are really good points. Particularly the one about how there are so few open source systems built to scale.

I think this is starting to change (slowly). I run such a project called SocketCluster and we recently released some Docker images and Kubernetes config files to make running SC on a distributed Kubernetes cluster super easy.

See https://github.com/socketcluster/socketcluster#introducing-s...

I think there will come a point when most open source stacks will be designed to run on one or more orchestration systems like Kubernetes, Swarm and/or Mesos.

The main problem at the moment is lack of skills in that area - There is currently a big divide between DevOps engineers and software engineers.

As a long-time open source developer, I felt somewhat out of my comfort zone learning Kubernetes but it was well worth it.
Coursera to offer course classes on Bitcoin and Cryptocurrencies
I got this one: http://www.ebay.de/itm/280794425758 almost two years ago, it just fits between the drive and the connector when using a modified drive hatch. The modification I made was simple, I removed the mounting brackets and the plastic edges around them from the inside of the hatch, replacing it with a bit of foam to keep the drive in position. Put the adapter on the drive, slide the drive into the bay as if it is a PATA-drive, push the hatch into place and fasten it using the special screw. Ready.

Performance is more than acceptable, the thing boots (Linux) in a few seconds (that is, a few seconds after BIOS has done its thing of course). In other words, those 3€ for the adapter (incl. shipping) were well spent...
I leave my current role in just under two weeks for the very reason you describe. I'm tired of being the "difficult dev" that everyone has grown to hate. Let them launch. Let it fail. Let's see who the arsehole is then.
Or, if you don't want to chase those blogposts down, here's the nutshell version, from reference [1]:

In order to explain current default Erlang’s GC mechanism concisely we can say; it is a Generational Copying garbage collection that runs inside each Erlang process private heap independently, and also a Reference Counting garbage collection occurs for global shared heap.

(To expand on that a little: each process has its own copy of everything that it needs -- if it needs something from another process, it'll get a copy in a message sent to its mailbox, so: no shared memory, links, etc.

This encapsulation means that when a process terminates, all its memory is instantly reclaimed -- no GC is required, since no other process can possibly be referencing any data in the process that's going away.

And, while a process is alive, there's per-process generational-copying GC, as mentioned.

However, for pragmatic reasons, items > 64 bytes are stored in a global heap and references to those items are passed used (i.e. to avoid sending large things around) -- that's where the ref-counting GC comes in).
Fake it until you Make it CSS
He makes suggestions at the end, in the section "Ideas for Alternatives", after the sentence "The default answer to any substantial criticism is "What is your alternative?""

In summary, he suggests eliminating the review, planning and stand-up meetings (replacing them with asynchronous & as-required meetings), increasing the frequency of retrospectives, and spending time analyzing the backlog to see what the underlying causes are and tackling those.
Nobody said otherwise, but they do provide employment and profit for the highly-skilled.

This development fits the "market of ideas" vision that developed countries have pushed ever since they lost manufacturing superiority to Asian countries. It's an overall attempt at maintaining some sort of upper hand in the commercial sector. Expect copyright and patent laws to be tweaked to cover more and more sectors - already they have been successfully leveraged in the food industry, for example, with "protected origin" programs.

The unfortunate side-effect is that we're edging closer and closer towards thoughtcrime: if the objects of crime are ideas, the agents to police must be minds.
I have been a profession operating system developer since 1990.

I made God's temple.

I have a space alien.

God says...
unequalled Nikon's stales printing's illuminations spunk Adidas's restored waken Presbyterianism hiker minuting moonstones Masai marchioness magnanimity sheeting's terrorize contentedly saleable breastplate's interviewees retiree's aviatrixes valorous bates Cecelia's tastelessly McDonald placer layman's Crimea's
> do we see bank analysts playing 'planning poker' when it comes to putting together pitch decks or research analyses? no.

Most industries (don't know about bank analytics in particular) are more personality driven and/or more repeatable. There are few industries that:

- make entirely new things on a regular basis

- are mysterious to laypeople

- cannot ship 50% of a solution and get 50% of the value
All that extra state is there to help overlap instructions on a time scale of nanoseconds. Every instruction has its own name->register mapping. If you're switching to kernel mode or maybe if you miss a branch or for whatever other reason, the CPU consolidates you back down to running one instruction. Once that happens, you only have one name->register mapping and all the registers have their correct values. The hidden state is reduced to nothing and you only have to save the "real" state of those 16.
"I just move new item from backlog to sprint and work on it." - This breaks traditional scrum estimating.
Bloomberg: iPhone 7 gets new home button, drops headphone port
I think you're conflating quite a few different people there. I mean, there probably are some people who simultaneously hold all those views, but most don't. For example many people doing social studies of science do find science interesting, which is partly why they spend so much time studying people who follow that methodology— they just don't think it's a methodology that is independent of the human culture that it arose from, and are particularly interested in how its social practices developed (even if the scientists themselves don't like to see what they do as "social practices"). Bruno Latour goes in this category, as something of a 'science-o-philic' social constructionist (although he's also a "soft" constructionist, because he views both humans and non-human entities, like lab apparatus and materials, as jointly doing the construction, vs. it being a purely cultural phenomenon). And generally (most) social constructionists and (most) Marxists don't see eye-to-eye, precisely because most Marxists do think there is a scientific, objective method (historical materialism) for analyzing social relations, history, economies, etc., and orthodox Marxists even tend to believe objective factors ultimately determine culture rather than the reverse.
> The current shift is replacing both muscle and brainpower. Outside of creative jobs, what is left for the human to do?

Guarding the robots.

Face it; self-driving cars and trucks are going to be a HUGE target of vandalism and theft at first, especially for people who're made unemployed by them and can't find other jobs.

You're gonna need other people to keep them safe, and carrying guns doesn't require a lot of retraining in the US at least.

Those soon-to-be-out-of-work drivers may very well be required to tag along with the upcoming robot-vehicles anyway, to sit in them as guards and protect them from the rioting Luddites.

Until we can make robotic clones of Arnold Schwarzenegger to automate this as well, that is.
Why living below your means can help you find a better job
> Curious, what is exactly a peer-reviewed book? Could you give me some examples of one?

Here's an article that describes the problems of the lack of fact-checking in books compared to the fact checking that some US newspapers do.

http://www.theatlantic.com/entertainment/archive/2014/09/why...

> Readers might think nonfiction books are the most reliable media sources there are. But accuracy scandals haven't reformed an industry that faces no big repercussions for errors.
The most recent is Liquid Intelligence by Dave Arnold[1]

[1]https://www.amazon.com/Liquid-Intelligence-Science-Perfect-C...
I use a similar workflow.
Emacs Org mode --> HTML --> Git Push --> Auto Publish