skysight-inc/HackerNews huggingface dataset:
It looks like Hakan K (has a super cool website where he solves all kinds of optimization problems for fun) was able to solve it using the Picat language in a very small amount of code with a solution (not sure if optimal):

http://hakank.org/picat/dogbunny_puzzle.pi

His website is a treasure trove for these kinds of problems and worth studying.
This. It's so tempting when a linter warns "This code is misleading; it would be clearer to do it this other way" to think "Easy fix: change it the way the linter suggests." But, make the change, and you may discover (hopefully before delivery) that the code functionality depends on the confusing behavior.
Odd that a quarter of the code is parsing the qsps
Not tellies but an interesting look by Dave Jones[of EEVBLOG fame] into how/why simple devices can use up so much power when idle. A lot of it is down to lazy design of the AC>DC circuits

https://www.youtube.com/watch?v=_kI8ySvNPdQ
I've used paper notebooks as working memories for almost 10 years, until I learned about Evernote, which I had adopted ever since. I quickly became addicted to it. I was storing absolutely everything in it. It was around 1000 or 1300 notes when I began to lose track of things, meaning, information and documents. Search stopped being effective to me and I ended of with too many tags. I decided to adopt the model which uses only 2 notebooks: .Inbox and Archive. Everything else is organized via tagging. Today I have around 3500 notes which are mostly a personal archive. I simply gave up trying to be productive finding things in that ocean of information. So I'm using Google Keep for basic note taking and txt files with long descriptive names in project folders when I need to keep specific notes isolated from all the rest. Nautilus search works fine in finding those files as I type parts of their names.
Nice. We've changed to that from https://en.wikipedia.org/wiki/Monte_Carlo_method#History above. Thanks!
I'm a patent examiner and I can't agree with "It's very precise if you can learn to read it". A large fraction of patent applications I've worked on are unclear. I even wrote a linter to help catch some problems.

(DOC lawyers make me add this: This post is just my personal opinion, not that of the USPTO, DOC, US govt., etc.)

Edit: I will agree that patent claims can be precise, but so can normal English. I think patent claims are too often not precise.
The US really does lag behind on this one; the push for plain English was phenomenally more successful in other Anglophone common law jurisdictions.

Having practised as a lawyer in one of them, I can confirm much contemporary American legal writing seems absurd and even comical. There’s something amateurish about it; like a layman trying to ad-lib some law talk at a party by cobbling together some obscure law terms he’s overheard.

“The first party of the aforementioned party - THIS PART IS IN CAPS - will henceforth wheretofore undertake that by no later than St Swithen’s Day - MORE CAPS MEANS MORE LAW - ”
There are. They're called memory models. I know Java's is pretty readable (see below). I think C and C++ have them too now. But when you're building on these things there's always lots of room to get them wrong!

[0]: https://en.wikipedia.org/wiki/Java_memory_model

[1]: https://docs.oracle.com/javase/specs/jls/se18/html/jls-17.ht...
I tried Zettelkasten, but I think it’s a good solution to a problem I don’t have. I take notes to remember and find information, not to publish it. ZK is more geared toward sharing with others.
Facebook and social media companies rely on viral phenomena to sustain their monopoly. It will take 1 inciting event for them to fall into an irreversible death spiral. The instagram + whatsapp acquisition, feeling threatened by 100x smaller dev shops demonstrates that.

Google's big advantage is that their core product has fundamental value (search and by proxy: ads) and their secondary products are such loss-leaders that outcompeting those freebies (Google office suite, Gmail, maps, YT, chrome, ml tooling) is where the real difficulty comes in. But building a core-search competitor is far easier than competition with Apple or Msft's core products. Google has a lot more scaffolding that FB, but they too have a single point of failure. A sea-change (like Mapreduce, pagerank, the smartphone) can see them collapse swiftly.

