skysight-inc/HackerNews huggingface dataset:
Well yes, no quote applies perfectly for all situations, but IMHO there so much time being wasted on getting to know all the theoretical intricacies of startups without getting anything out there that this quote is great advice for many.
Let me rephrase:

A statically typed language typically asks us to redirect our brains from asking the question, "Is type verification really needed in this particular instance to deliver my business value?" to instead solving the type-checker puzzle du jour.
Yes! And just remember, spinach is very healthy for you so long as your calcium/magnesium situation is balanced and you're drinking enough water and are moderate with caffeine/alcohol!

Spinach will help your urinary tract do what it's designed to do, but it needs your help!
Why the concern that the volume of tests is greater than the volume of code? Why should that be a constraint, other than some vague sense of wasted time spent typing them out?
Machine Learning Application: The Just Good News Project
It's really unfortunate to see how common it is to look down on people who spend their time differently. There are some tasks I wish to undertake that likely mean I would have to leave the office job experience for about a year.

Given how this may affect my future hire-ability, I doubt I will pursue it. I can't really afford to have my resume thrown in the trash because I felt something else was worth devoting my limited time to, even if only temporarily.
I think type systems that try to "close" aggregates (i.e. saying "an Employee is these fields that have these types and no more") kind of do contribute to the problem. I sort of agree that static types are not "causing" such problems. They don't "cause" bad design, but they tend to make it too easy to set bad designs in stone (and most designs are bad in some way). It's not so much about types causing problems or being bad, but having costs, and thinking hard about those costs vs. the benefits. Different folks will, and should, make conclusions for their problems.

I read him as exaggerating his critique a bit because types are often oversold (static type people can be really dismissive of dynamic languages). But I think he's mostly making a "no silver bullet" kind of argument.
Yes, that kind of tool - that lets you run Python in a browser - can be useful. I had discovered, tried out and blogged about some of them earlier (also trinket.io, which you mention):

Codingbat, Progress Graphs and Michael Jordan:

(for Java and Python - when I tried it)

https://jugad2.blogspot.in/2013/02/codingbat-progress-graphs...

Online Python Tutor looks quite interesting:

(for Python)

https://jugad2.blogspot.in/2013/03/online-python-tutor-looks...

PythonMonk - learn Python in the browser:

(for Python)

https://jugad2.blogspot.in/2013/04/pythonmonk-learn-python-i...

glot.io, an open source pastebin with runnable snippets:

(for multiple languages)

https://jugad2.blogspot.in/2017/04/glotio-open-source-pasteb...

Some of them use emscripten, IIRC.

Edit: These tools are good for beginners to learn the basics of the language. For more complete learning, I still think the traditional method of using the command line tools such as the interpreter and a text editor, and an IDE, are useful and recommended. Interaction with the real OS is a part of the learning of any (at least industrial) programming language (maybe there are some specialized exceptions) - i.e. things such as files, databases, directories, users, processes, peripherals, etc. - and not much of that can be done in the browser-only environment that these tools have.

In fact, since I am a trainer too, I sometimes come across some of my students who do not know the basics of dealing with an operating system, even as a user. E.g. some of them can only use the PC via the GUI (e.g. in Windows) and are not familiar with the command line and its commands, or even with concepts such as drives, pathnames, filenames, absolute vs. relative paths, how to reference a file in dir B from dir A, etc. In such cases I always show them some of the basics of that stuff and give them references for further learning. And I tell them that if they do not learn that stuff (or look down on it, as a few of them tend to do), it is like knowing how to drive a car (programming) but not knowing how to walk from your house to the car and from the car to the shop - in other words, you are not fully capable to even use a car due to that :)
Declining electricity mains generation compared to previous years. If you want more details then read the reports I listed in my previous post, collectively they have more than enough information to bring you up to speed.
When talking about high-quality franchises, it's a useful vehicle for people whose talent is in recruiting/managing a low-skill workforce and promoting a business within their community. Also, high-net worth people looking for stable businesses. I get how it could seem terribly boring to a creative person, but it seems to function a bit like an annuity.

This article is a good overview of who franchises appeal to (and why): https://www.bostonglobe.com/magazine/2014/09/17/the-secret-w...

This class of trade is impressive because you need to have several million dollars of liquid wealth to get started. There's a whole other class of franchises which are basically built to bilk the aspiring middle class and charge $30-100K for nebulous advice and marked-up equipment but provide almost no national brand appeal or product development. E.g. almost every frozen yogurt franchise that has sprung up in the last 5-10 years.
Well, even a PRNG is deterministic at some level. I think it’s a fine descriptor given the context.
This is a critique of popular testing practices by an experienced engineer who is trying to improve the practice of testing and increase software quality. This is a big part of how engineering practices improve. A culture where we call something "dumb" without reading it because we only care what "moron developers" will make of it (presumably also without reading it) isn't going to increase software quality or protect against the next Equifax. It's easy to have a knee-jerk reaction to a title and rationalize the desire to respond on that basis. Surely nobody else will read the article, and therefore I have already determined its true significance by having a knee-jerk response to the title or a few haphazardly skimmed sections. If that reasoning prevailed, though, people should just write headlines and never anything more thoughtful, and we should be stuck forever with "UNIT TESTING GOOD" and "UNIT TESTING BAD" as the two competing pinnacles of software testing wisdom.

