skysight-inc/HackerNews huggingface dataset:
Raising seed money for the first-time entrepreneur
You can find more information here (no specific figures though): https://fsf.org/appeal
Any plans for adding wifi or bluetooth capability? I admit I have little hardware knowledge, but would those normally be separate chips, or are they going to be part of the SOC?
The start of the comment is really out of context here.
What he wrote about the team case (what most of us are payed for) is this:

When coding on a team, I modify my strategy to carefully test code that we, collectively, tend to get wrong.
I could change the email if I know the username and password. I could change the username if I have access to the email and password. If it adds no benefit then it should be removed.
"I get paid for code that works, not for maintainable code."

Ah, I get it. That explains the piece of s--- I'm looking at right now.

That said, the title might be sensationalist, but I agree with the holistic sentiment of the text.
> "If I don’t typically make a kind of mistake (like setting the wrong variables in a constructor), I don’t test for it."

But for those of us who work on a team, it's far more complicated than that, and you have no idea who might be touching your code in the future.
It will be interesting to see what happens in the next economic down turn. I'd imagine that lunch delivery is one of the first things companies and individuals would cut back on.

Given their current state, that doesn't bode well.
There are enough people in the industry who are actually paid for writing the tests and discovering the potential failures of the mission critical code, where the tests are fundamentally important.

I've had a small team nicely paid for months only to prove and document the that the product my company was to deliver won't fail in some specific scenarios, specified by the contract.

Those who don't produce the mission critical code (or believe what they produce is not on the critical path) unsurprisingly see the investment in the tests questionable. Of course, there is always a real danger of doing something "just because it is done" even if there's no real need.
There are many processes that produce CO2. The article mentions cement. Cement production accounts for about 5% of CO2 emissions according to a quick Google.
What do you mean, you should not be testing internal implementations anyway? Does that also mean you don't do unit test, only integration or end-to-end ones, because unit tests are tests of the internal implementation of your software?
Yeah, Nah;

Maybe something like this is more useful to you if you wish to control what services have internet access: https://github.com/subgraph/fw-daemon
I switched to Lyft. Problem solved.
Not totally sure what you mean by "out there", but it holds up just fine for me. People comment that I have a good looking watch and only really notice that it's a smart watch when they try and see why I'm fiddling with buttons to read and dismiss notifications.

My only complaint is they try and be clever and detect when you move your wrist up to look at it, so it auto-shows you notifications. This sucks because it's not totally reliable (so half the time I press the button to bring up notifications and it ends up dismissing them because they are already in view, and other times it triggers due to an incorrect motion). I wish you could turn that off but I haven't found a way yet.

I've had this watch for about 3 months now. The first charge only lasted about 2 weeks but after that I actually got more than 30 days on the 2nd charge and going strong on my 3rd charge now, so the battery life claims definitely are true (though I did uninstall the weather app cause it was useless).

The build quality is good. People say it's a little thick but I guess my arms are big enough that I don't notice. I got the leather band and it's never felt uncomfortable to me.

I would recommend a screen protector (Amazon has some good fitting ones for cheap) but that's probably because it's been a decade since I wore a walk and got a tiny scratch because the first day I wore it I accidentally flailed my arm towards a brick column at work. It scratched the face a tiny bit (not really noticable) but I feel much safer with a screen protector.

Any other specific things you'd like to know I'm happy to answer.
> You get paid to make something people want.

Depends. As a coder for hire sure. When I am a company employee though, I tend to think one level higher as a person who solves problems. There have been times that the business has thrown a problem on my desk thinking they need software, when all the business really needed was a process change.
The quote is not anti-test. You should read the article.
The whole premise of this thread is absurd to begin with. I think we're bordering on the beating (or dare I say persecution) of a dead horse ;)
Handling "a lot of states" (rather, a large state space) is a hard problem in any paradigm.

