skysight-inc/HackerNews huggingface dataset:
Wow were you able to see the future?
There is a name for what you are saying but I do not remember what it is called false dichotomy?
- Option 1: Kill 200k.
- Option 2: Do not kill 200k

Which one do you choose?
I used to think like you, until my brother committed suicide from loneliness and rejection. I look at his suicide note every so often,and worry about my boys. Most men absolutely care what people think, and want to make other people comfortable. My brother, my father, your wonderful friends, probably do too.

Women and men have very different burdens, and its extremely clear the grass is not greener on the other side. Most people are not the high performing ruthless psychopathic type A personality common in Silicon Valley, New York, Miami, etc.

I'm a Korean woman that grew up in a white Surburbia, the meanest people to me were brown haired "average" white girls. They insulted my hair, my eyes, my nose, and my lack of nasal bridge, literally everything you can think of.

I believe the primate social hierarchy at play, and at our core many of us are trying to "win" that hierarchy. At the same time, I think certain types of people gravitate to cities and certain lifestyles.
My wife pointed out that the 3 minutes at highest setting they used in this study is not something you'd ever do for baby food. The goal of microwaving it is to simply knock the chill off and get the food/milk up to room-body temp. You wouldn't go further cause baby's are sensitive and you don't want to risk hot spots or burns. This means the food is never heated for much more than 30 seconds at most.
Biodiversity/species loss through habitat destruction (either directly or through anthropogenic climate change) should be one of the greatest shames of society.
Your conflating understanding biology and performing biology is very odd.

A bacterium can perform cell division, but it can't explain it. The evolutionary biologist's job isn't to personally have sex, it's to explain what happens when many generations of organisms do so.
I'm curious what you mean? Code is very much a symbolic modeling of a problem domain.
Busiest day ever for electric vehicle charging predicted on UK roads
(My fault for not specifying instant noodles.)

I understand the concept of cold noodles and all the other varieties of noodles, but to me instant means hot, maybe the branding is just too strong.

(Also I am south asian, pasta salad is rather fancy thing here)
Chip companies, top US officials discuss China policy
> 1. A low-level, open-ended language for describing infrastructure; it should have absolutely no facilities for abstraction, should be human-legible and machine-readable (so based on JSON, probably), and should be applicable to everything from configuring physical hosts and switches up to containers.

Sorry, but if it's doesn't have abstraction it's not readable. You get smothered in details. No forest, just trees. People will just create a framework that generates the file like Sass does with CSS.
Hi! I was involved in the Agile movement before the term existed. I came up through the "Extreme Programming (XP)" school of thought, and later on the "Lean" one (in the Poppendieck sense of the term). Here's my take.

The "sprint" is an artifact of the transition away from waterfall. Getting people to go from an 18-month planning cycle to a 30-day planning cycle was an actual advance. But as you are seeing, it has its problems.

If you keep turning up the dials, as the XP folks tend to do, you get to weekly cycles. Those are about the smallest effective "sprints". I like them a lot better than monthly sprints, which are much more likely to be mini-waterfall in orientation.

At a weekly cadence, you can start to see what might be beyond that. For me that generally involves a weekly meeting schedule, but otherwise a Kanban-ish flow of work with strong WIP limits and aggressive effort to keep work unit size to be well under a week.

So yes, I think you're correct that continuous delivery (which was invented well later than the original Agile methods) means that sprints no longer have a release-related reason for existing, especially when you have a good feature flag practice.

In practice, I think humans do need some regular rituals and that some planning work is better off batched, so I'm ok with keeping some sprint-like rituals, like a weekly planning meeting and a weekly retro. But I think high-functioning teams treat those as convenient sync points with flexible adaptation of plans as new learning happens over the course of the week.

