skysight-inc/HackerNews huggingface dataset:
Related:

Why bad scientific code beats code following “best practices” (2014) - https://news.ycombinator.com/item?id=12377385 - Aug 2016 (261 comments)

Why bad scientific code beats code following "best practices" - https://news.ycombinator.com/item?id=7731624 - May 2014 (168 comments)
Amouranth's AI chatbot wants to be your girlfriend as it rakes in cash
The linked section of this article illustrates burnout in the most believable way, IMHO.

https://commoncog.com/g/burnout/#the-development-of-work-bur...
> "I intentionally read very little fiction"

i read only non-fiction. but i retain almost nothing from it.

sometimes question the point. just to pass time.
Apparently tribalism works.
Mozzilla had an opportunity with Firefox OS and blew it, by caring too much about FOSS ideals instead of OEMs willing to make great experiences.
https://archive.is/2024.01.06-043855/https://www.wsj.com/wor...
Apple just called to let us know they're rejecting the HEY Calendar app
> This pattern is consistent with data on the average number of male sex partners for females per birth: gorillas, one partner per birth; human beings, 1.1; baboons, 8; bonobos, 9; and common chimps, 13.

I don't understand this statistic. 'Human beings average 1.1 male sex partners per birth...' we need to see the data behind this. This isn't implying that 1 in every 11 children are bastards, no?
Reminds me of a similar game I made https://qwertytiles.github.io/
Yeah I realised after I posted that that I'm biased from studying and practicing this for several decades.

The warnings section about possible death chimes with Krishna's experience, but also browsing the posts is interesting. People talk of intense heat, strange sensitivities etc, but I can see how someone new to this would probably just write them off as a load of weirdos.
I always wonder if passengers are compensated for like.. the trauma? The videos going around on Twitter show the oxygen masks dropped and people chatting in their seats about thinking they were going to die. Seems like a fine line between manufacturing "shortcuts" and criminal negligence.
Do you have any links to news stories about these firings? Curious to know more.

Also I think your analogy is a bit misplaced; I sure as hell hope the FBI responds differently to enemies than they do to allies.
It certainly was in the beginnings. But more recently? Can you give any examples or data how?

Of course they take all subsidies they get, but that does not distinguish that from many other big companies not founded on government initiative.
I suppose that depends on what matters to the user.

I'm not trying to deny you your experience, but I don't think (in 15+ years of use) that knowing that git stores snapshots (and not diffs) has ever really made much of a difference to me.

A commit to me is still a diff. When I commit something, conceptually -- to me, at least -- I'm storing a change, not a new snapshot. Because I didn't create a new empty directory on my hard drive and then retype everything, in the new state that I wanted. I took the existing code and modified it to the new state. How git stores that is not relevant to what I actually did.
100x relative to NumPy is still quite a lot, depending on how much of their code manages to stay in the C extension. If it was pure Python the delta would likely be much, much larger.

Julia is definitely built on the shoulders of giants. I don’t have experience with most of those languages, especially in high performance Lisp or Haskell. Calling C++ high level is definitely not in the same vein as Python or Julia. My understanding is that Haskell can run into all sorts of performance gotchas because lazy evaluation can be unpredictable and recursion may not always easily unroll into optimizable loops. I think the combination of features, especially borrowed from Lisp and C++, really come together as something very productive for writing fast, very high level code.
As far as I know, no - so it couldn't even be read that way.
Such a skewed world view! If I follow you, then:

a) you’re okay with companies (effectively) acting like mobsters, in their own pecuniary interest

b) you expect every (individual, human) government official to act morally and correctly in every instance, despite the pressure and temptation placed upon them

c) you see no problem with this setup, and see no need to alter this situation

Wow.
I agree with all the points.

It's been long time since I last used lua and only positive memories remained :) I used it for adding scripting in the apps I worked on and the experience was very good -- sandboxed from the start, decent performance.

