skysight-inc/HackerNews huggingface dataset:
I find that this list[0] is extremely geared towards a fairly specific style/culture/stack kind of thing.

Lots of companies will "fail" this list, and it could be a real missed opportunity.

SOURCE: I ran an organization that "failed" a good many of these, yet retained top-shelf C++ talent for decades.

[0] https://github.com/Twipped/InterviewThis#developer-coordinat...
It's easy to see red flags as a dead give away in retrospect and we all want to feel like something like this would never happen to us. But this is biased thinking. We all ignore massive amounts of supposed red flags on a daily basis, otherwise we would be permanently paralyzed by fear. But the ones we ignores with no consequence are not recorded anywhere.

Getting scammed could happen to anyone, no matter how careful you are.
That may sound promising on paper, but I give it at most 6 months before an up/downvote manipulation SEO industry emerges and starts destroying any burgeoning improvements in the quality of search results.
>I can never read anything by nytimes, even with removing cookies

Disable JS on nytimes.com (i use the Ublock Origin extension for this) and it works fine.
Right, I couldn't even answer "What percentage of the company is LGBTQ?" because why would you ask people that specifically?
Rofl, only Americans care about this..
Like which ones? I think Horizon is on par at least but definitely a step above the competition. Rec Room pales in comparison.
I mean I'm reading that and I just wonder if the grandparent only hired one person for that role; if it's that critical, you should never rely on one person. You need a team and thorough QA.

It does remind me of this article I once read about how things happened at NASA, with every line of code extensively documented and discussed, and teams competing with each other to find bugs.
From a FreeBSD comment I made the other day:

> If you want to try FreeBSD just use the Handbook, it documents FreeBSD very well. That said betrays childish aspects e.g. they refuse to list that FreeBSD can run on Linux/KVM (the mere fact it can, I'm not talking in depth instructions).

(from id=32369189#32372408)
The collective “we”, which is largely independent of your individual opinion.

The problem is not that we have a faulty map. It’s that you pretend it’s irreversibly faulty.

We’ve successfully navigated quite a bit of trouble and chances are that we’ll be able to do so in the future.

What you are suggesting sounds a lot like: let’s do nothing.
Source control is a tool I interact with daily. I should be able to ask you about it. I personally don't care which tool you use unless your process around it causes friction for me. I don't want friction from doing source control. That's easily fixable and if the company isn't willing to fix it, I am not willing to waste my time there.

How am I supposed to ship if your SC is such a mess?
Linux kernel programming is probably like this. There are no automatic tests, so the more pedantic you are, the less bugs you'll introduce.
Reddit Brand Guidelines 2022 [pdf]
Impressed by its comprehensiveness
It's kind of inappropriate to ask someone if they're LGBTQ+ as well; they'll tell you if you want to, but you shouldn't keep statistics or records of it.
There were so many war crimes in WWI. I'm sure partly the reason why they called it the war to end all wars first coined by HG Wells.

http://news.bbc.co.uk/2/hi/special_report/1998/10/98/world_w...
I think the concern is that the industry, including Facebook, has decided that the designation “senior” is a thing you can get in <5 years. It’s a norm in software so it’s easy to see examples of it, and in practice who cares what the titles were if they are used consistently.

But what if you were outside the industry and heard that term? A senior judge typically has decades under their belt. A senior chief petty officer is the second highest non-commissioned rank in the navy implying a whole career behind them. They might infer it only takes three years of experience to reach the near top of the software craft.
Microbatteries much smaller than a grain of rice
And replacing the water in your body with an aprotic solvent such as DMSO.
> 3) Grazing animals are good for carbon capture, as they need grass to graze, and grass is one of the best carbon sinks.

a) Citation? Most studies I can find on a quick googling show minimal effects.

b) Whereas clearing forest to create pasture for animals to graze is...not good for carbon capture. Quote from WWF: "Alone, the deforestation caused by cattle ranching is responsible for the release of 340 million tons of carbon to the atmosphere every year, equivalent to 3.4% of current global emissions." https://wwf.panda.org/discover/knowledge_hub/where_we_work/a...
History is written by the victors. When you're on the overall winning side you can wipe out war crimes or genocide within a blink of a decade. Just as long as you can stay on that side until your past becomes distant enough.

Even provable facts don't really get traction and things get swept under the rug. You don't get to read that much about such a British blockade against Germany, about a Belgian genocide in Congo (or any other major European country, even for things from the past century), etc. It's not that they're not considered big deals, it's that people are usually completely unaware they even happened.
Seniority is the fact or state of being older or higher in rank or status than someone else. Within an organisation, a senior engineer could be the engineer with the most experience with the codebase everyone else is working on.

