Please search for "food deserts"
Readit Newsthrowaway7783 commented on Job-seekers are dodging AI interviewers fortune.com/2025/08/03/ai... · Posted by u/robtherobber
throwaway7783 commented on Atlassian terminates 150 staff cyberdaily.au/digital-tra... · Posted by u/speckx
Needing to cut 150 people suggests catastrophic mismanagement. I get that workloads change, orgs pivot, business has to do business shit, but if you've missed your headcount requirement for whatever work you needed to do by a HUNDRED AND FIFTY PEOPLE!? What even.
Management and leadership is practically a lost art these days, so many organizations are just filled with managers who haven't the first fucking idea how to actually manage people.
All that said to be like: "Well how SHOULD we correctly fire 150 people?" I dunno, to me that's like saying how do I hit a tree with my car in such a way as to make sure I'm not paralyzed? Like so much has already gone wrong to bring you to where this is a pertinent question that I don't think there's really a right answer at this point, there's just gradations of bad.
150 people is less than 1.5% of their total number of employees (12,157 per google) . That is not a catastrophic overestimation.
Unfortunately there is no approved oral medicine to lower Lp(a) that I am aware of. (I mean given a normal LDL.) Statins don't lower it afaik. An oral medicine named muvalaplin is being tested for it.
There are some in trials. I'm part of one by Eli Lily. Lp(a) sucks, is genetic and so far there was no medication.
My cardiologist pointed out that hard calcified plaques are unlikely to come loose, so unless there’s significant narrowing, they’re not a big problem. However, that situation correlates with a high calcium score. So the calcium score is not always correlated to risk.
A CT angiogram distinguishes soft vs. hard plaques (and shows narrowing), so that’s the ultimate way to clarify the situation. (Bearing in mind radiation exposure risk and cost, of course.)
Calcium score is mostly for trends over a period of time, to get a sense of progression of disease. A single reading is not very useful is what I was told
throwaway7783 commented on Keep Pydantic out of your Domain Layer coderik.nl/posts/keep-pyd... · Posted by u/erikvdven
Return of Java DTOs!
throwaway7783 commented on It's time for modern CSS to kill the SPA jonoalderson.com/conjectu... · Posted by u/tambourine_man
HTMX does the opposite of this, it requires many more round trips to the server instead of using client side JS to do work.
I meant for the SPA-like experience.
throwaway7783 commented on It's time for modern CSS to kill the SPA jonoalderson.com/conjectu... · Posted by u/tambourine_man
SPA is not only about seamless transitions but also being able to encapsulate a lot of user journey on the client side, without the need of bothering server too much.
Let me give you an example - one of my biggest gripes about web ux is the fact that in 2025 most shops still requires you to fully reload (and refetch) content when you change filters or drill down a category.
A common use case is when you come to a shop, click on "books" (request), then on "fantasy" subsection (another request), realize the book you're looking for is actually a "sci-fi", so you go back (request, hopefully cached) and go to "sci-fi" (another request).
It's much better ux when a user downloads the whole catalogue and then apply filters on the client without having to touch the server until he wants to get to the checkout.
But it's a lot of data - you may say - maybe on Amazon, but you can efficiently pack sections of most shops in data that will enable that pattern in less kilobytes that takes one product photo.
I've been building web apps like that since ca. 2005 and I still can't understand why it's not more common on the web.
HTMX (and similar) solves a lot of this. It so happens that we end up building two apps one frontend and one backend with SPAs as built today. I'd rather build a lot of it on the server side, and add some dumb interactivity on the client (show/hide, collapse/expand, effects). There is still a place for SPA though.
A charitable interpretation is that it is a form of democratic control of wealth (neighbours decide what you do with your land) rather than individual control of wealth (building however many stories you want on your own land), and democratic control of wealth is definitely closer to communism than individual control of wealth
Yes, I agree. extending that logic, democracy in general is closer to communism, than to oligarchy (extremes on either side, ignoring feudalism ), but its not communism. I simplify the "isms" with communism - socialism - democracy -capitalism - oligarchy , extremes at both ends generally not good to society at large.
throwaway7783 commented on Parsing Protobuf like never before mcyoung.xyz/2025/07/16/hy... · Posted by u/ibobev
Thanks, I added it to the list. Keep in mind that the numbers may be off (both yours and mine), so I would not take them at face value. It is interesting how in yours JNI is still pretty good. Also Rust is "~5–20 ns" in yours, so I assume "0" is the baseline.
This is chatgpt. Not my own benchmark. So it is probably hallucinating
For any job-hunters, it's important you forget this during interviews.
In the past I've made the mistake of trying to convey this in system design interviews.
Some hypothetical startup app
> Interviewer: "Well what about backpressure?"
>"That's not really worth considering for this amount of QPS"
> Interviewer: "Why wouldn't you use a queue here instead of a cron job?"
> "I don't think it's necessary for what this app is, but here's the tradeoffs."
> Interviewer: "How would you choose between sql and nosql db?"
> "Doesn't matter much. Whatever the team has most expertise in"
These are not the answers they're looking for. You want to fill the whiteboard with boxes and arrows until it looks like you've got Kubernetes managing your Kubernetes.