On the other hand, enterprise / feature-checklist companies lie in a stable equilibrium. You can't really beat them unless you invest a similar amount of resources into it. And even if you defeat them, they'll catch up to you in time if they're run at similar levels of competency and can throw a ton money money at it. Microsoft and Apple are exactly that. It's like trying to start a Boeing or Nvidia competitor. You better at least be at Airbus's or AMD's level before even trying to compete against boeing.

Microsoft's weakness is best displayed by Adpbe's acquisition of Figma. If Microsoft is run in a similarly predatory manner and a competitor gets 10 free years to catch up on 1 feature while you continuously fail to innovate, then you feel a mild threat, at which point you can simply outbid and acquire them. That shows how remarkably comfortable of a position Adobe is in, and Microsft and Apple sit a couple of orders of magnitude above that.
This comment was posted when the URL at the top was https://en.wikipedia.org/wiki/Monte_Carlo_method#History.

We've since changed it to the URL suggested by sampo at https://news.ycombinator.com/item?id=32889436.
36 y/o, same here
Thank you for this. My failure at calculus in my undergrad really set the tone for my mech eng. degree. I felt exactly what you mentioned: that you needed to memorize the "trick" and then you could solve the equation.

I am still embarrassed at my poor performance in undergrad.
I knew some people who worked there, and one thing that was a red flag for me was just how much kool-aid everyone who joined on LinkedIn seemed to be drinking. It was like a Silicon Valley trope where people would write we’re gonna change the world! And then I looked up what the company did .. and I’m like logistics? Okay .. but basically I know startups are supposed to have charisma and all but it just seemed like too much. I’m trying not to become jaded and negative but I feel sadly that this is part of the rite of passage for software engineers, you join a hyper charismatic team and see hyper growth for a year or two, ride the high and then it falls apart and you have to figure out what you want to do next and how to avoid this the next time.
Technical Possibilities for a U.S. Central Bank Digital Currency
Many people were paying for SEO, which you can still buy today
In HFT, we typically pin processes to run on a single isolated core (on a multicore machine). That allows the process to avoid a lot of kernel and other interrupts which could cause the process to not operate in a low latency manner.

If we have two of these processes, each on separate cores, and they occasionally need to talk to each other, then knowing the best choice of process/core location can keep the system operating in the lowest latency setup.

So, an app like this could be very helpful for determining where to place pinned processes onto specific cores.

There's also some common rules-of-thumb such as, don't put pinned processes that need to communicate on cores that are separated by the QPI, that just adds latency. Make sure if you're communicating with a NIC to find out which socket has the shortest path on the PCI bus to that NIC and other fun stuff. I never even thought about NUMA until I started to work with folks in HFT. It really makes you dig into the internals of the hardware to squeeze the most out of it.
Start by not having a password manager that is universally adopted across the corporation.

Then maybe you've got a planned change that requires a manual operation on the production database, and you don't have the password already because it's rotated daily.

Maybe you need the agent license key for the monitoring system, so you can add it to the secrets file for the new host you're setting up.

Maybe someone created a new service and, and asked you to generate a new oauth2 client secret for it, and you need to send it to them.

Maybe it's corporate policy that every laptop must have an encrypted disk, and you've mailed a new remote worker a laptop and now need to send them the disk password by a different channel.

Maybe you occasionally need to work with some decrepit system that doesn't support single-sign-on - like a server's IPMI or some obscure bit of network equipment.

