skysight-inc/HackerNews huggingface dataset:
The problem here is that the punishment doesn't fit our collective understanding about the relative immorality of various crimes.

Years ago there was a movie review site called moviecritic.com (a demo site for early collaborative filtering technology). After you rated a movie from 1 to 10, it would show you your rating for several other movies and ask you if you're sure. Half the time you would think "wait a minute, no, I really didn't mean to rate this better than The Shawshank Redemption" and adjust the rating.

A guy robbed a bank. His friend who died understood the risk he was taking; his death is morally "on his own head", even if the "unlucky" robber may have a hand in it. The punishment for this needs to be put next to the punishments for "violent rape", "assault+battery", "willful murder" and adjusted accordingly. Otherwise the whole system feels unfair and arbitrary.
> I would assume [remembering to put copyright notices in documentation] requires more of a one-time effort than a permanent change (improvement) in work procedures.

You assume wrong. There is always another project, or another library.
That sucks. Any chance Apple will trade you for a non-defective model?
More complete units library. Note how the original author's units has 1311 units and 63 prefixes, OSX only has 586 and 56.
You know you've seen something special when the only thing you can think to say afterwards is "But it isn't supposed to do that...".
PS The name of the reporter was Richard Bradley, who's written a good new overview of the UVA situation: http://www.richardbradley.net/shotsinthedark/2015/04/07/in-t...
Quick explanation of compiled sprites:

Most commonly a sprite is represented as a 2d array of pixels that you for X, for Y over and use math or branching to blend on to the screen. But, that's a lot of reading and writing, and a lot of the math ends up doing nothing because a lot of the pixels are intentionally invisible.

So, you could do some sort of visible/invisible RLE to skip over the invisible pixels. That's better, but it's still a complicated loop and still a lot of reading pixels.

So, many crazy democoders have decided to write "sprite compilers" that read the 2D color array of a sprite and spits out the assembly for the exact instructions needed to write each visible pixel one at a time as a linear instruction sequence with no branching. The sprites are then assembled and linked into the program code as individual functions. I believe they can even exclusively use immediate values encoded inside the instructions rather than reading the colors from a separate memory address. So, rather than read instruction, read data, write data; it becomes a read instruction, write data in two straight lines in memory.
[Sponsored] Download a Free Copy of WinX DVD Ripper Before the Giveaway Ends
I stopped posting after one of my playful comments was down voted. That is a real affect of down votes.
I'll accept anything. Except the things that I won't accept. Which are arbitrary.
For what it's worth my XMonad config broke at some point, so I'm running an executable from october 2013. I've tried fixing it, but too much is broken for it to be an easy fix right now.
"It's not that these managers are incompetent or bad-intentioned"

+1. A "manager" can't replace a "team". And having a "team" is one of the key aspects of being agile(this is what "peope and interactions" is about).
“Attack on the Crimean Tatar language community”
You mean, for the whole XKCD? Not just this issue, but the whole thing? I envy you so hard right now. (Unless you were going to be productive today).
This is the coolest thing I've seen all year, way to go to everyone involved!
Bitcoin Lightning Networks Part I: Revocable Transactions
Rocket Internet’s Fashion Group GFG Raises $35M, Poaches Amazon Exec to Lead It
Counterpoint: I am often in earlier than 8 but our semi-daily meetings are at 10.

The real problem is that we do the meetings in person, rather than by writing a slack post/email, but there you go.
MagBak Now Turns Your iPhone 6 into a Fancy Magnet
Note: parts II - IV are there as well. I delayed posting until I'd finished them all.
Standups can't replace pair programming
Small, yes, but they just keep coming. As an example, Pandoc has a tree of something like 70 dependencies on Arch? (I can at least tell you that it has 37 direct dependencies)

It does add up.
I just had a weird idea.

Absolutely no experience, so this may be stupid.