Pure languages make this complexity apparent, and thus gives the programmer a true sense of how hard it is to do right. This makes it seem "harder" than in impure languages.

Impure languages let you get away with handwaving the state space, which – to be fair – is often enough. But when it isn't, you pay dearly for it after the fact.
Stop Calling Everything “Fake News”
I wonder whether this could be used to improve hydrogen storage technologies, as a way to store large amounts without needing cryogenic temperatures?
I implemented the snapshot functionality in Jest and I work on Jest at FB.

> Almost immediately after one of our teams started using snapshot testing, we had test breakages because an entirely different component that we used in an ancillary way had a semver minor change (added a new prop that was defaulted) and that broke tests (but not the app) in our component. Perhaps we're doing it wrong, but adding tests to packages that can trivially be incorrectly broken by your dependencies changing is fairly painful (and makes a mockery of semver).

Snapshots should make you more confident when making changes.

In the case you just described they correctly caught that something changed.

Imagine a minor semver update that works in 99% of the cases but has a very tricky edge case scenario they didn't consider when bumping to the new version, and you're super lucky and you have that scenario in your codebase, but only in a single page of your app under a certain condition.

Snapshot failures highlights subtle dependencies between seemingly unrelated components, making you aware of it.
I think at snapshot failures as warnings: those are potential breakages and I can now check that everything works, and with a good coverage I know exactly what changed and where, so I can go and check case by case.
Once I'm absolutely sure everything is fine I can safely update the snapshots, which as you correctly stated is easy to do, I've just to pass a `-u` flag.
i would declare those on-liners "fake news" or "hate speech" and then strictly censor these subhuman perpetrators who obviously abuse their state-given privilege, sorry, right to free speech.

...or i would simply cope with it. not sure, cause i'm no expert.
The invention that helped me write again [video]
Worse, there isn't currently any nondestructive chip imaging technology!
AI Could Help Solve Unemployment: By Helping Colleges Predict What to Offer
I rather prefer this scenario, labeling a package release with vcs revision id or even branch name, for example.
HN works fine with multiplication signs ("×"), it's asterisks that are problematic.
Depends what you use to categorise something as trivial - some functionality may be trivial technically but have an incredible impact on end users. Is that trivial or non-trivial?
In defense of SAML for enterprise customers.

I built an enterprise site that needed SSO to work for a number of different enterprises.

I tried 3rd party solutions, ping fedeate, Auth0, Azure etc. and these were nightmares to configure and get working.

Turns out it was way easier just to read the SAML RFC and handle the tokens myself.

SAML 2.0 is finally old enough that most enterprises support it.

So for me Enterprise SSO is a solved problem. For others having a hard time finding 3rd party plugins / services etc. I highly recommend whipping out the RFC and DIYing a solution. Only took me a couple of days. Far less than what I spent on other solutions.
As someone who worked as dev (4yrs) later moved as tester (4yrs) and finally returned to dev again.

Here's my personal thoughts/experiences:

- Testing job is underestimated.

- In General, Developers considered superior to testers.

- What makes Tester position difficult is 'repetitive tasks' . Yes you can automated tasks, but you still need to do some tasks that can't be automated. These are manual & repeated tasks, often boring.

- Some developers are so lazy. for ex: while testing we found 'python syntax issue!'

- Management thinks testers can be replaced once they automated everything. Obviously they push for this.

- I know for sure, there are projects with passionate developers but no-one can really take care of their testing side.

- Dev underestimate/avoid unit-tests & rely on testing team to find basic issues.
Microsoft officially closes its $26.2B acquisition of LinkedIn
I'm not a big fan of this mentality. Writing enough tests to be bug free just isn't enough. Sure it's bug free today and that's great but will it be bug free tomorrow after a junior dev modifies it?

I'm not advocating testing getters/setters but not testing because "I don't write those kinds of bugs" can burn the next junior dev who might.