Perhaps having 0-based indexes would've been bad for our users but I don't think they used arrays at all.
Because even if it is just a maintenance issue (which as others point out is weird for a a permanent part on a 10 week old plane that shouldn’t need maintenance on this part ever), Boeing and the FAA have completely shot their credibility over the 737.

Both in terms of original certification and also doubling down on “no issue planes are fine” until it became incontrovertible that the planes were the problem and then all the collusion and shadiness about how the 737 came to be came out.

So with that history, even if it would be an overreaction, rebuilding trust would look like immediately grounding in a situation like this out of an abundance of caution. Btw the 737 has had other maintenance problems crop up since they put it back in service since the fleet was grounded to retrofit the part that was needed to fix the original fatal-causing defect. Honestly this just looks like an unsafe plane top to bottom that could sink Boeing (except they’re not allowed to sink because they’re critical partners to the national defense industry)
> or close to testing the first prototype with the new engines

Considering that Russian engineering culture is even worse than that of Boeing (and probably massively so) it’s unlikely that they can ever be competitive if that’s the main issue
I've used git nearly since it was first released, and I also have (more or less) always known how git implements commits. But to me, they are still diffs.
Csvlens: Command line CSV file viewer. Like less but made for CSV
Is “both” an option?

The guy who invented git uses it to serialize code as diffs over email, so I think that speaks for itself.

At the same time, merge commits basically insist on being understood as snapshots.

My understanding is that for efficiency and performance, what’s under the hood is a little bit of both.
> Installing the extra doors would mean more things to inspect or go wrong.

Yeah, I guess. Facts don’t agree though.
https://www.navalgazing.net/ESSM says the range is estimated to be 50km, Block II no longer needs illumination from the firing ship, but may not be fully integrated into AEGIS such that it can take targeting data from other ships.

“But despite its capabilities, ESSM still had the drawback of all previous versions of Sea Sparrow. It relied on semi-active guidance, requiring illumination from the firing ship. It did have an autopilot and uplink from the firing ship, allowing illumination only in the last moments of its flight, but this was still a potential problem when facing saturation attack. The obvious way to solve this was to fit the missile with an active seeker head, and discussions of doing so were happening as far back as 2002, but it wasn’t until relatively recently that serious work began on what is known as ESSM Block II. Block II kept the motor and fins, and replaced the forward 8″ section with a new 10″ guidance section, with a new dual-mode active/passive radar seeker. This removed the need for firing-ship illumination entirely, allowing Block II to be used against swarm attacks or targets that the firing ship couldn’t see, although reports don’t seem to indicate that it’s fully integrated into the Collective Engagement Capability (CEC) system.”
> First write a bunch of config to undo all the bad settings and nonsense that comes with the stock editor

I've now used Emacs for 30 year. The only people who have large configs for basic text editing are people who don't understand the first thing about Emacs.

Emacs is not a text editor. It is an elisp environment focused on text manipulation.

For some reason these people are extremely loud and have a lot of blogs.

The only parts of my init.el which aren't stock are those used to setup speciality packages like the tui for connecting to the prod database.

The rest of my code is in packages which do something useful. E.g. local llm integration.
This model has been in the top for quite a while, what's so good about it?
Yes, the poor way this is taught is one of the reasons why so many people are stuck in the stone age of printf debugging.

Already in the mid-1990s it was possible to use C debuggers as poor man's REPL, have tracepoints, scripting debugging sessions, visualize data structures, track down memory leaks and corruption.
Spain has had train security even on long-distance domestic journeys at least since I lived there in 2008. I suspect it's a reaction to the train bombing they had, but don't quote me.
While I think there are a couple of valid points, in general my feeling is that the author is setting up a straw man to attack.