Has anybody tried to replace this with a "daily shared morning tea/coffee"? Create a collegial atmosphere that's intrinsically unsuited to active management; there's no real need to keep people ontopic anyways because they'll naturally talk about work. Plus drinks may keep people occupied enough that only one person would naturally talk.

[edit] Oh, is that what the watercooler does!
Make it profitable to share your findings.

Currently if you discover or understand something new, there are no easy ways you can benefit from it. You can't build a product because you don't have the money. You can't sell it to someone because nobody is buying. So all you can do is charge money however you can.

And with information, offering "consulting" services is the most profitable approach. Make the docs as cryptic as possible then charge a fee for helping people understand it. If you want to fix this problem, create a way to make research profitable. Until then, people will always protect their best asset: information.
The author sounds like someone who doesn't want to communicate and would prefer to stare at a screen all day.

It's just 15 minutes to give people a status update, sync up on what you are working on, and surface any problems. After that you can get back to your keyboard, headphones on and be anti-social for the rest of the day.

Too much process is bad, but complaining about a 15 minute sync up is just petulant.
I had the same thing happen to me. From the manpage I gathered that units uses the definitions defined in /usr/share/misc/units.lib, by running cat /usr/share/misc/units.lib | grep light I found I only had lightyear and it's shortcut ly defined. I added lightsecond, and since milli prefix is already defined it worked a treat.

Here's the line you'll want to add:

lightsecond	lightyear / 365.25 / 24 / 60 / 60
That depends upon such a package already being available -- it doesn't appear that Yi has any.
Reposts are fine when a story hasn't had significant attention in the past year or so.

https://news.ycombinator.com/newsfaq.html
... until your boss schedules meetings.
> I wonder if youngsters who didn't grow up thinking 1 MHz is a perfectly acceptable CPU speed and that 640 KB is a whole lot of RAM will understand what the fuss is about here...

They won't, and thus they don't understand the value of demos in the first place. But don't blame them, even back in the days I knew many people who could not appreciate demos either.
There is also the possibility of cross-reactive allergies, where something that normally does not cause any issues will cause problems if you've already exposed to something else.

For example, during birch season (pollen and such) apples can cause allergy reactions.
Some distributions only support lightyear so adding this line to your units file (which you can find with man units) will give you support for *lightseconds:

lightsecond lightyear / 365.25 / 24 / 60 / 60
> it becomes a read instruction, write data in two straight lines in memory.

So basically this kind of hack could not be used for a game, then, where interaction is needed?
One could ask the same of obesity. The simple answer is that the conditions of life we face day to day now are different from those to which our bodies evolved for.
How to install different app variants on one Android device
Excited About D
The law may work this way, but our social notions of justice do not. Talk to ten people on the street about the circumstances of this crime ("A and B rob a bank; B gets shot and killed"). Ask them how they feel about these two statements:

1) "It's A's fault that B got killed"

2) "It's B's fault he got himself killed"

I doubt you will get much agreement with #1 (I would expect responses like "did A talk B into it?") and I'm pretty sure you will get lots of agreement with #2. The law (effectively #1) is incongruous with our prevailing notions of morality and responsibility.
While I broadly disagree with the OP, I don't think this critique resonates.

The OP argues for more communication and collaboration throughout the day: Don't wait for the standup if you're blocking. Share status information immediately. Keep up to date with teammembers constantly.

Also, dammit, it's not a sync! And if your team has so many members that it last 15 minutes, there are too many people on the team (or the team is being too lenient with the format).
I recently found this paper: "Hearing the clusters in a graph: A distributed algorithm" http://arxiv.org/abs/0911.4729

Wish I had some data to apply it too :-)
> Daily Stand-up is a keystone of the Scrum framework

It's the Daily Scrum.

> 1. What did you do yesterday?

> 2. What are you going to do today?

> 3. What impediments have you encountered?

