skysight-inc/HackerNews huggingface dataset:
> Matchmaking only "works" in places where women are denied autonomy, and it results in them being sold off like cattle. This is not a desirable state of affairs to anyone but the most loathsome, pathetic basement dwellers.

This take sounds out of touch, and reveals a misunderstanding. There's no reason why matchmaking in America has to be one-sided, or treat women like "cattle". Women and men can both hire matchmakers to find their partner. That you can not see this is perhaps more of a projection of your own views on women.

Are you suggesting that all men who have arranged marriages in India are "loathsome, pathetic basement dwellers"? This viewpoint seems entirely indefensible.
"The massive power asymmetry matters."

Rules for thee but not for me? What's the boundary for company size that forces public release of code vs. allowing a small company to choose its customers?

If Red Hat's customers find the situation intolerable, they can and will stop paying Red Hat and do business elsewhere. It's not, by and large, Red Hat's customers that are squawking about this - it's people who have decided they're entitled to the clones and are actively undermining Red Hat.
Yet I find when rewriting from scratch there's a countering force of simplification where I find myself thinking "We spent way too much complexity on that part, and we can entirely do away with that other part, and we turned out never to use features X and Y."
Things like this really piss me off because it "poisons the pool". The "regular" person doesn't know the difference and I don't expect them too but they do remember such things and in the future it leads to issues.
Munis will almost always beat any other electric provider including rural coops because their customer per mile is a multiple of a rural operator. It ends up making the coops look terrible because we have to cut an order of magnitude more vegetation for the same amount of customers.
Please stop reinforcing the Red Hat ecosystem by using Red Hat derived distros.
Same. It’s too bad sonic expansion can’t happen faster. Wish they had detailed maps of which neighborhoods have it already.
> What did you do instead? It’s certainly frustrating to have people breaking docs that you fixed. But what else is there.

I concluded that it was a fatal and unfixable flaw in that community / product / company. This sapped my motivation, and I'm sure resulting burnout was a factor in eventually being laid off.

One thing that sucks about being a senior dev is you're subject to Cassandra [0] syndrome. In a tight labor market, that gets painful.

[0] https://en.wikipedia.org/wiki/Cassandra
Thanks! Even though I've been in software instead of chemistry for the last 8-or-so years, a structural diagram of a molecule still sings to me of bonds, torsion and symmetry :)
I'm a bit of a sucker for UNIX layout keyboards.

It's made it to the front page of Hacker News before, but I have a post about how I fell in love with the HHKB Lite back in the day (HHKB + arrow keys) [1]

After this I used a Sun layout Model-M Unicomp keyboard with classic IBM style buckling springs for a while. [2]

I used the aforementioned WhiteFox True Fox in the office, it's still there but we've been working from home since COVID started - I'll probably go collect it one day.

In the last couple years my hands started getting arthritic, and after trying a handful of ergonomic keyboards I finally settled on a Sun Type 7 [3]. The super soft rubber dome keys are the best I have used for my arthritis. They're soft, but not mushy. Really pleasant to type on. Not only that, but it looks cool but it's got the UNIX layout that I love.

I even managed to remap most of the extra left column in macOS to F13+ keys that the OS can recognize and I can use for keyboard shortcuts. I actually bought the thing from Oracle back in the day brand new. The RFQ/order process was a bit of a nightmare, they were set up to sell to major corporations, not to some dude who collects keyboards.

1. https://donatstudios.com/UNIX-Keyboards / https://news.ycombinator.com/item?id=21912184

2. https://www.pckeyboard.com/page/product/40PSA

3. https://i.imgur.com/PftSNnk.jpg
Definitely a feature. All the "lock" keys are bugs.
First draft? Final draft.

http://m.quickmeme.com/meme/3629ez
I rewrote a mission critical application. The original app was something else. One function had 1500+ lines of code. It was the ugliest thing I have seen in my life. We wrote cleaner code in early college years. However, that code ran the business for 12 years with almost 0 modifications. People created work around for some stuff. Error handling was poor. But the goal was achieved and business continued to grow.

