skysight-inc/HackerNews huggingface dataset:
Most guru's take an 'all or nothing' approach, this goes beyond programming, look at food-guru's "eat only carbs, never eat refined sugar" etc. This is for me the same as "always do TDD, never use static methods".

People without experience often look at guru's because they can not yet think for themselves.

I'm a developer in my 40s, have done a lot of projects in a lot of different companies. Having this experience gives me intuition about what to do in what situation. I just (think I) know when I should write a unit test and when not.

The 'all or nothing' attitude is created by people who want to be guru's and is followed by people who want to have some guidance.

This is not a bad thing, it takes time to shape yourself as a programmer. This takes years: http://www.norvig.com/21-days.html

Learn from the guru's, and be consious, people preaching an 'all or nothing' view of the world are NEVER right :)
The banality of evil. So many engineers just want to make the trains run on time with a better algorithm. Never mind that they cary oil or weapons or the victims of our next genocide. Engrossing technical problems are convenient blinders for inconvenient truths.
Agreed fuel cells remain very exciting and maybe patience will be rewarded
How to Return to the Top of a Web Page
I didn't notice if the HAP switch is available on earlier (pre ME 11) hardware.
And it's not like they'll just take the night off because of a solar eclipse.
New app uses smartphone selfies to screen for pancreatic cancer
Wouldn't those trade offs just be picking a different language? I mean Rust is going for no runtime low level systems programming, if you add a runtime, then it brings what more to the table then say Haskell?
Click on the headline to see an explanatory paragraph. (Terrible design. Why is it hidden?)

Also, there is a detailed explanation on the site here:
http://hevea-project.fr/ENPageToreDossierDePresse.html