Seemingly the main purpose of Scrum is to exert more pressure on the individual team member to avoid loitering.
I'm skeptical that a Western welder would command rates 5x or 10x above the national wages, which is what they'd need to be paid to substantially improve upon their domestic market value. And that's not even counting for relocation costs and time, living in another country with a substantially lower living standard, etc. If there really would be a market for this, it would happen. Instead, what I see is Polish welders moving to Western Europe, where they get some extra training, and after that are paid less than their local colleagues.

Despite fear mongering like the GP, welding is a commodity skill, and yes they make OK money (compared to most other blue collar jobs) - but much of that is in overtime and even more so, in hazard pay. I wouldn't want to put on a diving suit and weld an oil platform I don't know how many meters below sea level - and judging from what it costs to get someone to do it, many people think the same.

Lastly, and this is not to dismiss the skill of welding, but a welder is not an 'engineer'. Welding is a practical skill, not hard to get started with, and 90% of all welding jobs can be done by someone with 6 months of training. It's the few highly specialized jobs that take more knowledge and experience, and it's there that the money is. In that respect, welding is (dare I say it?) not unlike software development.
A search algorithm I don't think it should take more on iOS than on Android, geo-tagging can be done relatively easy on Android also and contacts sync it's pretty straightforward also.

So I guess it shouldn't take longer on Android.

P.S. If you need help on the Android part - I would be glad to help out.
> and then compact it with tools.

Did we have minification tools back then?
Lots of competition in that field though :)
The custom option looks like what I need - thanks
Since converting to the faith (cult?), I've re-mapped capslock to ctrl on every computer I've owned. Results? Blazingly fast operator on my own machines. Stumbling idiot that's constantly turning on capslock on everyone else's machine :/
I definitely see your point about most guides detailing how to make your init (I don't understand why so many people just tell you to disable tabs, as though it's understood that everyone prefers spaces), but there are certain things that everyone will want. For instance, when given the choice between an older bytecode file and a newer source file, Emacs loads the older one by default. That sort of thing doesn't really seem like the sort of thing you want people to have to experience for themselves.

(The setting in question I am referring to is load-prefer-newer)
There is some stuff on the edge of my perception and interest that I don't want to hear about immediately.

Instead, 15 minutes at the start of the next day are ideal to get a batch update on how the development of component X or the provision of server Y is progressing is perfect.
Standups can be very useful for entire team. But what bothered us was the sync aspect of it. People knew standup is coming at given hour and they need to schedule their work around it because they know they will be interrupted.

So we decided to went with textual async standups on dedicated slack channel.

Example: "Yesterday I finished the “fix the price calculator” feature, which was mostly about removing the Coffee code and rely on the value retrieved from the backend, via ajax. The nice thing was that the backend code was already covered with tests, while the Coffee one wasn’t. After that I helped Jack with the “allow logging in with email” feature (we need it now because we have a batch import of users from system X soon). After that I did a small ticket, where I block buying licences for special periods of time. This was nicely TDD'ed, thanks to the concept of aggregate, introduced by Robert recently - all the tests pass < 1s. Here is a commit worth looking at. Today I’m going to start with foreman'ing the recent commits and after that I want to work the XYZ system to allow a better editing of entries. I’m not sure how to start it, so all help is welcome"

Blogpost where we describe this technique: http://blog.arkency.com/2014/06/async-standups/ and list of them where we explain the async&remote approach: https://blog.arkency.com/story/async-and-remote/
`brew install gnu-units` should do it :)

Edit: You'll then want to run it with `gunits` rather than `units`
That's pretty slick, though the right-hand column is too wide and it breaks the back button.
Would be cool if this could generate into a framework to run the mock locally for tests. So you would run a local server instead of mocking the network calls and returning json on a method level, you would actual hit a server.

Or is that bad? Curious to hear other takes on it.

Either for testing an SDK or the network layer of app itself.
That's not wrong, but (at least source code size-wise), Haskell libraries are often very small. The compiled version, less so.
I've always assumed the intention is to treat older threads as history.
If it is used only in emergency situations, akin to the use case for kill switches, I think problems with Dilution of Precision and GPS hacking then become a lesser problem. As with any lock-out mechanism, the use of such restriction need to be done with human safety in mind depending on the situation.
Stop generalizing. Plenty will.
BTW, wanted to add...