And yes, I think the Agile community broadly got stuck in a mini-waterfall space rather than what I think of as actual agility, so your read there is correct too. I think the main driver of this is managerialist ideology [1], which centers managers as the vital actors in business. In contrast, flow-based processes like you describe make managers mostly irrelevant. Unfortunately for those of us who like to actually get things done, managerialism is the dominant ideology in American business, so much so that its tenets are not only mostly unspoken, but that alternatives can be unthinkable to many. So I expect things like "scrummerfall" and SAFe to continue to dominate large-company software development for the forseeable future.

[1] See https://en.wikipedia.org/wiki/Managerialism and https://www.amazon.com/Confronting-Managerialism-Business-Ec...
The urgency is often fake. You complete your sprint, only to find out you built a feature nobody needed any time soon (or maybe ever.)
Sprints do give faster feedback, early value and autonomy, but only in contrast with planning the complete project upfront in utter detail and committing to a deadline. It's a compromise. Instead of planning a whole project we just do two weeks and go from there.

Its a nice idea but it often doesn't pan out in practice. The sprint is way too detailed, the team gives too much time and attention to planning the next two weeks and too little to what comes after, often people don't really know what to do when they finish early or don't make the sprint, etc. But most of all, everything becomes this game of predicting the sprint and finishing it rather than solving the most important business problems right now. It becomes a bureaucratic thing (in a bad sense).

For me, two weeks is usually too small of a timeframe to get something really meaningful done, so the sprint goals feels like a collection of random things we stuffed in two weeks. Most people also adhere religiously to the goal of 'achieving the sprint', which pushes the team to planning together in way too much detail. Not achieving the sprint feels like failure and you will get 'punished' if only by disapproval. We should take it as feedback and rejoice in the opportunity to hone our estimation skills, but in reality it functions as a reverse gamification mechanism making devs conservative and risk avoidant.

In an ideal situation, what sprints give you is control over delivery schedules. But this control always comes with a price, and two weeks into the future isn't far enough by far. It's never free to set a hard deadline. So you pay with lower productivity in order to get higher control over schedule.

I think its better to set looser goals, have a course roadmap of things you will be working on, problems you want to solve, but don't fret over 'velocity' and 'story points', just like you are not counting lines of code produced per day. Story points are meaningless, what matters is if you have solved some problem. That is what gives you autonomy, value and feedback, not 'achieving the sprint'. Nobody cares about that.
You're asking this question of a process literally named "an unsustainable burst of speed"?

Big-A-Agile is a mechanism of naked greed to a) Micromanage employees times down to the 15m interval, and b) Ensure that the company is getting no less than 8 full working hours from each engineer[1] ... and then getting the engineers themselves to police each other over this.

Big-A-Agile "sprints" are a way to get the entire team to slowly move to the working hours of the most psychotic workaholic in the team.

If you think any of the above isn't true, try estimating less aggressively, and watch how your team "corrects" you if you keep it up. Or see what happens if you consistently miss sprint task completions on those tasks that were "corrected".

[1] Although they never complain when your sprint is completed, with every task completed, even though you were off sick for one day. They know that this means you legally worked more than 8 hours/day.
So, for some adversarial reading, I recommend taking a look at:
https://basecamp.com/shapeup
(The digital copy is free)
I'm 100% sure that the CTO is a megalomaniac and that the actual author of the book was fired for idiotic comments...but the book has some pretty wild alternative ideas of how you can plan and accomplish work that are focused on delivering work rather than charts for CTOs.
The book does make some base assumptions though:
1. You have good workers who think independently.
2. Your org allows you to have task-based teams, that is: Teams made up of a designer, an accomplisher, and a manager.
3. It works better when work can be done without external factors impeding it.
4. Your leadership takes the time to set the vision in stone and agrees to it. (This is generally the biggest issue with sprinting: You are allowed to change direction too rapidly so larger projects rarely get accomplished on time as priorities flip-flop.)
McCartney on not-knowing and doing it now
@cyberax said, "My problem with the current IAS systems is state storage. It should not be needed! Instead, the IAS tool should introspect the systems it's managing and build the necessary state on the fly.