It's hidden behind a link labeled "Folder", which doesn't really make sense in English (it's a direct translation of French "dossier").
7 Ways SaaS Companies Can Increase Conversion Rate
In-person interviews added to employment-based green card applicants
F# clearly lags behind C# in editor attention and integration into the latest and greatest GUI techs from Microsoft...

For many on the MS treadmill this is seen as a negative, as you can't always get visual studio RCs and be months ahead of the competition on the next version of blend/WPF/silverlight/whatever.

For others, the community driven aspect and lack of obsessions with technical fashion in the MS product line (with the track record they have...), is seen as a _major_ feature.

F# has a much more active open source community and presence than C#, most of the devs are actively cross-platform in a way C# still struggles with, and it has a better .net stack than C# aimed at command line efficiency and relatively stable approaches to common problems.

F# is still a first class language from MS, and would be quite OK on its own these days. Regardless, there is no chance MS will "lose interest" in F# given the impact on data science, machine learning, cloud computing, parallel computing, and stream-processing F# has. MS invested heavily in filling out their language portfolio to avoid being excluded from the big servers and big clusters. Time has shown those concerns to be growing, not shrinking :)
I wouldn't go to a $1200/day developer for a slackbot... it's not like a slackbot is going to be central business logic, almost by definition.
AngularJS Web Application Development Company| Hire AngularJS Developers
It would still apply. Them taking a percent of my money every trade hurts me. Is there any guarantee that my profit per trade is larger than their fee per trade?
> Toyota has been making some bad business decisions lately. They don't make battery electric cars. (They're fixing that, but won't be shipping until 2022.[1]) Instead, they've been pushing cars that run on hydrogen. Toyota sells the Mirai in California, and has a few hydrogen stations so it can be refueled. They sell about a hundred cars a month.

I can't speak to their autonomous technology, but Toyota has always been a leader in electric vehicles, from the early hybrids, to partnering with Tesla, to impressive long term improvements in fuel cells even after the U.S. Gov. Moved on to batteries.
Arguably Toyota has more electric vehicle prowess than any other company. It is relatively small potatoes to change the source from open system cells to closed cells, especially when many of battery manufactures are also Japanese.
Its really a matter of someone building it and networking effects and momentum turning into popularity, but there are at least a few decentralized platforms out there that could create a non-profit open source non-commercialized Uber alternative that individuals who want to sell taxi services could use. The key part is obviously decentralized payment -- something along the lines of Bitcoin or Ethereum (lightning networks? etc.) is needed -- but there are increasing numbers of less well-known options.

It may take a few years but there is just too much incentive to move away from the technopoly companies like Uber, Amazon, and Google etc. to decentralized open platforms.
Rizin FF[1] is the new PRIDE, in essence. It too has a 'relaxed' stance on PEDs.

[1]: http://www.rizinff.com/en/
I'm also wondering why the article is skipping pypy ? It's a python JIT which often be used as a drop in replacement of cpython.
Criticizing code for not being "clean code" is 70% of the time "I don't like this code for various reasons"

Not to mention of the pedantism of one of the biggest proponents of clean code.

So, in essence, worry that your code has a certain quality but in the end all projects will end up in the trash can. It's software, not the Mona Lisa.
In lectures on management focusing on people (not necessarily strictly HR, like what traits you want in certain roles) you often hear that one of the worst thing you can do is to promote the best salesman to head of sales, best programmer to head of engineering, etc.. Their qualities make them good at production, not management. There is a lot of truth to it.

The problem you describe is what some people call "excel managers" - managers who only juggle numbers and have no idea how processes work. I have seen some management course material and quite a lot of those focus entirely on production line management. There is nothing wrong with that. Problems arise when managers adept at controlling production line processes are given control over projects.
Why should I choose BEM as a modular solution for CSS?
I think you meant to say "US Government, as a policy, never tells the truth". If they did, we the people would have thrown them out on their asses before their terms are up.
The UCI is relaxing some of its aero rules, though: http://www.cyclingweekly.com/news/latest-news/uci-set-to-scr...
Tokyo and Shanghai has MUCH more people compared to Houston and it makes more economical sense to have more train infrastructure
I agree, Clean Code was the most important book for me too. But I wouldn't follow it blindly. Also, it's less useful for non-Java and much less useful for non-OOP languages (it's ok to have a focus, but one has to keep in mind that sometimes, certain idioms, best practices or design patterns are actually workarounds around the limitations of Java).

My favorite example: Overdoing the short functions thing. I've seen this a lot. Unsurprisingly, considering that for most devs, when you ask them what makes good code, "short functions" seems to be the first thing that comes to mind.

Splitting code into extremely short functions has a few disadvantages too: a) in what order they're called is not immediately clear, b) where they can be called from is not immediately clear, c) going up/down the stack can make it harder to follow when debugging interactively. d) It increases the LOC and noise. And e) especially in OOP languages, short methods make it more tempting to turn variables into attributes to avoid passing them around explicitly (bad due to longer lifetime).

Splitting functions should only be done if it makes sense semantically. Each function should make sense on its own. If some logic is highly cohesive (e.g. because it implements a specific algorithm), not independently reusable, and it's subblocks only make sense in one order, and it all fits on a few screenfuls, it might make sense to keep it in one longer function instead of dividing it into fairly arbitrary chunks.
The issue, of course, is that when people inevitably start losing the entirety of their savings in a fraudulent "investment", either the state is left picking up the tab or we wind up with a starving, homeless elderly population. Neither are acceptable outcomes, in my opinion.
If they had a solid revenue model, they might be a good target for blockchain fundraising. I dislike the term ICO, because a token makes zero sense for this company. They could do what we're doing and sell shares (token-shares/blockchain bearer shares). I think we'll see a turn to this model in the post-ICO era, once the hype dies or the bubble bursts.
To add to that, you can treat it like you would schema migration on databases: implement v1 to v2, v2 to v3, etc... and replay the migrations in order to migrate from whatever version of the event is to the latest version. This allows keeping event migration code as immutable as the event versions it migrates between.
They're probably already damaged badly enough from the lack of sleep in peacetime that they'd underperform on any less during an active operation.

This is like giving your sailors food poisoning every week to make them tougher. You just make them weaker instead. And when the time comes, you don't get soldiers capable of eating rotten food. You just get weak people.
> They don't have permission to write files as root without the help of polkit and pkcon. They can write files as root with the polkit policy's help. Broadly, or not... intentionally, or not! As an outsider coming from another distro, I would argue that policy does not follow the "principle of least surprise."

There are other services running which create files as root on other distros, too. Have a look in /tmp for example.

> If you set up sensible per-user disk quotas, you will prevent this.

If you are able to set-up per-user disk quotas, you're able to also change the policy.
Creating Push Notifications in Android O – Part I
I've read the explanation of the construction of the flat torus on TF-web-site. But I fail to see what kind of consequences this construction has. Does it open the way to new solutions to old problems, have practical applications or is it, for the moment, "just" a nice mathematical object ? (I'll be 100% satisfied with the later, it's incredibly mind bending)
As soon as the Western Australian state transit agency started submitting data to Google Maps, they released it to the public. http://www.transperth.wa.gov.au/About/Spatial-Data-Access

This has been going on for about 10 years. There are good people in this country doing good things.
Your partners talk to each other.

The problem with all economic simulations is that they assume extreme individualisation. Because that is what they want the world to be like.

In reality the world is a network. Reputation matters.
Tokyo's population is about 4 times that of Houston. So fine, instead of running 3000 trains a day from the central station, you can run at least 750?

That's what life would look like if people in the US actually used trains on a regular basis.

In any case, all I'm saying is that if a massive number of people need to be moved, trains can scale well, additional reserve capacity can be deployed during evacuations, and it's also a lot safer than having hundreds of thousands of people taking to the roads in bad weather.
China Internet Report 2017
Living Off the Grid: 7 Places in the U.S. You Should Consider
So You Want to Go Off-Grid
California may or may not be in the wrong here; I don't know, but I don't think there's enough information in the original article or the one you link to make that determination.

State residency is a complicated topic with no "bright line" rules that will definitively decide the issue, but California residency has a set of guidelines called the Bragg Factors that courts use in a "totality of circumstances" sense to determine residency. They are:

1. The location of all of the taxpayer’s residential real property and the approximate sizes and values of each of the residences;

2. The state wherein the taxpayer’s spouse and children reside;

3. The state wherein the taxpayer’s children attend school;

4. The state wherein the taxpayer claims the homeowner’s property tax exemption on a residence;

5. The taxpayer’s telephone records (i.e.1, the origination point of taxpayer’s telephone calls);

6. The number of days the taxpayer spends in California versus the number of days the taxpayer spends in other states and the general purpose of such days (i.e., vacation, business, etc.);

7. The location where the taxpayer files his tax returns, both federal and state, and the state of residence claimed by the taxpayer on such returns;

8. The location of the taxpayer’s bank and savings accounts;

9. The origination point of the taxpayer’s checking account transactions and credit card transactions;

10. The state wherein the taxpayer maintains memberships in social, religious and professional organizations;

11. The state wherein the taxpayer registers his automobiles;

12. The state wherein the taxpayer maintains a driver’s license;

13. The state wherein the taxpayer maintains voter registration and the taxpayer’s voting participation history;

14. The state wherein the taxpayer obtains professional services, such as doctors, dentists, accountants and attorneys;

15. The state wherein the taxpayer is employed;

16. The state wherein the taxpayer maintains or owns business interests;

17. The state wherein the taxpayer holds a professional license or licenses;

18. The state wherein the taxpayer owns investment real property; and

19. The indications in affidavits from various individuals discussing the taxpayer’s residency.

Presumably all of these issues have been hashed out and documented in court.
Four of the Best Places in the U.S. To Live Off the Grid
"...and Edwards drew his gun" - I think this is the situation where the problem arose, not the license plate scanning itself
Generating Off-Grid Power: The Four Best Ways
Technology to Proactively Run a Healthcare Organization
Redash: https://redash.io/

Self-hosted option absolutely annihilates Chart.io and Periscope Data on pricing.
I think the problem here is that 'clean' is an umbrella term for a bunch of different things. To sum them it is: 'how does this code make me feel inside'. But what goes into that are: readability, extensibility, maintainability, testability, clarity, correctness, simplicity, and yes, aesthetics. Some of these are objectively always good, and some of them are contingently good.

For instance, a simple algorithm for distributed consensus is probably not correct, and you should rightly not view it as 'clean'. Some things simply aren't simple. The goodness of simplicity is contingent on the complexity of the problem.

But aesthetics is at the final end of the spectrum: it's purely subjective. And yet we wrap all these things up under the term 'clean', and so it is confusing. People will defend their notion of cleanliness using the objective standards, and then apply it to the subjective cases.
I'm writing this from the UK, where the costs are much lower. But you're right, it's still a very substantial investment. I want to do some volunteering and hear from others before I take the plunge.
In the Battle of France in WW2 some German commanders (pretty sure it was either Rommel or Guderian) would regularly have radio "problems" isolating them from their HQs when they found tactical opportunities they wanted to exploit.
On cultured meat, the biggest win will be environmental because CAFOs are flatulent-powered atmosphere procession stations, e.g., "climate change" is a nice manta but it's more honest to say "we're currently terraforming ourselves onto an inhospitable planet."
Well, that is the approach of the new Fitbit smartwatch.

It makes use of only SVG, CSS and JavaScript.
RE: Automated testing.

Modulo certain forms of static analysis, your code is ultimately only as good as it is well tested[1]. Non-automated tests do count here, but for long-maintained codebases the cost of automating pays for itself very quickly.

1: Note that pretty much all code has been informally integration tested (A "can I run it" type of smoke-test is a very simple integration test). Similarly all compiled languages (and any interpreted languages that parse an entire file before running code) has some static analysis, as syntax errors will be caught. Unless you check in code without compiling or running it, you are already doing some testing.
> Bannon's estimate of 20 million is perhaps exaggerated, but probably not by that much.

It is exaggerated by two or three orders of magnitudes from most published estimates.

For that many people to die, the entire population of Seoul ( 10 million ) plus half that of the greater metropolitan area would have to move to the northern regions of the city within range of the North's artillery and the latter would have to be 100% fatal.

Even counting the population of cities between the DMZ and Seoul only adds two million.
For most everyday plotting tasks freedom is overrated. What ggplot gives you is unparalleled productivity, combined with a 'grammar of graphics' API that makes it very pleasant to specify and experiment with visualizations. It's also easy to make ggplot look publication ready with little effort.

If you need something highly customized it can be quite a bit of work, but at least in my experience you almost never do.
Please, it's just "gurus", no apostrophe needed.
Where is your evidence that the lack of this regulation would lead to that outcome? Plenty of countries don't have these regulations. Most, in fact. Europeans and Canadians have no legal problems participating in these ICOs. Perhaps I simply haven't heard about the massive elderly starvation problem it's causing over there.
Instead of listening to a podcast/audiobook once on normal speed, you could try listening to it twice on double speed.

* Especially audiobooks generally have only one core idea so even if you miss a part, you're not missing much.

* By listing twice, you will 'revisit' the topic, increasing comprehension.

* Most podcasts/audiobooks actually don't have a lot of new ideas (especially after you've heard a lot of them), so in those cases you're only wasting half the time.
How Can Predictive Analytics Enhance Customer Experience
I think the point was that the costs are justified by the burden of meeting regulatory requirements, not the benefit of the regulation.
There are a few things I consider when I try to improve performance of my code.

