skysight-inc/HackerNews huggingface dataset:
Quite. It’s the difference between:

> You wake up in front of a box which has a label that says “treasure inside”. Should you assume there is treasure inside?

to which the answer is clearly “maaaaybe?” and

> You wake up in a world with accurately labelled boxes, in front of a box which has a label that says “treasure inside”. Should you assume there is treasure inside?

Where the answer is yes, and if the person setting the problem says “hahah no!!!” you can say “well look, that wasn’t a fair puzzle”.

It is primarily a “do you have sufficient information” problem, like in the GMAT, with a level of misdirection thrown in.
For concurrency issues you don't want a debugger or printing as both are terrible for this, you want a library designed to specifically detect these issues, I have a custom one but many other people use valgrind etc.
A few of them definitely aren't lined up right, but wow! What a fun thing! Today I learned the bike path that runs by my apartment was once a railroad.
What's the rough bit count of the largest numbers anyone's quantum computer can factor today? Breaking RSA2048 would be a huge breakthrough, but I'm wondering if they can even factor `221 = 13*17` yet (RSA8).

And as I've mentioned elsewhere, the other QC problems I've seen sure seem like simulating a noisy circuit with a noisy circuit. But I know I don't know enough to say that with confidence.
The real issue was that I didn't get that you were talking about Solar Orbiter, I thought you were saying that the irradiance of the sun was 20kW/m2, which seemed low to me, but I didn't even know the word "irradiance" so I didn't know what to type on Google to check it.
Thanks for your detailed calculus :)
There is nothing wrong with using print debugging but if you are only using print debugging, finding yourself doing a ton of compiler round trip, and don’t know how to use a debugger, you are doing yourself a massive disservice.
I have developed ethical qualms about AGI. We end up either enslaving an intelligence, breeding it into submission, or end up with a powerful adversary.
Exactly this. Especially an article that picks a side without showcasing an understanding of the pros and cons of the "competing" approaches.
Loads of inexpensive quality games - so kids wanted one, but also programmable with a decent enough BASIC for the era - so parents could see it as an educational tool too.

Plus, cheap enough to be affordable for most families.
> That creates a problem for supermassive black holes.

I don’t think the black holes are the ones with the problem.
crates and cargo are better than Rust actual
Print debugging is a great tool in unfamiliar environments. As the article notes, it’s simple and works everywhere.

I do think that it’s worth learning your debugger well for programming environments that you use frequently.

In particular, I think that the debugger is exceptionally important vs print debugging for C++. Part of this is the kinds of C++ programs that exist (large, legacy programs). Part of this is that it is annoying to e.g. print a std::vector, but the debugger will pretty-print it for you.

I wrote up a list of tips on how to use gdb effectively on C++ projects awhile back, that got some discussion here: https://news.ycombinator.com/item?id=41074703

It is tricky. I understand why people have a bad experience with gdb. But there are ways to make it better.
Does it matter? As pg says, startups should Do Things That Don't Scale.
With Commodore-64 you also had to buy their tape recorder (same thing as with Atari 800XL), while Spectrum worked with any existing recorder, which every house already had at the time.
> ...I still want that kind of system, but I expect it would fail catastrophically in the real world

Julia has its own version of the orphan rule called Type Piracy, which is merely discouraged instead of disallowed: https://viralinstruction.com/posts/latency/#a_brief_primer_o...

It's not a net gain, but rather a different tradeoff.
Print debugging is the tool most people reach for when they can, but its biggest problem is that you have to change the source code to add the printfs. This is impractical in many circumstances; it generally only works on your local machine. In particular, you can't do that in production environments, and that's where the most interesting debugging happens.
Similarly, traditional debuggers are not available in production either for a lot of modern a software -- you can't really attach gdb to your distributed service, for many reasons.

What print debugging and debuggers have in common, in contrast to other tools, is that they can extract data specific to your program (e.g values of variables and data structures) that your program was not instrumented to export. It's really a shame that we generally don't have this capability for production software running at scale.