Most of the “programmer sins” are of the type that more seasoned engineers will easily avoid, especially those with experience working with scientific code. Most of these mistakes are traps I see junior developers falling into because of inexperience.
No, NPM has never been thought out well. Many of the improvements in npm over the years were all either (1) due to accidents that many other package managers like NuGet already prevent by default or (2) features that were already implemented in Yarn 1.x.
That’s hardly comparable
There are at least four issues with your comment:

1. The weird implication that people who use tools are doing so to make up for lack of skill. This is so obviously misguided I'm not sure where to start.

2. Dismissing AI as "a procedural generator". It's clearly much more than that.

3. Assuming that the 30% of my job that AI does is the valuable bit. It isn't. AI mainly relieves the tedious stuff at the moment (looking stuff up, typing semi-repetitive code, etc.).

4. Trying to make yourself feel better by asserting that people who use IDEs are worse than you, or that I don't understand my work. Rather pathetic.
I think I remember calling it the butterfly key at some point.
Chromium bug bounty money tree browser
No - and renting out scooters is a model that can totally work.

But do micro mobility companies have the scaling potential/dynamic of a Google or Facebook (which would justify the way they raise money)?
That isn't what "door to door" means though.
I'll assume those 15 years of Vim acquired a lot of stuff in your .vimrc. Stock Vim is similar to stock Emacs (as you concluded), so I don't know about this comparison.

> then do three days of Googling to add basic features like fuzzy finding, LSP, VCS support you would expect to be built in in 2023.

All these things are built in Emacs, except fuzzy finding. For that, you use fzf, just like in Vim.

> add in the damn stuff we all know people expect in an editor in 2023

What did people expect in an editor in 2023? I don't use LSP, popups, fancy themes/modelines, or fancy fonts, and I know many devs who prefer the same, especially experienced ones. We expect the same behavior from the editor in 2023, just like we had it in 2003 and want it in 2033. Also, I know many devs who spend all day making their terminals, editor(s), and window managers fancy to show how cool their setup is. But to each their own, and these things are highly subjective.
I missed out on the codes, of course, but bought it anyway. Interesting so far; not fast yet, but more accurate as the larger keys are easier to hit - I struggle with most phone keyboards. Can't find the brackets though...

Is there any chance of a Welsh language pack, please?
This is going to be my daily driver to schedule our team meetings, great work! A feature request would be to give me the option to input the time apart from the existing slider input.
The problem is not teaching C, for better or worse it is going to stay around us for a very long time, thanks to UNIX's victory on server room and embedded systems.

The actual problem is doing a half baked job, teaching it as if PDP-11 were still current, without any consideration for safe programming practices and modern tooling.
Nuclear reactors and thermal depolymerization seems promising. We could probably mine every landfill site in America for a century before needing to think about something else.
I actually think the variadic logical and is more readable, and wish more languages had it. As long as all the arguments are lined up vertically, you can think of it as a sequence of tests for true that exits at the first failure. It's more obvious with the variadic operator. Contrived comparison:

if (a != null && x != 0 && a.use_it(x))
{
...
}

(if (and (not (null a))
(/= 0 x)
(use-it a x))
...)
The cool part is that the way CloudFlare does it is really cheap
Imagine mixing beats with just a wave of your hand. Synthy
The Fun Parts:
Synthy uses Computer Vision, to let users use there hands to mix music, and GenAI to generate beats / songs.
1⃣ Far higher fidelity for controlling the music with your hands
2⃣ Mix, and match, the right beats, to your audience.
3⃣ This is actually sort of fun.

Been playing around with these sorts of tools, thought it may be of interest to the hackernews crew, i'll make a youtube vidyah demonstrating it :)
Picard: The first vessel that I served on as captain was called Stargazer. It was an overworked, underpowered vessel, always on the verge of flying apart at the seams. In every measurable sense, my Enterprise is far superior. But there are times when I would give almost anything... to command the Stargazer again.
In my experience this is not how Germany works at all. "This is how we've always done it" is a lot closer to reality. Germans have an incredibly low standard for efficiency. At best they're just very thorough and methodical, but change aversion permeates every later of society.
"the more complex the spec is, by transitivity, the more complex is anything that comes out of it"