Of course there are better options than slack (which doesn't even have an off-the-record mode) but if slack is what everyone uses? Well....
Monopoly literally means a single seller. Duopolies and oligopolies are distinct both in theory and practice.
That's good, people should be able to do that. If people want to exchange cash for items of value there should be nothing stopping them. Police should just investigate crimes and stop laying totalitarian dragnets and checkpoints for everything people do that in some cases might also be done by a criminal.
One of his articles helped me in a debate about a codebase once. There were two camps at the company. One camp believed that we should be looking to optimise the code we wrote by choosing faster options such as for loops over slower chain functions such as forEach (application was written in Typescript, I don't know if this is the case for all languages). The other camp classified these kinds of changes as micro optimisations. I belonged to the former. The code base was huge and the application was slow bordering on unusable.

I used the Dave Brailsford British Cycling analogy from Atomic Habits that the aggregation of marginal gains can result in big changes on the macro level. Or put in other words, one non-optimised function might not make much of a difference but lots of them in a massive code base with millions of lines most certainly does. My co-worker's response was that he was not sure that the analogy from cycling transferred over to coding but I could tell that it was at least giving him pause for thought.

In reality, there were many reasons for how slow that codebase was. There were most certainly bigger fish, but I still believe that choosing more optimal language options where possible would have helped.
The article is based on… nothing? And a bit of TikTok mania? I thought this was really low quality in essence - providing no real proof for any substantial change.
> Writing tests for something that is already not functional, will be a waste of time.

This is not TDD; it's writing tests to confirm the features that work now. Then, when you make changes, you can get an early warning if something starts going south.
And each time they think (or get the citizens to think) they can escape the natural laws of the universe, money printing causing no inflation.

"It won't happen here!"

It's not us doing money printing.. it's uh.. COVID, uh.. the war, uh.. Climate change, uh.. corporate greed.
I ate fried bee larvae in Yunnan back in the days and there's nothing to be scared of or apprehensive about.
Yep. views in RDBMS are much underrated, IMO just because they are old tech. It should be possible to use views to:

1) normalise the database (fold these ugly add-on tables as columns in the parent table, with suitable null constraints, then drop the add-on table).

2) Use views to add the add-on tables (now views) back in again.

3) Continue running the old application code against the views, which present the old, ugly schema.

4) Simultaneously write the new code against the normalised core tables.
Full report: https://www.whitehouse.gov/wp-content/uploads/2022/09/09-202...
never did, books become outdated too quickly, so I use online resources
> I don't have the luxury of caring what your suggestions are about how I run that class

You can't expect respect for that. (BTW, other teachers have told me their reason for not caring about parental input is they were trained professionals and parents were ignorant fools.)

> You are still trying to shame someone who is making below a living wage to purchase it

$4 to supply all your students with pencils. You brought up the pencil thing. Besides, you should move to Seattle where public schoolteachers make 6 figure salaries, have a pension for life, gold plated health insurance, and 2 months off per year.
Pretty cool author bio from the end of the article:

N. Metropolis received his B.S. (1937) and his
Ph.D. (1941) in physics at the University of Chicago. He arrived in Los Alamos, April 1943, as
a member of the original staff of fifty scientists.
After the war he returned to the faculty of the
University of Chicago as Assistant Professor. He
came back to Los Alamos in 1948 to form the
group that designed and built MANIAC I and II. (He
chose the name MANIAC in the hope of stopping
the rash of such acronyms for machine names, but
may have, instead, only further stimulated such use.)
From 1957 to 1965 he was Professor of Physics
at the University of Chicago and was the founding
Director of its Institute for Computer Research. In
1965 he returned to Los Alamos where he was made
a Laboratory Senior Fellow in 1980. Although he
retired recently, he remains active as a Laboratory
Senior Fellow Emeritus.
You're not the one who is insane.

Assume you have a $25k budget for a Dell server and $20k for attached storage . Go see what you can build on Dell.com's online configuration tool.

You could colocate everything you can buy for $45k in a half rack at a reputable datacenter for $750 per month including a burstable to 1gbit internet connection.

I estimate that at least 75% of the people who are commenting on these threads, will not have a product or service that could cause that server to choke on the load, nor saturate the 1gbit feed with legitimate traffic from their applications.