That's why I'm working on Side-Eye [1], a debugger that does work in production. With Side-Eye, you can do something analogous to print debugging, but without changing code or restarting anything. It uses a combination of debug information and dynamic instrumentation.

[1] https://side-eye.io/
You're criticism is an apples vs. oranges strawman. LLVM IR and libraries provide powerful plumbing. It's not meant to be a turn-key or cookie-cutter solution, or inherently memory-safe VM or compiler generator. It's also not formally verified and written in C++, which adds project configuration complexity and C++ pitfalls. It's possible to plug in a custom GC using their strategy model their way, or manage GC yourself like Pony does because it's built around ORCA.
For non Linux there's Microsoft's WinDbg integration of their (very capable, as I understand it) time travel debug tool: https://learn.microsoft.com/en-us/windows-hardware/drivers/d...
Built a 40-person agency in 3 years. The brutal truth about growth
On paper, we're living the web design agency dream:

- Top-tier clients (Jasper, Kajabi, Riverside, Sequoia Capital,...)
- 40+ talented employees
- 7-figure ARR

The reality behind the scenes:
- Haven't taken a proper vacation in 4 years
- Work 12+ hours daily, including weekends
- Constantly worry about keeping clients happy and employees paid
- Most of the revenue goes back into growing the business
- Miss important family events because "something urgent came up"

Success looks different from the inside.

Not posting this to complain or flex or anything. Just want to share the full picture for those dreaming of scaling their agency.
The extra day off is probably equivalent to getting paid ? Last time I had on-call part of the job, I think the pay increase for standby would have amounted to roughly 8h as well (actual interventions were also 150% for regular nights and Saturday, 200% for Saturday night and Sunday)

Lugging around a laptop and the on-call phone when going anywhere, checking every now and then when the phone was not with your for a while (e.g. pool, gym etc), making sure you don't go places with no signal was enough of a PITA that knowing we were paid every hour of that had a nice psychological effect.
no mention of Qdrant in vector databases? Huh?
1,400 Pegasus spyware infections detailed in WhatsApp's lawsuit filings
I can still smell the unboxing of my +3 on Christmas Day.
Yes, but you can repeat your print-debug-loop once a second, maybe even faster. Hit play and look at the output. Hit play again and see if it changed. It may or may not turn up the concurrency issue.

Stepping through with a debugger will take you at least a minute per cycle, won't turn up the concurrency issue, and will spend a great deal of your daily concentration budget.
Applying Test-Driven Development to Detection Engineering
And for that a proper tracing tool will make you faster and help you solve problems easier.

Just like printing, a debugger would be a suboptimal tool to use for that usecase.
Cyberattack at French hospital exposes health data of 750k patients
This depends a lot on your stack. If we're talking about concurrency issues in a multi-threaded systems-level program, you're probably right and I can't speak to that. But as a web developer when I talk about concurrency issues I'm usually talking about race conditions between network requests and/or user input, and print works fine for those. The timings at fault are large enough that the microscopic overhead of print doesn't change them meaningfully.
Concise argument for print debugging:

Print debugging is how you make software talk back to you. Having software do that is an obvious asset when trying to understand what it does.

There are many debugging tools (debuggers, sanitisers, prints to name a few), all of them have their place and could be the most efficient route to fixing any particular bug.
The comment said as they do to musk and his businesses.
Downloading doesn't work at all.

I enter the URL and I get: "Twitch URL or ID not found."

Clip used: https://www.twitch.tv/t2sde/clip/KawaiiChillyCarrotDancingBa...
I felt the same way. But after a second it was again sort of interesting to me wondering if it generalizes so that a 4D space can be tiled by a shape with only 3D portions meeting at an angle.
The US owes it to the Vietnamese people to clean up the arsenic, but of course they're never going to do that. I know several elderly Vietnamese who developed leukemia after serving in the war.

If you eat rice, please eat white not brown, parboil it with a ratio of 4:1 water to rice, and dump the water afterwards [0].

