skysight-inc/HackerNews huggingface dataset:
Base-4 (in the form of PAM-4) is already used for high speed data transmission. But IMO given how "analog" digital signals become at high speed, using anything but binary for compute logic seems like a fruitless battle.

https://blog.samtec.com/post/understanding-nrz-and-pam4-sign...
Any examples anywhere?

Being prompted to log in/sign up is a show-stopper.
I work for a competitor to Boeing as a senior integration and test engineer as one of several final approvers of flight assemblies before they leave for final integration and packaging prior to flight and I can’t tighten a bolt without scanning the QR code on the handle of the wrench to log its use or reposition a benchtop power supply four inches to the left to make more space without requesting a variance.

If a board makes it from SMT to testing, or from testing to integration, or from anywhere to anywhere else with even a fingerprint on it a nonconformance is logged and it gets kicked back.

That’s like 9100D 101.

The thought of stamping or initialing something I am unsure of is a literal impossibility and the report says it is happening all of the god damned time at Boeing.

I cannot for the life of me understand what’s going on over there.
However, in the case where someone means "This interested me so much that I stopped what I was doing and looked up more information," peaked is almost more correct, depending on how one defines "interest" in this context (eg. "capacity for interest"? probably no; "current attention"? probably yes).
People's moral values change with the seasons
> Consider that the software you're using, buggy and kludgy as it is, isn't the reason your business is making (or failing to make) profits.

You seem to be making that assertion with 0 evidence. I've seen plenty of businesses fall behind because their tech is old and becomes an anchor, and I've seen businesses whose primary competitive advantage is their tech.
I have worked freelance in similar situations.

Personally, I find it really fun. It's a nice mix of development, design, and organizational understanding.

What I want to do is divide up the project. Usually, these legacy systems don't have clear division points; it's all a big bundle of interdependence. But in my experience, there's usually some less impactful secondary functionality that can be spun off.

That will allow you a few things:

Figure out what you quantify as success for such a project. Its limited scope makes it easier to identify the endpoint.
Allow learnings about the legacy system, and perhaps identify what elements you can extract from it—not necessarily code, but in previous work, I've been able to wrap or scrape data in certain areas to provide a sort of external output.
Figure out how to work with devs, manage your own time, and educate your organization about what you're trying to do.
The third and last point is critical. The failure modes for development are obvious, but the political and design impacts are less so:

1. Lack of experience

2. Poor scope

3. Overly complicated solution

etc.

But the real failure mode is political. You need a developer with some political acumen as well. There's going to be a lot—and I mean a lot—of interviewing people about how exactly subsystem X fits into their workflow. You need the political skill to navigate that, in terms of getting buy-in and quality information.

Downstream of the political dimension, in my experience, is the possible design solution. The actual interviews with people and the regular, constant contact with staff about their job are critical to building something that replaces the existing system but doesn't replicate its design failures.

One mistake you want to avoid is building something too similar to the old solution and missing out on critical information about how the job is actually done.

Also, I'm not currently looking for work—enjoying my current role—but if you want to hit me up, feel free. I can at least impart some experience on what to do.
There's a fantastic associated YouTube video that talks through these too: https://www.youtube.com/watch?v=JcJSW7Rprio

It's a rabbit hole that had be fascinated for quite a while.
This is like saying not being poor is as simple as earn more and spend less. It's simple as. It's not that people can't do this, it's that they don't want to. Hopefully you can see how absurd this framing is.
Why does a password manager needs to be online. I understand the need for synchronization, but being exclusively online is a very bad decision. And git synchronization is basically ssh, and if you mess that up on a regular basis, you have no job being in business in the first place. These are examples, but there's a few things that do not need to be online unless your computer is a thin client or you don't trust it at all.
Good summary of Google's monopoly on the Internet today:

> Now, the world's largest websites are owned by the same company, which also owns the world's most popular browser and search engine. Coincidentally, they are also the world's largest advertising company. And people are wondering why they can't block ads on YouTube anymore.

For some people, Google is their ISP (Google Fiber), mobile internet provider (Google Fi), DNS provider, email provider (GMail), search engine (Google Search), web browser provider (Google Chrome), and entertainment and news provider (YouTube). Google tracks their online activity with Google Analytics and shows them ads with Google Ads. Google provides their phone (Pixel) and their phone's OS (Android) and backs up their files (Google Drive) and photos (Google Photos). When they go to work, perhaps they use Google Docs and Google Meet.

Some products are more popular than others, some are genuinely better than anything else, but still... for millions of people, Google practically _is_ the Internet.
Read my post again.

Just because k8s is the only game in town doesn't mean it is technically any good.

As a technology it is a total shitshow.

Luckily, the problem it solves ("orchestrating" slow webapp containers) is not a problem most professionals care about.