But they will instead recommend that for 600k/year in spend you over-engineer all aspects... I call it CVops instead of DevOps. CV being another word for resume...
How much does an Apple TV 4k 2nd gen use? My 4k first gen turned off when I turned off the TV. The 2nd gen does not. I assume it has something to do with the iot support
That is not how logic works. "Better languages with less marketing are less popular than Java" means that "marketing matters" and that "quality isn't everything", not that "only marketing matters".
Introducing 'innernet' a tailscale alternative (2021)
Is heating/hot water in that 1.5kW?
Apple is focused on consumer products and consumers can be fickle. While it won't be anytime soon, it's not impossible for Apple to someday lose the design mojo that makes their products popular. Steve Jobs and his RDF aren't there anymore and neither is Jony Ive.
All of retail is in a way a matchmaker.

Cosco doesn't make the goods they sell - they are just being an intermediary between you and the the manufacturer. An intermediary that takes a 60+% fee for their work.
New Frontiers in American Philosophy (1977)
Microsoft is reliant on Azure for growth. Although cloud initiatives are designed to save money in the long run, in the short run they cost money. If we go into a strong recession than at the least I would expect Azure to do worse than projected.

Likewise, Apple sells luxury goods.

If I had to bet on one FAAMNG in a sharp recession it would be Amazon. They have the most diversified revenue streams.
Honestly, that sounds like making bad code even worse.
I bought a 55” LG 4k tv in 2018 and I am so glad that I bought it before all this always-on ads-infused nonsense became integrated.

It works great and I hope it lasts a long time.
FAANG is kind of a weird classification: 4 web companies, 2 of which are primarily ad companies... and then Apple, a devices company with real low-level chops.

Why don't we put Apple in with somebody like: MAIA -- Microsoft, Apple, Intel, AMD. Maybe add NVIDIA, you have to work out a good acronym though.
> one basically needs to reproduce the thought process of how one would come up with the given model [...] people are much better at deriving the rules from a few examples than the other way around.

Indeed. I don't think this is as mystifying as some people seems to believe. There seem to be at least two errors poor communicators make.

The first is that communication doesn't transfer any content from one person to the other. We use signs and symbols with conventional meanings both parties accept to express things which are then interpreted by the other party. If you're not both on the same page, you have to first establish that common ground. Much of education involves building up that common vocabulary and system of signs so that we can even have the conversation. To think of communication as if you were some act of piping the actually semantic content from your mind to another's is to completely misunderstand communication and a recipe for failure and frustration because you will be unable to understand why someone cannot just grasp the content you think you've just poured into their head. "It's right there! I just gave it to you!"

This brings us to the second error. Knowing your audience means knowing what their current state of knowledge is. Part of that is knowing the vocabulary and system of signs your interlocutor knows. Explanation is therefore a matter of using what they already know to lead them to the conclusions you already have (introducing claims as necessary). Once the aim of explanation is stated that way, it starts to resemble something like a chain of reasoning...or an argument, which it basically is. I cannot derive certain theorems if I have not yet derived certain prior theorems, much less if I lack the axioms from which they are derived.
idle as in OS not running is around 2.5W for rPi. No real power management on rpi either so you can't sleep.
As a user of a current ARM MacBook Pro 16 inch and a former x86 MacBook Pro, being able to have a battery that last 20 hours, doesn’t get hot, nor does it sound like a 747 when I launch Slack, I very much appreciate Apple being able to transition processors.

Also seeing that the iOS game market dwarfs the PC game market in revenue and number of titles (if not quality), I think Apple made the right choice.

Microsoft has been unsuccessful trying to get Windows on ARM to be viable for years before Apple did it and has failed partially because of the behemoth that Windows is.

Speaking of Windows and backwards compatibility. There are at least 8 different ways to define a string in Windows depending on which API you are calling. String handling in C is one of the biggest causes of security vulnerabilities on any platform.

https://learn.microsoft.com/en-us/cpp/text/how-to-convert-be...
You may be interested in this article:

https://medium.com/@kris-nova/organic-and-mechanistic-system...

What you are dealing with is organically grown software. No one really understands it, and it's likely to be fragile.

I agree with all those here that say the first thing to do is to introduce version control. You don't want to break that money machine without a way to revert.

