skysight-inc/HackerNews huggingface dataset:
Nobody can be bothered to quote the most important part of the article?

> "At Apple in 2007, organizationally it was the wild west," Burrough said. "I was hired under a particular manager, but for the first two years worked on projects that had virtually nothing to do with that manager's core responsibility. That's because the organization wasn't the priority, the projects were the priority. It was the exact opposite of 'not my job.' It was 'I'm here to solve whatever problems I can, irrespective of my role, my title, or to whom I report.' It was wild. But it was also very rewarding, because everything you did had maximal impact on the product."
>
> But today, the "dynamic has clearly and distinctly changed," and Apple is much closer to his job at Palm, said Burrough, who most recently founded a 3D printing company called Bilt It.
>
> "Working at Palm, the teams were highly organizational, [hierarchical] and responsibilities were siloed," Burrough said. "There was a clear sense that each person had a clear responsibility, and rarely deviated from it. When you went to someone for help solving a problem 'not my job' was a common response."

Is this something for startups to be worried about, introducing hierarchy and silo'ing and a culture of "not my job" especially as they grow rapidly?
> I disagree that I'm being "idealistic" (often used as a condescending pejorative by people who want to lower standards)

A poor word choice on my part. It was certainly not meant to come across that way, so apologies there! Agreed that a cost vs risk analysis should be one of the first items on anyone's list, especially given the perceived value of the digital assets in this instance.
It doesn't sound like the 'Agile' team is doing standups right.

There are either too many people in the room, or people are talking too much, and probably about the wrong things.

And, if they are doing standups wrong, I question how much else they are cargo-culting.
Snowden should be pardoned for his work revealing domestic wiretapping program, the other programs he leaked he should do his time for.
CIA 'Star Gate' remote viewing programme
Plivo 2016 Year in Review: 100+ Team Members and 3 Years Profitable
Is everything else between these two groups completely equal? I seriously doubt it is, in which case I don't think it's fair to make any conclusions that hold weight.

This is one of the problems I have with these sorts of things. My company went Agile about two years ago, and lots of people like to rant about how much better everything is now and how much more productive we all are because of it. Except we actually have no way of knowing whether it made any difference at all.
Yes, but for ISO you owe AMT. It amounts to ~28% federal tax rather than ~39%. But it's still a big number.
Though perhaps it's considered a component of 2), one could add Docker/containerization. I've watched folks spend weeks and weeks getting Docker setup for a service that probably didn't need to be containerized at all. And then once it's Dockerized, introspection/debugging/etc... seem to become much more difficult.
Thanks!
Yes, I do plan to get married before I make the move.
I saved up some money to spend two months traveling cheap with my GF before we make the full move and get into jobs.

Denmark is amazing in the sense that my GF's future employer(an University) says they will employ her partner(me) for an year according to my skills at market rate and also help us settle in with local culture and even help find jobs after the one year ends...
How would one go about mirroring these documents?
A map in a book: no algorithms
A book and some fruit: no advertising
A book and some yarn: non-profit

Even more than stock photos, maybe they should be somewhat, at all, related to anything. Yikes.
When visiting the residence of a user of such devices, how should a privacy conscious person approach the thorny issue of desiring one's voice not to be recorded and transmitted?
"We will never sell or give away any data concerning you. Not one single bit."

and

"Lyra Communications Ltd, UK reg. 10534260"

are unfortunately not really compatible statements, particularly after the IP Bill passed.
Pros and Cons of Bootstrapping VS Investment
Most countries have sane tax codes that say you only owe taxes when there's a liquidity event for you. The US is exceptionally bad in this respect of taxing illiquid paper profits, and of onerous lockup periods (SEC rule 144).

An investment of mine that yielded 5X exit transaction ended up being 1.3X for those reasons, and I was lucky - if it closed a couple of months earlier, I would end up with 40% loss and a useless tax credit.
Do they hash and store these possible 'other' passwords?
- 1) Choose languages that developers are familiar with, not the best tool for the job