In case anyone was fooled by this comment into thinking the article takes a lazy approach to testing, it argues for keeping a certain class of unit tests; for another class, preferring system tests instead; and for third class, turning them into assertions that ship with production code where possible. That's not lazy. Depending on how you currently test your code, it may actually be a harder standard to meet. It's possible you personally have nothing to learn from it, but I would wager there's something in it that will make you see your tests in a different way.
Defense has career progressions? Is this for management? From what I've seen engineers are treated like cattle and hired and fired for the whims of every project.
Why place matters and possessions don't
Savage!
About that heuristic, when hiring for sysadmins in the early 2000s, I found there to be an inverse relationship between résumé quality and candidate quality (with one notable exception — résumés written in LaTeX were usually of high quality and almost always indicated a quality candidate).

Originally I had a similar conception about résumés — they should be one or two pages max, should look nice, and should contain no errors. For obviously this indicated a candidate who cared about how they represented themselves. How could a candidate with a slap dash résumé be any good?

But time and again the better candidates had the worse résumés ... résumés that were pages long, or completely unformatted, or filled with errors. Perhaps these candidates with poor résumés have simply prioritized their time on their work, not tending their résumé. Or perhaps they feel that they should be judged on the content of their résumé and not its presentation.

Regardless, I no longer put any stock in how a résumé looks, only wheter it indicates an appropriate background for the job.
There needs to be more of this. I know how hard it is to work on a stylized video game all by yourself: just remember its a marathon not a sprint so pace yourself and keep at it! <3
https://rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste...
I've used something similar before, gave up on it. I just use Nginx manually now, so much more room for customization, plus I know where everything is because I set it up.
What's to stop the discovered solutions from being similar? Nothing but the dimensions of interest. If the best solutions with respect to features a, b, and (a&b) are all the same, then it does not seek different solutions.

This may indicate you chose reduntant features though.

Here's an interesting application that provides some motivation.
https://arxiv.org/abs/1407.3501
New Kind of Recurrent Neural Network with Decaying Attention Span
> Do not underestimate the power of make a "full stack development" with just one language.

unfortunately we already have that language and to use it you need to transpile... It will always be Ryby/js, py/js, php/js until web assembly becomes a thing I guess.
But "interface bugs" are the least of our problems. As evidenced by most bug queues that I've peeked at.
I wouldn't class it as revolutionary either, but it /is/ innovative.
It's easy to look at the raw numbers analysis and admire the invisible hand of the market guiding the economy down the middle line through an endless trail of pendulum swings. This abstraction ignores the raw human cost. These shifts ruin the people, the actual implementers of the economy.
> What you've done with those two years is going to really matter.

Caring for their child is what he'll have done with those two years. It's an exhausting full-time job. These suggestions are great for someone who's unemployed, but unrealistic for a full-time caregiver.
Quote along the same lines from _why that I really like:
"When you don't create things, you become defined by your tastes rather than ability."
Why do you think the second part specifically is "a recipe for a disaster waiting to happen"?
In terms of user security, that's just not a good idea. Google has likely prevented an absurd number of account compromises (and therefore identity theft, fraud, personal information leakage, espionage...) by recognizing logins from new devices and unfamiliar locations. Google's user account security practices are pretty much the best in the business.

It's silly to think Google doesn't already know everything about every device you log in from, so that horse is already out of the barn and running on the highway privacy-wise. They might as well use that information to actually protect their users since they're already using it for advertising.
After playing one round this completely froze my Macbook Pro and I had to force boot.
Touched my first computer almost exactly 40 years ago.
I can troubleshoot most hw/os issues with one ear and eyeball tied behind my back.
Can program decently in many general domains.
Never went past my associate's because the work was more compelling.
Knowing how many PhD's never work in their field, and how many Master's get earned and laid aside, I can't agree with you at all.
I think you might be imagining that correlation.
Disagree. As a user, I want file-level or directory-level analytics. I want to know how much time I'm coding in the backend services vs the front-end react client.

If you have concerns about this, do you also have problems with Github literally having access to all of your code? Or Google having access to your search history?

I'd be more concerned if it wasn't using SSL. That would make sense, but it seems secure on that front.
That's good. I suggest that you're doing unnecessary work (having to stash and unstash) when you had "broken" code at first, but at least you are testing your tests, so well done.

