skysight-inc/HackerNews huggingface dataset:
This project is co-led by Ben Goldacre, who the HN crowd may know as the author of Bad Science and Bad Pharma:

https://en.wikipedia.org/wiki/Bad_Science_(Goldacre_book)

https://en.wikipedia.org/wiki/Bad_Pharma
It looks like math blog posts. They are written for other mathematicians but not experts in the fields, and a layman will find them unreadable.
BTW, others I tried where iOS 9 cannot complete account setup:

* Yahoo

* Gmail

* An IMAP account from 1991
The concept of refactor does not apply in context of publicly exposed interfaces—i.e., you logically never “refactor” a public API, you release a new version of it. As such, it would have different inputs and outputs and therefore its own separate tests.

This becomes more difficult to reason about when what you build is not just a library but something more like a web service or a GUI/CLI app. For a library, a unit test may be able to cover public API and be an end-to-end test in effect, whereas for a more complex product intended to exist over time in production unit tests do in fact provide less of a guarantee, and versioning public API becomes difficult (unless you immediately drop support for any non-current API version).
Shame, MRSK was a good name.
> One long for high ground three short for… huh, that’s new. What do? Oh it says here,

you just added a dependency for something that only had one meaning.
Amazing work and contribution. Thank you.

Maybe the author could consider another article or script that really simplifies the permaweb hosting stuff.

Also, what's the situation with current browsers and immersive portals or transitions between websites without exiting VR?
It's really easy to do. Particularly the getting them made bit. I just did a quote for a 2 layer board that's TKL keyboard sized and to get 5 made it's about £20 delivered to my door from JLCPCB.
Ok, but diodes are more expensive than resistors, and from what I can gather you also need more components in total.
The Plan for Helios NG – A FOSS Cluster-Native OS Derived from Tripos
> What you written about lack of scalability of emoji for me is their advantege over gifs.

What I mean by lack of scalability is that there is insatiable demand for new emoji but only finite Unicode code space for them.

This is has even become a social/political problem, because everyone insists on equal "representation" in emoji in terms of skin color, gender, etc. We couldn't just stop at Simpsons-style yellow faces.
Comparison of Dataframes.jl with Python, R, Stata
Haven’t managed to get a Genoa server in the US yet. Wonder what are the odds…
> How long am I supposed to bring my mind back for?

One point of view is that once your mind no longer wanders, you no longer need concentration meditation. The whole purpose of the exercise is for you to learn to bring your mind back.

Don't worry about your mind wandering, it's normal. When you notice, bring it back. There is no disconnect, you're doing fine.
I opened a couple of issues and did some minor contributions in the past and at every point problame has been approachable and a pleasure to interact with.

From a user perspective, I'm still feeling a lack of UX in restoration/clone-management from the snapshots synced by zrepl - things can easily get messy if you don't know exactly what you're doing and keep track of things properly. That might be out of scope for zrepl itself, though.