I think devs in general sweat too much about code quality.
It's responsive but most people aren't so technically skilled.

I have a game that works fine with proton on one machine, but doesn't on another machine. But works fine with windows on both machines.

I tried for hours to get it to work on the other machine, since it clearly can. No luck.

In the end with proprietary software, it's always a black box.
Not defending macOS here, but switching between windows and managing them is usually performed via Exposé, (ctrl-uparrow)
Well, I'm practically some flavor of communist and would like to see all of society organized in a fundamentally different way :)

But that's not helpful, and I think it's not what you're asking. To answer your question pragmatically, no, of course I do not "expect authors or publishers to operate without a profit motive." I think art is very important, and under a capitalist society, I want artists and (to a lesser extent) publishers to get paid to they can buy food and have a nice place to live.

Public libraries themselves do not work on a profit model, though. Libraries buy books, but libraries themselves are not profit-driven. They do not sell a service, and instead receive money through other ways. Rather than understanding Overdrive/Libby as a product to be bought by libraries (analogous to physical books), I would rather see Overdrive/Libby/something-else to be understood as a service that is offered by the library (analagous to the librarian checking out books). The service would have to be owned by a different kind of entity, maybe some kind of non-profit that is beholden to libraries, or some kind of federal government entity. And the service would need a different funding model (one more similar to how libraries are funded, or one more similar to how inter-state or federal projects are funded).

Perhaps you disagree, that's fine, but I hope I've articulated my position reasonably well.
Did NeXTSTEP have any support for threads and their synchronization? POSIX introduced its thread model around the time Apple absorbed NeXT.
> In Verilog a simple "+" or "*" can turn into thousands of gates. Without understanding this your designs will be inefficient and slow.

Trying hard to avoid this because it is inefficient, is (imho) a typical case of premature optimization. Who cares whether you're wasting CPU cycles (in C) or FPGA logic (Verilog & co) when you're just learning what's what?

But there's a better reason: to make sure that whoever is learning Verilog (or other HDL) actually understands what they are trying to do.

With that understanding in place, the learning becomes "what logic construct(s) would be suitable" followed by "what Verilog to write that describes that logic".

Versus: "Verilog intro course has this example, does it compile? And does it appear to do what I think the Verilog says it should do?".

In programmer's parlance: semantics vs. syntax. The algorithm + how it maps to a CPU's resources, vs. red tape required to implement it.

If you 'feel' the syntax but underlying semantics is black magic, then you could keep stumbling in the dark forever. Spitting out copypasta along the way.

But if you understand basic concepts of the underlying hw (and how you intend to use that), learning syntax to describe that is straightforward.
> in vitro test

Means nothing for human treatment. It means something to the people working on the drug.
If you use the navigation, or use the Energy app on the car, then both of those will appropriately tell you your expected remaining range and the arrival state of charge. It does this quite well.

If you look at the state of charge % (and use the miles setting, instead of %), then sure. It'll be optimistic unless you drive the standard EPA route.

Honestly though, because battery drain is so dependent on route, elevation traveled, temperature, etc, I find the 'guess-o-meter' estimates to be mostly useless. You'll frequently find other vehicles that will start optimistic and degrade over time as well.
Throwing away an established code base is a completely different thing from throwing away a few-days-old prototype, and not what the article is suggesting. The points you mention don't apply to the prototype case.
> waiting for somebody else to type

> trying to verbally communicate something that would be better done in writing/code

> somebody looking over my shoulder

At the risk of sounding flippant, none of these activities comprise pair programming. What's better written should be, and the simplest way might be "can I just show you?" or, from a particularly well-atuned pair, "would you mind showing me?"

