skysight-inc/HackerNews huggingface dataset:
I think this is a good example of a hack. She used the say command as a practical joke. That's pretty good to me.

I don't like when people start trying to pick when this word is appropriate to use. The word is really old and has been used for a lot of different things. And besides, I think it was a pretty good hack.[0]

[0] - https://stallman.org/articles/on-hacking.html
How many people get a three month, paid vacation at any point in their life?
I'll stop short of a comparison between sushi mastery and programming but I recognise the feeling when the more advanced your skills, the further you recognise you are from (unattainable) perfection.
I'm not sure how to gauge this. I think Holacracy may be one of the dumber pseudo-science management theories that's ever come out. If it works for Zappos I'll eat my hat I guess, but I have a feeling that all we'll hear about it is that "it's working great!" as the ship goes down in flames.

Holacracy and other ultra-flat org structures always share two features:

- It consolidates power in the people at the top (the people who do not participate in the flatness of the new structure)

- as social animal, humans will always naturally self-organize into de-facto hierarchies that may or may not be aligned with the needs of the organization

Prediction, the 14% that took the buyout are probably the ones that couldn't fit into the new clique driven de-facto structure and were kissing years of promotable work goodbye. These folks will likely be successful wherever they go. Meaning that the people left behind have either cemented a position in the new structure through force of personality (not competency) or are not otherwise employable elsewhere and will suffer as the assholes fight it out on the bridge.

Here's an employee review

http://www.glassdoor.com/Reviews/Employee-Review-The-Zappos-...
I took a chance and wrote a solution in Python.. in less than an hour. https://gist.github.com/agrison/1a27a50c22a7f46df17c

Next step is to print that and show my boss what a privilege it is for him to have me in his team :)
Say what you want about the particular policy, but I'm glad Tony has the opportunity and authority to implement it. "Management by committee" is the best way of reverting to a non-spectacular mean. It's much better to have companies that have variance, i.e. larger organizations actually define a direction and do it, thereby taking risk.

Plus as an employee I'd be more inspired working with an actual leader, rather than a faceless bureaucracy. We got big co's for that.
I use onenote on my surface for this, although I've still found myself going back to real notepads, mostly because the battery life is better.
"If a circle member has a need for support and they are not getting it..."

How does circle member recognise that they need support? What indicators/who provides feedback?

My (limited) experience as a manager was mainly about nurture/support/challenge of colleagues. We could not allow them to fail/fail to 'ask' for support because of implications for clients (we did not sell people shoes).
I disagree. I think we have more understanding of the physical world (physics) then we do the complex human interactions that make up society (politics) and the economy (business). To me the fact the latter fields are not well described alludes the them being more complex.
Has anyone read the book they reference, and do you want to give us a synopsis? I'm hoping it answers some of the practical questions surrounding how this Holacracy would actually work.

http://www.reinventingorganizations.com/
walking 20mins a day is part of my commute so I guess.. yay for me!
No he did not mean just don’t depend on LinkedIn. He meant don’t place the fate of your software and company in the hands of any third party. The list of companies who have burned developers includes Twitter, Apple and Google just to name the three spectactular examples. Facebook has been somewhat better to their developers though there have been a few instances there too.

Unless you have an ironclad contract with whomever you are partnering with(whose API you are using) and know exactly what you get from them and they get from you and for how long, you should not be depending on them.

If you want to spend a few weekends writing to some API and don’t care if the rug gets pulled out from under it, and all your users then fine. If you want to support an API in a product that will survive without that integration that is also fine. Just don’t gamble your entire product and your future user base on API's that can disappear overnight when some dickhead MBA decides he isn’t making his numbers and the free loader third parties aren’t worth it any more.
There are also people that don't know but get lucky.
You still have to schedule interviews, take vacation to interview because it takes all day, etc. You should probably interview at many places to get a better offer, and because you can get rejected for pretty silly reasons. You might want to review your whiteboard coding too. It can take a few weeks / months.
What We Talk About When We Talk About Making
ConferenceCloud: A virtual attendance platform for professional and industry conferences. We use LinkedIn as a part of our login stuff, more specifically the fullprofile to help us understand our attendees and add to our "Contextual Networking" features which enables us to recommend other people at an event that you should connect with.

Really saddened to see LinkedIn restricting this API access. It won't cause any significant disruption to our platform, but destroys the convenience of using LinkedIn.
Upsert lands in PostgreSQL 9.5 – A first look
It's hard to say how much they make on each car sold because they are purposely obscuring this. If you listen at 6:15 to the earnings call you'll hear them totally dodge a totally straightforward question on how many credits per car:

http://seekingalpha.com/article/3147926-tesla-motors-tsla-q1...