https://www.sciencedirect.com/science/article/pii/S004896972...
GNS3 work pretty good
I love print debugging. It gives precise and fast information without any prior setup and when I am fully aware of every bit of code I wrote, it never misleads me.
That seems like a reasonable explanation lol
Egoless Engineering: Misery Is a Bad Proxy for Results
I've also had Computer Networks, 1st Edition by Tanembaum as my textbook back in the days.

Nowadays, you will be much better of with Computer Networking: A Top Down Approach by Kurose now in 8th edition:

https://gaia.cs.umass.edu/kurose_ross/index.php

There's also videos by Prof Kurose himself teaching from the book from Youtube, and additionally the ppt slides and exercises are available without registration unlike many textbooks.

I think the book set a very high standard on how textbook should be written and presented (any subject not only computer networking).

Fun facts, the 1st edition already logically and fundamentally separated forwarding and control planes for better understanding even before the modern software-defined networking (SDN) was proposed. The newer editions already have forwarding and control in separate chapters, nice.
For Hi-Fi systems, MDI was skeuomorphism too. Actual sound systems had separate boxes that did graphical equaliser function, amplifier function, tape function, CD player function, etc.

When portable CD players were still chunky companies would give them a bit more funk, buttons that followed the curves of the device and such. Similarly, before MP3 players went tiny there was some extra space for a bit more design that some Winamp skins would mimic.
Can it be that black holes are mainly eating dark matter?

Or maybe they already proved that black holes consume some dark matter but at a much lower rate to explained this.
>it left me wondering if you could tile 3d space with edge-free shapes.

Probably not, but maybe a 4D space lol
With a shift to renewables, will oil production's end come sooner than we think?
Don't duplicate what already exists worse except as a brief experiment or for learning. For real use, it will just cost money and time to fix and support for no reason.
None of my friends who graduated with me are still software developers and I’m several years from retirement age.

There’s a bunch of filters. Many people quickly realize they don’t enjoy development, next is openings in management. One of the big ones is at ~40 you’re debt free, have a sizable nest egg, and start thinking of you really want to do this for the next 20 years?

A part of this is the job just keeps getting easier over time. Good developers like a challenge, but realize that the best code is boring. Tooling is just more robust when you’re doing exactly the same things as everyone else using it, and people can more easily debug and maintain straightforward code. So a project that might seem crazy difficult at 30 starts to just feel like a slog through well worn ground.

Having significant experience in something also becomes a trap as you get rewarded for staying in that bubble until eventually the industry moves on to something else.
> The point is that Othello GPT is not in fact playing Othello by 'memorizing a long list of correlations' but by modelling the rules and states of Othello and using that model to make a good prediction of the next move.

I don't know how you rule out "memorizing a long list of correlations" from the results. The big discrepancy in performance between their synthetic/random-data training and human-data training suggests to me the opposite: random board states are more statistically nice/uniform and suggests that these are in fact correlations not state computations.

> This is evaluated in the actual paper with the error rates using the linear and non linear probes. It's not a red flag that a precursor blog wouldn't have such things.

It's the main claim/result! Presumably the reason it is omitted from the blog is that the results are not good: nearly 10% error per tile. Othello boards are 64 tiles so the board level error rate (assuming independent errors) is 99.88%.

> The multiple comparison problem is only a problem when you're trying to run multiple tests on the same sample. Obviously don't test your probe on states you fed it during training and you're good.

