skysight-inc/HackerNews huggingface dataset:
Demand for AI is driving the derivative of demand to go up, breaking forecasts.

I wonder how much money will spill over from AI investment into the power plants needed to support them. they're not going to stop a data center from coming online because there's no power for it, they're just going to build power for it.
> and per watt

Part of the advantage of using "one 4090" is that the max TDP is only 450w, as opposed to 5 M2 Ultras running at ~150w each. When you scale up to Nvidia's latest Blackwell architecture, I genuinely don't know how Apple could beat them on performance-per-watt. Buying M2 Ultras wholesale is probably cheaper than an NVL72 cluster, but certainly not what you'd want to use for Linux or maximizing AI-based performance-per-watt.
Picotouch – Tiny Capsense Touch USB MIDI Keyboard from a Raspberry Pi Pico
Computer-Checked proofs are one area where ai could be really useful fairly soon. Though it may be closer to neural networks in chess engines than full llm's.

You already use tons of solvers because proving everything by hand is mind numbingly tedious and time consuming, but tactics/solvers really struggle if you throw too many theorems and lemmas at them. Neural nets as search machines to pattern match relevant lemmas fit perfectly.
Similarly induction and higher order unification are full-on code synthesis where brute-force iterating over all possible syntax trees is really inefficient.

And solvers do a backtracking solve anyway, so if the ai returns 95% irrelevant lemmas it doesn't matter. Still would be a dramatic improvement over manually searching for them.

Though I'm not convinced that computer checked proofs are necessarily good for communication. There are reasons beside page-count that proofs for human consumption are high-level and gloss over details.
Airport came out in the beginning of the year, maybe January, at Macworld. WECA renamed themselves the WiFi Alliance a few years later, but the name (and trademark) had to exist for it to be worth them doing so.

WECA reminds me of other "memorable" names of the era, my favorite being PCMCIA, though VESA is another fave.
There's ways to black out windows and darken rooms to counter all of that daylight, but when it's dark it's really hard to counter that when going outside.

Without actually personally experiencing it, I think I would have the opposite struggle. If it were dark for that long without clouds so I could have all of that extra time to view the sky I think it would be a much different situation though.
What Type of Voter Are You? Take Our Poll to Find Out
All of these have happened to me:

- The interviewer is wearing a suit.

- The interviewer asks "you've worked with [person who now works at our company] before, what do you think about them?". Bonus points if they insist after I give a diplomatic answer.

- "Why are you using microservices?" "Because everyone is doing it"

- Not following up. For weeks.

- "Can you send us your high school diploma?"

- Take home assignment with a time limit.

- No feedback on take home assignment except "we didn't like your approach".

- Developers use separate laptops for coding and for internet access.

- There are three architects on a single project.
If you've got a Kobo, Pocket seems to recognize it as an article (it often doesn't) and renders it well enough.

EDIT: Nevermind, Pocket only captures the preface (first four minutes, basically).
Back when in-person interviews were a thing, I’d use the opportunity to just look at the office space.

Specific red flag signals:

1. Dominated by Windows

2. Too many people in formals

3. Nobody wears badges (and other indicators of a lax security policy)

4. Old/worn out office furniture

5. Low resolution displays

6. Old laptops

7. No evidence of people collaborating or chatting at a microkitchen etc.
Have worked with several trans folks at major legacy corps like IBM and while I'm sure there may have been rank-and-file issues, discrimination was not tolerated by mgmt in the latter 90s. My memory is IBM and HP added non-discrimination policies around that time.
Easy solution; just swap multiple gigabytes of your model to SSD-based ZRAM when you run out of memory. What could possibly go wrong?
Show HN: Epidemik a Python package for epidemic simulation
Hi everyone,

I'm happy to share `epidemik`, a Python package for epidemic modeling.

Epidemik, currently supports:

- Homogeneously mixed Model: Easily define compartmental models by just specifying the transitions and rates