A little surprised you've remapped capslock to ctrl, but also remap keybindings to alt. IMHO, alt is more of a stumbling block than control, because you pretty much have to take a hand off of the home row to use it. I find pressing capslock with the pinky not to be a problem, and if anything, have really appreciated a Steve Yegge tip of binding C-x, C-m to M-x (as well as C-x-m, for ultra laziness.)
Writing a compiler in C# for pre-compiled templates
Your game could dynamically modify the instructions.
Could you de-activate public insights into respondents email addresses via Google Forms, please?
The "YC XYY" tags are for launches and major third-party articles. We take them out of other titles, especially blog posts and things posted by the startups themselves.
Maybe for single-team scrum projects, but if you have one manager per team you've got way too much management.
Gestalt Principles for Data Visualization
If you're on a tight budget, I'd suggest a smaller drive rather than a used drive.

With Ubuntu, lots of dev stuff (big IDEs, big RDBMS), and a decent number of videos, I'm using about half of my 120GB drive.

If you aren't storing/editing music or videos, you should be fine with ~64GB SSD on *nix or Windows 8.1+, and then you'll get the manufacturer's warranty.

If you do need to store those things, you should just bite the bullet and buy a cheap HDD. The major downside is speed. You can then save up some money to buy a SSD in the future.

Finally, if you have access to one and are in the US, you should buy all electronics with a credit card that offers defect/damage/theft protection (like a standard American Express).
It certainly can be (and has been) used for games where a limited set of sprites are drawn - each frame of animation is just a separate compiled sprite routine. Compiled sprite routines write at video memory addresses relative to a specified position, so they can be moved around at will.
IIRC, because of relative-address store instructions, the destination address does not have to be hard-coded. So, the sprites can still move around dynamically.

What's harder is clipping against the sides of the screen. With no branching, there's no way to prevent the sprite from writing past the end of a line/screen (wrapping/mem-stomping). So, there does need to be a test per sprite to detect that case and fall back on a more complicated blitter.

The Allegro game framework had a compiled sprite jitter as a feature early on. So, that would be existence proof of them being used in games :) http://alleg.sourceforge.net/stabledocs/en/alleg016.html
It could probably be used for games as long as you keep within the bounds of your pixel data.

However, modern games use GPU acceleration instead of plotting the pixels with the CPU, and most higher languages don't expose the sort of functionality you need to use this trick in the first place.
If you create code for each sprite and only change the base address to write to, you can use it for games alright. Jazz Jackrabbit is one that I've seen mentioned using compiled sprites. Lots of DOS games basically had to.
Plus: as soon as you have some people on-site and others remote, simple things like updating the board are done at best inconsistently. Having a standup with your remote devs on hangouts/whatever can save you a whole day's duplicated work.
Yeah, it's fine if you have external people listening in. If there's five people at your standup though, it means they probably don't have anything better to do (like idk, manage).
It makes sense that this could be the case, but do you have evidence that it actually is?

For example, one could make the argument that they favour people with good situational recall, because they're better able to think about occasions where they've done something that applies given the criteria specified. Or that it favours people who have depression, as they tend to be more self-aware and self-critical, so have a larger bank of answers readily available.
Zenefits is pretty awful. A startup I was advising was using them and they were ridiculously slow to respond, failed to make sure payments were processed appropriately causing their insurance to lapse, screwed up payroll taxes, continued paying someone who had quit, and basically failed at every task they were supposed to be helping with. Further they had no personal accountability and did everything they could to shuffle blame rather than just trying to resolve the issues.
Thanks for a good read. Its strange to think about a time when there were a myriad of incompatible networks, and their different capabilities could be exploited.
I said a toy DB, not hype machine ;)
Sure, but wouldn't that incur a loss of performance ?
It's a good overview. I'm thinking about it now :)