Some more proactive/pre-emptive pruning would also be great - falling behind on syncing can be downright painful if you don't pay attention... Which is just to say, don't skip setting up some basic monitoring with alerts for production loads (:

Either way, all things considered zrepl is the nicest zfs replication option I found so far.
But green isn't the equivalent to goofy conic sans, it's just a color. People in Europe use WhatsApp and it's green.

The problem is that money based status competition is so rampant in America and this is merely an effect of it.
Sigh. Releasing more often is not an ideal situation. Yes, being able to release every single change on its own, fully tested, is a nice to have tool. But the real world works in office days, weeks, and quarters. And whatever amount of work you put into your test suite and automation, sometimes you cannot test some things. Sometimes you have to wait for a real day (or God forbid a real quarter) to pass.

Yes, testing, especially unit and integration tests, are a sine-qua-non for quality work. But so are automatic proofs of absence of certain errors (vulgo type checks) and non-functional tests.

But all this has been at least partially resolved. What we are still sorely lacking is simulation. Everyone who ever worked with a staging environment knows how limited this usually is. What I would like to work with before I retire is a tool that lets me standup a complete copy of the production environment, isolated from the real world of course, with all external services automatically mocked. Now that would help to improve the quality.
We don't, but it is the easiest way to ensure the package manager is adapted to the language and the library ecosystem. It is also easier to add features, remove misfeatures, and fix bugs when the package manager only has to handle a single language.

Once we understand package management better -- we don't understand it well yet -- it will likely be feasible to consolidate many package managers into a few omnimanagers.
Reminds me of a short story about an AI that is conscious without anyone knowing:
Cat pictures please
By Naomi Kritzer

https://clarkesworldmagazine.com/kritzer_01_15/
Lost me at the end, but, don't inner-tubes have 2 holes (genus 2), topologically: one for inflation and one for the wheel to fit in. This makes them distinct from a torus (genus 1) and no homotopy exists between them.

Clearly IANAM.
This POV is debateable (but I sympathize strongly with your sentiment). If quick but shitty allows me to capture a lot of value then quick and shitty might be the way to go. Yes there are major downsides but especially in a "scaleup" setting they are often dwarfed by the upsides of shitty but fast. As an engineer, I hate it because I want to build perfect and long term all the time but in many cases you can't really argue with the monetary benefits of knowingly delivering underwhelming things that get the job done well enough for now (even knoing deep in your heart that many of the issues might never be fixed).

A good example is security. Sometimes it's righ to ship stuff with security issues that you know exist and might even be 10+ million dollar issues if discovered quickly if for example fixing thoses issues might interfere with adoption because they make user onboarding slightly more annoying.
Blink Code
Soldering 1N4148 so close to the glass body, plus using a thick drop of solder, makes it really easy to overheat the diode. They are everywhere because they are cheap, not because they are robust... The diodes may become unconditionally conductive, so it may not be an obvious bug.

I fried many of them, because my soldering skills were not that good, I did not read the data sheet and so my iron was too hot and I soldered them for too long. Plus by using short wires, all the heat transferred into that fragile glass body.
Types are wonderful, and a good type system makes so many errors disappear / impossible, that I'd otherwise have to write tests to cover in a dynamic language.

Types however, are not a substitute for unit tests. No type system is going to tell me if my income tax calculator covers all the edge cases.
If only there was something like the mirror test for a disembodied mind...

https://en.m.wikipedia.org/wiki/Mirror_test
I had the same question. I feel like they should clarify this. But also I don't see how they would want to apply that restriction in this case, since using their models to generate training data will make them more money and makes fine-tuning vastly more manageable.
I've been taught in many cases you can indeed fine-tune the last (i.e. closest from the output) layer(s) of a network. Of course, it does not give as good results as fine-tuning the whole model, but it is obviously way less expensive in compute.

i.e. you actually don't want your model to re-learn _everything_.
Production Ergonomics: Work Systems for Optimal Human Performance
YOU seem crazy.
For the file not found errors, I recommend the fs-err crate. If you ask for async support, you should use spawn_blocking anyway as that's what tokio::fs does too
The thesis of the article seems to be that "the world has changed" so that Wirecutter and similarly rigorous product review sites are less appealing than they used to be but... I don't see it? Products now are mostly "good enough" so that careful research is not necessary, and ten years ago that wasn't true? People now are interested in personal recommendations via social media and YouTube, and ten years ago that didn't happen? People now impulse buy, and ten years ago they didn't? There are so many reviews now that it's a commodity, as if ten years ago that wasn't exactly the problem that Wirecutter hoped to solve by promising to be the only product recommendation you'd need to read?

I think Wirecutter has always been a somewhat niche offering that appeals to a slightly neurotic, slightly nerdy audience that doesn't want to be fooled by marketing – like most of us here on HN, I guess. If they can keep up the quality of the reviews, I think they'll be around for a long time.
a huge part of it I will say is antithesis to current state of programming. Emacs is literally a live elisp interpreter with everything in global scope. You literally replace parts of the application in runtime.
Its nonsense and totally unnecessary and wasteful for every country to try this.
He's not promoting that removing dedicated testers is a good idea. Full(er) quote:

> Several strategies are getting deployed — shift left (e.g., more unit tests), shift right (e.g., test in production), transitioning from manual to automated testing and even removing distinct tester roles and trying to hold developers accountable for the quality of the code they are writing.
>
> These testing strategies are met with varying degrees of success and can even differ from team to team based on skill level, maturity, and culture.

By all means, have developers write their own unit tests. To show their intent, document use cases, etc. And do not leave that to a junior colleague or a brain dead AI, optimizing for high McCabe complexity code coverage or whatever metric.

AND (indeed) have QA done by someone with different skills. Development requires a focused mindset, in the zone for long stretches, int the box. Test requires distraction, exploring, out of the box — "hey, that's weird" or "I wonder what will happen if I do this".
You need both. The type system is not going to catch if you do Rectangle(width, height) where you should have done Rectangle(height, width).
> > TDD itself is also overrated, as writing testable code is much more important than the actual tests.

> Indeed, that is exactly the point of unit test and code coverage: proving that your code is well organized and testable through its API.

You can have 100% unit test code coverage and your code can still be absolute sh*t and do absolutely nothing useful. Also, your code can work, with 100% unit test coverage, and have the tests test nothing useful. So reasoning about the quality of your code through the quantity of your unit tests is highly suspicious.

And btw, TDD does not advocate code quality and well organized code - if anything, it lends itself to the opposite.
Wappalyzer removes public access from all repositories
It looks like Wappalyzer has gone closed source, they have deprecated the wappalyzyer-core package in npm as well. What gives?
I don’t know about iPhones, but bicycle tourers who ride long stretches of washboard or rough singletrack have frequently complained that the vibrations broke their autofocus lens on an ordinary DSLR or mirrorless camera. And that is not even with the camera mounted, but rather tucked away in a handlebar bag.
Yes, this could be a possible direction. However, judging by reports from Reddit [1], Windows on ZFS still produces lots of BSOD. Maybe one needs a ZFS Volume formatted as NTFS?

Anyway, these days, I work 60% of time on my VMs, and the other 40% in WSL. Windows is reduced to a graphical interface, maybe I should simply ditch this last mile, too.

[1]: https://www.reddit.com/r/zfs/comments/yxipyy/anyone_using_op...
@dang I'm honestly not sure what the correct cause of action is when one person is effectively taking over a thread with their comments. They appear to have a deep-seated hatred of Scott McNealy, so perhaps should not be commenting for their own mental and emotional health. But their comments have lots of information that will probably spark a lot of conversation.

My gut feeling is that we shouldn't "encourage" such commentary, but I know many in the HN would disagree with me.
This could be written without heap allocation.
No, it is not. Although I can't fault you for thinking this as there are so many people using this term incorrectly.

"Dead bug" is referring to mounting chips on their back with wires connected to leads going in all directions. Hence "dead" -- live bugs don't usually spend time laying on their backs. When you see it you immediately know why it is called "dead bug"...

Here, this is how it looks like: http://dangerousprototypes.com/blog/2012/11/15/fine-pitch-bg...

This technique is usually used to connect to leads of packages that usually have their leads hidden on the bottom of the package (for example BGA). These packages usually require a PCB made for them or some kind of adapter. They also require a bit more complex soldering process that might be just out of reach of an enthusiast (like good hot air station or reflow oven, etc.) If you find yourself with a component you want to quickly test and don't have an adapter... you improvise and this may result in a dead bug. I did it a lot of times myself.

This technique is also sometimes used in production where they have an existing through hole board (or other board that is incompatible with the process required to mount the component). Sometimes it is easier to just "dead bug" the component than redesign entire board for the new process.
Sounds a lot like chatgpt
Let's flip this around. As a customer, if time to market is your primary driver, I don't want your product because you're choosing to put me at risk.
RISC-V is open and far to big already to be associated with any one country. India, Europe and the US have major investments both private and government.
My 3yo now helpfully exclaims "Stupid ads!" when a Youtube ad comes on. Dad mutes it and lets it count down to "Skip ads". Repeat as necessary.
"""
Saw McNealy on his throne

All alone and only bones
"""

I will forever associate his name with this song: https://www.openbsd.org/lyrics.html#33
What evidence do you have that the people and bots here think the math is within their reach?
The Unix way is not gospel, and even if it were, this is Computer Science, not Computer Faith :-)