In practice what is done is you keep re-running your test/validation loop with different hyperparameters until the validation result looks good. That's "running multiple tests on the same sample".
Not so much. I have personal involvement that informs my opinion.
This is the exact realisation that made me take a second look at FP around 10 years ago. I haven't looked back since. I certainly couldn't debug concurrency issues in imperative code when I was young and sharp, but at least I tried. Now that I'm old, if I get a concurrency issue, I'll just file a ticket and grab a coffee instead.
GUD: An open USB display protocol
ZX80 iirc had to be built by the owner. Possibly the '81 too (memory fading but my brother was the "softie" in the family and I was the engineer so I got to solder them together for him). The spectrum came pre-built, significantly expanding the target market. The '80 followed on from Sinclair's previous products which were mostly user-assembled (MK14 and some of the calculators). The very first Acorn computer also iirc was self-assembled.
I understand the frustration Europeans have with watching america get richer and richer while experiencing lower rates of growth themselves, but Europe is doing pretty damn well in almost every respect except comparison to the US and China. But if you also want to sell your society out to the thick-skulled morons that run our market, go right ahead.
Nope, I don't think so.

We (at FusionAuth) started out the same way, hyperfocused on the needs of bigger customers. It was super helpful, because nothing indicates commitment on both sides in devtools like a customer paying money and a devtool company building out a solution.

It also sharpens the team's intuition about what other customers will pay for, as long as you are aware of the market and competition and other solutions. What you don't want this to lead to is being a consulting company for 1-3 big customers.

Having an OSS or freemium option (as we do, and Lago does) is a great counterweight to customer demand, pulling the devtool company towards community needs.

As you grow, you have more constituencies, and that means that your pool of time to do concierge work for a larger prospect goes down. It doesn't disappear, but it decreases.