@firesteelrain said, "you can do that through abstraction. You "include" your Terraform Azure Provider or Terraform AWS Provider. At the end of the day, your module needs to know what it’s interacting with but not the higher level of abstraction. We have done it at my work to make it cloud agnostic just in case we need to go to another CSP"

Single ops eng in a 3 person startup here. Ops eng is only one of my hats right now :) I found crossplane to be a solid tool for managing cloud inf. My assertion is that "the only multi-cloud is k8s" and crossplane's solution is "everything is a CRD". They have an extensive abstraction hierarchy over the base providers (GCP, TF, Azure, AWS, etc) so it's feasible to do what firesteelrain did. My client requirements span from- you must deploy into our tenant (could be any provider) to host this for us.

I can setup my particular pile of yaml and say - "deploy a k8s cluster, loadbalancers, ingress, deployments, service accounts (both provider and k8s), managed certs, backend configs, workload identity mgmt, IAP" in one shot. I use kustomize to stitch any new, isolated environment together. So far, it's been a help to have a single API style (k8s, yaml) to interact with and declaratively define everything. ArgoCD manages my deployments and provides great visibility to active yaml state and event logs.

I have not fully tested this across providers yet, but that's what crossplane promises with composite resource definitions, claims and compositions. I'm curious if any other crossplane users have feedback on what to expect when I go to abstract the next cloud provider.

cyberax's note on state management is what led me away from TF. You still have to manage state somewhere, and crossplane's idea was- k8s is already really good at knowing what exists and what should exist. Let k8s do it. I thought that was clever enough to go with it and I haven't been dissapointed so far.

The model extends the k8s ecosystem, and allows you to keep going even into things like db schema mgmt. Check out Atlas k8s operator for schema migrations- testing that next...

I also like that I can start very simple, everything about my app defined in one repo- then as systems scale I can easily pull out things like "networking" or "data pipeline" and have them operating in their own deployment repo. Everything has a common pattern for IAC. Witchcraft.
If you finish your 8 point story in a day, you should pace your work better. ;)
That 48C measurement widely quoted was a surface temperature, not the standard 2m above ground. See the original source that was and still is being poorly quoted here: https://www.esa.int/Applications/Observing_the_Earth/Coperni...
So far, glass bottles have been fine for my kid.

I was guessing the commenter was referring to the expense of buying glass bottles, because they cost about double, and that "literal nightmare" was hyperbole.
Exactly what I was trying to imply. Very difficult to classify what is not relevant to language.
How do you do constant time lookup an graph databases?

My intuition let's me know that you can not get below O(n log n) (Lower limit for comparison based ordering)
"For the past few months I've been working extremely hard on this side hustle in my spare time"

Please for the love of god stop using the term "side hustle". I don't want to spend any time helping "hustlers". The term gives me instant negative vibes.

Am I the only one?
Their previous blog post (linked in the first sentence) about why the switch from Go to Rust is insightful.

I'm currently learning Go but have had my eye on Rust as well and have been wondering about the strengths and weaknesses of each language and how they compare and where each language is best applied.

The linked blog confirms my first impression that Go is well suited for networking applications and simplicity whereas Rust is well suited for OS/low-level applications.

Does anyone here have any experience using Go and Rust? What are your thoughts on the two languages?
Lit looks really cool it would be great to see some more examples and starter kits. Perhaps an example of how to build web components for use with other projects that are not Javascript based as well. Bundle up components into individual deployable files for example
People are talking about me, and I started it
The concentration they used was 1000ppm or about 0.1%. Many things are toxic at that concentration. (This doesn’t cross the threshold of absurdity of “sodium chloride is toxic at that concentration,” but it would be preferable not to drink 0.1% salt water.)
Yes these are legitimately real problems in university education, and not always talked about openly: that optimizing for student learning is not necessarily a primary goal, that ‘weeder’ courses exist to dissuade some people from certain majors, and that some departments and some professors aren’t interested in training people for industry, but only for academic research. Some of that was going on in my undergrad program as well, and it has been shifting toward being more industry friendly over time.
"Toxicity" in the LLM space is much less well-defined and there seems to be a reticence on the part of the research community to admit that defining "toxicity" is a necessarily subjective and often political exercise. I mean, people will agree to this statement, but a lot of the evaluation and research methodology makes definite political commitments that practitioners won't admit are political.