I do agree that certain habits or experience from working for additional years might be missing, but as the first engineer of a codebase, IMO, there will always be something to learn from them. Which makes the article credible enough to warrant a read.
I used this list recently: https://github.com/viraptor/reverse-interview
Just a note that functional programming here seems to be conflated with declarative programming. They do have some things in common ("no mutable state" being the main one I can recall), and technically I think FP is categorized as a subset of DP, but in reality a declarative program ends up looking quite different from a functional program, so it's with distinguishing the two.

To give a trivial example to illustrate the conceptual difference: a declarative program could say something like "the output is the solution to f(x) = 0", defining f explicitly and leaving it to the compiler/interpreter to supply the algorithm for figuring out an x that satisfies it. Note that, as long as x is unique, "try all legal values of x" works, so a viable fallback algorithm always exists; it's just inefficient. Whereas with FP you actually have to supply an explicit function to (hopefully efficiently) compute the output, i.e. you basically have to write f^-1 yourself, which typically results in a very different program - sometimes harder to read, sometimes easier.

Now, of course, you could do "FP" by writing f instead of f^-1 and then enumerating all possible inputs as with DP, just as you could write a DP to compute functions explicitly at every step, and you could write imperative programs for all these. But those would be unnatural, and would generally defeat the advantages of the paradigms.
The really unfortunate part of this is the number of people who will use this as evidence that what he did with Gravity Payments either simply doesn't work, or is an actively bad idea.

Because, as several others here have pointed out, either someone is a Perfect Paragon of Purity, or they are Evil To Be Shunned And Cast Out...and everything associated with them must follow in either case.
Yeah, cattle and sheep farming is hugely destructive to the native Australian environment. But sadly nobody wants to eat kangaroo.
I use the "Search the current site" Chrome extension. You can just hop to a YC or Reddit page and click the search icon, but it works with all websites.

https://chrome.google.com/webstore/detail/search-the-current...
A GPU from 2008 has to fill a quarter of the pixels at half of the refresh rate and has no latency, weight, or heat requirements. The Quest 2 has to carry a massive burden being on a face and fill nearly 4k pixels at 72 FPS. Meta has stringent requirements on maintaining that FPS to prevent VR sickness
How did you go about improving it?
Non firing presence is not blockade. It is just another ship you pass through, maybe waving flag. I do not think any navy ever had so many ships they would be able to cover the see.

Blockades are enforced by firing.
It is bizzare. People care about "diversity", but don't ask whether the company sources materials from horrific kobalt mines of Congo, or whether the company is actively working to addict its users, or whether it's doing tax evasion etc. It almost looks like a corporate psy-op - people were made to care about the one "social justice" thing that does not cut into corporate profits that much.
There are different kind of small EVs of course. It depends on the role the EV fills. Sidewalks absolutely have to be reserved for pedestrian-level traffic, but people who are unable to walk need to be able to go there, so EVs on the sidewalk should be as small as they can possibly be, open, and go a maximum of 5 kph.

Ideally, all urban street traffic should be slow enough to accommodate all other forms of traffic, so about 30 kph. Large connecting roads where you want cars to go faster than that should have a separation between car-level traffic and bike-level traffic, with bike traffic going about 15-25 kph and being narrow and preferably open, while car level traffic goes 40+ kph and is preferably enclosed.

Of course there will always be vehicles that don't quite fit one of those categories, which leaves the question to what extent traffic design should accommodate those vehicles, and to what extent those vehicles should just try to fit into the category that fits best.
It's not the same thing. Not by a long shot. They are not in prison for the crime of being a minority. There are no US laws criminalizing behavior according to ethnicity or religion, nor could there be.

You are equating state-sanctioned cultural genocide vs an imperfect justice system with a racist legacy. I could go on, but I really don't need to.
For anyone curious, the (modern) guideline for humanure is to let it sit/compost for two years before using it, for the purpose of letting any parasites in it die. This is compared to 3-6 months for eg chicken manure (which is primarily, IIRC, about "mellowing" the fertilizer ie letting it undergo some chemical changes).
Typically companies have the pick of the litter unless you are exceptionally skilled and/or already have a super good reputation the power dynamic is - unfortunately - in favor of the company and ignoring that fact is likely going to be counterproductive.

Ideally companies would be up-front and transparent about all of these but none of the companies that I've looked at over the last 15 years had the foresight to prepare an information package that would answer the bulk of these.