While we have a product vision we execute against (and I'm sure Lago does too), pulling work forward based on customer demand is a great way to prioritize pieces of it.

However, the bigger you get, the more competing voices you hear. When you have limited time, do you focus on:

* work needed to land big customers

* work needed to land smaller, self-serve customers

* work to support existing customers

* work to support the community

* strategic work that will pay off in months or years

Some of these categories overlap, of course, and that's what you want. You try to do it all, but you can't do everything you want. You have to build against the vision while also allocating enough time to support current needs.
How to give a good 20 minute math talk
this exfiltrates data somehow? looking forward to the poc
Dude, I went through the European PhD system and it's not as glamorous as you depict it. First of all, you forgot to mention that the norm is to give contracts of 50% to 75% FTE. Secondly the hours worked and the vacation time is a complete forgery that you are basically forced to sign. Although the contract is nice on paper, in practice the norms and expectations are different. Thirdly, unlike in the US, in Europe you often don't have a graduate school (although it is a thing) so you are in a very vulnerable situation where you invest 3 to 5 years of the best years of your life and during those years your graduation is completely at the mercy of that supervisor.
> "Heavenly Numbers: Astronomy and Authority in Early Imperial China" by Christopher Cullen

I'd be curious for a book about the ~1500s AD, roughly when the Europeans/Jesuits initially showed up, and the ~1600s (post-telescope), and how the various worldviews interacted.
Solving LeetCode problems with Racket: I don't know what I expected
Seems pretty run of the mill. I can’t think of a good I’ve purchased recently that was made 100% by a single source.
Great implementation, very enjoyable. Any chance that you will use this foundation to make an actual game (I mean, challenging, with scores/time/etc., and without the marketing component)?

I have always missed a worthy sucessor to Marble Madness. I have tried several partial implementations or demos inspired on it, like this, but never an actual full game with the same philosophy (maybe there's some I'm missing, in which case I would like to know, of course).
I've had similar experiences on a with various ideas for compilers and for C++ debugging.

Although I'm my case, the other people were mostly at FAANG companies, rather than academia.
After spending all week reviewing and commenting on gdocs, I have to say that the Papyrus interface looks really beautiful. I love how they implemented sticky notes!
Performance optimization is an excellent example of exactly the opposite. Why thinking first, creating the model of the code, to put a trace, metric, log call is better than mindless debugging. Interactive debugging has its uses but it may be less than appears at first and it encourages the wrong thing (local focus, irrelevant details). You should ask yourself first how fast the code should be and why (build the model), and only then measure. Learning happens when you get unexpected results. There is a limited utility in running profilers without a thought.
As Telstra put it, after making all public payphones free in Australia: "Hugh Jass, Anita Bath, and Ivana Tinkle are always welcome at our payphones".

https://x.com/Telstra/status/1428566347491909640
Schwab. I worked across from it in the reclaimed basement of Toyon like some sort of hidden Brazil ductwork steampunk menagerie for workers. Their IT department was well-regarded because each department did their own thing, which was inherently efficient in flexibility, control, and service but not in cost of delivery. I was an obsessive control freak, wannabe computer science researcher, and LTT-like PC putter-togetherer masquerading as a Windows sysadmin playing with a $100k budget trying to get barcodes on every single cable, every single asset tagged, inventoried, and reporting basic info 24x7, having everything racked in a real datacenter rather than the housing draw NetBSD "server" desktop going brrrr behind my head, and adopting DR/BCP so that the organization could survive another semi-malicious Microsoft RCE worm or maybe a building fire (the datacenter had FM200).
I do sometimes use print debugging despite having (in my opinion), a decent knowledge of the debuggers in the toolchains I use. Part of is that you could set a conditional breakpoint for a condition, if you know what it is, but sometimes you're just probing to see what differs from expectations, and putting every expectation into a conditional breakpoint is a pain with most debugger UIs. In theory you could use logpoints instead of print statements, but again the UI for this is often a pain compared to just typing in print. And even when you get to the breakpoint, you'll run into the dreaded "this variable has been optimised away" increasingly in modern languages, and it also doesn't give you a history of how it got there - maybe if rewind debugging was more commonly supported that would help, but it isn't.

Also suspending a thread to peek around is more likely to hide timing bugs than the extra time spent doing IO to print.
Print logging is pretty good for concurrency IMO because it doesn't stop the program and because it gives you a narrative of what happened.

If you have a time travel debugger then you can record concurrency issues without pausing the program then debug the whole history offline, so you get a similar benefit without having to choose what to log up front.

E.g. use Microsoft's WinDbg time travel integration:
https://learn.microsoft.com/en-us/windows-hardware/drivers/d...

Or on Linux use rr (https://rr-project.org/) or Undo (https://undo.io - disclaimer: I work on this).

These have the advantage that you only need to repro the bug once (just record it in a loop until the bug happens) then debug at your leisure. So even rare bugs are susceptible.

rr and Undo also both have modes for provoking concurrency bugs (Chaos Mode from rr - https://robert.ocallahan.org/2016/02/introducing-rr-chaos-mo..., Thread Fuzzing from Undo - https://undo.io/resources/thread-fuzzing-wild/)
The Myths That Made Elon Musk
Indeed - correct!
How do I use this? When I enter an address in the search box it just comes up with "Error:". There is no map showing.
OpenLook would like to have a word about those corners…

(But yes, in general it's all custom "cards" and list views. HTML didn't allow a good set of GUI widgets, so people adapted, and now the cruel circle has closed with desktop UIs being "informed" by web and mobile views)
> corners by the definition I would use

You would speak of "vertexes". Tile a 3d space with cubes: you'll have faces, edges and vertexes. Curve the edges in smooth paths ("with continuous derivatives"): the vertexes disappear. But the equivalent of the 2d "corners" remain, as apparent in the 2d sections: no miracle happens.

The interesting part is the induction that by adding a dimension we may lose a "constraint".
Because name implies that car is going to drive itself. If it does not it is a deceptive marketing, false advertising or a fraud.
https://archive.ph/f3tMW
> "your perspective is incredibly dismissive of the real reasons iOS is gaining market share."

I do not know the real reasons, but I have heard 2 things repeated often:

1 -- the ability to work smoothly with other apple products, which is sort of a circular argument, but it makes it harder or costlier to switch away from apple, so could tend to increase market share.

2 - There were a ton of recent articles about teenagers being made to feel inferior for having an android phone instead of an iphone, which fits with the fashion aspect.

There are of course other reasons why people say they prefer iphone, but I find it difficult to distinguish what people think is better from what they are simply already accustomed to.