Testing is as much about finding bugs early as it is making your more agile in the future.
One possibility is that there is some unoptimized code that depends on certain CPU features in the newer models, and that they're working to optimize it. One of their later comments says:

> We have recommended and still recommend using the Core i7 in order to maintain a constant 90FPS with advanced physics.

There's also this:

> These surprise game modes were meant to be a reward for those players with high-end VR systems who were looking for the most immersive experience possible.

Does Intel own a stake in any VR companies? Did they bundle their game with any PC building companies? It could be that they made all their money on the bundles, not on the CPUs directly.
these are not problems, only small details that you have to be careful of..not a large tradeoff to pay
On the other hand, if you ask the author to think of the edge cases first, they're more likely to list them and then write code that handles them. Still no guarantee, but better than writing tests for code you just "finished".
This article talks about that specifically: http://readwrite.com/2014/11/06/slack-office-communication-p...

An excerpt...

Which raises the question: With such a good tool for team communication, why does Slack need an office? Why not do all your work virtually?

Slack CEO Stewart Butterfield gives product manager Mat Mullen advice, and a ukulele serenade. “There are some conversations that are much easier in person,” says Brady Archambo, Slack’s head of iOS engineering.
exp, ln and sin are elementary functions, so they can be given in terms of elementary functions.
Great, you've proved that 100% test coverage doesn't mean 0% bugs. The actual question is whether there is a significant difference in reliability in software with 80% test coverage compared to software with 100% coverage.
use 4 spaces in front of code lines instead of ```
FarmBot Genesis Grows All of Your Produce by Itself
tried listening to why OOP is bad and it was painful. 10 minutes in and 0 insights. He kept saying things like "encapsulation doesn't work" and then moving on. Not willing to stay another 20 min to find out why.
Higher levels of abstraction are harder to translate to efficeint machine code.

Non-strict (what you call "lazy") evaluation can make it more difficult to predict when resources are needed. In strict languages, the resources needed to evaluate f() are needed exactly at the point where you typed "f()".

With non-strict evaluation, those resources may be needed then, later, or not at all! If those resources happen to be needed when a) they are no longer available, or b) at the same time as a bunch of other computations need resources, you have problems.
Absolutely. There's some subtle wordplay going on here -- frankly it's probably done on purpose to draw out a lot of public discussion.
F# is probably a pretty decent candidate for this (it's next on my list of languages to really take a critical look/attempt at).

I've done a lot less statically-typed code than dynamic (mostly Python) in the last few years, but I was playing with Unity3d recently and had a chance to write a good deal of C# with Visual Studio.

I hit a hairy problem some time along and had to do a big refactor to support a new feature. I deleted a single line of code, followed an error trail for 10 minutes, and suddenly everything was just done.

It was a pretty interesting moment for me. I realized that statically-typed languages can really have the potential to be as or more productive than dynamically typed languages paired with a good enough IDE. (And Visual Studio with C# is about the best pairing you can get).

I've had to reconsider my thoughts on these things a bit. Sure, there are things that statically typed languages can make much harder to test or work with. (Want to stub an external provider? Okay, you're going to need an extra interface, then you'll need to create a new stub version that implements that. Want to read/write pretty-arbitrary JSON? Good luck). But there are other places where you get huge wins by bugs just disappearing by the boatload.

I'm still not on board with heavy OO/inheritance, and love the pattern of simpler struct-style constructs with just functions in functional programming, but the static typing can give a lot of wins.

I think something that gives an inherent advantage to OO languages in IDEs is that SomeThing.<tab autocomplete> makes a lot of sense and is easy to compute! I can take an object and know what I can do with it at a glance. I haven't seen a functional language with enough structure to support that simple feature yet (though maybe I'm just not looking hard enough). This is really where statically typed languages can make the most of an IDE.
For some reason, that's the big thing I think of when I'm thinking about the downsides of functional programs I'm working with. The editors just seem to help a lot less (though I haven't written any FP professionally-speaking, so have less experience in general with tooling).

F# using Records with member methods looks like it might be able to get that sort of benefit though, I'll need to try that. It looks like they're just pure functions declared on immutable structs, which I think is the perfect middle ground.

A lot of object-oriented languages have taken tips from functional languages lately (map/reduce/filter is the new hottie), but I think there's a lot of benefit still to get in the opposite direction.
Some of us have weaknesses that can't just be overcome. They are continual struggles and probably always will be. You work hard to counteract these natural tendencies.

I'd go as far as saying everyone has these. The question is intended to tease out whether you're aware of yours and whether you actively work to counteract it.
The advantage of the Arduino is that it's a standard that "just works" with absolutely minimal time investment of getting started. You can have an Arduino up and running with a flashing LED before you've even assembled the breadboard and installed the toolchain for another solution.

As a standard, users benefit from being able to share instructions that have a high chance of working on someone else's system.

Obviously these are most relevant for beginners or those with a short time to invest. But that's the market that Arduino practically created. It simplifies the decision making process: if you're a beginner, start with Arduino. Once you've used it for a bit, you'll be aware of the limitations and have an opinion on which alternative to switch to.
I happen to work in a team. So I get paid to write code that works, that other devolopers can make sense of and hack on as well. That's why I write lots of tests.

If Kent Beck is coding in a private bubble, he can do whatever he wants that makes code work.
Boy it would be great if writing code that added features could also be that safe and difficult to screw up.
"When coding on a team, I modify my strategy to carefully test code that we, collectively, tend to get wrong."

I think addresses that point quite nicely?
It's also an issue of scales. The volumes of CO2 we need to store are absolutely staggering, as in tens or even hundreds of Hoover dams every year.
To be fair, the person quoted by the author does reference this in the article. He says he changes his frame for how much he tests based on his team's historical challenges.
I'm sorry, I'm not sure I understand. Their suggested replication mechanism was precisely correct. Please explain what you mean (btw I have a PhD in Biophysics, and my thesis was on the structure of DNA and RNA, you are free to use scientific language).
Whoa, that's very cool. Achieves superconductivity above liquid nitrogen temps. You wouldn't happen to know what the cooling setup looks like for REBCO superconductors? I wonder if you could use some kind of clever magnetic refrigeration setup to create 'electrically activated' superconductors? (i.e. use electricity to run a conventional motor in a rotary mag fridge setup discussed here: http://sci-hub.cc/10.1063/1.4880818)
I like how, when showing the increasing star size, they show a little piece of the next, bigger, star just to let you know "hey, we're not done yet!". There are big things out there, people.
You can program functional in almost any language. Its more a mindset. I can not emphasize this enough, keep it simple.
Macs are also notorious for running hot.
IBM, Intel, Microsoft, Mozilla and NodeSource Join Forces on Node.js API
Does your comment still stand for the cheap end of things? If Intel struggles to compete on price, then low end ARM may have better perf characteristics.

From what I read, doing binary translation from x86 to ARM is actually not that hard since ARM has many more registers, so I'm sort of hopeful they get decent perf from it.
They aren't going to be able to counter analog malicious hardware or dopant level attacks:

https://lwn.net/Articles/688751/
By "lots of state" I don't think he meant "lots of data", but rather data that get changed a lot: Q&A forum, CRUD application, etc.

Functional paradigms can still be used (e.g. HackerNews, though let's be honest...I love it but it's not the most challenging feature set). But FP isn't as natural of a fit as the problems chosen to introduce it.
Adding to that, a lot of homeless people have to dumpster dive to get out those returnable bottles, which obviously is pretty humiliating. So some guys first developed stickers saying "Bottles belong next to the trashbin" and put them on a lot of trashbins - later, another group invented the "Pfandring" or deposit ring which is attached to a trashbin and asks you to put your bottle in the ring, not the trashbin.

I find it fascinating how small regulatory practices can have enormous social effects.

[1]https://images.duckduckgo.com/iu/?u=http%3A%2F%2Fmobil.ksta....
Ideally you'd want to prune unregistered/unconfirmed accounts after a set time period. There shouldn't be any user action required.
eh ... if you want to audit code being committed (and for open source projects - you really do, or if you have SOX compliance regulations, or other audit processes) it is one of the best safeguards.

I have seen many many bugs being introduced as part of a fix for a review comment.

This is why you re-review.
So what did you mean? The processor clearly does everything, so why say that it does nothing? You're railing against "complexity" that you show no sign of understanding.
Compared with the Windows experience, Android is certainly lacking and it remains to be seen if Android N will improve it, but given that OEMs are now all betting on Windows 10 for that market segment, I don't see a bright future for it outside mobile phones.
you shouldn't be testing internal implementation anyway

Why not? When my big black box stops giving me the expected answers I want to know exactly which cog inside that box that broke.
at which point we first need to talk about the type of coverage ... tree coverage or line coverage (or something else?)
Perhaps you meant to comment on this thread instead? https://news.ycombinator.com/item?id=13128518
I aim to test for the version of myself that's having a bad day (tired, rushed, wrong caffeine level). That's a better target market than the idealized version of myself that makes only expert-level errors.

That seems to cover the team element, too. Even if I'm not having a bad day, someone else messing around in my code might be.
Yes, but even so it's a huge undertaking to build your own event sourcing. Many get burnt.
The first part of your comment sounds really odd to me. I definitely write tests to check if my code works, among other things.

Why do you think that is the wrong approach?
Soros, Buffett and Role of Robotic Logic of Investing Riches
Learning Theory, Video Games, and Popular Culture [pdf]
Does non-ionizing radiation pose a health risk?
Users with negative experience are more inclined to leave a rating than users with a positive experience, which makes the ratings not reflecting the reality of the overall user experience in the first place. (http://cdn2.hubspot.net/hubfs/232559/The_Mobile_Marketers_Gu...)

This technique is a genuine way to encourage sharing positive experiences about the app. In the same time, it offers a chance to the app provider to improve a bad user experience.

Whether it's a dark pattern or not, I think really depends on the motives, are you genuinely trying to make the app better or are you only interested in the people's perception of it.

Here is a great article on the topic which discusses the same issue: https://www.smashingmagazine.com/2014/06/a-better-way-to-req...
It really depends on the implementation, the range will be from microcontroller up to fast 64bit chips. There is also talk of 128bit.
Yep, I meant between Jr & Sr, I wanted to use Midlevel but but I had to keep the title short for hn 80 char limit

Thanks for answer, that's a real help, all the postings I've been looking at ask for github url & examples of work so I thought not having anything was abnormal
https://xkcd.com/1513/
Open Source also does not mean free products and support.

As a case in point, you were giving out about 2 different pieces of open source software in this thread.

Neither of which you have to pay for. Both of which are complex system that have taken many many people hours to build. As a return, is suggesting that you may submit a PR (or even a bug, with suggestions so that the people CoreOS hires to write docs know there is an issue)
To really improve privacy you should use Tor Browser and only HTTPS websites.
Not saying your wrong about what he meant, but Spark can also keep state across the Cluster, not just data. Check out the "UpdateStateByKey Operation" in the following page.

http://spark.apache.org/docs/latest/streaming-programming-gu...
Testers to programmers is like cashiers to cooks at Mickie Dees. I think you are resentful that your job can be automated and thus, the value of what you do is quite low.
Denest: A different way to read threaded comments
This is one of the few things that makes sense, but as much as I liked my windows phone 7, the lack of apps was a disaster.
Even if they don't decide to go public, equity can pay dividends. Maybe it was just me but it felt like the founders are just trying maximize their upside by dangling a small bone for employees. But let'a not forget who this is benefiting. I'd love to hear from some Basecampers on this.