95% of the time, a language that your developers are familiar with is the correct tool for the job simply for that reason! There are cases where it is not the case but those involve special case languages and special case systems. If you don't know what special case means then you're situation is almost certainly on that list.

- 2) Avoid microservices where possible, the operational cost considering devops is just immense

"If your data fits on one machine then you don't need hadoop ..." Same thing applies here. Microservices have place and putting them in the wrong one will bite you bad.

- 3) Advanced reliability / redundancy even in critical systems ironically seems to causes more downtime than it prevents due to the introduction of complexity to dev & devops.

Then there's probably something wrong or limited with the deployment that needs to be reviewed (2 node when you need a 3 node cluster, bad networking environments, etc.) If you have a reasonable setup with solid tech under it, deployed per specs then this should not be true. If, on the other hand, something is out of whack (say running a 2 node cluster with Linux HA and only a single communication path between them) you're going to have problems and the only way to fix them is to get it done right.

- 4) Continuous integration seems to be a plaster on the problem of complex devops introduced by microservices.

I'm not sure about this but, if your deployment system requires CI you have a problem. An individual, given hardware and assets/code, should be able to spin up a complete system on a fresh box cleanly and in a reasonable timeframe. (Fresh data restores can take longer of course but the system should be runnable barring that.) If this requires (i.e. it can't reasonably be done manually) something like an CI script or ansible/chef/etc. script then you're deployment process is probably too complex and needs to be re-evaluated.

- 5) Agile "methodology" when used as anything but a tool to solve specific, discrete, communications issues is really problematic

Agile is commonly used to gloss over a complete lack of structured process or a broken. Even with Agile there should be some clean process and design work that goes into things or you're hosed.
> Ask yourself: after you watched that, did you get any idea at all of what they were trying to say? Even from a creative perspective?

Yes. It was fairly clear. "One idea links what we do" (despite you misspelling the copy in your own comment), it goes on to show how the branding can be used in it's various events and endeavors. The goal is to introduce the new brand, not Mozilla and all that it does.

Your solution doesn't solve that problem. For example, with the new brand, you ignore show how this works with All Hands[1], something you dismiss as "all hands." Already your "solution" fails at showing the branding at work.

1. https://wiki.mozilla.org/All_Hands
I think it looks like a marvelous idea, but the question is, how do you intend to afford to run this with all this promises of zero advertising, never selling out to investors, and remaining nonprofit forever?

Please don't misunderstand me, Wikipedia is also nonprofit and seems to work quite well, and it's a noble goal. I just happen to also remember my "eternal, irrevocable and always free" name@usa.com email address. They went bankrupt pretty rapidly. (I'm pretty sure that was the domain then, now it seems to be owned by some guide to US states and cities.)
Thanks! Needed to hear that from someone else.
She doesn't do statistical studies, no. But I think she has good sense of the relative confidence she can have in "new discoveries" and older institutional knowledge (which also isn't 100%). And sometimes she puts in more time and attention than a few previous doctors did, considering all the symptoms and previous attempted treatments, to come up with an accurate diagnosis and effective treatment. By not being dogmatic, and spending a bit more time, she can fix some things.

