skysight-inc/HackerNews huggingface dataset:
The children afflicted obviously. What gives the unaffected the right to impose their judgment when they will never pay the price? Their skin will not slowly harden to bone over the course of decade, making every movement an agony, until eventually they asphyxiate when their chest can no longer expand. Their limbs will not grow twisted, their heart will not rip and tear, their immune system will not rise up against them.

The votes to criminalize reproductive outcomes must only come from the population experiencing those negative outcomes. Otherwise the 99.999% of people who will never experience that particular horror will always outvote them to save 20 bucks of testing.

We have a rich history stretching thousands of years of the damned returning to warn society to avoid their mistakes, their follies, their hubris. We listen to Tiny Tim about the importance of relationships over wealth, but seem to discard his other message on the importance of polio vaccinations.

Almost 300 years ago society decided that cruel and unusual punishment was unjust, and forswore its use. Yet today the power to summon new human beings into any of millions literal hells on earth is completely unchecked. We have the technology to know

> Probably 90%-98% of the population has one or a few things "wrong" in their genetic makeup

I read this argument as the slippery slop fallacy. Criminalizing bringing children to term with Huntington's disease is very different that murdering all babies at the hospital that have brown eyes. The current technology level makes it cheap enough to society to eliminate the low hanging fruit of the most crippling genetic diseases.

Eugenics is not limited to concentration camps. There are many moral forms of eugenics. For example: a society could recognize that certain genes impose steep costs, and tax those who choose to impose those genes upon new humans. Society then uses the tax revenue to compensate the victims.
Subversion, for all its improvements, was the same way. I remember jumping through a lot of ssh proxytunnel hoops just to be able to check svn history when I was working at a remote customer site in 2006.

The first time I ran “git commit” and it finished almost immediately blew my mind.
> Eventually the pain of working within a single massive source file became overwhelming, and I decided to write my own literate programming tool that could consume a filesystem hierarchy

I wonder if that’s where they went wrong.

Perhaps when your code is too big to fit in a file, it is too big to describe serially at all. And it’s time to split it in two separate pieces, two modules with a formal interface between.

The idea that you could have a nonlinear narrative without any formalism dictating the relationships between paths is perhaps asking too much of the narrative form.

Perhaps that’s the whole point of a module system: creating formalisms so that you have a chance at holding in your head the relationship between one series of procedures and another.

(This is not entirely academic. I have about 100 richly connected single file modules on NPM)
I wish The Onion were still funny; can't really recall visiting them in the past 3 years because of some funny video they were famous for.
Ah yes, taking an IQ test for Amazon wasn't enough of a contrived hoop to jump through already. Let's take one example of a tech firm and broadly declare the resume dead, because silicon valley is the only industry that exists, right?
Hand-crafted parser:

Building LISP: http://www.lwh.jp/lisp/index.html

- Parser: http://www.lwh.jp/lisp/parser.html

Full source: https://github.com/kimtg/ToyLisp
People should be paid relative to their accountability.
I'm reminded of this brilliant but horrific short (12min)

https://vimeo.com/21216091
Seems to me an all-too-convient rationale to force devs to use the proprietary Metal framework directly.
The title is misleading, if you read the article the author doesn't try to convince us that motivation doesn't exist, but that motivation is not necessary to get things done.
Web apps ignoring these types of conventions are fine, but the key issue is that a lot of sites aren't web apps/don't need to be web apps yet are built like they are regardless.

For example, your average news site. So many of them are built as single page applications with JavaScript frameworks like React or Angular, and for what purpose? None. At their core, they're basically blogs. They would work much better with traditional server side rendering and standard page loads and what not.

Same with stuff like Reddit. At it's core, its just a set of forums, with the vote button and a few other minor aspects being the only thing that could possibly benefit from JavaScript. Same with Wikia, which seems to have forgotten its a wiki host and not an application platform.

And the list goes on and on. Why? Probably because either the management team like to think they're 'on the forefront of web technology', ala Google or because the developers wish they were working for Google/Facebook/whatever.

Many sites really are seriously overdesigned and over engineered.
People had their flagging privileges removed before, in cases "someone at HN" actually gave a fuck. If you give people the tools to flag this and let them abuse it, you're complicit, and you cant't effectively support browshirts and then cry about being called a meanie. It's like doing a murder and then complaining about being called an asshole. Which is not a nice thing to do, in a vacuum, but this is not a vacuum, and it's hardly the first time either.
Who needs unity when there is puzzlescript and pico-8?

And before you say “it’s a different use case” that was a rethorical question.
Yet it's an American website where the discussion of such serious things is censored, too.
No, it says: "And we doubt you’d take a multivitamin if it contained 10 teaspoons of sugar." I'd sooner take that multivitamin than a pure sugar tablet. Soda has zero nutritional value.
>why does it take me six months to find engineers that understand basic concepts like cohesion and loose coupling beyond a text book level