It depends on what you want to do.

If you're hobby hacking stuff, sure.

Any kind of software that's supposed to come out of software engineering, probably not.
You are mad.

I love you.
Maybe _your_ type system doesn't do that. It is perfectly possible to introduce type aliases to differentiate between X and Y coordinates - though usually it is not worth the trouble. (Unless you are working on the firmware of a nuclear missile - in which case it probably is :))
No, we tried escalating the issues on those practices to the exec team, explicitly requesting a change in policies to enhance the quality of our book. The middle managers we were dealing with simply threw in the towel after that.

PS: This was several years ago, and the policies may have degraded even further since then.
Thanks! As a developer, these are the kind of sites that I want to develop for myself.
I think it similarly lacks substance, but doesn't have the ChatGPT tone / cadence / vocab imo.
Weird Utils: Advanced SkyBlock Malware
I would argue that your income tax calculator logic should probably not be unit tested, it sounds complicated enough to involve multiple classes / units of code. What you really want to test is business logic, not code logic.
Announcing Ideogram AI
And one of my favorite commercials ruins everything with small print at the end: "liquid damage not covered by warranty". This shouldn't be legal :)

https://www.youtube.com/watch?v=DYCnHebwTCM
For the maybe 2 or 3 times I've thought "we probably shouldn't include that in an error visible to end-users" there's probably 100 times I've wished it had been included though, and would've been able to save said end users considerable time if we/they had known which file/resource was being accessed at the point a critical error occurred.
At any rate at most I'd expect the file name to be written to a log file, to which only relatively privileged users would have access.
Indeed, our code base is littered with fmt.Errorf("...: %w", err), but that only works if enough places in the code add context. Currently only about 15% of return sites do this.