I don't usually "do science" the statistical way either, I usually come up with a plausible theory for a bug, fix it, and use the results to confirm or refute my theory of that one bug. Usually it's something dumb, simple, and obvious in hindsight, not a whole new algorithm or technique.
They prefer London because the jobs and the money are there. Will they prefer it in the future? Who knows. Plus, Paris is more beautiful and enjoyable (subjective, but I'm sure most would people would agree).
This time it was a statement of fact, he said they will move the staff.
Hiring is the primary source of dilution at new companies. Stock packages have to come from somewhere.

Also, equity rounds reduce your percentage ownership, but (usually) not the current value of the stock you hold. If a $100M company raises $100M, the number of outstanding shares doubles. However the company is now worth $200M (the cash in the bank counts towards valuation). Now, your 1% share is a 0.5% share, but it is still worth $1M. If the company spends the $100M without growing, then the funding round was a mistake, and your shares are now worth $0.5M

So, spending money lowers the value of your stock. Issuing shares lowers your upside at a fixed future valuation. If management knows what it is doing, raising cash should increase the chances the company grows, and so should hiring.

(these calculations are oversimplifications, but the intuition is right)
http://www.mozilla.org
When meeting with clients or other teams in a big organization, it's obviously discouraged.

When speaking with colleagues, it's discouraged only when there's people who are trigger-happy about complaining to HR. Fairly or not, women in particular have a reputation of running to HR when someone says something offensive or crude, which leads to them being excluded from office banter, which leads to them feeling left out of the group. Tough problem to solve.

It makes sense really. You let the profanity flow when you feel that you can trust people. You're also most honest when you feel that you can trust people.
> Instead the EU plans to simply pass new laws in order to force the people who live in London to sell their homes, pull their children out of school, learn new languages and move elsewhere.

I think you've got this the wrong way round. The UK voted to leave the EU, and its not like nobody in the run up mentioned that it might lead to companies leaving the UK for EU countries. We made this bed. Time to sleep in it.
I wouldn't call it "tech debt". Present-day AC systems may not be completely optimal (given current electronics technology), but they do work well.

As I understand it, "tech debt" is something that has to be reckoned with at some point, or else you're going to have real problems in the future (just like refusing to pay off a money debt will generally cause you real problems at some point when the creditor sues you and gets a judgment). You can't just let it go on forever; eventually you need to "pay it down" (by cleaning up the codebase, migrating to newer technologies, etc.), or else catastrophe happens (the company is unable to compete and goes under). One common factor cited in these stories is that the code becomes too unmaintainable and unreliable: too many weird changes for customers pile up and introduce serious bugs which cause the product to not work properly.

This isn't like that at all. We can go on with our current household AC power systems indefinitely. Maybe we could get a 1% improvement by switching to DC systems (at an enormous cost because most of your appliances and devices won't work with it without adapters), I don't really know exactly how much better DC would be (not much really), but what we have now works fine. Furthermore, it's not like the whole electric grid system needs to be changed: it's entirely possible, for instance, to switch distribution systems to DC and leave household systems AC. Instead of distributing the power at 30-something kVAC in your neighborhood and using outdoor transformers to step it down to 240VAC for your house, it could be distributed in DC form, and those transformers replaced by modules which convert the 30-something kVDC to 240VAC. In the old days, this was hard and expensive to do, but with modern power electronics it's not. But even here, the question is: are the gains worth the expense? And the answer is very likely "no". (For reference, I'm not a power engineer, I just studied it in college as a small part of my EE curriculum.)

So this does not, to me, resemble "tech debt" at all. It's just a system that we use for legacy reasons and which is extremely reliable and works well, even though it might not be the absolute most efficient way to solve the problem. This is no different than many other engineered systems. Perhaps you have a decent and extremely reliable car. Could it be better? Sure: you could build the chassis out of carbon fiber, use forged aluminum wheels instead of cast, etc. all to save weight and improve fuel economy. Are you going to do that? Of course not, because the cost is astronomical. There's cars like that now, and they cost $1M+.

So for AC systems that we're talking about, the question is: what is wrong with them that we want to consider replacing them with something else, instead of just sticking with them even if they're not quite as efficient as they could be? Because the cost to upgrade them would be enormous, so you need to have a very good reason.
Beautiful, thoughtful. I love seeing the intersection of science and art through such a talented artist!
Seems like people think using Agile and using your brain is an either-or kind of thing. It's not magic.
Yes, we are over complicating software development.
Absolutely, in no way am I saying their cloud offering is successful. What I am saying is they have shown you can be successful with the very same ideals and goals that the RethinkDB team had, with a very similar developer-minded audience. The biggest factor here is obviously the platforms their database runs on - Mobile (or local as you put it nicely) vs cloud.
Scrum != Agile. Heck its sounds if your doing scrum wrong anyhow.

Kanban board, prioritization, CI + CD, automated tests is probably about as much agile as most companies need.
This is about the 3rd or 4th attempt at this idea since I attempted it. My effort was moderately successful:

http://lifehacker.com/deeper-history-searches-the-contents-o...

http://www.hongkiat.com/blog/chrome-deeper-history/

That being said, there are serious security concerns with kind of project (which is why I stopped development) and likely why full text search was taken out of Chrome by google years ago. It is not insurmountable, by any means, but I didn't like the idea of know that if I was successful and reached a very large audience that I might also be responsible for serious identify theft and other hacks.

I'll also point out that I did collect usage stats for a time, and they were horrific. At my peak I had ~5000 installs and out of those 5k something like 3-5 searches/day was the norm.

I would be happy to share my experience with the dev team. I still have code that may be of use as well.
And all startup employees are expected to know all these rules? Before I joined a startup I spent days researching all the rules about options and I still didn't quite understand all the nuance.
US, Russia, Asia don't care. London does clearing and derivatives work in dollar, renminbi etc without any of those countries having problems with it.

If you check, you'll find it's only the EU that has a hangup about the physical location in which euro-denominated transactions occur.
Anything that differs from uniform grey goo is discouraged in business.
Hy is also great, but it is even further away from Clojure than Pixie is.
Isn't "5M JPY investment" (45k USD) the requirement for the visa, not the cost?
I am working in huge non-IT company as a software developer. I guess that is what gives me a totally different point of view on your lessons:

1) Without a unified technology stack and a common framework we would not be able to build and maintain our applications. We decided on C# as it works best for us. Currently we are 5 developers. Not a single one of us has ever written a line of C# code before entering the company - learning the language from ground up enables us to pick up patterns that our colleagues who joined the company earlier found to be best practices.