The flip-side is also true: a lot of people on the "anti-ethics" side of this debate are too coy about the fact that there are definitely parts of the definition of toxicity that the vast majority of people will agree upon.

And even if we could define toxicity, what to do about it isn't obvious. E.g., let's take something uncontroversial: graphic depictions of violent rape of children. Is this something we should suppress? Not necessarily. It depends on the context. E.g., in descriptions of war crimes and genocides, we shouldn't censor victims who want the audience to know what happened to them. But those same descriptions shouldn't be co-opted into erotica, for example.

One way "out" is to say something like: "look, what we're interested in is providing tools for enforcement of community norms when communicating with a given audience; the community/culture gives us its definition of toxicity and we provide the tools to prevent toxic generation". But those tools aren't neutral: that could be a description of guardrails for children, and could also be a description of overtly political censorship.

It's a difficult and fraught area, and I think all sides of the debate could benefit from more empathy for the other sides of the debate. In particular, this includes presumption of honest intent. There is nothing wrong with filtering toxic content per se -- we can almost all agree that it's reasonable if a company doesn't want to buy a customer service AI that sometimes quotes Mein Kampf to customers with Jewish last names. But the techniques for doing so are not context-free goods, either.
But a hash() destroys information.

When you are trying to reduce collisions, why would you use a function that is known to introduce collisions?
The four-hour work day
These are the problems that arise when everyone and their moms start talking about scientific studies this way.

We don't have enough information. We don't know how they collected their data, we don't know how they analyzed it, even if we did most of us don't know enough to judge those methods etc.

Most "science" is honestly worthless crap done by some random person mainly because they want a PhD or are trying to pad their publication count. They look for some arbitrary thing to test, half-assedly design a study, collect as little data as they can get away with, do a little p-hacking and such to make sure the results are significant (otherwise the time was wasted) then they publish.
Would you prefer iMDB or Rotten Tomatoes?
The usual approach is to just find the archive.is/today/ph link in the comments to read sans-paywall.
> Sprints are one tool in your toolbox. Use them when it makes sense to do so.

This sounds great in theory and I would totally agree (in theory), but my experience has been that it's the PMs or executives or higher managers that make the decision, regardless of what the engineers think. In fact, most of the times I've seen sprints pushed back on it ended up in bad feelings and unintended offense taken by PMs. In the end nothing chnages, except that the engineer who "stirred the pot" loses favor in the eyes of management.

If it was up to each developer or developer team, I would agree, but in reality it rarely is.
A long time ago I visited my ex-gf family in Guangdong and they were making "炸酱面" with homemade la-mian. The sauce didn't really have much black bean and it was mostly just minced beef and tomatoes with noodles. I was like, hang on a second...
Knowing GPT, this is probably as simple as priming it not to overly explain every time that it has considered the instructions. Otherwise every single time it would say “I have thought about how relevant this is to your preset instructions and…”.
I'm the CEO of a startup specializing in personal electronics and communications equipment designed to withstand rising global temperatures. We're in our second round of funding and are ramping up production as we speak. Our goal is to get global-warming-hardened phones into the hands of nearly every human on the planet before it's too late.