Yeah, that's why so many languages don't have spec at all.
Pure P2P node discovery is practically impossible. You can use DHT till some extent, but initial discovery will be done using some traditional peer tracker
Air is going out at that height, not in! Pressure falls so rapidly that it should be rather quiet after a short while.
Congrats on finishing and launching the project. It is slick! Are you planning to monetize?
git diff by default outputs valid patch files that you can feed to patch out git apply.

--word-diff does not

Kernel development involves working with patches a lot, so it made sense to default to that, and --word-diff was added later anyway.
If one door falls of the aircraft, it's most likely a service tech didn't do the job properly, not that there is a systematic issue. That'd require much more fallen doors.
> Don't get me started on how the home/end/insert/delete/pgup/pgdown cluster got massacred and merged with the arrow keys.

Worse than that is how the arrow keys are often different sizes nowadays. That one actually influenced my current choice of laptop, all my arrow keys are the same size.
Doesn't help you now, but often data recovery companies such as DriveSavers only charge a fee if they are successful.
I don't think that's a very good explanation. It only considers one possible use of rebase, to resync a feature/topic branch with a main branch that has diverged since the branch was created. Another common use case for rebase is to clean up an already-linear history.

And even then, when using rebase to "resync" different branches, I don't think it's accurate to characterize it as a merge at all. It's a hard reset plus a series of cherry-picks.