Elon says credits sometimes sell for as little as 50%. They are rumored to be getting 9 credits for most cars sold in ZEV states (most cars in US). Credits are worth $5000 in offset fines. So $22k per car even at heavily discount ZEV prices.
For the couple of them that I live with (either now or in the past), yea I'm sure. I have a glass of beer or scotch or wine in the evening ~once a week at work, and it doesn't seem hard to imagine people doing it every day (the reason I limit the days I do it has more to do with the fact that I control my nutrition fairly tightly).
Politics isn't tied to job titles. There still are people with different amounts of influence that try to influence others for their own goals. FWIW, Jeri Ellsworth (who was hired to do hardware stuff, didn't do well there and was fired in the end) described office politics at Valve "like back in high school". Not saying that it can't work, but it also is not without its flaws.
No, the interactive touch-screen tabletop computers that used to be called "Surface" are now "PixelSense".
Sounds like Twitter all over again. How soon till they are floundering and begging developers to come back?
I think Flockport is doing some amazing things. When I read the pagerduty bug-hunt post and saw that they were using ipsec between "hosts", I wondered if perhaps they used LXD with some of your services.
Figuratively, not literally.

But to your point, LinkedIn's practices can be a little pushy, but the site still provides decent value to me (it got me my current job). I can put up with ignoring mass invite requests, recruiter messages, and configuring my notification settings to maintain this professional network. It may get me my next job in 5 years, so for me it's totally worth it.
The difference is that this editor will supposedly not even allow the code to be in a state of type errors. You literally can not construct a program that is not well-typed. Don't ask me how that editing experience is supposed to work, or if it's a good idea.
> io.js[0] is a fork of Node.js, started in December 2014 by a contributor to the Node.js project.

[0] http://en.wikipedia.org/wiki/Node.js#io.js
Some important people from Node forked it into io.js. They want to release quicker and stay on the cutting edge. IO.js is managed by consensus, whereas Node is governed by Joyent. Some were upset at the slow pace of node's progress, accusing Joyent of holding it back for "compatibility" reasons.
Cosmos: A foundation for maintainable web applications. Powered by React
> Deliberately relinquishing power means we can't be corrupted. :-)

Nicely done!
I think it's fair to say that this is 95% of people's first reaction to hearing about MMM or similar bloggers.

Here's something you can take away from MMM even if you don't agree with everything he says.

Based on your post, these are the things that are important to you (or at least a start):

- Newer car
- owning a house over 300 sq. ft.
- Traveling to Arizona to visit relatives.

Maybe there are a dozen or so other things that are important to you that you could add to that list.

Now open up your bank account and find out how much spending happens on stuff that isn't important to you. 50%? 80%?

If you can dial down the spending that doesn't make you happy or the spending you do that just out of habit then you would be able to do more that does matter to you... nicer house, nicer car, more frequent and longer trips to AZ.
SLC Built the first Protected Intersection for Cycling in the US
I once started a gig at a broadcasting company that had just bought a respected multimedia/internet company running several major high traffic websites. The broadcaster didn't like the employment contracts with all the "cushy" benefits, so they offered the staff a buyout. The entire technical staff took the buyout, most of the easily replaceable editorial, project management and graphics people stayed put.
> What mattered to me most was getting away from "1 process per container" mentality. Phusion realized right away that this was an unnecessary constraint

It's a necessary constraint because otherwise developers continue to utilize a monolithic application development process. The goal should be isolated, interchangeable processes, not an entire virtual environment. It's just delaying the inevitable. Makes scaling a lot more straightforward as well etc...
http://www.local10.com/news/does-flier-safeguard-drunk-drive...
Rand Paul steps into tech territory, opening office in S.F
Unicorns are much the same. From the look of them, you'd imagine they must have gored at least a few people, but then you remember they don't exist. If we feel compelled to fear something, we can probably find more immediate dangers.
That's why quinn uses async/await
Akka's location transparency gets rid of a bunch of the network bs that the first paragraph talks about.
> For me, drinking is mostly about feeling different from what I normally feel. Having one drink doesn't have any noticeable impact for me, so I virtually never have just one drink except in social situations or when I just think a beer will taste good with a meal, perhaps.

I'm not the person you asked but I'm in a similar position. Alcohol's effect on the body is as psychological as it is physiological, so even with one drink, I tap a little into those feelings of "unwinding". Throw in the fact that I'll drink beer or scotch that I really enjoy the taste of, and having a single drink is an easy way to have a nice, tasty bit of relaxation after a long day, while avoiding the disruption to my activities that 3+ drinks might entail.
That's from 2013. There have been more recent discussions.
Notice some say they started out at less than $25 an hour. Others started out at $50 or more. The difference isn't in profile, it's in what they were asking when they got that first client.
Sorry, but that's not how large groups of humans self-organize. Many idealists have tried, but power vacuums don't stay for long, nor are they efficient.
More and more people are using io.js now, and they have more releases, using a stable engine, already reached v2, I'm sure others will add more to this list.
As are all the best things in life.
Semi-related: "Jiro Dreams of Sushi", a excelent 90minute documentary movie about "Jiro", an 85-year-old sushi master is available on YouTube w/ english subs: https://www.youtube.com/watch?v=GYN7p8dvr64