1) I really like the advice of "make it run, make it right, make it fast" [0]. First I build it, then I write a thorough test harness (or make multiple versions run at the same time and check their results at runtime), then I rewrite it.
2) I don't really like optimising to the core, like it's mentioned in the article, things like Cython and numba often add dependencies that don't port well and they may reduce legibility and maintainability (that's more about Cython than numba). What I find most useful, and this should be obvious, that algorithm/data structure changes often yield the biggest benefits.
3) The old rule that if you speed up code that only runs 1% of the time, you're not gaining that much, I try to keep that in mind. (There are exceptions, of course.)
4) Performance is not just runtime, it starts with coding it up in the first place. So start to finish, you're not always better off with a fast language. If it's a one-off, it can be more performant to use a slow language, if it's a tool that will run untouched, you might want to spend some time tinkering with it. Etc.

All of this seems obvious in retrospect, but it took me a while to appreciate these principles.

[0] https://www.facebook.com/notes/kent-beck/mastering-programmi...
As the VP engineering of a company in the Build process our CEO do most sales thing and won’t hire capable people and fire incapable people. What should I do?
> scapegoat

I wouldn't be surprised that happened ultimately, but I really don't think that she was hired with that role/goal in mind. No one could be that evil. Could they?

If you look at the history of reddit over the years, they've always lurched from one crisis to another. An absence of adult supervision. Reactive solutions.