Sure, the mass-manufacture of 5 billion more phones is only going to contribute to this global warming, especially since we're making these in third-world countries under lax environmental laws. But that just means we'll be selling even more phones!
So, that notion of putting up solar panel roofs to cover car lots might not just be a good idea, but necessary to prevent the insides of cars parked outside from melting.
I have a few questions about the garbage collection. One of the hard parts of implementing a garbage collector is making sure everything is properly rooted (especially with a moving collector). you have the `do_garbage_collection` method marked unsafe[1], but don't explain what the calling code needs to do to ensure it is safe to call. How do you ensure all references to the heap are rooted? This is not a trivial problem[2][3][4].

Also note that I cloned the repo and tried to run `cargo test` every test fails with 'should be able to add entries to the classpath: InvalidEntry(".../vm/rt.jar")' vm/tests/integration/real_code_tests.rs:15:10

[1] https://github.com/andreabergia/rjvm/blob/be9c54066c64a82879...

[2] https://manishearth.github.io/blog/2021/04/05/a-tour-of-safe...

[3] https://without.boats/blog/shifgrethor-iii/

[4] https://coredumped.dev/2022/04/11/implementing-a-safe-garbag...
my friend went to visit their once pretty famous research center years ago: she was shocked by seeing these workers pretty sad and angry they had not much to do, and the building was crazy hot. She had the clear feedback that center was not considered strategic at all anymore (!)
The milk doesn't need to be that hot. Warm is fine, and if the bottle is that hot, I'd worry that the milk is too hot to drink.
Yeah, I think this is Scrum in specific. Unlike the other Agile methods, it had a revenue stream through certification. At the time I was like, "Hmm, something doesn't seem quite right to me, but I'm sure the best ideas will win out." I was very wrong. C.R.E.A.M., etc.
When I ran out of time on AOL as a kid, I just hacked someone else's account and used it, or used AOLHell to create a new account. I remember this other kids account was hacked for time, now he works for Google. Fun times.
I worked for a dial up ISP as a network engineer around the same time frame mentioned in the article.

A standing instruction was to, as time allowed, manually look at usage across members and force resets on any long standing connections! Mainly this was because it was a small company and this freed up the number of possible incoming connections to avoid busy signals.

I was very junior and cringe at how naively unaware I was of any ethical considerations!
I live in a hot climate and Carplay is barely usable because my iPhone X slows to a crawl whenever it's >80F. Wireless charging exacerbates the problem.
Farmworkers thought a new overtime law would help them. Now, they want it gone
nope - it'd be plain wrong. Literals must be equal by reference, comparing them by value would just break JLS, as they would be equal to any other composed string by reference as well.
> By serializing to JSON, a format with robust support in both Go and Rust, we were able to minimize our FFI surface area, and avoid a whole class of cross-platform, cross-language bugs.

There’s been a lot of discussion of the marshaling and unmarshaling costs of Json (and really any other text format). Should we be looking more strongly at binary formats, and if those have better outcomes than Json?

I’m guessing they didn’t want to introduce more change to the Go code than necessary, but I’m wondering if people have any horror stories to share about any of the binary formats available?
AlphaPheonix on YouTube has an excellent and informative video of a very similar process of testing seals, though the vacuum is pulled for a different reason: https://www.youtube.com/watch?v=VD69crOFx10
I'm personally at the interstice between "the government shouldn't have the right to mandate lot sizes, it creates artificial scarcity and puts a soft floor on property prices" and "tiny, congested lot clusters are really ugly, don't offer much more value than apartment living, and make a poor replacement for the woods bulldozed to make room for them, and could stand to be dis-incentivized".
I'm not sure why people are asking for search queries and posting search reaults. These are either way filtered by the profile determined for you as a "category" or cohort of users.

So saying that Google is useful for a generic search like "the best gaming laptop" is a bit wrong. The issue starts when the response to this begins with "scrlling past the ads and sponsored content" to "SEO optimized but not necessarily useful content".
Not the same, but in the early 2000s (Germany, so ISDN dial up), my dad got a call at work from my ISP, because they got a call from blizzard, because my dad's son was hosting WC3 closed beta cracks and servers on the ISP webspace…