And I disagree that the cost of carrying around the callstack is something to worry about. Errors are akin to exceptions in C++/Java: no happy path should rely on errors for control flow (except io.EOF, but that won't generate a call stack). They should be rare enough that any cost below about 1ms and 10k is negligible.
The Feynman algorithm is very underrated. I think some people see it as a joke, as though it's clearly not a working method. But it's how I do most of my difficult work, possibly as a result of majoring in physics where "stare at the problem for a few hours" is the standard approach.

I think my strongest asset is not understanding when a problem is difficult and staring at the problem for hours anyway.

There are classes of problems that don't trivially decompose into a series of easier problems. The only way is to punch your way through them.
Yup, and you have to be pretty lucky to hit the nail in the head on your choice of vocation and profession.

A lot of people diversify, which is good for the mind, but bad if you have to compete for success.

Other people choose very unforgiving fields: want to live a life playing the guitar? Tough luck.

Some other people realize they don't like a hobby or job past some point, but turning over decades of skill to start a new path places them in a huge disadvantage.

It's not a person's fault to not choose the right career path when they're naturally too young to foresee their future in the field.

I personally feel pretty lucky to have chosen computers and technology for my vocation. If, for any chance in life, were to choose anything different when I was 12, then my life would have been entierly different.
Was he able to back up and restore his boot/ESP partition as well using ZFS, or did those need to be reprovisioned manually?
First hit using Google: https://www.reddit.com/r/golang/comments/cokcuw/the_kate_edi...
LSP support for Go was introduced 4y ago. There were some discussions regarding go-langserver vs gopls, but that could be dated (Christoph & contributors are quite active).

Personally, I'm an e-vi-l person and never worked on Go projects, so I can't tell you from experience. Also I don't know your requirements. Maybe just give it a shot? After all, its FOSS, so the only investment is your time ;)
https://youtu.be/e-uGQlT97lc

For example this. I'm trying hard to click on the "Sun 1 Oct" button.

Google sites - with exceptions, like Maps or YT - are full of things like this.
Microsoft/Acivition takeover – MS to divest streaming rights to Ubisoft
I've come to view applications which rely on JavaScript to be fundamentally broken, no matter how small the functionality it implements. I don't even have to give specific examples, with developer tools open it's rare not to see red as you traverse the "modern" web, and even when it isn't I can break the world by disabling JavaScript, I don't even need an extension to do it. The same doesn't apply to HTML, or even CSS.
I hate reading quanta mag because of the narrative, and didn't have the patience to weed through this to learn something conceptual. But I'm glad there are people who enjoy it.
Yeah. I was an Android user from 1.5, and remember anticipating Flash for ages, being very excited when I could finally download it, then being disappointed at how poor an experience it was

In fact, the fact that Flash "worked" on Android became more of a curse for users. There was a period where many big organizations had nice native iOS apps, then threw a shitty webview wrapper over the wall for Android users, and they invariably used Flash for video streaming. BBC iPlayer was the one I remember loathing the most. It was smooth and sharp (for the time) on an iPhone yet blocky and battery intensive on flagship Android phones, if it worked at all
> As for cost, it's cheaper (for me) to store my data in the cloud, than the cost of electricity required to run my NAS.

how much data are we talking about?
Add dir=“auto” to your inputs and textareas
Yep one tester I know had as his first tests

Hit multiple keys on the keyborard at once and do that for a few seconds.

Then if it p[assed that he would get down to more structured testing.

Testers have to assume the user is an idiot and also will always do the wrong thing.
> I could travel and eat & drink very well perhaps, but I think I'd just find it futile.

I tried that and found it absolutely depressing and futile. Quick experiences never did anything for me or my family. But just doing what I like/want to do only (which not everyone can; some people seem to like/want things that cost a lot of money) is what I should've done for the past 40, not only the past 20 years is what I mean. Maybe dying next year is stressful for most, so make it 5 years; is that better? Or 7 as the article says?
I would love to see accident statistics that supports that claim.

Last time I looked at it small bikes, generally used by delivery drivers to be fair, vastly overshadowed any other motorcycle accidents.

On the same note death rates per vehicle on the road was lower for motorcycles than all other vehicle classes and a large portion of those deaths were passengers on a motorcycle and not the driver.

This was all from the mid 2010s though. The statistics showed more to me that wearing correct protection equipment significantly reduced your chance of dieing, the displacement of the engine or even the type of motorcycle had some impact but definitely wasn't a major factor.
That perspective, that scooters are somehow safer, isn't borne out in the data. In city after city we see mounting injuries and deaths, as usage and popularity increase. Consider https://news.sky.com/story/e-scooter-deaths-triple-this-year... and https://www.timesofisrael.com/in-scooter-crazed-tel-aviv-70-... (light Googling).

If one wishes to take the perspective that licensure helps prevent injuries and death, then apply the licensure requirements to these lighter vehicles too. If one prefers the perspective that all such transport is inherently risky, and thus prioritize personal responsibility and assumption of risk, then let's get rid of the licensure requirements, which will surely help get more people out of their 4-wheelers, with knock-on improvements for the environment, traffic congestion, and parking. My problem is with the arbitrary distinction in the middle.
We opted for a more manual approach, we have a ctx!() macro[1] we use for wrapping errors we want to enrich that we then use like this[2]: ctx!(some_fallible_fund(foo))?

I wodner if anyone is doing anything better? The nice thing about our approach is that we store the data on each error, so we get a full backtrace, even when using async.

1: https://github.com/svix/svix-webhooks/blob/main/server/svix-...

2: https://github.com/svix/svix-webhooks/blob/main/server/svix-...