skysight-inc/HackerNews huggingface dataset:
Inclusive UX Education: Designing a Free Online Learning Curriculum
Agreed, if it is their profession they know it better. The thing I was initially refering to is stuff like people who do a horrible layout in word and ask to to literally do the same thing without having any qualification on the matter. Or people who want you to put a whole page of text nobody will ever be able to read onto a roadside sign.

This feels like if one would ask a electrician to use wires without insulation because they like them better — you can totally have your taste, but some stuff is just plain stupid and won't work as intended.

Graphics e.g. is about communicating certain things, and a graphic designers job is to be aware of what this communication does and how effective it does it. And so just like with a bridge (but arguably less dangerous) there can be design that does the job and design that does the polar oposite of what your customer intended.
Agree. It’s all telling, no showing, which violates a basic rule of good fiction writing. There’s close to zero dialogue. No characters or their development. So applying the expectations of a traditional novel will leave a reader very dissatisfied. But it’s compelling. One of my favorite books (whether we’re calling it a novel or not).
I use it all the time to correct password mistakes: I would be really irritated if that went away: in fact, I frequently use devtools on my laptop to change password inputs to text inputs
Is this any different from “software engineer”?
> There have always been some restrictions on elected officials (age, for example) and I think it’s obvious that you’d want competent literate people in positions.

Things like this happen sometimes:

https://en.m.wikipedia.org/wiki/Bosco_the_dog
> I find it hard to believe that something like this wouldn't collapse under its own weight fairly quickly.

At least in the case of that company the collapse will be a slow crumbling, not a big bang. What I expect will happen is that 5-10 yrs from now they will be out competed by nimbler new-comers. By then however all the important people will have executed their options, gotten their bonuses etc. and moved on. The rank and file will remain unhappy, there will be churn and nothing will change.
Apple News+ reportedly had 200,000 subscribers within 48 hours[1]. May we all have "nobody" customers.

[1] https://www.macrumors.com/2019/11/14/apple-news-plus-subscri...
God I hate these things ever since I had one break from underneath me and cut my leg open as a kid. Ugly, waste-full, cheap, choose all three.
I was taught at an early age to never trust anyone who wants power.
If I employed fulltime now, then I'm unlikely to consider switching to 3 months contract.

On the other hand, I think it may be a good idea for the company to consider:

- either hire fulltime somebody, who has solid track record and "prooved" themself during on interview

OR

- offer 3 months contract to someone, who is not that good at passing interviews, so they can prove themself doing real work.
I didn't say it was. I said the two countries changed "after (different) traumatic war, occupation and colonization events".

Japan was traumatized by its encounter with westerners, by being forced to open its borders for commerce (through force), and later by WWII defeat and subsequent nuclear obliteration of two of its cities, and occupation and supervision by the allies (or, well, the GIs).\

For South Korea, ironically, it was Japan itself who at some point was the colonizer and occupation force...
Class actions are also impossible, because of those mandatory arbitration clauses.
Interesting. Is this how catalysts work? By bringing the atoms/molecules reacting together and providing a path for taking away the excess energy more easily?
1. Not saying they should or shouldn’t and as I noted if you can’t match salary and all other things are equal you may as well take the raise.

2. If that’s HR policy and you request for an exception and it’s denied, that may be a sign to start asking more questions.

3. You’re assuming that’s HR policy. Again, example dictates you have one option without actually thinking through how an organization could position themselves differently. Of couse salary is a component and rightly so, but at a certain point it’s just not everything

Think of it this way: lifestyle, ancillary benefits, “perks” etc can be all valid reasons to stay a place that treats you well and displays real loyalty (which is often displayed in more generous long term planning like big 401K contributions and fully paid health insurance for the family, open source software time etc). Can’t say I would just arbitrarily leave that for an extra 20% because that 20% can be easily eaten in other ways. Not to mention transparently knowing that your job won’t evaporate if the economy gets soft is a win. All this salary gloating is fine until that happens. 1999-2001 was not a fun time to be in the upper band taking pay cuts