2) If you are not introducing a whole new stack with every micro service that you develop the devops costs are quite low.

3) I agree with you on that - I think redundancy always introduces more complexity. However there are systems that handle that job quite well (e.g. SQL Server). For application servers we use hot-spares and a load balancer that only routes traffic to them, when the main servers are not reachable. This works for us, as all our applications are low traffic applications.

4) Continuous integration works brilliant for our unified stack. In the last two years we went down from 1d setup + 20min deploy to 10min setup + 20s deploy.

5) We use agile methodology whenever possible and it works like a charm. However we had a lot of learnings. Most recent example: Always have at least one person from all your target groups in any meeting where you try to create user-stories.

Planning our software architecture has been a key element in my teams success and I do not see a point where we are going to cut it.
Russia extends Edward Snowden's asylum
Check out startups growth strategies
I read the same blog when I had issues, and I've had it on more than one openbsd machine 5.9 and 6.0

phobos :: ~/Ghost » npm install --production
npm WARN prefer global forever@0.15.3 should be installed with -g
npm WARN unmet dependency /home/dijit/Ghost/node_modules/amperize requires image-size@'0.5.0' but will load
npm WARN unmet dependency /home/dijit/Ghost/node_modules/image-size,
npm WARN unmet dependency which is version 0.5.1
npm WARN unmet dependency /home/dijit/Ghost/node_modules/ghost-gql requires lodash@'3.10.1' but will load
npm WARN unmet dependency /home/dijit/Ghost/node_modules/lodash,
npm WARN unmet dependency which is version 4.17.4
npm WARN unmet dependency /home/dijit/Ghost/node_modules/knex-migrator requires bluebird@'3.4.6' but will load
npm WARN unmet dependency /home/dijit/Ghost/node_modules/bluebird,
npm WARN unmet dependency which is version 3.4.7
npm WARN unmet dependency /home/dijit/Ghost/node_modules/knex-migrator requires debug@'2.2.0' but will load
npm WARN unmet dependency /home/dijit/Ghost/node_modules/debug,
npm WARN unmet dependency which is version 2.6.0
npm WARN unmet dependency /home/dijit/Ghost/node_modules/amperize/node_modules/nock/node_modules/chai/node_modules/deep-eql requires type-detect@'0.1.1' but will load
npm WARN unmet dependency /home/dijit/Ghost/node_modules/amperize/node_modules/nock/node_modules/chai/node_modules/type-detect,
npm WARN unmet dependency which is version 1.0.0
npm WARN unmet dependency /home/dijit/Ghost/node_modules/brute-knex/node_modules/ghost-ignition requires debug@'2.2.0' but will load
npm WARN unmet dependency /home/dijit/Ghost/node_modules/debug,
npm WARN unmet dependency which is version 2.6.0
npm WARN unmet dependency /home/dijit/Ghost/node_modules/brute-knex/node_modules/ghost-ignition requires prettyjson@'1.1.3' but will load
npm WARN unmet dependency /home/dijit/Ghost/node_modules/prettyjson,
npm WARN unmet dependency which is version 1.2.1
npm WARN unmet dependency /home/dijit/Ghost/node_modules/ghost-editor/node_modules/ember-cli-babel/node_modules/broccoli-babel-transpiler/node_modules/babel-core requires
npm WARN unmet dependency /home/dijit/Ghost/node_modules/bluebird,
npm WARN unmet dependency which is version 3.4.7
npm WARN unmet dependency /home/dijit/Ghost/node_modules/ghost-editor/node_modules/ember-cli-babel/node_modules/broccoli-babel-transpiler/node_modules/babel-core requires
npm WARN unmet dependency /home/dijit/Ghost/node_modules/lodash,
npm WARN unmet dependency which is version 4.17.4
npm WARN unmet dependency /home/dijit/Ghost/node_modules/passport-ghost/node_modules/ghost-ignition requires debug@'2.2.0' but will load
npm WARN unmet dependency /home/dijit/Ghost/node_modules/debug,
npm WARN unmet dependency which is version 2.6.0
npm WARN unmet dependency /home/dijit/Ghost/node_modules/passport-ghost/node_modules/ghost-ignition requires prettyjson@'1.1.3' but will load
npm WARN unmet dependency /home/dijit/Ghost/node_modules/prettyjson,
npm WARN unmet dependency which is version 1.2.1
It took an Industrial Engineer to get rid of the headphone jack.
For what I care, the feature in itself it is not new, but I am happy to find out things in the JVM space that I haven't known about before. Especially since Java 8 came as one of the biggest releases to date in terms of new features and functionality added to the language.
Maybe it's just me but I find this series incredibly annoying to watch. I doubt I can tolerate 5 hours of these two. Each hour of video has 10 minutes of content.
Straight honesty isn't always a virtue. Plus cussing signals lots of other things, too.