Great watch, even if you never had sushi or don't like sushi. The extreme drive for perfection is admirable.
Anyone being interviewed about their hobbies is at risk of coming off as a narcissist. Relax.
Maybe I'm mistaken, but when I read stories of succesfull startups (aside from the usual startup porn), I keep hearing stories of people who didn't know. Sure, they had ideas, intuition, a deep intuition about where the market was -- but they didn't really know.

So they tried experiments and learned. Then they did that some more. The constant refrain is intellectual humility and seeking to understand the people they are trying to help at a deep subconscious level.

Contrast this to the way I and many others think about various skills. We take a few classes, we play around and are able to achieve some simple level of competence. Somebody then gives us a certificate or other form of public "gold star". Then we feel like we know something.

Socrates was right: true wisdom comes from understanding how little you know and using all of your energy instead to concentrate on asking better questions.
Research on fusion engine is AIAA Best Paper
On the other hand Apple, Google, Faceobook, Twitter, Amazon and LinkedIn are increasingly sucking all of the oxygen out of the rest of the software ecosytem. Software developers are increasingly being painted in to a corner where all the users are sitting on those platforms all the time and unless you are there too its really hard to get eyeballs to look at your software.

Developing for the open web and trying to get people to websites in the current mobile/social era is increasingly brutal unless you are willing to be completely dependent on a handful of big companies.
That's exactly how it supposedly works at Ricardo Semler's companies. Everyone participates in self-organization.
This is the same case with bombs.
That's like comparing grains of wheat to fully baked lasagnas, buddy. What matters is what the market is prepared to pay for the tech. No arguments here. Fifty:one. It's a verifiable fact just like my ipython example.

Now that does not mean that grains of wheat are not useful. As I said, I love the Pi and I own two arm platforms for which I have ambitious use cases. I just don't delude myself about who owns the performance.
Looks like it has issues running with nosetests. It would be awesome, if I could do nosetests runtests.py | fpp and if any test fails, i could select it and it would open it up in my editor.
Someone should ask them how they will solve the "safety" concerns: “because the brewer has no way of determining what beverage is being used or how much coffee is being added, and therefore cannot adjust to factors such as brew strength and amount of water, which could represent a safety concern…”
Radix sort on a fixed width key is actually one of the most predictable sorting algorithm. In a traditional Radix sort the complexity is O(kn) where k is how much bucketing you want to do on the key size. Buckets are fixed at 2^n bit size so more buckets = less space, less buckets = fewer passes.

Say for a sorting 32bit values you might split your buckets by a factor of 4 aligning to a byte boundary. This would give you 4, 256 entry buckets.

The sort then becomes a linear walk of the data doing the standard Radix sort. This is where the prefetcher and packed arrays really start working to your advantage. Your memory access is trivially predictable and the prefetcher gets to work eliminating all DRAM cache misses. Most algorithms will hint at the fetches but it usually takes just a few loops for the prefetcher to do just as well. If you want to some parts of the passes can be batched to get better than O(kn).

Now if you want to get fancy you can take your key, and find out what bit width for your buckets line up nicely with your cache line size and watch Radix really scream.