"Waiting for someone else to type," in my experience, is either a good opportunity to finish a bit of thinking that'd I'd put off moments prior, or else premeditate on our next move. Sometimes, however, the typing is, as you alluded to, an attempt to communicate something, in which case watching them type is roughly equivalent to listening to a person in conversation, and therefore an opportunity to learn, catch bugs, etc. In other words, when I am pair-programming I am never waiting qua idling.

And, lastly, I completely agree that "somebody looking over my shoulder" is an unnerving condition to code under. As purely ergonomic concern, "over one's shoulder" is not a healthy position from which to operate a computer. ;)

But, seriously, it's not pair programming if you're not on equal footing (seating?), with equal access to mouse, keyboard, and monitor. Don't stand for someone standing behind you!

I am sorry for the unpleasant experiences you've had. As a practitioner, I would not have subjected you to them. I am, frankly, vicariously irritated with whomever did.
Given the importance of this medication and it's promising initial data I have no idea why it's not given "warp speed" clearance. We cleared mRNA technology almost overnight in response to the pandemic. I feel like society as a whole has collective amnesia on how this happened. A relatively novel strategy to rapidly produce a vaccine in response to a pandemic was trialed essentially on a global scale. The phase 1/2/3 trials may as well have not existed.

It seems strange to me that we can't give such an important novel drug the same treatment. The population size is smaller than global and the effect would be huge. I would seriously doubt anyone stricken with cancer would hesitate to agree to the same "experimental treatment" paperwork we all got when we were vaccinated.
Here you go:
https://en.wikipedia.org/wiki/Bia%C5%82owie%C5%BCa_Forest
Can you explain to a layman why works to kill tumors and not healthy cells?
How about we use a different analogy. Google, Facebook, Amazon, Microsoft - they all have patches to the linux kernel which they do not always open source. And nothing in the GPL compels them to open source them so long as they aren't distributed outside the company, and are only used on internal systems.

Let's say an employee with access to those internal kernels, who is under an employment contract and non-disclosure agreement, releases the kernel source code with those patches included. Would the GPL prevent that employee from being fired and/or sued for violation of NDA?

Nope.

>GPL says that you can't impose further restrictions on the people you distribute GPL software to.

That's just the thing. Red Hat does not impose any further restrictions on the software that has been distributed to you. You can continue using RHEL, in theory, even with an expired license. There is no "kill switch".

But Red Hat is not obligated to continue providing you with access to their services, including their software update repositories.
When you launch a cloud RHEL VM you don't really have a contract with Red Hat; you have to "agree" to their EULA or whatever, but I don't know if there is any way for AWS to cut off a customer from accessing RHEL. In theory Red Hat could ask AWS to kill your whole AWS account, but would AWS do that?
Anecdote: I know a guy who works solo and throws every project away (usually games) at least five times, often more like ten.

According to him, each iteration tends to go smoother and faster than the last.

Edit:

There’s probably some nuance to whether this approach is a good idea based on type of software, size of team, experience level, personal and/or team skill set, etc…
Could they not change their contract/license and forbid "exporting" or something?

IBM is big enough to make an example out of a few unlucky individuals, and compel everyone else to play their way.
It is the one unambiguous strength of an LLM, I think.

It's kind of core to its being. It's very difficult indeed to get ChatGPT to write ungrammatical english even deliberately. I've tried several times.
I've thrown away and redone a lot of code, both mine and others', and I've never regretted the time spent vs continuing to use the old thing.
Sodium on Steroids: A Nuclear Physics Breakthrough Thought to Be Impossible
I have a bunch of IoT stuff that hit my Pi-hole with the same DNS query a lot, like every second in some cases. Definitely plenty of badly designed consumer devices out there doing horrible things with phoning home.
Role mentions security. Candidate shows no experience with security.

It would've been weird... but then you remember it's Python. It's by amateurs for amateurs. Well, god speed and god bless. Who knows, maybe despite the counter-indications something good will come out of it.
The logic of science is logic. Statistics is used to provide confidence intervals.
I with AudioCraft were that good but unfortunately it isn’t.
This advice depends a lot on how your "first draft" was coded to begin with. The concept of "first draft" shouldn't exist as code. You design it properly, then you implement it properly.

