skysight-inc/HackerNews huggingface dataset:
This is a huge problem for “red” states/cities. Many of these people are fleeing a mess they had a hand in making and they haven’t learned their lesson.

They’ll be pushing the same political ideology of big government in their new home and blame the problem with their old home on corruption, while never understanding how the two are inextricably linked.
Did they just add it? a link on the 'vote'?
Awesome. I came to the same conclusion and this is how my phone shook out...

* No SIM, data only.

* Safari is hidden via parental restrictions.

* I have Bear Writer for notes, Headspace for meditation, Spotify for music.

* iMessage for im, ProtonMail for email - notifications disabled.

* My everything else folder has undeleteables, 1Password, and an authenticator.

I schedule a daily block to check notifications and read blogs, publications, and check out the front page of HN.

No browser on the phone is a huge step. If you have a portal to the Internet, your phone is very much intelligent.
My problem is I browse hackernews and news.google.com in my browser in my phone.

Please send help I haven't spoken to my child in three days.
SO have a very well-defined purpose: To answer practical questions about software development - questions which have answers. The site is not a good fit for open-ended discussions - the UI is not designed for this. How would you select the "accepted answer" in a questions like "what is the worst language you have ever worked with?" What is the actual problem in search of a solution here? Upvote/downvote is supposed to indicate "helpful"/"not helpful" - how would you determine this for such a question?

Think of it in unix philosophy - a site which does one thing and does it well. If you need something different, use another site which does that thing well.

And what is lost by pushing general discussions to sites like HN or Reddit which is much more suited for such discussions?
> The lack of links makes me less likely to go to a newspaper article the next time.

My least favorite case for this is "a new poll shows people think X", with no link to the actual poll with the actual questions.

Given the many, many demonstrations of how a wording change can completely reverse poll answers, I'm inclined to view non-quoted, non-sourced poll results as essentially dishonest. It's the sort of thing that will make me think twice about going back to that source for anything I can't cross-reference easily.
Certainly it isn't hardwired in any relevant manner, and people are in fact just fine not reproducing, see vasectomy.

Don't just repeat platitudes. People are killing themselves over not being able to have sex, or rather not being able to prove they're proper functional men. It has at least as much to do with social status as with actual sex.
I would love this to work with the same phone/carrier technology that allows Apple Watch LTE and iPhone share a phone number.
Etleap scores $1.5M seed to transform how we ingest data
30L Outdoor Backpack Bags Camping Bag Waterproof
>Errors are opportunities

I love this. I've found that my most engaged users are the ones that report errors, churn less, etc.
I've personally tried this using cooper tape when I had to make a quick SMD prototype.

Having the ability to take notes on your circuit is fantastic.
I've been involved in hiring senior engineers for a while now, and here's a few counterpoints:

1) Ruby is hard to get a job in, so you are off to a rough start.

2) A lot of people with lots of experience actually can't code for crap. Do you know how many python developers I see that don't know the difference between a tuple and list? Like, how could you be a real dev if you never even wondered why sometimes you use [] and sometimes you use ()?

3) These tests and interviews aren't intended for you to get some certain score. Usually we make them way hard to find out what you do to handle that.

4) That said, you should know how to write code that isn't super slow and with a data model that isn't insane. You should also know how to articulate that, since as a Senior dev, you WILL be mentoring junior devs, and communication is not optional.

5) Every company's process is different because every company is different. Heck, my process is often different per applicant.
Cool "anthropology" method. This triggered my interest to go look at the C source code for linux[1]. Turns out the command actually relies on a few different files, including a "remove.h"[2]. I was surprised I didn't immediately see the call to unlink in the source code, but obviously there's a lot of useful infrastructure to build on. Further investigation that the unlinkat[3] syscall was actually being used. Minorly fascinating :)

[1] https://github.com/coreutils/coreutils/blob/master/src/rm.c

[2] https://github.com/coreutils/coreutils/blob/master/src/remov...

[3] https://linux.die.net/man/2/unlinkat
I'd take that a step further, in that adding a link to a related (or even duplicate) question shouldn't _close_ that question, it should be a potentially valid answer to this person's question.

If enough people upvote the link to the originally posted question, or even if it gets selected as the answer, then SO can simply _not index_ this question. But the poster doesn't feel rejected, and can in fact choose to continue engaging in his question in cases where it's subtly different.
You make it sound like yarn was some sort of community a fork to plug some gaps.