Second, introduce some lightweight form of code review, but don't tick people off.

Third, if you want to do something like revise the user interface, consider adding an API to the existing organic code base, and build the new UI with that API. Generally, take that approach and avoid jamming something into the middle of the existing code that no one fully understands.
TikTok was only able to compete so quickly because it's literally sponsored and funded by the CCP.
It’s just something to negotiate with the dealer, being that as software it’s a “zero cost” thing. I’m doing just that on a Duke 890R now. “Give me the software for free”, and they do (I’m not in the US; YMMV. Go buy a Ducati)
Do leads not write proposals or RFCs? I’m not sure why you wouldn’t keep them around long if they laid out their plans in a clear way, and then pitched it to others
This worked for me a year ago. You can cancel the new one within x days. Couldn't believe it worked, but was happy with it.
My experience working as a patent examiner agrees fully with the title: legal texts tend to be hard mostly because they're poorly written. (DOC lawyers make me add this: This post is just my personal opinion, not that of the USPTO, DOC, US govt., etc.)

I've been trained in patent legal terminology, which isn't that bad. Patent documents are still frequently difficult to understand. I have one application on my docket where I'm going to have to rewrite one of the claims to understand what it's saying, and no, that shouldn't be necessary... And the situation with patent documents is worse than the situation described in the abstract as many attorneys write vaguely.

The argument that "lawyers are the intended audience" isn't legally sound either, as under 35 USC 112(a), patents are supposed to "enable a person skilled in the art [...] to make and use the [invention]". If an attorney argues that patents aren't supposed to be understood by non-attorneys, they're wrong, full stop.

Unfortunately, I'm not really allowed to do 112(a) enablement rejections. I'd do those sorts of rejections frequently if I could, but I think I can count the number of times I've done 112(a) enablement rejections on one hand. The law in other countries seems more strict than in the US. I'm told that Japan in particular takes enablement a lot more seriously than the US does.
That's funny, I had similar experiences moving from the United States to Canada. When most people were paying with their debit cards at the terminal, I would tap my credit card (at the time issued from the United States) and have no signature. Like in your case, some clerks seemed surprised.
Minimal in terms of direct costs to you, but merchants pay 2-3% on EVERY transaction, and I can guarantee you that does end up baked into the prices you pay.
Conceptually, the book is a mediocre method of learning a language or tech subject. Anything "Learn X the hard way" with recent commits will be more helpful. The concept is to run the exercises needed to gain fluency in the key features and accessing/understanding the core documentation. A standalone book frozen in time with idiosyncratic documentation is not helpful.

At their best, books can provide analogies and parables to build a narrative about a technology without specifics.
this really punches a hole in the idea that "if you're not the customer, you're the product"
What is the biggest Ada-based project currently in use? Does anyone know? Is Ada more for DoD-type backend-stuff, where Fortran or C would be used, or something else? What is Ada for?
It was a reddit thread with a baity title on a guaranteed flamewar topic.

https://news.ycombinator.com/item?id=32823355
> ... would need to be detonated at extreme altitude.

Perhaps it would be more accurate to say "would need to never be detonated."
The text at the bottom says "unless otherwise noted". The .md files for the AARM are autogenerated and it seems the legal + foreword pages are missing. These indeed need to be added. The announcement was done by an external person, but nonetheless thanks for bringing it to our attention. The website is still work in progress and is intended to be handed off to the Ada community.
I’d like a terminal email client inspired by vim’s usual keys and behaviour. I didn’t particularly like mutt’s default keys.
Chromecast Ultra also uses 20W in standby.

I was going through the all devices and found that a TV which is most of the time off, was using that much power. Now I keep it unplugged.
The hack being described was very very old, this is exactly what the AppCompat system does in Windows now. AppCompat shims only apply to specific versions of specific apps (or get rolled up into "layers" which is what you get when you mark an app to "Run under XP compatibility"), and don't end up affecting other ones