Now, if for some reason, and there are plenty of good ones, you cannot do the former, then sure, you pay that price by redoing some work. But, at that point, you do the same thing you should have done: you design it properly, then you implement your design.

One could argue that implementing a first draft is a way of designing it. Which, I cannot imagine making sense unless you don't know what it is you want to end up with. Maybe if you're making computer games or other creative endeavors?
No, but the entire Android ecosystem will collapse if it's challenged, so...
> leading to the usual "let's set up a call [to actually discuss everything in the e-mail thread]"

You forgot the part where the call is scheduled for next week even though today is Wednesday. And any attempt to discuss further in text is met with "let's leave that for the call".
I've been following this flow where I write a few successive versions and perform refactoring steps to move one version "towards" another version, as if there is a conceptual force of attraction. It's often unclear which version will prevail, as if I'm acting out a genetic algorithm with a small population.
I graduated from school in Spring 2020 and started working in Aug 2020. In that timeframe, I had not been inside an employers office more than 3 times. Since Mar 2023, we've had a "mandatory" 4 days in office every week. Here's what I've experienced since going the office:

* Occasionally I'll get a good conversation with a teammate or manager about something technical, but the frequency has not gone up. The technical conversations are still scheduled on a calendar and happen at the same frequency. I really haven't experienced many people stopping at my desk and I think I've only stopped at the junior engineers desk to check in.

* Socializing at work has not been my strong suit. I am pretty introverted when it comes to strangers (e.g. anyone who has not been introduced to me). I find the socializing to be more energy draining.

* I walk to work. I like that typically. The walk can be... disturbing to say the least since I walk through downtown Seattle.

* A lot of people in the office prefer to speak to each other in languages other than english. Everyone on my team (my manager + all my coworkers on my team) prefer speaking something other than english and do so unless I'm involved in the conversation. This surprised me and at times I find it frustrating because I wish I could know what they're chatting about when it's technical (certain keywords I can pickup on since they're the name of internal things).

* working in office 4 days a week has given me something to really look forward to each week, and that's the WFH day.

* I don't think my productivity has gone up. Some days it's definitely worse. Now there's an obligation to go sit and eat with others for 30min-1hr a day. Previously, I'd just bring my lunch to my desk and continue to work.

I don't think my experience is the norm. But I certainly miss the pure WFH days.
My intention was to object to the parent post replying with "No" to something that wasn't a question or a falsehood. I find it annoying and inflammatory and not conducive to good discussion. Since brevity is wit, I thought that would be a good way to get my point across without having to write an explanation like this one.
It seems to be getting more popular here to link to a twitter blurb, which links to the actual article. In this case, the blurb adds zero to the discussion, if anything adding blatant misinformation.

This is the actual article:

https://www.cell.com/cell-chemical-biology/pdfExtended/S2451...

I recommend replacing the link and the title with what appears on the Cell website.
> Why is it that every OSS desktop has to look like a demo from the 70’s?

You need some unixporn[0] in your life.

Also people have different tastes and preferences and like the NeXTStep or Win95 or OS/2 or BeOS or Classic Mac or whatever look.

[0] https://www.reddit.com/r/unixporn/
Good god, no. Or, at least, let us never make this a sort of standard way of developing that you're going to push on to your engineers.

Containers have their place, they can be great, but I've tried the whole "containerize everything" approach, and it's no less time consuming than not containers, and now you have another Thing You Have To Learn (TM).

This isn't to say that virtualization is a bad thing for a development environment. It can be a very good thing, actually, but you don't need containers. A development environment, in my opinion, should be well organized, easy for a new developer to pick up, but also scrappy and adaptable to new and interesting situations. Containers, at least in their current conception, are antithetical to this. They're best kept to deployments or running things in a scenario where you know for sure you're not going to tinker with anything. I don't think I've worked on a software project where, at some point or another, I didn't need to reach under the hood in some unconventional way to investigate an issue or simulate some circumstance. Yes, you can do those things with containers, but now you have to deal with that complexity, which can get in the way by merely being confusing and indirect.