Feature creep of k8s into domains it is utterly unsuitable for because devops wants a pay raise is a different issue.
Why would an article lump a gas burning hybrid in the same category as EV? They seem diametrically opposed.
But notice that you cherry-picked accomplishments that sound impressive. You didn't say "I watched 10 seasons of The Office", "I wasted over 8000 hours on HN", or "I impulse-bought a shed full of tools I never use", it happened organically!
Maybe look at it this way: they're going after people because of what they're posting, not their age or gender.

also 55 isn't old! but I realise I may be closer to it than you are.
Yes it’s primarily variations of your first one. At the owner level it has some flavor of the final one you list though.

I’d encourage you to have a conversation with Theil or Larry at some point and really hear in person how detached to the point of ‘evil’ they can get — and wrapped up in reshaping society for their own egotistical reasons.
The bar is low, but somehow mac is even worse than windows. I had this screen to set new password. The tooltips that detailed the password requirements were shown off the edge of the screen, unable to read them. White text on white background. No default windows (heh) management. You have to enable right click in settings (what?!!). Their own silly mouse can not stay connected on bt to their own laptop. A cheap mouse worked better. And on and on...
"they can easily laugh at some particularity of your face and that would be very hurtful. "

Forgive me, I'm not saying such insults aren't hurtful, but if that's the worst they have to throw at you, then believe it or not, you're getting off relatively lightly.

How about undermining your memories of your not-long-dead parents, based on things you've told them about your childhood? Doing their level best (and they are VERY persuasive, and persistent) to convince you that you were never loved by your mother, extrapolating from stories you have told them, to construct an alternative history that paints your parents (and particularly your mother) as an uncaring, sexually profligate monster.

I have many other examples - but it's Friday evening, and I don't want to put either of us in a low mood. :-) So I'll just wish that no-one who reads this ever runs into someone like that, and wish you the very best of luck!

Cheers
Crypto is a scam. Always has been, always will be. No amount of technical jargon will ever make it useful.
> It’s very hard to say. I’m aged in gamer years, and over the last few decades I’ve seen the average age of gamer climb much higher than I expected.

I remember being in the car and talking to my sister about Teenage Mutant Ninja Turtles. My dad's face crinkled up in a mixture of confusion and disgust. "Teenage... Mutant... Ninja... Turtles? Teenage... Mutant... Ninja... Turtles?"

These days I see dads the age he was then, walking with their kids, and they're both rocking TMNT T-shirts. The same with Zelda or other franchises I love. I'm convinced that people my age and younger are sort of living an extended childhood. I don't know whether I should feel bad about this... but I don't.
It's not about monads as an abstract concept. It's specifically about the State monad.

The key idea is that you can have something ressembling states with pure functions if you pass the a representation of the initial state as an argument and have the modified state be part of what the function return. You can then use this modified state as an argument for the next function call. The State monad is just an handy way to do this chaining.

But, yes, the actual state representation is in the way the argument is encoded, that's true.

Edit: I find it hilarious that I’m the one downvoted here while all the comments saying complete non sense about monads - including the ones clearly having no clue of what a monad actually is - are not. Never change HN.
Harming end users is often a commercial interest.
I think the “developer friendly” critique is a fair one for Ory, especially Ory Keto, which I found to be an absolute nightmare to use. But as a dev I found SuperTokens really easy/nice to use.

Open core vs. full open source, fair.
And whats the problem with that? Our entire world is built upon conveniences. We don't grow or hunt our own food, or travel cross country with our own two feet, or countless other things.

Its not that I can't do those things. I don't want to. I rather spend my time, physical and mental energy on the things that are more important to me. Does that make me lazy?
Python was a curiosity/tiny niche for over a decade from the earliest 0.9 releases I used. I was advocating it to thoroughly deaf ears in the mid-90s with rejoinders of "just use Common Lisp".

Then several things happened. 1) Large businesses like Google openly saying they used Python in the early 2000s helped for things like web / Internet work. 2) Linux distros like Gentoo leaned on it heavily helped push it in systems/sysadmin. 3) the "Numeric -> NumPy/SciPy" transition helped a ton - spurred by things like `f2py` and exorbitant licensing costs of Matlab, the main competitor, which also had a lot of 1970s/early 80s language problems like 1-function per file and scoping craziness and not doing reference semantics for big matrices and junk like that. Then 4) the culture of open source in scientific software helped build out that aspect of the ecosystem as the other, 1/2/3 were growing fast. Then 5 by the late noughties/early teens universities were switching to it as a teaching language and finally 6 ML/data science as a specific area of the NumPy/SciPy world started taking off in hype cycles and even real applied work.