In my experience coaching teams on TDD, its quite easy, when writing code first, to add more code than is needed to solve the problem. And then only the problem is tested for. Meaning that there is code that is not tested. Maybe an if statement where a branch is never taken. Strict TDD means you don't write any code without a failing test, and you write the minimal code needed to make it pass.

Now quite often, a programmer has no idea how to tackle a problem, so I advise that they just write something that works. Just have a go and get something working. Most programmers (if they test at all) will then just go and write a test for it, usually for happy path. And that usually results in code with bugs. I know this because many times the programmer has done as I suggested and commented out their code, and reimplemented from scratch using TDD, and doing TDD finds a bug in the original that nobody saw.
They're "easy" to operate and scale. All the systems are already pre-built for you - everything is on rails - and all you have to do is secure the funding, lease/buy/develop the space, and hire the right people to run it. Over time you can open more locations or step into a territory manager role. All that together makes franchises attractive to people who want to run a restaurant but want the support of an established brand or who have capital and want a revenue-generating investment that can be made to operate mostly autonomously. Not my cup of tea but I see the utility.
FWIW, I've used https://www.npmjs.com/package/tracery-grammar before. It's maintained by the creator of Cheap Bots Done Quick, which the creator of Tracery pretty explicitly endorses (she calls CBDQ out as an inspiration for Bottery)
No. But he is right that if you do some activities in the meantime, you will be in very very different position then if you don't. Maybe the biggest difference is level of confidence, bit it such a huge difference that it is worth mentioning.
Direct link to the PDF: https://openreview.net/pdf?id=BJ78bJZCZ
>Having learned Clojure this year without asking a single StackOverflow question, I don't think this means Clojure is shrinking. I suspect that Clojure's crazy good stability means no new questions are really required for core things.

That seems like wishful thinking. If new people are picking up the language there should be noob questions on StackOverflow no matter how stable the language is.
Marketing is effective
Those trying to hire super-ninja-ex-google-guy want to raise more funding and need to brag to VC's to get more money.
> Any estimates on what the economic cost of entry is for developing a competetive browser?

I doubt you're gonna get numbers, but I can give you two rough reference points:

1) All popular modern browsers use browser engines that started out their lives in the last millennium:

- Edge uses EdgeHTML, which was forked from IE's Trident, which was first released in 1997.

- Firefox uses Gecko, which started development in 1997.

- Chrome/Opera/Vivaldi use Blink, which was forked from WebKit (which Safari uses), which in turn was forked from KHTML, which started development somewhen around 1998.

So, all of these had their architecture laid out before multi-core CPUs were a thing in desktop PCs and before the web became more than just text with the occasional image thrown in.

As a result, all of them lack severely in parallelism and use of the GPU, and writing a browser engine from scratch would allow you to get these things right and give you ridiculously better performance than all other browser. But no one's done it yet, because of this insanely high cost to redevelop everything.

Which brings us to reference point 2), Mozilla has actually started work on writing a browser engine from scratch in 2013. The project is called Servo and they even find it worthwhile to basically develop their own programming language, Rust, for writing Servo in it.

And well, Servo shows off quite nicely the aforementioned potential in writing a browser engine from scratch, but it also still explodes spectacularly, trying to render out ACID3, which was released in 2008 to try to represent what a good browser should have been capable of back then.

Now, Mozilla is not working on this full-pelt, but it is a big organisation with lots of browser-making know-how. They're also sort of bootstrapping Servo by including production-ready Servo components into Gecko, resulting in the maintenance work being shared.

So, basically I wouldn't expect any new player to enter the market in at least the next ten years.
This is basically the inevitable smashing together of Yahoo and AOL under Verizon. Cue misplaced 90's nostalgia in 3...2...
This means Google is scanning your stuff one way or another. How much would one like to bet that they're surreptitiously stealing secrets to use to make money?
i think the degree to which Three.JS has allowed programmers access to the world of modern 3d is severely understated. If you haven't tried it, go to threejs.org/examples/ and copy and paste some source, it's _incredibly_ simple to start hacking.
I think “randomly” is being used here in the sense of “without a good reason.” Regardless of how the content gets classified, they shouldn’t be policing private files.
Top-level await operators in the Chrome Console
Claiming something is easy to do and then making the same errors simply diminished the strength of the argument presented. The comment comes across as "do as I say, not do as I do."
Ask HN: What facets of nonprofit technology are ripe for disruption?
I'm new to a company that provides SaaS in the nonprofit technology space. And, while we're successful, there doesn't seem to be a "next problem" for the product development team to be thinking about. I want to help validate new solutions, but its difficult not knowing the challenges being faced by nonprofits. Since gaining context for the problem space in a new industry takes time and I'm just not there yet, do any fellow hackers have any insights or ideas to share?
It's not more helpful as tests than "write tests as you code". But "pure" TDD is more helpful as a guide to low-level design. I'm not sure that most studies can quantify that.
Though i think to fully appreciate this you would have had to have bashed your head against the wall of platform dependent opengl in the past...
I deliberately put 3-4 typos on my resume to weeed ouut the carelesss screeners.
And adding on to this, these people are understandably most of the people looking for work.