(As an aside, this is why rebase can be much more annoying than a merge! Merging a branch onto another is usually quick and easy. Git's merge algorithms usually do a decent job of figuring out how to do a merge without conflicts. And if there are conflicts, you only have to resolve them once. If instead you rebase, you may have to resolve the same (or similar) conflicts over and over and over, once for each cherry-pick. And there might be conflicts that wouldn't have even occurred with a simple merge. Git's rerere mechanism does automate some of it, sometimes, though.)
A gas camping stove is like $50. A toaster oven is another $50-100. The best reviewed chefs knife on the market for commercial kitchens is $30.

You don’t need thousands of dollars to start cooking.

I have friends in the who cook on this stuff at home all the time. We in the west have elevated our kitchens into something luxurious. Nothing wrong with that, but it’s overkill for many people.
"It seems the author indeed is not a SW Engineer".

This is a pretty ridiculous notion if you just cursorily glance over the page. It is quite clear that this guy is more of a software engineer than most with that title will ever be. Hint: a blog that contains a post with a title like 'Coroutines in one page of C' is a software engineer.
Base load is a social construct used by coal and nuclear to justify the economically viable bid model which suits them. You can target the duck curve by batteries, and by demand management. People are perfectly capable of moving significant load in time, as evidenced by time of use charge models and off peak pricing.

More and more solar owners here in Australia deploy a battery when they can afford it and in Victoria the state government is funding solar and battery deployment for social housing.

Almost no new wind or solar can be deployed at scale in Australia now without battery deployment. Both individuals and grid scale batteries are fine. They serve different parts of the supply chain.

FCAS can be supplied by batteries and reactive loads by condensers.

Base load is a debating point. It's the load we can't currently supply from renewables. When we can, coal, oil, gas and nuclear may become uneconomical stranded assets. Nuclear would presumably last the longest because of the sunk cost of public money.

Networks are, and always were a public utility function. Converting to bid models was a huge mistake.
I've written a book that I sell as a physical copy and an ebook. I don't advertise this, but when they buy the physical copy they get sent the ebook for free with this message:

"You bought my book, and because of your support, I am able to make a living as an artist. It means a lot. PS. if you want to read the ebook, it is included in your purchase of a physical copy. Press "View content" to download. However, I recommend waiting for the real deal."

The reason I do this is because in my mind, they have paid for the content not the paper it's printed on, so the ebook is a part of the same purchase and is an extra convenience for someone who might want to read on their Kindle or phone. It's also a way to reward customers with extras, leaving them happier and more likely to leave a positive review. They also get all future revisions and editions emailed to them.
It wouldn't be so bad if they didn't take 4+ weeks to do anything. My friend had a child and he got a soul a year later. It's even worse in Berlin.
Excellent performance for this model size and inference cost. Best model you can run on a device a small as a phone and get performance close to GPT-3.5 level.

The structure and the training data are also interesting - sparse model using curated synthetic data to achieve much better accuracy than is achieved in models trained on random internet text.
I used example2.png (https://www.canyouexplainthejoke.com/example2.png) to test it, but the state highlighted in the joke image is Oregon, not Minnesota. Bot still says the highlighted state is Minnesota to explain the joke.
To be honest it's mostly not their fault. Most people want to do the right thing and that's what they're taught. Doing things differently is frowned upon, and most people don't want to stick their neck out and say the emperor is naked.

Recently at work some people argued "things" (methods, classes, even files) should have a limit in size. I think that's valid thinking because you want to strive to having smaller components that you can reuse and compose, if you are able to do that. But what happened is that people started creating dozens of little files containing a function each and then importing those. To be it's obvious that this is now a lot worse because the complexity is still the same, just spread out across dozens of files. But most people were somehow convinced that they're "refactoring" and that they're doing best practices of keeping things small.
Everything in one file can be good organization for many even relatively large projects.
Please don't include LSP in fancy things to show off. It's a productivity game changer if you work on large codebases.
Rocket Lab are in development hell at the moment and while their financials are decent, Electron has had a failure every few launches and Neutron is due NET 2024, but with no news of an Archimedes hot fire, it seems unlikely that we'll see anything before mid 2025.

By saying development hell I'm saying that other new space companies other than SpaceX are in that difficult in between point where they're burning cash on developing the rocket without yet being able to sell significant rides and without the leverage of knowing that the government will give you a blank check if you run out of money.

The important factor being that small launch doesn't make enough money to fully fund medium launch, there just isn't enough demand for small launch with rideshares being cheaper. However, medium launch can fund more medium launch or even heavy launch, as there is much more demand in the medium weight range.
> I'd be more concerned about how gas is feedstock for pharma, and fertiliser.

Would you elaborate on what you mean by this? I don't follow.
This article is not about the bankruptcy. This is an article about the "gig economy" of the fleet manager sub contractors. This article was being researched prior to the bankruptcy announcement, which presumably upped their publication timetable since it was published the day after.

This difference of topic is also why you see such a different discussion in this thread.
The trick, and I say this as someone who's gotten to meet a fair number of musicians, including some semi-famous ones, is that they're people. Plus they're also huge music nerds. Just mention Cheap Trick and you're in... (Although at the same time, do know how to read the room - it's not that hard to tell when someone just wants to be left alone.

Those genuine interactions are better than any autograph or selfie.
Aha! advertises as far as New Zealand and I also never heard back when I applied. The excuse they supply (at least they do that much…) is that they receive too many applications to respond to everyone. But then why advertise all over the world? A scummy tactic when I think about it.
Cool! I don’t see myself needing them any time soon, but max 2TB was too close for comfort.
> it could've written said sufficiently advanced compiler itself.

They couldn't, because that compiler would need to solve the halting problem.
I did that too, worked for a computer shop and often got hired by clients.

Never got offered sex on lieu of payment unfortunately, I would have taken it :) Nor drugs but I don't do those.
Indicates Phi-3 and the next cohort will obsolete Phi-2
Wow this is amazing. This is what the internet should be like
Plastic is only cheap because it's a byproduct of oil. It'll stop being as cheap and plentiful if we stop producing oil and we'll naturally move to cheaper substitutes

Although I don't think oil use is going to end anytime soon