Let’s not grossly oversimplify this. I’m never going to say don’t maximize your value, you should, I’m saying there is more than one (salary) way of doing that.

FAANG or not.

Oh and one dirty secret FAANGS don’t tell you? They happily underpay on salary once you’re in, or freeze you into a specific department etc. it’s not all roses.
I know AWS uses it heavily in distributed algorithm/system domain. I’m wondering if this is also useful for verification in other domains like data modeling and machine learning. So far I haven’t seen too much TLA used outside the core system/infra engineering/database groups
> Why are you telling your students that “no professional environment you’ll ever be in will encourage something like that,” counter to what’s guaranteed them by US labor law?

Encouragement and acceptance are two completely different things.
Interesting factoid for perspective - if you take the US and exclude every metro area at least as big as the Austin* MSA...you still have a majority of Americans.

*I think Austin is the smallest mentioned.
How many actually paid once their free trial expired?
They also (East-Asia at least) have the highest average IQ. Some admission process of big US universities precisely have floating requirements to discriminate against them.
Yes, racist imposition of cultural norms to the world at large tends to strike some nerves...
For us it's simply the runtime you target. A frontend engineer writes code for the browser. A mobile engineer writes code for iOS or Android. A backend engineer writes code for servers. A data engineer writes code for the analytical/warehouse environment.

It was typically backend engineers doing the data pipelines to expose records from their own services, until the company got bigger and the analysts got more demanding, and that became a dedicated role.
Somehow it neglects to mention that, but instead uses a vague term of "Impacts the mission", which very much sounds like corporation-speak for "negative public attention" and similar things.

Luckily, that's easy to fix by adding a sentence or two to this section.
I think you missed the point. The guide is fairly upfront about it being a bad idea and a very atypical approach to learning Rust.
It may have, and it's not just a conspiracy theory - there have been reports about man-made genes in the virus and the sloppiness of government employees is well known.

It may take a while until we know for sure. Those of us who survive, that is.
There seems to be a pervasive misconception by the very employees at Uber, that they built their own chat platform. When in reality, and someone please correct me if I am wrong, uChat was a white labeled Mattermost.

I have heard that the team that put it together actually tried to hide that fact from the company (for the glory, I guess). But that could be apocryphal.
Hiring is broken, but so is all of software as a profession:

1) Terrible Algorithmic interviews, AI-based evaluations, whiteboard coding.

2) Hey you are hired! Now move to $BigCity, with expensive real estate, schools, transit and everything else.

3) So, welcome to the job. You'll be maintaining this shitty old python 2.4 CRUD app that multiple people have tried and failed to upgrade. And one of the web guys wrote his own UI framework for it, kinda based on Backbone but with a lot of custom stuff. Yeah he doesn't work here anymore. Anyway that part is in coffeescript, no we can't change that, too expensive to rewrite.

4) But don't mind that, because you'll spend half of your time in Agile meetings! How are you with story point estimation?

5) Hmm also we're behind on the schedule. You don't have a problem with 10-12 hour days right? And no we can't cut back on the Agile meetings, that would hurt productivity.

6) Open floor plan! We think this will help productivity a lot. But sorry, no noise cancelling headphones, that will hurt interactions. Also the VCs love it when they tour. Nothing like butts in seats.

7) Here are some options! But they are probably worthless, because we'll never be successful. Even if we are, we probably won't go public. Even if we go public, your share is probably worthless because of preferred shares and liquidation preference. Oh yeah, there is a 4 year vesting schedule and its ridiculously expensive to buy the vested shares if you leave the company, which is of course intentional since we don't want people doing that. Anyway maybe you'll make enough money for a new car, eventually. Imagine commuting in some sweet new wheels, 5 years from now!