- Age Structure: Convert any compartmental model to an age-structured model by simply adding an age contact matrix and a the population of each age group

- Network Model: Easily define epidemic models running over an arbitrary network structure

- Meta-Population Models: Define metapopulation model

In a previous life (circa 2008-2012), I worked as the leading developer for a large-scale epidemic model so when CoVID hit I wrote a series of blog posts (see https://github.com/DataForScience/Epidemiology101) working through the mechanics of how this kind of model works. Epidemik is the result of all the code that got written during the lockdowns, and in the years since that, I finally cleaned up and decided to publish it in case others find it useful (perhaps as a teaching tool?)

This is my first package, so feedback, comments and suggestions are definitely welcome.
Search Engine's Blindspot: Continuity and Context
> are there services which don't support [non-TOTP MFA]?

Yes, there are many which still only support SMS MFA -- and if you meant TOTP-On-Yubi, that's its own can of worms (limited size, [intentionally?] hard to sync or backup, vender lock-in?). I hope passkeys lead to brouder FIDO/U2F support.
Yeah I've got a variety of dev boards already, but thought moving away from that as part of a move to PCBs might make sense. Esp given the cost diff - raw rp2040 seems to be at least 1/5 of the dev boards. Dev boards are probably the better deal overall, but also less scope for learning
No it doesn't.

It could just be that some food is the catalyst to it, but not the cause.
Good topic for Pride month
The problem with rare earths is you get a mix of different rare earths in the final concentrate, which then have to be separated from each other using a lot of time-consuming steps, since they're vary similar chemically (technically, having identical d- and s-orbital configurations, only differing in f-orbitals). An active area of research:

https://www.ornl.gov/news/game-changing-rare-earth-elements-...
Please do mention about the complete sea, air, and land blockade of Gaza, when you do that. You can mention the raid on Gaza freedom flotilla as well.

While Israel supposedly disengaged from Gaza, it had conducted similar attacks with hundreds of human casualties under the pretense of operational readiness, training, and the notorious mowing the lawn operations.
Of course some of them were so called retribution and responses, which mostly begins by rockets on Israel soil, but not by the brutal oppression it administers to Gazans.
CryptAttackTester: high-assurance attack analysis
You cant beat an insurgency without local support. The Tamil Tigers are the most obvious case, but all the other ones you mentioned involved settling the disputed territory. Israel is nowhere close to squashing Hamas
https://archive.is/mvzRh
High frequency traders provide liquidity—-making it unprofitable would reduce liquidity and increase the bid/ask spread of all stocks.

What you propose would mean more profits for market makers and less profits for retail investors.
So it's perfectly fine for Norway to trash the planet, and profit off of nestle doing shitty things in Africa? Because it's good for one group of people, at the expense of others?
US proposes banning medical debt from credit reports
When they start describing the dysfunction in their team or the org as a whole. One interviewer talks about a "legacy team" that needs help "modernizing" and "migrating to the cloud", and then you talk to the "legacy team" and they don't think they need any help. Or they're just a collection of acquisitions with no standardization. Or they try to avoid talking to corporate IT about anything. Or they regularly get woken up at 3am on-call. Or they deploy less than once a week, or need someone to manually validate it and schedule it and have all-hands-on-deck. Or you ask about test coverage and they laugh. Or they have one database for 100 services. I don't find a ton of huge deal breakers, but a lot of "ehhhhhh......." things. The biggest deal breakers are attitude and culture, whether the business creates abusive demands on employees, signs of poor leadership, disorganization. And pay. The business shows you what they really think of you in their offers.
Yup. During the big initial wave of Covid. He was living in New Jersey at the time after retiring from a career at Princeton.
Exploring PostgreSQL 17: A Developer's Guide to New Features
In Java, typed exceptions are now considered an antipattern, because it caused problems in multiple parts of the language such as in lambdas. Results from rust tend to be more composable.
Pompousness and self importance, we all get interviewed at some point don't power trip, it should be a humble two way conversation.
Development costs money and that's fine, but I don't like it when companies act like their pricing is based on the cost of providing a service, and the service is "syncs a single sub-megabyte file between a few devices". You can get that service a thousandfold for free. (And even if they give you more space, that's a worthless addon to almost all customers.)

In particular, the reason it's annoying to sync keepass is because of how the program is designed. There are other managers in that ecosystem that let you log in to google/microsoft/dropbox/anything and then you're done. It all syncs perfectly from then on. It's a development problem, not a need for a dedicated service tied to a specific password manager.

And when I'm considering development cost I'm going to look at things on a 5 or 10 year timeline. I think that's a reasonable length to expect a software purchase to last. On that timescale, Bitwarden is okay but 1Password is not at all a good price.
Postgres Table Replica Identity
How to Shrink Rust
It's very attractive, but even as a 100% distraction-pilled person, my phone really needs Whatsapp, Signal and Spotify to be viable. Much of a phone is unhealthy mind garbage but not all of it.
I like working at places small enough that we don't need badges because everyone just knows each other. I remember way back at an old company (that was quite large by the time I joined) learning that someone had quit rather than wear a badge as the company "grew up". I thought it was nuts back then, and I still would be willing to make that compromise myself, but I get it a lot more these days.
Exactly, secrets management is a really critical need that 1Password meets for me, and I'd much rather they charge me an honest price than sell out to advertisers. These things require upkeep (not just defending against everyone trying to break in, but also keeping current on the latest technologies like passkeys), so I find the yearly price of admission is totally reasonable for 1Password's quality and importance.
>If you're competing with X, you can't just not do a thing X is doing

this simply isn't true

there are reasons to compete, like not lose the share of those who find that feature important, or to attack the profitability of that service for your competitor

but there are reasons not to compete, like losing too much money and not impacting your competitor.

This is why Google and Apple as corporations barely look alike at all.
If they have the company values written on the wall, it probably means they don't actually live them.

Engineering leadership doesn't understand (or care about) the business side.

Trying to shoehorn you into a role obviously you're overqualified for.

A focus more on time spent and dedication rather than achievements and outcomes.

No clear business model. Maybe it isn't an issue today, but for 99% of businesses it will be an issue soon.

A pattern of getting interns or juniors to do an initial chunk of work, and then getting seniors to clean up after them, rather than letting seniors lay a foundation and the juniors/interns filling in the gaps.
I always have to default to the Simon Tatham version of whatever. Bookmarked!
Interesting. I've done both desktop app dev and web dev professionally, in both cases complex applications that required localization etc. I still found the traditional C++ desktop app a better developer experience. It's significantly more straightforward, and I could be more productive of the simpler mental model of "OS runs application, calls out to thin GUI abstraction layer which calls out to either Cocoa or win32" vs "backend runs on service fabric in one of three different data centers, calls out to x different DBs and y different microservices, user connects to it via frontend after auth (another can of worms) via roughly a dozen different common configurations, but we're only going to test with Chrome on Windows, using TypeScript and an unholy combo of three different frameworks because the frontend team keeps chasing the new hotness"

Web dev just feels insane to me. The amount of logistics and infrastructure and tooling you need[0] is beyond the pale.

[0] "need" is maybe strong, but in an enterprise setting like I was that's what you have
Ah, OK. Thank you.

My question was how "pertinent and important" is determined since those are very subjective criteria.

I would say that you're aiming for "high quality" instead, which is a fantastic (and more realistically achievable without knowing your reader) goal.
"Take home assignment with a time limit."

What's your concern there? (Honest question!) I feel terrible about asking for home assignments but I feel like it's good for people like myself who are terrible about coding live. (I usually have a choice of live or homework.) I put a "limit" as a guideline about what kind of quality to expect, usually with language about things not to worry about. I don't expect/want folks to burn a bunch of time on things.
Yeah, there is one flaw that I recently noted: how does the HSM authenticate legitimate users?

Like "I am an app, dear HSM, please perform following crypto operation for me."

If an attacker can pretend to be a legitimate HSM user, then she does not need key access, she just asks the HSM to perform a crypto operation on her behalf.

On the other hand, if the HSM needs secrets in order to authenticate legitimate users, then those secrets are prone to those attacks, against an HSM shall protect.

Or dont i get it?
https://forums.raspberrypi.com/viewtopic.php?p=1837408&sid=6...

I haven't seen a more recent update, unsure if they abandoned the patent bid or if it's just taking a while to go through the system.
Wait till you find out about diesel generators!
Reasonable point to point out.
> humans aren't great at it

Yeah that's fine, although my point is that being unable to figure out the return type is a symptom of a bigger problem imo. It means we're outsmarting ourselves.
That's a bit rude isn't it? Please consider instead choosing not to reply if you don't want to discuss a topic.
Why not Taco Tuesday?

(I ask with all seriousness; I'm kind of hoping the answer is interesting)
The entire top part of Denmark is missing. Everything above Limfjorden is missing, leaving a weird grab between Denmark, Sweden and Norway.
If all you're doing is normal word processing / browser things, this basically sounds like a good enough daily driver.

Add in a fold, and some folks could probably live with a single device across all use-cases, and it'd simply be better because of not needed to sync files.

It might not be good, but not because the idea is bad.
Sorry to hear about that. I am not an admin so I can only do exact searches in the Deletion Log https://en.wikipedia.org/wiki/Special:Log?type=delete&user=&... and so I was unable to find the original article. Do you happen to have the contents of the page somewhere (I understand if you don't)? I will try to create the stub article with sources somewhere and see if I can defend it sufficiently this evening.

EDIT: I was able to find the draft deletion over my lunch break! I have requested an undelete here: https://en.wikipedia.org/wiki/Wikipedia:Requests_for_undelet...

But this evening, I can just create the article directly. Not because I have any particular authority but just because confirmed users from a long time ago can do this. If the draft is undeleted, I can recover your work! If not, and you still want to, I'll send you a message when I create the article and you can add to it. Totally understandable if the last experience soured you on it and you'd rather not.
> Decoupling capacitors need to be placed "close" to the chip

All of these rules are just rules of thumb.

The "rule" is that your Power Delivery Network (PDN) needs to have low-enough impedance to function properly. High parallel capacitance and low series inductance/resistance. Longer leads increases inductance and resistance so closer is preferred.

But for even 100MHz designs, you're well under the size where 100mil or 0805 would cause any serious problem.

-------------

So the "secret" is that all faster designs (100MHz to 300MHz) have substantial on-package capacitance.

Take a look at this design, which I admit is Microchip/Atmel MCU, but its running at 300MHz and not just the relatively low 133MHz of the RP2040.

https://lcamtuf.coredump.cx/bob-the-cat/

Those are LARGE 1206 1uF capacitors. Which is actually scary to me because we're not looking at tight 100nF decoupling caps anymore but instead substantially relying upon "on-package" capacitance.

Still, it shows that lcamtuf was confident in this 300MHz processor handling far-away 1206 capacitors, showing how much wiggle room we have in practice in these designs.

You shouldn't worry about 100mil of movement of 0805 caps on a 133MHz design. After all, there are real designs that are closer to 500 mil that use 1206 caps on a 300MHz MCU.

--------

I'm honestly scared for lcamtuf here and would never design a board like this. But I'm really not worried about 0805 caps on relatively low speed 100MHz (or even 133MHz) MCUs. Especially if you're properly "teaming" them up so that their resistances are paralleled and inductances are paralleled. (Notice that lcamtuf's 300MHz design doesn't even have the 10x recommended parallel 100nF capacitors close to any of the pins!! He's really stretching the specs)

-----------

But yeah, my personal preference is majority of 0805s and 0603s for the "close" decoupling capacitors. I know there's plenty of wiggle room here (even if I'm not as aggressive as lcamtuf's designs).

If you're using PCBA from another shop, I guess its all "free" to you to use 0402s or whatever they got loaded in their chip-shooters. So might as well take your free pre-loaded resistors. But if I'm assembling a board myself, I definitely prefer the larger size.
Oliwa is a district of Gdansk and not the city itself. Up to 1926 it was indeed independent but way smaller.
Communist countries built large cities for pedestrians and public transit. I grew up in a place like that, it was an amazing place for a kid. School was a 5 minutes walk away, there were hardly any cars within hunrdeds of meters of my building. There were large green yards, playgrounds etc. for kids. Very quiet, very family friendly. It was largely contingent on most people not being able to afford cars, and not missing them that much due to decent public transit.
All's well in Balkans. Moving along...
The ones that come to mind:

* If they are a small company who outsources any step of their interview process to another company. If you're only interviewing for a couple positions—people you will work with every single day—take the time to do it yourself.

* If they are a startup that says they are looking for people who are interested in solving exciting problems. For some people, this is going to be an enticement, but based on my experience, what I hear is "we're going to work you like a dog and pay you in equity, and at the end neither your work nor your equity will matter because we're definitely going to go out of business". I recognize this is a bias, but it's happened to me a couple times, and I'm in my 40s now and just not having it anymore. Plus, the problems are never that exciting, they're usually "how to sell a SaaS product that is basically a CRUD app, in a crowded marketplace with lots of competitors".

* If the interview is composed of like 10 rounds of 30 minute interviews, each with different groups in the company, that to me is an indicator that Conway's Law is at the helm of that organization: lots of groups that want input into everything, nobody empowered to make a decision on their own. Plus, it's just not a very good format. Give me a smaller number of hour long sessions where we can actually get into it, rather than racing through pro forma questions.
After my last move I ended up in a bedroom with excruciating amounts of windows letting in so much daylight you'd probably get a sunburn if you didn't get up. I "fixed the glitch" but I was thinking that it would make a great alarm to set up a lot of overhead lighting (such great LED fixtures these days) and ramp them up slowly to full power over say a half hour. And leave no way to shut off :-)
The precision argument is so amazingly bogus that I won't refute it except with a link[1], so here are refutations of some other parts:

> My kids sometimes ask me how high I can count. I’ve noticed that they stop asking this question once they reach a certain age, usually around six or seven. This is because the question does not make sense once you understand what a number is. If there’s a single highest number you can count to, you don’t really grok numbers. The difference between computers and humans doing math is a bit like the difference between the younger kids who think that “how high you can count” is a real thing and the older kids who have successfully understood how numbers work.

There actually is an answer to this; most people's short term memory for digits is less than a dozen, so the author likely can't count higher than 1e12, as they won't be able to go from e.g. 374841483741 to 374841483742 without getting one of the digits in the middle wrong.

> The representation of the numbers that occurs only in the mind of the human is conflated with the execution of a particular program that takes place in the computer

This merely argues that computer math can be different than human math, which even that I'm not quite going to concede, since it would imply e.g. that the mathematicians behind the IEEE 754 standard were unaware of the implications of
floating point arithmetic.

> To us the transition between the theoretical and the actual happens almost instantly and unnoticeably.

Indeed it is happening almost instantly and (being generous to the author) without the author noticing throughout this paper, conflating concepts to the point where one could demonstrate almost anything is beyond the reach of computers, even things that are clearly well within the reach of them!

1: https://github.com/stylewarning/computable-reals
I appreciate her making the effort to tell her story. I struggle sometimes to understand what it means when people say they feel born in the wrong gender. They way she describes it - not just about wanting to do 'girl' things but wanting to be soft and round and feminine - is eye-opening for me.
I'd agree here. As a trans parent I have worried about what living an often non-socially acceptable lifestyle would do to them. But then I see the acceptance as my daughter proudly introduces me as her "mama" to her whole class. I'm a better parent alive living my truth than I am an "unalived" parent leaving a gap for those that loved me for me.