This used a lot in computer graphics for determining draw order, intersection tests, etc(in fact the book "Realtime Collision Detection" is one of the best data structure literature I've read, it just happens to be about 2D/3D problem spaces).

This is why understanding the implications of memory access is so important. Paraphrased from the talk: Big O notation is really a blunt tool and sometimes those constant factors can be incredibly painful.

[edit]
They also have the nice property of being stable which can have some useful benefits.
Yeah. It's essentially creating a power vacuum.

People don't work without structure, ad hoc structures develop. The conjecture is that this is a good thing, that these ad hoc structures are more natural, and you will have natural leaders take lead where appropriate and this will be more effective.

But the issue is structure deals with quirks in human behavior. It deals with the emotional side of it, it deals with the cliquish, tribal nature of our default social behavior. You can put a highly productive, less social person into a position, give him a set of tasks to do, evaluate him fairly and see him produce. In doing this, you need an objective manager, you need a fair structure, and it works.

Without those things, the less social, highly productive person is easily sidelined. The person who takes leadership isn't given that position, they don't lead because they have been shown that they can motivate people to do great things, because nobody gives them that position. The people who get into leadership positions are those people who can convince other people to work with them on a personal level instead of on an organizational level. The really smart, less social person doesn't even get brought in to participate, and little power struggles happen between factions of people who want to be the person who directs the project, despite the fact that none of the people looking to do it might even be very good at doing it at all.

The real problem with traditional management structures is that it often breaks down to this sort of system to start with. Where the people building the systems aren't very good at it, and where they invite their buddies to be management because management pays the best, and they want to help their buddies out. It's because you have poor systems, and because you have the wrong people managing.

The issue with this is that rather than potentially falling short and missing the mark, they start with the worst of it.
How does it improve on rsync?
Could not agree more, the only downside is that some companies see you as a job hopper, but you can just explain to them that losing 30K-40K/year (aka staying in your job) is not an option
Canonical plans to switch versions of Ubuntu to its new Snappy package manager
The company I currently work for uses whiteboards, but simply snaps a photo of the whiteboard after a meeting/discussion/etc. and pushes it to some shared location. Works well enough for our purposes.
Yes, I am speaking from experience directly with a holocratic organization.
Xroach was way more fun.
My opinion is that if all of your talent & knowledge can be replicating by reading some guy's blog start-to-finish, then you're not someone I want to hire.

I'm not trying to be an ass, I'm just not sure you're aware of exactly what goes into good design. I'm not either, but I sure as hell know it takes more than reading someone's blog "start to finish" and "literally" being as good as "the next guy."

I also can't envision a world where keeping your best design work a secret could benefit you in any way.
Is this a true "leak"? Maybe I'm naive but I would think you couldn't have a leak without using JNI. Maybe a reference cycle is hard/impossible to GC?

>Later, in a background thread, it checks if the reference has been cleared and if not it triggers a GC.
> If the reference is still not cleared ...

Sounds to me like it's not a leak so much as unbounded-memory-growth.

But sounds like a useful tool. And I guess you can suppress warnings using AndroidExcludedRefs.java if you have intentional cycles.
Here are some more blog posts about the project: http://pchiusano.github.io/unison/

As far as I can tell, the goal is to put interaction with a UI on the same level as editing a program. To this end, Unison expressions, values and UI elements all live in a single syntax tree which can be edited in a structured way.

A demo would go a long way toward making this all clearer. Even some text describing what it would be like to use the finished product would help.
Not every leader is a good manager.
I liked 'polishing with a leather' myself. Adds a sense of mystery!
There are several entropy sources like this -Havege, jytter and Dakarand all tries to use jitter and unpredictable behavior in CPUs.

The chief advantage is that they don't need another HW source beside the CPU itself. I've been sceptic to how well they work on simpler architectures like ARM. (Havege for example tries to force cache misses in multi level memory system, which implies a need for caches). But at least Jytter actually seems to work fairly well on embedded CPUs too.

What to remember is to use these as entropy sources, not source for random numbers. Seed a proper csprng and use that to generate numbers. Quite a few CPUs today can implement AES efficiently so AES-CTR is probably a good choice in many systems.
But that involved unauthorised access by guessing (mostly default) passwords; that's a pretty standard definition of hacking.
An argument for open global immigration
That's good to know...I'm preparing a data set to test them now.
> In terms of where I am competing now though; he he; wouldn't you love to know :)

You seriously sound like a troll. It's hard to take you seriously, though I did make a response in good faith.
I got the impression that, in addition, electric engines are less profitable to maintain because they wear out slower, so maintenance and repair have a much lower profit. Is there any truth to that?
Now that is a one-sided article if I've ever read one. Not to say that her position wasn't frustrating- I imagine that it was incredibly frustrating- but yeah OK she gets fired from Valve and then immediately goes on to do exactly what she was doing at Valve with the same engineers at a spin-off company that has Gabe's blessing producing stuff for Valve. How is that a loss?

It sounds way more like Valve wanted to do something that was a radical departure from anything they'd ever done before (hardware), the intrinsic structure of Valve meant that it was difficult if not impossible to set hardware up to succeed (peer-evaluated hiring, bonus tied to value of work), and then Valve realized it wasn't working and decided to make a clean break instead of drag it out. So then Valve immediately says "OK guys we couldn't make this work within Valve but we will back you up 100% if you want to go make this work external to Valve."
The tension meeting makes it hard to avoid asking for support because it's so easy for people to bring up small problems as they're noticed and get quick resolution. Also, responsibilities are worded as objectively and measurably as possible (like good KPIs) to increase transparency into how people are doing in their roles. If a circle in an org like yours needs to avoid showing weaknesses to clients and to suss out problems before they're noticeable, they would be able to define those as responsibilities and assign them to the right people.

That said, I think one of the bets holocracy makes is that a group of people with a better understanding of their responsibilities and who receive quicker, clearer feedback will naturally be more proactive about problems. A circle is pretty unlikely to assign themselves the kinds of restrictive processing and reporting that are traditionally used to control interaction with clients in organizations that don't have perfectly reliable people. But in the short term, the control method would probably have more consistent results and that is not acceptable to every organization.