8) Sorry, only a 1% raise this year. Health insurance costs and all that. But if you like, goto step 1 with a new employer to try to get a real raise.

9) Yes we are aware that the expense ratios on the 401K are 2%, and you are only allowed to invest in target retirement 20(fn($YourAge)). Indeed that sucks, for you.

10) By the way you only have maybe 10-15 years of useful programming life before age discrimination kicks in. So you better get crackin'
This is why I love HN. Also his blog is endlessly fascinating: https://www.bookofjoe.com/
I meant 1TiB total.
If the legs broke it probably wasn't weight concentration but just embrittlement due to UV and weather exposure. In my experience that's how most of these chair break, at the legs not in the seat.
Not at all compared to salaries.

I mean just think about how many VMs you can buy for $200k-$500k/yr (total cost to the company of a senior engineer).
Doesn't seem relevant unless the point about slack being too expensive and unable to handle the load is untrue.
Engineers are professionals in the business of solving problems :)
10x is a very safe margin. I suppose 2x is fine if you really know your code (usually you don't, really, unless you wrote all of it yourself).
It's impossible to build anything here. This overregulation at work. I wrote a blog post about a plot of land in Bolinas which I hoped to build something on:

http://jz.io/2018/05/12/development-is-difficult-in-californ...

TLDR there is triple overlap of legal authorities (City, State and County) who prevent you from building anything, with a 48 year old "water emergency" in place.
>Not to be a jerk, but

Then don't.
> Ultimately, developer retention and hiring suffer because no one wants to work on these products.

This was/is indeed the case for that organization.

> The institutional knowledge leaves through attrition

They have addressed this problem by simply silo-ing knowledge with a few key people who were very well compensated (think 10's of millions in stocks). These guys (the senior developers in my example) would only give out knowledge in bits and pieces, enough for you to do your job, but not much more.

> Eventually the quality of the product declines until customers leave.

I think more than the product becoming worse, it will simply be out-competed by better products. This will happen slowly though. By the time it does everybody who's anybody will have cashed in and moved on.
Listen, I don't know if you've ever lived in an honor society, but if you're a man in an honor society, "you could be seen as dishonorable or cowardly" (the word they used for me here was puto, which means "faggot") is pretty much a death sentence. Your understanding of comparative anthropology seems to be as weak as your understanding of ancient Egyptian mathematics.
Yeah, or a generation system where the pointer holds a frame count too that's asserted on deref.

The point though is that it's a step back still from shared_ptr/unique_ptr by becoming a runtime check instead of compile time.
Like any other product, various levels of quality construction are possible.
They can do it once their library is 100% Netflix originals.
SE usually at least knows what language they're expecting you to mainly work in. Not always the case for DE.
> If there are legal issues with a quota (I'm legitimately not sure whether there are), then the law ought to be changed.

That would be quite literally destroying the anti-discrimination laws which safeguard the exact thing that you think you're arguing in favour of. Quotas implemented the way you describe are the antithesis of equal opportunity. That 'instinctual negative reaction' you come across is people seeing the complete logical reversal going on in your claim.
Another big factor is how they're stored. If left outside in the sun they'll become pretty brittle. Most people probably experience poorly stored and older examples of these chairs just by sheer probability.
I expect that a substantial number of nonvoters suffer from learned helplessness.
You assume they might know or appreciate chairs and thrones. More likely they see it as an ancient monolith.
> How is hundreds of political campaign volunteers considered far-reaching?

Are these volunteers or are they being paid?
How the World Mourned Abraham Lincoln
I used it for the first time in firmware design at MSFT a few years ago, and I've used it since in the areas of protocol design. I don't use it frequently but it's a tool I'm glad I took the time to learn, and have to hand when I need it.

My experience is that, using TLA+, or other tools like it, encourages you to think precisely about the problem and at the same time exclude unnecessary details. That alone I find useful in terms of the insights it gives e.g. surfacing interesting invariants, or alternatively, invalidating them. In any case, you use the model-checker (TLC) to test these assumptions quite easily, and then bring these invariants into your code, either in the form of assertions, contracts or perhaps in property-based testing. In any case, I would say the process of writing such a specification yields benefits. Perhaps this can best be summed up by something I think Leslie Lamport once said: "If you're not writing when you're thinking, you only think you're thinking."

I should add that despite claims about TLA+ being particularly well-suited to concurrency problems, my implementation targets have never been 'concurrent' in the 'multi-threaded' sense. Rather, they have been single-threaded event-driven state machines, and I personally find that it excels in this space. However, as you will find, in TLA+, concurrency is just a matter of abstraction...

I have found that, because TLA+ doesn't 'generate code', many colleagues struggle to see the tangible benefit. I personally think that there is a gap between the whiteboard and the editor which tools like TLA+ fill very nicely. It's not a panacea or a magic bullet, and like any tool you must still exercise judgement about when to use it, and how to use it effectively, which includes understanding the limitations of the tooling (TLC cannot check arbitrary specifications).

But if I find myself faced with a potentially tricky algorithm, or indeed want to understand an existing algorithm, I reach for TLA+.
Said another way, people who work 80hrs a week cut their salaries in half.
To me his comment wasn't being a jerk at all.
I'm guessing those are way more used for private projects (inside companies) than public ones.
> the only way to really discover the requirements is to build the thing.

I totally get what you're saying here and in an ideal world, this would be it.

Unfortunately, we don't live in that world, projects have budgets and need to be delivered within a given interval.

They touch other aspects of the business and are interlinked with marketing, support, legal, financing and so on.

I think it's our job as software engineers to figure out the requirements. One issue we have in our industry is that we do a sub par job of educating people regarding how software works and giving them alternatives instead of binary yes/no answers.

I would say most developers (and I'm generalizing here) lack the communication/social skills to do so.

The key here is to strike a balance between features, budgets and deliverables.
Of course they do. React-helmet is great!
This Gonzo approach of running headlong into a bad idea is refreshing.
I am one of those poor saps that would use this.
But that would still happen at the point of dereference, no? Or does it allow to tag even operations like moves and adds?
> What would you propose as an alternative?

In my company (totally remote) we decided to automate hiring (also remote) as most as possible and we are happy with the results. We also value the candidate's time very much so we made the hiring process very straightforward. It works like this:

- First the candidates must do some online tests, which are mostly multiple choice questions. The subjects are logic, english and a specific test for the coding language. All of these tests were hand made to us and customized to our needs. The candidates spend about 2 hours in total doing theses tests, and they know immediately their score in the parts of the tests that can be accessed automatically (which are the most part)

- The candidates approved in the theoretical tests - about 10% of the candidates that applied for the job - do a practical coding challenge that was also made from scratch by us. We have looked at the available solutions in the market and thought they are too focused on textbook algorithms that are rarely used in the job market. So we made our own tests that contemplate practical problems a programmer has to solve daily in our company. The questions are NOT too complex. The objective of this step is to weed out the candidates that can't code in the language, not to get the best. We design this challenge to take about 2 hours. The implementation was a lot of fun: we use the Docker API to run the candidate's code against the automated tests we made and the score is calculated as the number of tests that passed. Using Docker means we can work with any language that runs on Linux. So far we have made tests in Javascript, Typescript, Ruby, Postgres and Elm.

- The candidates that are approved in the previous step - about 2-4% of the candidates that applied for the job - are called for an interview. Now is the time when we take a look at the candidate's resume and look at the human side of things. Given that we have very few candidates to look at and we know they all meet some minimum skills we are very confident when conducting the interviews. By now we usually have a very clear signal to tell who the best candidate is even before we conduct the interviews. So in practice the interviews are NOT used to select the best candidate. They are there just to see if a red flag doesn't show up.

We are very proud of our coding challenges app. If someone wants to collaborate on it just drop me a message. It's a Rails app on GitHub, but it probably not good enough for an open source project yet - one needs to know a lot about Docker and Rails to make it work.
Invoking racism on someone who disagrees with you isn’t usually a hallmark of the intellectually honest.
The "user's cloudAlbums" example is awful. Might as well use callbacks if you aren't gonna chain promises to avoid callback hell.
Security is a thing that is implicitly pervasive. If it doesn't apply, that should be explicit.

And yes, elementary data structures concern themselves with such things all the time - because, regardless of how they "must" be used, in practice they do get used on untrusted inputs on the time, simply because it's the easiest thing. Have you noticed how many languages and standard libraries have switched to random seeds for their hash tables lately?

And no, it's not true that you're going to "have a bad time regardless of the data structure". You're not going to have a bad time with an RB tree, regardless of where your inputs for keys come from - because it is a data structure that doesn't have a quirk of extremely bad perf on pathological inputs.
Trust me, the device audio/MIDI APIs are not the bottleneck.

Things like JACK (which tend to draw complaints) don't exist on other platforms (except ... by running JACK there), so complaining about its complexities (not that you did, explicitly) isn't really fair since that is based on an apples-to-oranges comparison.

I would guess that the options you miss are the result of application and plugin developers (not) being willing to include Linux in their target platforms. As cool as PipeWire might turn out to be, it isn't going to have much effect on those decisions.

Finally, lots of people seem to manage to forget how for years (decades, perhaps), high performance audio software on Windows required new device drivers (ASIO) for your audio hardware, because the ones that came with Windows couldn't do the job. This has mostly changed now, but ASIO is still with us nevertheless.
The Harsh Facts of Life in the 'Gay' World (1964)
Remote working is on trial in both China and Silicon Valley – upvotocracy.com
"we're all obligated to chant "interviews are broken" without ever suggesting alternatives"

Nah, there's somebody who hates everything, but there are plenty of things that somebody likes. I'd be happy with both take-home problems at a moderate effort level, and Fermi problems. Clearly many people go out of their way to declaim how much they hate those things, and I don't know where to find companies that hire based on them and pay a lot, but it would make me happy.
A video game that lets you make video games
I think this is actually a reasonable point from a certain perspective. I know personally since having kids, I work like half the time that I used to before, and I'm far more out of touch with the latest and greatest technologies. I nailed the hype train on functional languages and NoSQL databases in the early 2010's, but docker, k8s, and such, anything 2013 or later I'm clueless.

But I'll put the counterpoint on it. I've become a lot more focused on getting the job done in the limited time available rather than going off on tangents and integrating each new thing I think of into the project. I also am more careful in my work, because I don't have the time or energy to deal with mistakes after work hours. And I try to figure out the best use of my time to the company. I've mostly back-burnered the idea of creating the "next big thing" and that allows me to focus on doing the thing in front of me and maximizing my utility there.

So, boring, yeah, but I think career wise it's helped me figure out how to maximize my contribution.

That said, the two anecdotes you describe sound more like a Peter Principle in action. They probably did the same thing before kids too, is my guess.
It looks like Apple doesn't want to use the NPM ecosystem.
Yep, this is spot on.

In other atomic physics experiments it's a problem - three-body collisions are able to dump energy into one of the three atoms and that atom has enough energy to escape the trap. These are "three-body losses".

Whereas with two-body collisions, neither atom can be going any faster afterwards than the fastest one was before the collision. So they remain trapped.

Since the three-body collision rate is proportional to the cube of the density of atoms, and the two-body collision rate only to the square of density (for obvious reasons), this phenomenon limits the density of atomic clouds we can do experiments with. If we increase the density to the point where three-body collisions are significant, we rapidly lose atoms.
You seemed to miss GP's very next sentence:

>At least from our current knowledge of interviewing practices