If it's so basic, just hire them and take a day to teach them those things.

WTF is with this trend of waiting 6 months for a hire vs. spending a day to fix the holes in someone's knowledge.
Makes me glad I work in a specialty (data storage) which provides the parts and tools the plumbers need. Sure, there's a shared grab-bag of techniques etc. that we all use, but it's far from plug and play. While the market for people like me will never grow anywhere near as big as the front-end plumbing stuff, demand and pay have been much more consistently good for the last couple of decades and are likely to remain so for a while.

My advice to new software engineers is to get into one of the more "boring" specialties. You might not be in the lottery for the really big bucks, but you probably weren't going to win anyway. There will still be plenty of interesting and fun challenges, with greater stability and (TBH IMO) more mature coworkers.
There's an issue for this on the MoltenVK github page: https://github.com/KhronosGroup/MoltenVK/issues/193
I think jQuery gets a bad name because of it's historical context. Newer devs in the field view it as outdated and seasoned devs have seen the mess it can lead to when just sprinkled in here and there for this and that reason; and as frontend work became increasingly more programmatic and complex, this sort of approach becomes pretty hard to maintain.

Because frameworks/libraries like Angular and React were largely adopted due to this issue, people who have had success with them (or just need to justify the switch), have come to see these as part of the solution and jQuery as part of the problem.

If you're an interviewer who only sees jQuery on an application, you can use this as a chance to get to see what the candidate thinks about the evolution of web development. See if they can have a reasonable discussion about trade-offs made on choosing one over the other. This will expose their critical thinking skills and values as a developer and you may even get a new perspective yourself. To be honest, I'd rather work with someone who could have this discussion rather than just blindly adopt what everyone else is using ... well ... just because.
And NetBSD: http://cvsweb.netbsd.org/bsdweb.cgi/
Can you reference that timeframe? I can’t find anything from Sonos announcing a specific date. Thanks!
Literate programming is fine for done things - e.g. the sort of things you might put in a Jupyter notebook - maths, algorithms etc.

For large normal programs though? I don't think you need that much prose. A program with 100k lines of code would become enormous.

Still, I do wish programming languages had better support for rich comments - why do no IDEs render comment blocks as markdown? Why can't I put diagrams in comments? I have to resort to shitty ASCII art like a commoner.
Native ES Modules CDN
US community college instructor here. Students use the title professor as described here. I prefer either “Mr.” or my first name. I tell students, “Please don’t call me professor. Even my mom gave up on the idea of me ever getting a PhD.”
On the other hand, Subversion will be quickly done before a git clone is finished.
Oh yes, of course. I just wanted to point out that it's not quite fair to compare out-of-pocket costs.
No airplay 2 support yet, but they’ve given a July release date. https://www.theverge.com/2018/6/6/17434294/airplay-2-sonos-s...
That is what I kept thinking while reading the article too.

1) The YouTube link from the article mentions that most children let the robot pass, while the article reads as "100% of children are evil for no purpose".

2) Another comment mentioned the survey results possibly being skewed, because the children give the answer they expect is the correct answer. I think that's at least plausible.

3) Only a small section of observed children were interviewed: 28 total, because of a high list of selection criteria, according to the second paper linked in the article.

It all feels strangely written.
Bretheren, and Fellow Commitizens !

You may depend, that thoſe odious Miſcreants and deteſ table Tools

to Miniſtry and Octocat, the Tea Consignees, (thoſe Traitors to their
Company, Butchers, who have done, and are doing every Thing to Murder
and deſtroy all that ſall ſtand in the Way of their private Internet,)
are determined to come and reſide again in the Town of Redmond.

I therefore give you this early Notice, that you may hold yourselv-