Examples 3 and 4 are very neat. And they do make sense as a way to have a pipeline operate on a range of values which may or may not have resolved yet. They promise consistency regardless of the "readyState" of the resource. And the syntax could even be shortened with property getters to something like:

pipe.read(x).split.map(upper).join.write(y)

Which is okay.

There's still something I dislike about them. I really just like the pattern where everything is a separate service, which send messages to each other. You can have message queues, and all services can operate simultaneously, and distribute them across wherever, you can hot-swap them, they're totally de-coupled, parameter formats aren't limited to Node-style callbacks. And each service can be "programmed" with a state machine, so everything is totally declarative, and totally expressive. Throw in complex event processing and you can do anything. I just really like SoA, and think if you're going to bother trying to create a solution for the "async opportunity" you may as well do the most awesome one possible.

I think I mostly get what promises do and how they're useful -- I don't get why I'd use them over just JSONP and callbacks for something where I'm not trying to create such an epic solution.

Fundamentally tho I think one major reason contributing to my choice to not use promises is maybe I'm comfortable with the ambiguity of a value that a value hasn't resolved yet, I don't need to pretend there's something there when it isn't!! :)

Or maybe I just have "trust issues", and I don't trust promises in general, no matter what language you say 'em in! :)

Yeah, that's probably a reason contributing, too -- I like SoA because everything takes care of its own stuff. No need to promise, just do!!
People forget culture is the original technology.
I don't know about what "units" support, but if you ever need picolightseconds in your web design, CSS got you covered:

http://dev.w3.org/csswg/css-egg/#astro-units
Dang. Hopefully someone with more information and less risk can discreetly notify an attorney and/or the EFF and/or the ACLU.
People seem to generate more interest/upvotes on HN when they keep things personal. You're promoting your company with other people's articles as though you're not part of the company. Your headline should be something more like, "Check out this BuzzFeed article on my drone-flying software". If you're self-promoting, be upfront and honest about it. Maybe even tell us something extra about the product that we can't find on your Kickstarter page.
I'm curious how often you had people voluntarily drop out of the process without completing the work sample, and whether that frequency would change if you didn't have a phone screen.
(I take it from your questions that you never actually stopped doing phone screens).

If my first contact with a company is them asking me to put in hours of my time, when it costs them "almost nothing to run" (your words) then I'd be inclined to pass.

The company I work for has a work sample exercise, and we intentionally place it after a phone screen and first interview, because we feel it is (and appears) more fair to the candidates.

From our point of view, we'd love to put it up front, as it is the best source of information we get, but if it caused us to lose good candidates before we even started (and we believe it would) that would be a show-stopper.
> Stop generalizing. Plenty will.

Look at modern forum discussions on Smartphones, it's full of youngsters comparing specs of their respective phones without grasping at all what they mean. Or maybe you are referring to a highly educated subset of youngsters, but that's very few of them.
It will give you the foundation to advance to modern day Intels. You won't last if you jump straight to x86_64
Please do not editorialize submission titles.

The HN guidelines ask you to use the original title unless it is misleading or linkbait.

https://news.ycombinator.com/newsguidelines.html
I didn't know about the units program. Is there any resource out there that lists these little *nix utility programs?
The Amiga had such tricks as well to display 4096 colors at the same time on screen while it could only display up to 32 specs wise. Not sure how they do it on PC, but there's probably a way to achieve it as well.
Let's Develop an Entanglement Clone Using D3.js and TypeScript
Now I know where the rapper got his name.
As a guy who grew up coding Basic on a 4mhz MSX I have no idea what's going on here...
Just because Obama used your website doesn’t mean your product is worth a damn
If I recall correctly from the last time I had to deal with this, it's the first 3 towns on the Eyre highway in WA coming from the SA border. This[1] suggests there are actually 4.

[1]: http://www.postcodes-australia.com/timezones