I've literally seen engineers with 20 years of experience grind for 45 minutes on FizzBuzz, not able to make any progress.
The Drive API allows you to export to docx, which can be converted to markdown (or whatever) via Pandoc. This works surprisingly well for me.

For web-based collaboration, you could self host something like Etherpad (there are a few alternatives).
Heh. We had something really close to that until about a year ago. And yeah, nobody wanted to work on it.
Keeping Clojure close to the host language was a design decision that was made at its inception. Choosing the JVM and Javascript as the target runtimes (for lack of a better term), has provided Clojure/ClojureScript a huge amount of reach, and I credit these decisions as the primary driver for the success of the languages. I think that saying that the languages are too tied to the underlying platform represents a misunderstanding of the goals of the languages. If you want a self-hosted language, there are plenty of options to choose from, and each simultaneously carries with it the benefits and disadvantages of a platform that's built from the ground up.
Wittenberg in the spotlight: Luther rules, 500 years after Reformation
Latest episode of ‘Bubbleproof’ showcases a partnership with unusual terms
I use OpenVPN Client. It works really well and supports autoconnect (including at boot) so that you don't need to worry about disconnects. The pro version even supports TAP without root. You can find the free version here: https://play.google.com/store/apps/details?id=it.colucciweb....
the paper, for those interested: http://repository.cmu.edu/cgi/viewcontent.cgi?article=2874&c...
Interestly the US page[0] gives an end date of the end of the year but the GB page[1] doesn't and the FAQ for the GB page states they "will make a public announcement before ending the offer".

[0] https://www.microsoft.com/en-us/accessibility/windows10upgra...

[1] https://www.microsoft.com/en-gb/accessibility/windows10upgra...
Kevin Rose launches free rapid meditation app Oak
The point is, you don't actually need a believable image in many cases. In the same way that a poor fake ID gets you in to a bar, a poorly generated low-resolution photo justifies the fake news written next to it. Just look at the history of bigfoot and UFO sightings! Now those would be mischievous to generate...
All projects that have been created using TDD have tests, but not all projects that have tests have been created using TDD. You're saying that having tests is good and I would assume most people agree... But that doesn't mean that TDD is automatically great. It's the DD part a lot of people find themselves skeptical towards.
I'm not the original commenter, but I just started using cryfs in Dropbox and it's working very well: https://github.com/cryfs/cryfs

KDE plasma has just started incorporating this into their desktop as a product called 'Vaults'.
ICO Review: US Dollar
> I'd be more concerned if it wasn't using SSL. That would make sense, but it seems secure on that front.

Yes, I agree with you, using SSL is definitely better than without.
100 users buy the same hardware but decided to resize their browser window slightly differently. Bravo, window.outerHeight and window.outerWidth.

100 users buy the same hardware but some decided to install some custom font they need. Bravo there’s a difference now.

GP is very clear that there’s no single magical API used for fingerprinting. It’s anything and everything.
For them it's got to be frustrating. It's fun for me. I like brainstorming.
I think it's fair to keep in mind that the developers you want don't have a lot of experience interviewing (they tend to get snatched up as soon as they're on the market, if not before), and the ones you definitely don't want might have more experience interviewing than doing their actual job.
It is absolutely a goal to match Vulkan/D3D12/Metal with the new Web GPU efforts.

If you're talking about matching every single feature in every API ever, of course no API can do that; no "native" API does that either. There are always gaps around the edges where some API has features others don't (e.g. conservative rasterization support is spotty). But general feature parity with the new generation of APIs is the target. I'm going to the W3C Web GPU meeting next week to talk about just that…
Google is shutting down the QPX Express API for airfare data
Google has been offering an API for airfare data at https://developers.google.com/qpx-express.

I just received this email:

"Dear QPX Express API Customer,
After careful consideration, we've decided to shut down the QPX Express API as of April 10, 2018.

How this affects you

After April 10th, you will not be able to access the API and will no longer be charged for this service. Until then, you will be charged a reduced rate of $0.02 per query for any queries beyond the 50 free daily quota.

Next steps

You don't need to take any action. However, if you are actively using this product you may want to find an alternate solution before April 10, 2018. If you have any questions about these changes, please don't hesitate to contact us at any time.
Sincerely,

The QPX Express API team"

More info on the shutdown: https://developers.google.com/qpx-express/faq#EndOfServiceFAQs
Yeah this is really impressive. Right now I can't think of a use case for it but if I need charts like this in the future I will most likely use this be library.