I would bet that reddit was under pressure to monetize somehow and ads (a la Facebook) on that "community" wouldn't cut it. I believe that they had an influx of funds around the same time, and the investors were looking to start getting some returns.

Their various stealth marketing schemes were suffering at the hands of the entrenched trolls. The unsavory subreddits were probably putting off established customers.

Maybe Pao just happened to be at the wrong place at the wrong time.

yishan's comment is interesting, thanks for linking to it. I didn't follow the whole Pao affair, but I do remember someone telling me that yishan might have been trolling reddit.

One thing jumps out at me from his comment. He calls Pao "the only technology executive anywhere who had the chops and experience to manage a startup of this size, AND who understood what reddit was all about."

Technology executive? Really? That's news to me. I thought she had spent her pre-reddit days in finance.

And she definitely did not understand reddit.
Make it easy to throw away; you will, anyway (to mix-gurus).

The problem with modules that are easy to throw away is that the hole they leave is not so easily discarded. This negative space traces the module boundary; the interfaces between modules.

The only way to throw away interfaces is to throw away...? Everything. You will, anyway.
Recently enough a group of doctors went on strike with perhaps one of the most reasonable demands I have ever heard. They didn't want to continue to do shifts that were over 24 hours long!
At least the name sounds female if you didn't know the guy.
I guess it's a success.