Incidentally, that's a thing I could really get behind: to standardize a list (possibly this one) and to get companies that are on the market to pre-emptively answer them so that employees would have a fair shot at comparing companies on their own time.
Yeah, I have an issue with state employees (bloated school administrations, police...) getting 300 to 600k in compensation. I bet most people in the US would also have an issue if the media gave fair coverage.
Employees at my last company complained loudly when the diversity question was asked and the CHRO responded that they didn't collect that info because it was either misleading or of questionable legality. This was by far the youngest & most diverse group I've ever worked with (and I'm an old, white, straight male) so pick your poison.
Hotel stays do cost something but much of this is just the daily carbon emission of the traveller, just done elsewhere.

The delta exists but how big it is actually? Wash the towels and bedsheets, vacuum the room?
I've noticed many of these articles about what it takes to be a good software engineer talk about code quality.

I recently started to work in a team of very senior engineers (with relatively little experience) and what I've noticed is that code quality is rarely mentioned. Everybody write "good enough" code and there's never much discussion around code quality (occasionally a few remarks in code reviews) or design.

Generally, there's very little bikeshedding on code quality and that kind of things. People are pragmatic and wants to get the work done. It also means there are trade-offs regarding code quality (also dictated by management and pressure to deliver).

The challenges are elsewhere. Prioritising, communication, relationships with colleagues, setting up roadmaps and milestones, proposing designs, solving various challenges.

Generally, I found software engineering is less and less about writing code. I'm impressed how my colleagues are good at everything. Fluent in most programming paradigms, able to debug complex production issues, do low level performance analysis and so on...
> There's this whole scene of people who do performative, almost theatrical, quality programming but nigh on forgot how to actually ship features, and questions like those are a hint they might be in that camp.

Sorry, but I think you're probably wrong as well. Do you actually sell features? As in: Is your revenue directly tied to the number of shipped features per year? If so, who pays for the perpetual maintenance? Did it ever occur to you that every feature is a liability? Security issues, bugs, incompatibilities and odd side-effects with other features, legal changes all add cost per feature.

If you're (like many in the industry) piling features on top of each other because you currently have no idea what your finished product should look like and you're hoping that your feature pile will someday somehow turn into a profitable product, I think you're wrong. And even if it does, you'd better exit shortly after because mid-term maintenance will be a proper nightmare.
I feel like I didn't get the joke. Can someone explain WTF is going on? This feels like the subject was using precise mathematical terms by metaphor to do ... procedural generation?
Nice if it be done in the lab, and then?
How do you take it out of the full environment without a successive contamination do to cleanup chemicals?
I count one advert on the original, and the page loaded instantly for me on my 10 year old laptop. What am I missing?
I don’t care what “social justice” is being used to mean in this article, but it’s not a new concept. The Big Guy from Galilee was real big on the concept, what with turning the other cheek, helping the poor, giving more to those who take from him, …. Oh, and He was real big on being non-judgemental.

If you claim to be X, then you need to follow the rules and philosophy of X. He wasn’t big on hypocrisy either. I’m sure the related religions along with many philosophical systems share similar beliefs and motivations.
As an LGBT non-white non-man, they seem like perfectly reasonable questions to me. In my experience, diverse workplaces are always more welcoming (or at least less likely to be outright hostile) to someone like me.
The global burden of cancer attributable to risk factors
Something of an aside, but your comment here seems largely well-written, reasonable and a positive contribution to the community, but the usage of "muh privacy" really, really harms it. It makes an otherwise sound argument come off as childish and rude and is derogatory towards people who have slightly different priorities or views.
>...You could imagine a remediation process that uses this process but the combo ain't exactly Dawn dish soap.

"...The relatively high freezing point of DMSO, 18.5 °C (65.3 °F), means that at, or just below, room temperature it is a solid."

, per Wikipedia.

I guess, it could be powdered before use. Though the whole application proposition hardly fits into a common household let alone kitchen.
Thank you. I'd read CC ... 15+ years ago, but couldn't remember this specific step (but I know I've internalized it). I had criticism from folks a couple years back because I used "x" and "i" as variable names in loop counting - for (x=0; x<limit; x++) - that sort of thing. I had folks block my PR because "don't use short variables - that's unprofessional". These were loops inside a test file, and, at that time (8 months after launch), I was committing the first test to the project. It was blocked while I had to think of something better, like for(loop=0; loop<limit; loop++) - which was deemed "acceptable".

This concept from CC was at the back of my mind, but couldn't articulate it, or even remember where I'd first read about it, but it's been something I've worked at adopting and growing over the years. 6 line loops - x/i/j/k/etc are all valid and usable. In some ways, it's actually more helpful to me, because the longer names indicate something concrete/real, and the single letter names indicate local/throwaway values.
It’s great to hear them admit that there is a problem. For years we’d get “our internal quality measures say we’re doing great. You’re imagining things. Fuck off to Bing and see how you like it.”

I suspect they have an inventory problem, not a ranking problem. Why would any real humans publish publicly on the internet at this point?

If you’re posting for fun you have to deal with moderation and stolen content.

If you’re posting for pay Google just takes your content and shoves it onto the SERP, skipping your ads.

Bill Gates had it right. If you want a sustainable ecosystem, you need to make sure the other players are making more money than you in aggregate. As far as I can tell, that’s only true on the internet for eCommerce and so that’s all that’s left.
Ask HN: Anyone using Swift on the server-side?
What are the challenges and advantages?
Strong agree. It reminds me a bit of the format of interview that unskilled or inexperienced hiring managers come up with:

- "How big was your team at your last company?"
- "What languages do you use at your last company?"
- "Do you prefer to use for..in loops or [].for() notation?"

And using the surface answer as the way to make a decision. Being able to navigate a topic from broad-to-specific is a specific skill that is rarely taught and are very lucky if they manage to stumble on to it after enough experience and self-reflection.
I think it's going to require a social rating system. Which is why people append "reddit" to searches these days.
Actually that's a cool idea, put a graph on the scroll bar which shows where most people spent their time, same as the Youtube widget.
Actually, I find that conceding the remaining safe surfaces and normalizing powered transport is exactly the solution.

As the general population experiences both the benefits and the drawbacks of powered transport, cities are much more responsive to creating dedicated space for vehicles of this type. Even painted bike lanes are preferable to the usual status quo of rolling the dice in a regular lane against multiple F150 drivers on cell phones on a city street. And as such infrastructure improves further, the benefits of using that infrastructure for the powered transport rider increase dramatically vs competing against people walking on a sidewalk.
Some conferences require that you publish your code. So all they have to do is add to the paper "our code will be published at this url: ..." and then once they're accepted they never do it.

Similarly supplementary material makes their paper seem better and more solid than it is, so they say they have it then never publish it.

It's just generally scummy behaviour from people who are under a lot of pressure to publish.
Oh, jaywalking. Lock them up.
This is the same problem, but your algorithm was not n/e.

If there are 100 homes on the market, doesn't the optimal algorithm suggest

100/2.718 => 37 homes must be assessed

after which you commit hard to the first home that would be above all of those top 37?

I mean: you can't argue with the results. You underpaid and are delighted with your home! But you share the problem space without having implemented anything close to the ideal solution. In this case your intuition and sophistication resoundingly /trounced/ the ideal solution in terms of efficiency.

So you won!
Any pig meat has a very very distinct smell to me.

I can also recognise cooked poultry vs beef by smell (more so when raw, but when cooked I'm sure I can figure it out as well).

I thought most people could.
And this would be a great way to explain how optically active materials [1] work.

[1] https://en.wikipedia.org/wiki/Optical_rotation
I've encountered a company without version control in recent times. Interesting aside: they produced very high quality software, so it's not even a cut-and-dried thing on that front. Personally, I wouldn't get through the day without it but apparently there are people disciplined enough to manage. But I suspect they are quite rare.
Again disclaimer - I work on Cypress, but I think I can speak objectively, as I was user for many years prior to joining.

> ... defending a sunk cost, rather than than advocating for the best API ...

If you really go all-in on the Cypress API, writing custom commands, etc, not having to mess around with async/await is really nice. It's a strong point for onboarding QA devs, who might not be familiar with JS, Promises etc. This is also one of the major drawbacks - for any proficient JS devs, who are used to async/await and the usual business, the obvious question is "why isn't this just standard JS?". I definitely had the same feeling when I first starting writing Cypress tests.

> It would be hard for Cypress to change the API now ... I doubt Cypress team would design the API this way if they started again today ...

I am not sure of the technical complexity or priority of decoupling Cypress from the Chainable API. I'd assume the complexity is not supporting async/await, but supporting it alongside the current API.

I think the ideal case would be loosening the coupling between all the parts of Cypress, that would allow someone (either the Cypress team or a third party) to write their own selecting/assertion API, and they could then optionally write it with chaining, async/await, or something else. Perhaps even create bindings for another language (currently Cypress is JS only, since a lot of the code executes in the browser, unlike Playwright, where everything is via the CDP - another example where one of the main strengths of Cypress can also be a weakness).

Hopefully this gives you some more context and insight! My goal is better testing tools for the web, I think both Cypress and Playwright are solving this problem in different ways with a different philosophy. I'm glad to see so much innovation in the space, I hope we can keep pushing things forward.