I cuss a lot at work. But I don't cuss at people. I have a coworker that says things like "It's fucking ridiculous that X task isn't done" to the people who are doing that task. This dude is toxic to be around. I... think I'm not? We'll see how many of the people I'm managing still work here in a year, though. Hopefully all of them.

So yeah. In addition to signaling honesty, cussing can be part of aggressively damaging relationships, which is something businesses (and HN) benefit from discouraging.
It never seems complicated when I am doing my own side work for some reason. There are no design meetings, no hours tracking, no arguments on best practices, no scrum, no testing frameworks, dev ops, etc. I do use git and minimally create bash scripts to simplify repetitive tasks for deployment but its just a huge contrast to working in teams where something simple takes about 50 times longer.

I think keeping things as simple as possible and always going for that goal will increase velocity overall. Everything should be subject to scrutiny for promoting productivity and open to modification or removal. I know there is a balance where you have to increase complexity in a team environment but keeping friction as low as possible in terms of process and intellectual weight couldn't hurt.

The most productive place I've seen so far is a huge athletic brand I worked for where they kept teams at max 5 people in mini projects. This forced the idea of low overhead and kept the scale of management needed small. The worst place I worked for in terms of unnecessary complexity is a well known host, although it is the best place to work in terms of people, hired offshore that has a one-size fits all mentality and layered in as much shit as possible to slow down development to a mud crawl. I don't buy into process over productivity.
When GIMP happens to be not the best tool for photo editing (Photoshop definitely has an edge in this department), I turn to the excellent darktable (http://www.darktable.org/).

Since I don't do any paper printing pre-processing that requires CMYK support, the duo above completely replaces Photoshop for my tasks.