Having given up on using containers for development, when I want to use virtualization, I just spin up minimalist instances of Debian under Qemu (using the UTM GUI). This way, I can run a Thing (TM) in isolation, easily open up a shell, or SSH into it from the host shell, or start a GUI from within it if I need to, or install however many services I want within it and open up ports to the host, or have shared folders, etc. etc. etc.

But what if I need multiple of a Thing (TM) running at the same time? In that case, I just clone the VM. No Dockerfiles, no docker-compose.yml, no "volumes", no orchestration, no images failing to build because reasons, no qcow2 files blowing up with Docker For Mac (though that situation has improved), no pruning of orphaned containers/images, no worrying about whether your container should only be running a single process/service, and so on.

The only drawback to this is that, if the host is Linux, then it's indeed kinda dumb to be running other Linux kernels in VMs. But hey, it's 2023 and the difference in performance may not be meaningful depending on what you're doing. I know that, on an M1 Mac, I can run graphical applications at monitor resolution with incredible speed (perhaps moreso with Parallels instead of Qemu), so I'd struggle to care about any performance drawback if my host was Linux on the same hardware.

I'm sure that, for some, containers in development will be totally worthwhile. But if they don't seem worthwhile to you, dear reader, then that's probably because they wouldn't be.
I personally still use old.reddit, but no longer browse reddit on mobile, which was by far the largest usage of my screen time.
So to receive a product where the GPL dictates you have full right to redistribute that product, you must first enter into a (sub?)contract that says you cannot redistribute it…

If that’s not one hell of an ingenious loophole, I don’t know what is..
I think this depends greatly on the product area and ease of updating. Removing problems categorically from designs early has been valuable to me in the past to reduce surface area, avoid impossible refactoring, and eliminate systemic bug classes.
Precision Medicine and Its Imprecise History (2020)
Yet another reason to have dogs on your bed at night.

The don't specify the actual scents? Just that there was a selection of seven.
Isn't that cherry-picking? That was the peak of the oil crisis
I agree completely. Path dependency is such a huge component of how the world is built and many people are oblivious to its effects.

Even the freeest "two-way door" decision becomes one-way over time because every day is a step farther away from that door, and another step you have to backtrack in order to go back through it.
Very few people own a Bahncard 100. It's only useful if you need it for your job/business, otherwise it probably won't pay for itself. Most people prefer the car or plane (if you frequent between big cities) anyway
well, maybe you are right and it's not as clear cut. But I think people very intentionally buy a PC or a Mac which to most means the hardware and the operating system together. And, not to put too fine a point on it, but NOBODY here is counting mac user as BSD users either.
It really comes down to finding the right balance and using your tools effectively. I worked at a place at was super OO heavy, multi-layer inheritance, gang-of-4 type OO patterns. And another place that was writing code in a functional manner, little to no classes unless necessary, using FP patterns in the codebase.

Both were codebases were TypeScript. I think I was more effective in the second, FP, codebase than the first. But really it's more about finding the right balance. One of the flaws in either approach is you try to fit a paradigm forcefully: trying to write Java in JS/TS or trying to write Haskell in JS/TS. The TS code will be better if you understand and accept the JS/TS paradigm and apply patterns where they fit elegantly.
In Australia, the ATO knows everything. Employment income for a start, but also bank account interest, dividends, health insurance payments, and a lot more. For the average person, the pre-fill is all you need and you can just submit the return as-is.

Not sure why the US isn’t able to do that. All employers and banks have your SSN, right? Sharing data with the IRS at the end of the tax year isn’t rocket science.
It's like saying you have freedom of (let's say speech) but not freedom of consequences, so the government will still discriminate against you.

It shouldn't hold up on court and hopefully it won't.