This is just a long-winded (but still woefully incomplete) / historical way of saying "software has network effects" (not just PLs, but OSes and applications as well), of course. As Jack Reacher likes to say "details matter in an investigation". ;-) I don't think Python was purely lucky, exactly, but with one or two those big reinforcement/feedback factors missing, it might not have become so dominant.
It’s because they are considered “big digital projects”. Any significant it change necessarily involves an even larger organizational change. Ignore that, and fail.
I’ve led the software development at a design agency to build project and client collaboration tools in a web app over the last seven years. The company founders never set out to intentionally run a design agency with custom built software in house and from the outside looking in, building “project management” from scratch would sound like a terrible idea. Yet we’ve been profitable in every year and grown +30% more than half those years and were acquired last year with decent equity payouts. The acquiring company (300m+ rev / year) is now expanding the engineering team to build SW for their adjacent market.

Myself, my boss (former CEO) and current CEO strongly believe in the power and potential of in house engineering, in particular for spaces that “sound on paper” like solved problems. The efficiency and productivity gains from building exactly what you need is hard to quantify but has been proven in our business as indispensable and, we believe, a significant competitive advantage.

Of course, as others have mentioned, you need the right person to make this happen in your business. I would look for someone with proven startup and product development experience that you could ultimately see managing a small team. None of this is cheap but the ROI long term is likely justified given the issues you’ve outlined.
I think that another aspect of this verbal difference is that quests are meaningful because they inherently possess some level of difficulty and adventure. Taking on a quest means that you have a mindset with room for stumbling and getting back up and that you will eventually overcome. Focussing on a goal may sooner lead to frustration and giving up.
Is there are correct way around?

St -> (a, St)

vs

St -> (St, a)

I've found both in the wild and it can be very confusing!
DALnet FreeBSD Security How to (2002)
Great advice, perhaps I can share some personal experience.

I had a similar experience working with a large agricultural company, where we developed a track-and-trace system to manage their entire workflow. This system provided them with insights into all aspects of their processes. They gained full insight into their margins, mass-balance and quality control, from field to fork.

Our agreement included the agreement that we would own the system, with the option to eventually resell the system in the market, ensuring we could establish a company to support the system after development was completed. As you don't want to loose the knowledge after the system is finished and don't want to have a complete team of developers on your payroll.

We only developed the components that were crucial to the business process, relying on existing software packages, such as the accounting system, and ensured seamless integration between them.

One approach that worked really well for us was working on-site and providing support to the people using the system. This was invaluable in resolving issues that users were experiencing, and it also kept us focused on delivering quality—otherwise, we would be the ones responsible for providing support.

Please note that if you begin development, don’t expect the first version to be the final one. This was a major pitfall for us. The first version was good but not future-proof. Only after developing the second version, essentially a complete redesign and redeveloped from scratch, did we achieve the best solution for the business.

Ensure you maintain an open dialogue with the development team and allow for quick iterations. For us, a significant challenge was aligning expectations. Budgets were tight, and expectations were high, which created a high-pressure environment, that worked great for us and helped us focus. However sometimes this led to a lack of appreciation for our work, as expectations where not met. Keep in mind that developers think differently from business owners. We addressed this by having a technically proficient, data-savvy production manager in the company who understood most of our challenges and helped realign expectations.

Unfortunately for us, the company we built this system with didn’t respect our contract, preventing us from distributing the system and killing future opportunities. This resulted in legal action, which didn’t end well for us, as the company was much larger. We were naive in thinking we could make it work, assuming it would be in the best interest of both parties, but they didn't share the same intention.
That's a meme-worthy mini-rant in Spider-Man: Across The Spider Verse https://youtu.be/0jTN9YqyXOU?si=JjvNEy0cgj81ksRp&t=71

On a more serious bit - the word origin of each is interesting. The word used depended on how it got to its destination - by land or by sea.

https://qz.com/1176962/map-how-the-word-tea-spread-over-land...

If it was shipped over land across the Silk Road, its name stems from 'cha' (茶). However, if it was shipped from the coast, the dialect spoken there pronounced 茶 as 'te'.
Milwaukee's 50-Storey Timber Skyscraper to Smash Records
I preferred Charles Duigg's book the Power of Habit for similar reasons. All the material in Atomic Habits with more meat.
Reading Tim's posts gives me the exact opposite impression. As far as I can tell, his "defense of "reverse racism"" was simply:

> Can’t say I’ve paid it much attention in recent years. Last time I did, “all races can be prejudiced, but only whites can be racist” was the Correct View™. [...]

> While it still largely makes good sense to me, I don’t want to see the PSF insisting that any other view can only be held in “bad faith”. Other views are common too. Among people of my age, very common. I can attest from personal experience that some people near my age never even heard of the view the PSF endorses. [0]

So, to my understanding, PSF's stance is that only white people can be racist. Tim's supposed offence wasn't even disagreeing with that, but saying that people who don't share that stance aren't acting in bad faith.

The slur alluded to was when discussing removal of a PyPI package named "slut". Instead of using the word directly, Tim said:

> It was about kicking a package off of PyPI, because its docs repeatedly used a word that Dan Akroyd used to apply to Jane Curtin (brilliant comic actors from America’s “Saturday Night Live” TV show, but back in the days when it was genuinely funny). [1]

It all seems exceptionally mild to me. I'm not sure if this is an escalation of purity standards, or those in power wanted him gone for other reasons (like the mentioned questioning of PSF decisions) so twisted anything they could find to match CoC terms.

[0]: https://discuss.python.org/t/im-leaving-too/58408/10

[1]: https://discuss.python.org/t/for-your-consideration-proposed...
> I'd be willing to bet that the Japanese would have been willing to pull out of Manchuria

Given the success of Soviet's new combined arm doctrine (later called “deep battle”), I don't think “pull out of Manchuria” would have been a possibility, as the Japanese force there would very likely have collapsed to a point where getting back to Japan would have been impossible (think Dunkirk but with much more land to leave behind you and with an enemy moving even faster and where you don't have neither air or sea superiority).
The Days are Long but the Years are Short. OSM at 20 years
Since not all of them fail, one should maybe look at those who don't and try to understand why.

The article mentions corruption (in softer words) and lack of expertise on the government side. But there is little talk about the quality of suppliers.
I think of it as scaling a mountain. When you're at the base the mountain looks imposing and out of reach. As you begin the climb it's hard work and you don't know your way around and feel lost, and every time you look up the mountain remains as imposing as before. But then you begin to make progress, and the mountain begins to seem smaller. Now you can finish the climb because it doesn't seem like that much more work -- you've done the truly hard part, which was: getting started.

Admittedly when I'm at the base I take my time getting started. But once I'm started, I can power through.
I brokered some portion of the omnibus agreements between the big 4.

The many parts of the agreements were clearly net negative outcomes for markets and users. Basic forms of collusion and cartel making were common.
A droplet-sensing bionic e-skin that could further enhance robotic perception
1st to anything is considered a significant metric, it's simply picking the larger tasks and working your way down to possibility to find effective goals.
> Sure, you can check if it's mathematically coherent, but that tells you nothing about whether it describes the physical world correctly.

This is a very good point I think a lot of people miss. (Including some who should know better.) Pontificating about speculative physics is all right for Aristotle but you need actual experiments to ground your results.
A/B testing is not for startups
Curious to hear people's reactions to this take on whether A/B testing is appropriate for startups and the concerns of false positive signals. A/B testing (or not!) has been a hot topic in the past at startups I've worked at, both in the early stage and even post-PMF.
Second aichat. Super good. For Linux I created a little bash script that downloads the latest binary and unzips it into /home/me/bin
They have billions to lose if they comply the way other devs want them to. They like money.
The issue with drain/pump solution is that at that point you're doing hydrological engineering.

There isn't a "perimeter" per se, because water is literally coming from depth (in most locals / soil types).

So drain/pump just creates drier 3d soil areas. Whether that's enough to attract all the surrounding water (at a high enough rate) that would otherwise be infiltrating depends on soil permeability (e.g. sandy or clay?).

A lot of the "handyman"-type "dry basement" shops have no idea about any of this, toss a generic solution in there, and then blame the gods if it doesn't work (and they've billed for time-consuming and expensive excavation).
Sure, but the Telcos seem perfectly fine with taking the monies from the scammers until they are forced to do something.

I mean, it's validly been 25 years since I received my first scam text and I still sporadically get them once in a while.
Let's say, hypothetically, we do enough RLHF that a model can imitate humans at the highest level. Like, the level of professional researchers on average. Then we do more RLHF.

Maybe, by chance, the model produces an output that is a little better than its average; that is, better than professional researchers. This will be ranked favorably in RLHF.

Repeat this process and the model slowly but surely surpasses the best humans.

Is such a scenario possible in practice?
Yes. They are still there, and like milk bars, still have an anachronistic name: newsagents.
https://en.m.wikipedia.org/wiki/Newsagent%27s_shop
In fairness, they aren't making that assertion, they are asking for OP to consider and pressure test that assertion
Are you using SES for actual sending?
Did you build an api or a server with an api?
For some weird reason, I know exactly where I was when Jobs died. (Driving upper market street in SF on a sunny morning)

But Ill never for get what he was claimed to have said as his last words: "Oh.. wow"
If corporations are people, can't we execute the serial murderers ?

Human grief in, human relief out.
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4383600/ ("Pharmacology of manipulating lean body mass")

https://newatlas.com/medical/drug-mimics-exercise-weight-los... ("Drug that mimics exercise triggers weight loss and builds lean muscle")

https://en.wikipedia.org/wiki/Exercise_mimetic
Once you understand the fundamentals, knowing about the newer stuff would be a good step forwards:

https://github.com/tc39/proposals/blob/main/finished-proposa...