Edit after flagging: I forgot that you can't be snarky about the anti-feminism of Silicon Valley here on hacker news. Duly noted.
You don't lose anything (assuming your whole team uses the same bouncer, which is a good solution, IMO), logs will remain saved on the disk drive, but people will be unable to connect. Personally I have a bouncer running on a VPS since 2008 with 100% uptime so far, costs me $3/month and is used by 10 people.
Show HN: A video podcast for engineers with unconventional backgrounds
I love the story about a group of American car manufacturer executives visiting factories of Japanese car manufacturers in the 80's. After returning to the US they were asked about their visit and they remarked that the Japanese did not show them their real factories, as the Japanese factories were too clean according to the American executives. As it turns out, a clean work environment (and that includes source code) has benefits if you are doing logical work.
Ya, I think a financial literacy test could be appropriate, although that's not my preferred solution. I'd prefer it all be mediated by civil law. That is, everyone is free to do what they will: create financial products, purchase financial products. But the court system would intervene in cases of clear deceit, or manipulation of naivete (obviously there's some subjectivity here, but I think that's ok).
Indeed. You aren't insuring one driver anymore, you're insuring a million instances of the same algo.
The Russians have already mocked the UK's new carriers as "large convenient targets". Sinking of one of these carriers by the Russians also features in a (not particularly good) novel by a retired UK general about a war with Russia.