es in Readineſs, on the ſorteſt Notice, to give them ſuch a Reception,
as ſuch vile Ingrates deſerve. JOYCE, jun.
(Chairman of the Committee for Tarballing and Feathering.

If any Perſon ſould be ſo hardy as to git rm this file, they may

expect my ſevereſt Reſentment. J. jun.
As a side note: I find the literate programming pattern is more appropriate for combined demo and tests. I am not sure implementation really belongs in the same source location.
Rental bikes exist in London and NY for many years now. I'm not sure if the city pays for them or not.

Scooters are also amazingly convenient - see the many articles about them where the author started unconvinced (and don't tell me all of them are submarine). They will survive in one form or another, maybe with subvention by the city.
Lovely proof!

Proof by contradiction is so much simpler than constructive proofs.
It's no surprise then that plumbing also pays pretty well.
Apple News is even better and you don’t have it building a profile about your interests with the purpose of tracking you across the web.
You also don't need a server for SVN, it can use another directory as repository.
You can never have all the people pushing the rock. Women, children, and the elderly wouldn't. And you need a large supply chain to feed and shelter the rock pushers along the route.

As a benchmark, 31% of Germany's population were in uniform in WWII. That's probably the greatest fraction a society can devote to a project.
Good points, but it's also about how much would your replacement cost.
Hyphenation is technically not required. A low number of hyphenated words can be regarded as a quality metric of well justified text.
You sound like my friend who gives me hell because I bought an Audi instead of the BMW he recommended. He says “the BMW has much better cornering!” and I say “my car has great cornering!” and he sends me some data as if I care. I simply liked the car I bought better than the one he recommended.
I hope u have a big flag. Cargo bikes scare me so much when they are on the road and kids are in them.
It's an opioid. (Or rather, contains opioids—more than one, by the way!)

Every purported "non-addictive opioid substitute" in history has turned out to be an opioid. If it acts like an opioid and quacks like an opioid, assume it is one.

> https://erowid.org/plants/kratom/kratom_journal2.shtml

Try:

https://erowid.org/references/refs_view.php?ID=7348

(linked from
https://erowid.org/plants/kratom/kratom_basics.shtml)
Please don't encourage people taking marketing classes. The internet needs less advertising not more.
>ride in the right tire-mark left by the cars.

If you're going to do that, why not just ride in the center of the lane like a motorcycle?
I was found it odd that I can choose to euthanize my dog but not myself. This is an interesting workaround.
I did a little digging and even started reading "System design from provably correct constructs: the beginnings of true software engineering". From what I can see, it's mostly garbage used to sell the products of the HOS company. James Martin was on the board Higher Order Software, Inc. A company that despite claiming being able to provide "bug free software" went out of business.

Here's Edsger Dijkstra debunking the books written about HOS.

https://www.cs.utexas.edu/users/EWD/transcriptions/EWD08xx/E...

An evaluation by the US Navy concluded. "the HOS literature tends to advertise their ideas and products more than making a contribution in substance to the field of Computer Science. The author recommends that USEIT not be used in the TRIDENT program or any program development at NSWC. Even for a high level system specification, USEIT is not seen as a good choice. A mathematical functional notation or a PROLOG-like notation appears better suited for that purpose. The examples in the Appendices of this report, especially Appendices C, D, and E, show that a LISP-style mathematical notation is more compact and normally easier to read than the control map notation of USEIT. On a more positive note, the author considers the functional approach to system development and programing very promising. Systems so conceived and programs so constructed are more amenable to analysis and therefore, in principle, more reliable and better manageable."

http://www.dtic.mil/dtic/tr/fulltext/u2/a198753.pdf

So are we just talking about functional programming when we say HOS? If so, the pros and cons of functional programming have been discussed at great length.

Here is an interview with Simon Peyton Jones (one of the creators of Haskell) talking about why Haskell is "useless". It's a short interview worth watching if you want to understand the nuances and challenges and costs around creating high quality and bug-free software.

https://www.youtube.com/watch?v=iSmkqocn0oQ
For most projects I've worked on in the past 10 years, the energy has majorly shifted towards front-end development. Building blocks have improved dramatically, but expectations have been rising even faster.

Backends are getting more and more homogenized. There's still a fair amount of work that goes into accurately implementing business rules and a much bigger focus on quality and maintainability than ever before. But there's not a ton of serious thinking involved. I can pretty much follow a script for implementing microservices that will scale up to millions of users. I somehow ended up with a high-paying enterprise architect job and when they ask how we can build a system that will have 1000 users, the answer is that you can do pretty much whatever the hell you want so long as the framework is less than 5 years old and it will be fine. Then I go get a coffee.
There's a middle ground where you have a life and also a fulfilling job that you care about. Finding that middle ground, and the job and lifestyle that allow it, is important for putting out a sustainable effort and not burning yourself out.

I've never been able to put my full effort into jobs where I felt like a mercenary in the way that you described. I've found that breeds a more dangerous (existential) form of burnout, where you feel like you're spending a solid chunk of your lifetime on something that means nothing to you.
I've done a bit of plumbing and I would say it is much easier than programming. Even basic "plumbing" programming.
This has been a thing-everyone-knows-but-no-one-talks-about in hospitals for a long time.

And honestly, I wish it would stay that way. Because while I support the right of terminal patients to die at the time of their choosing and avoid pointless agony, opponents of euthanasia do have a good point– which is not appreciated nearly often enough– that state-sanctioned euthanasia opens the door for family members to start pressuring people to die when they don't really want to. This is a thing that happens more than anyone wants to admit in areas where it is legal.

Deliberate ambiguity, where euthanasia is allowed but we all pretend it's not, is the best way to square this circle. Doctors have implicitly understood this for a while, hence this practice. Unfortunately, most people hate ambiguity in their laws, which I understand and think is a good priniple in general, but I wish they'd look more carefully and see that the benefits outweigh the costs here.
While you may think BC/AD is clunky, having a static reference point in the past obviously has its advantages. 200BC will forever correctly and uniquely reference the same year, 2218 YBP not so much, as it depends on year of writing (which is fine for a live interaction, but less handy for written and archived content).
Agreed. I think the free market argument that "if advanced engineering skills were so unnecessary, some company would scoop up all the underpriced, underemployed junior engineers and make a killing" is a compelling response against the strong version of what the OP is saying.

That's not to say that tech screens are perfect, or even testing the right thing. But they do play an important role: they're an attempt by the company to not give too much responsibility to someone who will use it irresponsibly: whether by accruing technical debt, or dropping tables willy nilly, or by taking down the website.

99% of engineering isn't plumbing. It's pushing back on all the feature requests that can't be done responsibly in the amount of time allotted. It's using your intimacy with the code base and inner working of the company to anticipate problems. It's taking advantage of your prestige as "some smart wizard that makes crazy things happen" to slow down and fix problems before they occur.

Others in the company can't tell whether you're acting like a spoiled brat or doing your job. To them, it's literally indistinguishable. And that's why it's very important to not vest anyone with this amount of authority unless you're very sure that they're going to use it well.
I started using org mode at work and home a few months ago. Love it.

I want to try both Haskell’s built in literate programming support and try the ideas in this article.
Marketing != advertising
You never saw A.I. by Spielberg? Water balloons won't cut it when you have that one psycho kid who doesn't care about you.
I asked that during my last interview but it turns out the job actually is a lot of new algorithm development, which is fun and challenging.
Totally this.

I use SVN exclusively when non-IT people are involved, such as designers, site editors etc. Random person and even those without high school diploma can grok SVN in less then an hour, particularly as you don't need to `git pull` all the time which is HUGE saver as most people in the team work on independent repository paths and thus git pulls are meaningless. Git stage is also more of an obstacle then a benefit in that context.

Everybody using computers should know SVN, I consider it as basic as managing files.

Git is great tool, but IMO targeted at developers.
Agreed. It’s like advertising that a car has an engine and goes faster than walking. Having an engine isn’t a feature, it’s the the essence of what makes a car, a car.
The existing AccountChooser interface, which was Google’s preferred SSO strategy until their recent experiments with zero-click SSO, was hosted at AccountChooser.com by the OpenID folks.
Machines are very productive. Humans don't always need to be.

Or, if you expand your definition of productivity to include raising happy children then it sounds like you're extremely productive.
It starts with a water gun.

It ends with a plunger and the robot screaming EXTERMINATE.
The birds and frogs distinction is interesting, but seems to be a false dichotomy to me. Ideally a researcher is both a bird and a frog. I try to be. And unfortunately many researchers probably aren't either. In my own subfield I can think of many contributions which lack either depth or breadth.
Unless you centralize the list as AccountChooser.com does using Local Storage.
While I lived in Denys Lasdun's halls of residence at the University of East Anglia it was normal for complete strangers to climb through the kitchen window, as that was the easiest way to get around.
I only take negative inspiration from Brutalism when I think of usability.
Mastodon: An overview of features for dealing with abuse and harassment
It's not bizarre. Unfortunately, clickbait is good for business.
> Ok, so “hate” is a strong word, but hopefully this click-baits enough folks into reading this article with a clearer, more rational and unbiased demeanor than what the title suggests.

Self-aware clickbait is the worst kind of clickbait.
Are you suggesting all plumbers should know how to make siphons, valves, or even water pipes from scratch, just in case they ever get into a situation where shops that sell them for peanuts aren’t available?

Yes, you’ll need some people who know how to make siphons and valves, but that some is only a few, and most of them won’t even be plumbers, but work on building machinery that builds siphons and valves.

I think that in most jobs in the modern world, there’s plenty of low-level details that one doesn’t need to know about to do the job.
And plumping is not badly paid either. But it's a trade that you can learn in relative little time and it's a field that you don't constantly have to readapt your approach. someone who learned plumbing 20 years ago is not outdated. meaning that the supply of people who can fix your pipes is far larger than if it would be similar with IT.

and also there are a lot more people around who have the mental capabilities to learn plumbing than there are people around who are capable of consistently apply the abstract thinking patterns that involve software development.
I wonder whether something like pijul (https://pijul.org) might represent the next step forwards; I am no expert in these things but the patch based approach it takes sounds interesting and potentially very intuitive to work with. I might have to actually give it a go one of these days!
Just remember, they'll be watching you back.