Why should yarn bow out? Correct me if I'm wrong, but the yarn project didn't do the following:
- put a pre-release build under a tag that looks like a normal build without a pre suffix
- had documentation that expressed sudo as an acceptable way to do things to end users
- then had a bug which torched machines if they ran any npm command under sudo. (which you shouldn't do anyway, but see point 2)
- when pushing the fix, put hashtags in the announcements with a distinct tone of blame towards the end users.
I agree completely. Why discus some apps access to cardbalances, when the issue is actually, why do people, making the minimum wage (or similar), need foodstamps?

Here in Europe we had foodstamps during WW2.. but not since.
> Trouble is that NAT solved a huge chunk of the problem.

Well it solved the roof collapsing, but the problem is it makes innovation difficult and straight up impossible in some cases.
Thank you for writing this post. It was informative. A few comments from a fellow software developer who is approaching 50...

I don't think the coding test isn't there because people think you're lying, it's there because we have no industry wide, respected entrance exam. Actuarial interviews don't (to my knowledge) contain a whiteboard vector calculus exam, but this isn't because people just sort of believe actuaries, it's because you have to pass a rigorous exam on these topics to become an actuary. I sometimes wish we had something like this in our field (not necessarily a legal requirement, just something that is widely recognized as legit). I'd be happy to put the time in and really study for a proper exam, but I'm not as interested in doing this over and over for companies that may administer and conduct these exams frivolously and in secret.

Also - I actually do agree that it's bad if someone can't write fizz buzz, but every interview exam I've taken has been vastly more difficult than fizz buzz. It's "find all subsets of a set of integers that is divisible by the sum of a different subset of integers". At a whiteboard, in 45 minutes. These aren't impossible problems, but they're much tougher than fizzbuzz.

I am saddened, angry, and relieved to hear of your problems with homework. The response you got back makes me realize that the two times I've done a homework assignment were probably pretty typical. I won't do this anymore, and I do accept that this will limit my career options. It does anger me, though, when the companies who do this complain about a shortage of engineers.

True story: I did an on line exam and take home homework assignment, waited over a month (crickets chirping) to hear back, pinged the recruiter politely now and then, and finally got a one liner "we've decided not to continue at this time.' A few weeks later, an article with came out with a picture of the CEO of this company standing next to President Obama, who nodded gravely as the CEO talked about the desperate shortage of software developers.
>Though I know it also can go very bad for people in small companies that have mini dictators in charge.

By definition every company has a dictador. They might be "benevolent" and willing to delegate their power to some degree, but at the end of the day, they have the final say.
Yeah. In all honesty, I would prefer _more_ of our interviews be straightforward coding problems that are reflective of the job the interviewee is going to be doing. Not whiteboarding. Not pseudocoding. Not puzzle problems. Just: write some code, let's see how well you google when you get stumped, let's see how clean your code is, let's see how quickly you implement it relative to other people, let's see how well you document it, let's see how well you collaborate with the interviewer.
Usually the latches are only accessible from inside the cabin, however; if only the trunk is unlocked, you can't fold down the seat.
I have one on 5" phone. I lately think that I would gladly go back to my old Moto G 1st gen that actually works better now on LineageOS [0] than before on original ROMs. It's smaller - it fits my pocket. It is a bit less convenient to stare at the screen, but now I think that's good. But sadly it has broken SIM slot. Maybe I will sell my phone and just buy something smaller, used with good LineageOS support. Or maybe something even more inconvenient - at most 10" 3g laptop.

[0] But last April Fools' "joke" was really testing my nerves and I'm still not settled on this.
I find the coding thing interesting as well, in part because there is coding and there is coding.

I suspect it is the difference between "coding ability" and "coding fluency." In the former a candidate can apply known patterns of a give language to a problem and with just a few searches on StackOverflow get it working. A person who has code fluency can create the algorithm in the language of your choice, pretty much on the spot.

In the music world you meet people who can play a song on the keyboard that is note perfect, but they can't transpose it into a different key. Its the difference between playing the keyboard and using the keyboard to express a musical concept.

Can you speak a language if all you have done is memorize an extensive phrase book? Yes, are you fluent? No.

The number of candidates who really understand the nature of coding and so they can quickly adapt to any idiomatic language is still quite small in my experience.
As a nerd interested in all things future and retro, thank you for sharing that subreddit. I will definitely check it out!
Amazon was "bleeding" cash for the first 2 decades of its existence, and nobody complained.
The intended target audience of this article are people who already know what all of those acronyms mean.
I think this is most people who “can’t code”. Just nerves

I’ve been in that situation myself.
This is such a weird industry. Most current devs will be still coders when they are over 40. Only a few can make it to management or high level lead engineer roles. There are not that many openings for that kind of role. I used to work as mechanical engineer and there it was totally normal to have engineers who were 60 years old.
I found my current gig by using a recruiter I was referred to by a respected coworker, and it's by far the best job I've ever had (out of 5 or so). Super small sample size I know, but if you can find a recruiter that you can trust/isn't just pimping you out for a payday and nothing else, you can skip a ton of bullshit.
Well, if you have multiple layer 2 networks, you need multiple subnets, and you should assign a /64 per layer 2 network for stateless autoconfiguration to work, so splitting a /64 into smaller pieces is not a good idea, therefore an ISP should give you at least a /56, better a /48, that you can subnet for any layer 2 networks that you might have.
I was a charter business fiber customer for 5 years. (multiple sites in multiple states) I asked every few months, got relayed to the same web page sayings "its rollout is planned in Q4" (for 5 years it said that, never included the year) and gave instructions on how to setup the single 6RD server they had in St. Louis. They merged with a few other cable companies, who had working ipv6, but nobody could give me timelines. We had customers wanting to access our applications via IPV6. We actually had to setup a remote proxy on an IPv6 network to then proxy back over IPv4. I left that job a year ago, so perhaps Charter has had a huge change of heart, but I strongly doubt it.
I believe this is what TechDirt already does for court decisions, and a few other sites I've seen. It's not the cleanest look for a webpage, but I appreciate having primary sources available right alongside the article.

e.g. https://www.techdirt.com/articles/20140122/11374325957/supre...
I agree, but the problem is that unions notoriously favor the older, entrenched generations of a profession over the newcomers. Talk to people from NYC (a place with still much union influence) and you see a stark difference between the old folks and the younger folks in how they view workers' unions.

Software development is already so heavily dependent on enthusiastic young people that I don't see how a union could get enough traction without completely reinventing the idea of a union in people's minds.
Even if they started giving it out, it would be next to useless due to all the legacy network gear that wouldn't play with it.
In my experience, getting hired for those "post-senior" roles is even more ridiculous than for senior roles. You often run into biased, judgmental, and insecure directors and vice presidents who seem to be terrified that you know more than them. I say this as a 37-year-old with nearly 20 years of experience. Sometimes, people don't want to believe that you know what you're doing.
Intellectual "Property" is an intentional misnomer used by IP holders as propaganda to support the idea that IP is "just like property."

It's not, because unlike property you can't establish that 100% of a project were your ideas and your ideas only. Every new project is a recombination of ideas. It's not 100% original.

If copyright and patents would be enforced perfectly and automatically, there would no longer be any new inventions.

More on this here:

https://www.theguardian.com/technology/2008/feb/21/intellect...

https://mises.org/library/intellectual-property-not-true-pro...

https://www.everythingisaremix.info/watch-the-series/
Repos. Watch the Kelsey Hightower keynote video I added to my post.

Don't get me wrong, I think auto devops is a good thing, but it's most certainly not gitops.
> npm@6 is up to 17x faster than the npm of one year ago.

I think by "npm of one year ago" they mean npm 4, since npm 5 came out last May. If so, "up to 17x" is plausible. But even though technically true, this is a cheap marketing move, IMO. If one doesn't read carefully, it may register as "npm 6 is 17x faster than whatever came out last year, that is npm 5".
Been coding professionally since '99 - C/C++/C# until 2012, then Rails/React/Angular over the past 6 years. I guesstimate I've been on some 50 interviews.

If anything I feel that things have gotten better, although this may be a difference between my former enterprise Windows-stack life vs. open source tech life. The main differences I see are:

- Take homes are more prevalent... but I recall only one which has taken more than a half day, and that was fair as I was relatively new to Rails at the time. I actually like doing these for jobs I'm interested in as they give me an opportunity to flex my skills.

- There's about a 50% chance that you get a CTCI type interview vs. a more pragmatic, what-you-experience-on-the-job type domain modeling, write out in code in Rails (or whatever framework being used) type of pairing. When I'm on the hiring side I focus on the latter and feel it's quite effective. When I was starting out you almost always got the CTCI type.

I typically red-flag potential employers who don't sufficiently validate the skillset of potential hires. I've worked with plenty of people who were terrible, it's one of the reasons I transitioned to Rails.
I don't find this line of argument to be at all plausible.

The purpose of the Courts is to dispense Justice. This will invariably involve making new law. If you insist upon saying this is just "interpretation" when you do it, but is some sort of over-reach when other people do it, I feel the same way as when I see a sports star insist they were "within the spirit of the game" despite cheating while their opponents aren't... (e.g. ball tampering in cricket is very bad for this)

The thing that's special about the courts compared to say, a legislature or executive government is that they deal only in Specifics. They must consider _actual_ things that happened and judge those. All those named cases like Brown v Board of Education are about real people, to whom real things happened. That's what the judges are for. It will be necessary, from time to time, in the process of achieving Justice for the people those real things happened to for the court to make up from whole cloth entirely new law, and a good judge should not shy away from this practice where it is necessary.

Sure enough "Originalist" judges do not, in fact, shy away from making up new rules to achieve justice. They use their "originalism" instead to defend situations which presumably _they_ think are just but which seem wholly unjust to their fellow judges, and they deserve nothing but scorn for that. Say what you mean, and mean what you say.
This comment really demonstrates a lack of knowledge and understanding of the situation. Not to HN standards.
Thanks! This looks awesome
I guess I don't understand why companies do this process.

When I was hiring Senior engineers for Computer Vision and 3D rendering jobs my process was thus:

1. Post job and simultaneously search for engineers we thought were a good fit technically

2. Reach out to people I thought were qualified based on their specific previous work that was related to the job I was hiring for

3. Review submitted applications for relevant experience

4. If we thought it was a technical fit, we would do a <30 minute team phone call with some basic work history questions, description of role/salary and work logistics (remote, dev environment etc...)

5. If we were satisfied with that, send them a <10 hour total, paid, production project at an agreed upon hourly rate. If the candidate didn't have the required IDE etc...it would basically be pair programming

6. Review code, speed and communication

7. Send a hire/no hire decision immediately

From first contact through Steps 4-7 it would ideally take less than a week, depending on the candidate's schedule.

We were only burned on this process twice.

Once the guy kept trying to negotiate salary up over two weeks so that he could get a higher price somewhere else.

The second time, the guy did well with initial production, but over time he ended up using local college interns to write his code, who got other jobs and his commit speed fell off of a cliff.

Since we are a remote team, trust was paramount, and we trusted quickly by default. Nobody ever had complaints about the hiring process and we had a higher than average success rate for hiring fantastic developers and getting quality code into production quickly.

We never asked current salary because it wasn't relevant. I knew what I could pay and that's what was offered. If they asked for more and were worth it, then I would try and find money to make it happen, but generally it wasn't an option.

I would do it the same in the future.
It was like waking up and not knowing your own name, it was such a strange feeling to watch myself fuck up so badly, and be utterly incapable of stopping during the interview.

And I wasn't even particularly nervous about getting or not getting the offer either! They approached me, and I wasn't fully sure if I would even like the job yet!
It reminds me of a husband who says, "My wife might not stay true to me, so I'd better forbid her from speaking to other men." That's one way, but another is just to continue to provide something of value in the relationship.

Anyway, it's not like I want to do further research on every article. My time is limited, and I appreciate a good, professionally-written summary and analysis. If a news site can provide that, I have a reason to keep engaging with the site.
Ask HN: Is Grasshopper a good tool to teach myself how to code?
I have just started using it and like it so far, but didnt know if there were better resources for a beginner like me.
An Introduction to the GNU Core Utilities
> At the end of the interview, I would recommend asking "are there any concerns or issues you would have with hiring me for this position?" and LISTEN to their feedback.

At the end of each interviewer. Asking the HR person at the end of it all is a waste of time for 2 reasons:

1. they won’t know yet

2. they won’t tell you

but the tech interviewer almost certainly isn’t trained to keep his mouth shut and also generally isn’t expecting this question. caught off guard, you can usually get a close to honest response. you do have to interpret a little because people generally don’t want to hurt other people’s feelings right to their face. apply modern day party invite response rules:

yes: maybe
maybe: no
no: fuck no
I have found it to help.

It's not a perfect solution, but I find part of the process of being less involved with my phone is acceptance of the fact that I might not be able to be able to address every need at every moment and that's ok.
7-2 is striking for a Supreme Court decision - I usually read that as "the legal situation of this case is blatantly obvious, nice try".

The Roberts/Gorsuch dissent isn't exactly shocking, either; it's a nice display of the move from Republicans appointing originalists to appointing semi-activist corporatists.
> As a hiring manager, I’ve given homework assignments to weed out candidates from the pack but I always kept it reasonable, just a few hours in length.

"Just" a few hours has always, always been an underestimation when I've tried these. I've been burned a handful of times now; both from my time and from my belief that it would amount to something. I'm reminded of one instance where follow up emails kept coming after submission: "Add in this now." "Okay, now this." "Handle this." I consider myself an average engineer. I'm not interested in increasing my sample size to try and average out variance any longer.

I'm looking outside to one of the first sunny, warm days we've had here in months. I can't think of anything more I'd rather not do than some arbitrary company hiring project. I simply pass on these now and politely pull out from consideration.
For an entire degree program I agree, I've seen lots of agonising about these and many roadblocks. But for a module many universities are pretty agile right now - much to the student's benefit.
Pipenv: A Guide to the New Python Packaging Tool
At my job we have so many libraries in different parts of the code trying to do the same thing that I don’t even try to memorize anymore. I just look it up.

What’s the order of arguments on this one? Does it modify the data passed in or create a new one? How does it handle nulls?

It’s cheaper to look it up than to debug. So that’s what I do.
> I find this ludicrous because it is like interviewing an attorney and then saying to him “Please prove that you can cite a Supreme Court precedent”.

They don't need to do that for lawyers because the bar exam handles that (and, for those with traditional legal education, the highly-standardized law school curriculum.) The programming “profession” has neither of those features.