skysight-inc/HackerNews huggingface dataset:
2 observations, first the cynical one, but the second is optimistic.

For leadership, the whole idea of "breaking down silos" is almost always lip-service, and to the extent that is/was a core mission of DevOps, it was always doomed. Responsibility without power doesn't work, so it's pointless unless the very top wants to see it happen. Strong CTOs with vision are pretty rare, and the reality is that the next tier of department heads from QA/Engineering/DataScience/Product are very often rivals for budgets and attention.

People that get to this level of management usually love building kingdoms, and see most things as zero-sum, so they are careful to never appear actually uncooperative but they also don't really want collaboration. Collaboration effectively increases accountability and spreads out power. If you're in the business of breaking down silos, almost everyone will be trying undermine you as soon as they think you're threatening them with any kind of oversight, regardless of how badly they know that they need process changes.

Anyway, the best devops people are usually excited to code themselves out of a job. To a large extent.. that's what has happened. We're out of the research phase of looking for approaches that work. For any specific problem in this domain we've mostly got tools that work well and scale well. The tools are documented, mature, and most even permit for a healthy choice amongst alternatives. The landscape of this tooling is generally hospitable, not what you'd call a desert or a jungle, and it's not as much of a moving target to learn the tech involved as it used to be.

Not saying every dev needs to be a Kubernetes admin.. but a dev refusing to learn anything about kubernetes in 2024 is starting to look more like a developer that doesn't know Linux command line basics. Beyond the basics, Platform teams are fine.. they are just the subset of people with previous DevOps titles that can actually write code, further weeding out the old-school DBAs / Sysadmins, bolstered by a few even stronger coders that are good with cloud APIs but don't understand ELBs / VPCs.
Judges are generally less politicized than bureaucrats.
Average number of pages in the Federal Register is around 70k each year since the mid 1970s.

I found his and other interesting facts about USA govt rule making in

Counting Regulations: An Overview of
Rulemaking, Types of Federal Regulations,
and Pages in the Federal Register Sep 2019

https://sgp.fas.org/crs/misc/R43056.pdf
I introduced RCS to my sysadmin team in the mid 90s but again you always had those guys with god complexes who couldn’t be bothered to ‘ci -u’ or ‘co -l’ properly because that’s not how they do things. And if your entire team isn’t onboard then it’s worse than having no VCS at all

God riddance to those guys. They thrived in silos.
I think you know what they're arguing. It couldn't be clearer.
That's how accent marks still work on Spanish keyboards, these are used less these days as autocorrect does it for you.
This is solved by also using wind and hydrogen. Europe has salt formations that could store millions of gigawatt hours of hydrogen, far more than they'd need for long timescale leveling of variable supply.
Counter-point: whitespace PR’s, refactors I didn’t ask for, aren’t attached to a larger initiative, etc actively annoy me as an owner.

Every PR takes time to manage, compounds complexity, and carries risk. We only get so many out a week, and I want them to count.

Maybe it sometimes goes in hand with disfunction, but I’m guessing there’s more going on there.
seems they are legislating less and less by the Congress.

The list of acts of the 115th United States Congress includes all Acts of Congress and ratified treaties by the 115th United States Congress, which began on January 3, 2017, and ended on January 3, 2019. The 115th Congress enacted 442 statutes and ratified 6 treaties.

The 116th United States Congress, which began on January 3, 2019, and ended on January 3, 2021, enacted 344 public laws and zero private laws

The 117th United States Congress, which began on January 3, 2021, and ended on January 3, 2023, enacted 362 public laws and 3 private laws.

The 118th United States Congress, which began on January 3, 2023, and will end on January 3, 2025, has enacted 65 public laws and zero private laws

[1] https://en.wikipedia.org/wiki/List_of_acts_of_the_115th_Unit...

[2] https://en.wikipedia.org/wiki/List_of_acts_of_the_116th_Unit...

[3] https://en.wikipedia.org/wiki/List_of_acts_of_the_117th_Unit...

[4] https://en.wikipedia.org/wiki/List_of_acts_of_the_118th_Unit...
I should have known better then to take that bait. I'm not interested in pedantic philosophical debate about theoretical obligations skewed by imaginary prices that don't reflect real world business scenarios. In fact, I'm opting out of this entirely. Have a good night.
The most recent two have no business being on the bench in the first place, so maybe not so much.
I wonder how cars traveling east/west between Queens-Brooklyn-Long Island to New Jersey affect traffic? I wonder how congestion pricing will affect already problematic George Washington Bridge and Staten Island routes.
CPUs and GPUs are in very different situations.

We've got 60 years of experience with RISC ISAs showing that they are as good as any other approach, since Seymour Cray's CDC6600 in 1964 (and of course his later Cray 1 in 1975 would also be called RISC today). By the late 70s researchers at IBM were also converging on the same ideas, as were academics at Berkeley via experience with the DEC VAX. Multiple RISC ISAs, with mostly only cosmetic differences between them, hit the market commercially in 1985 and 1986 -- almost 40 years ago.

It's pretty clear what works, and for example Aarch64 and RISC-V were developed in parallel with each other [1], without either being aware of the other, but came up with very similar designs, both taking lessons of what to do and what not to do from MIPS, SPARC, Power, Arm32, Alpha and others.

In contrast, the first modern programmable GPU was the NVIDIA GeForce 3 in 2001, just 23 years ago. Even today leading GPU vendors have not settled down on how a GPU should be designed. Every NVIDIA generation is radically different from the previous one and NVIDIA, AMD (ATI), Intel, Imagination GPUs are very different to each other -- and the exact details are still often closely kept secrets. NVIDIA doesn't let anyone program their CPUs directly, they provide a pseudo machine code (PTX) and different closed source compilers from PTX to each generation's real architecture.

The chances of anyone coming up with the "forever" GPU design in the near future, let alone making it open, seem pretty slim. The whole field is still too new, changing too much.

[1] Aarch64 clearly started earlier, and unexpectedly published the ARMv8-A spec in October 2011, 1 1/2 years after the RISC-V effort started, by which time the fundamentals of the RISC-V design were firmly established, though details continued to change for the next 7 years. The first Android phones with Arm64 CPUs (e.g. Galaxy S6) hit in early 2015, with SBCs (Raspberry Pi 3, Odroid C2) following in early 2016. The first commercial RISC-V board, the Arduino-style HiFive1 shipped in late 2016. Note that Apple's iPhone 5s launched with an Apple-designed ARMv8 CPU almost 1.5 years before Arm's own designs.
It is true. After his debate with Foucault, Chomsky said "he struck me as completely amoral, I'd never met anyone who was so totally amoral".
Pouring out for QA over here. My first gig ever, we had lovely QA people who spent all day just... using the application and trying to make it break. When it did, they'd fail tickets back to us, and we'd fix them. It worked so amazingly well. Now? Hurried, bored devs do it to get the next release out the door, and it shows.
> time inside a black hole locally works the way it does outside a black hole

That doesn't mean that it actually runs though, you can interpret the lack of possible shared reference of time as the black holes time either happens instantly, but also that it never ever happens and everything in it is stuck and time is frozen from our perspective. In the time frozen perspective the singularity would never form, all objects are frozen and never reach it.
If we could build such a device we would effectively have unlimited energy. At that point, why fight each other when we can colonize the galaxy?
it removed restrictions on abortion, allowing local parties to decide for themselves, it seems constitutional but not partisan, RvW was also an abortion ban don’t forget
Yeah this is just a queue system, lots of agent versions of these already. There’s nothing special about agents that they need their own queue system
Part 2: https://markuta.com/eero-6-hacking-part-2/
Have you ever worked at FB / Google / whatever other company has huge mono repo with great tooling?

I went from many years at FB, to a place like you describe - hundreds of small repos, all versioned. It’s a nightmare to change anything. Endless git cloning and pulling and rebase. Endless issues since every repo ends up being configured slightly differently, and very hard to keep the repo metadata (think stuff like commit rules, merge rules, etc) up to date. It’s seriously much harder to be productive than with a well-oiled monorepo.

With a monorepo, you wanna update some library code to slightly change its API? Great, put up a code change for it, and you’ll quickly see whether it’s compatible or not with the rest of the whole codebase, and you can then fix whatever build issues arise, and then be confident it works everywhere wherever it’s imported. It might sound fragile, but it really isn’t if the tooling is there.
YAML over SSH, primarily.
R has a pretty particular use case though, Python use for statistical programming/data analysis would be an apples to apples comparison. People doing a coding 101 course in Python don't really count against the R user base.
> So 260m would be absolutely devastating, but wouldn't end civilization as we know it

It really depends. A ~100 m asteroid is roughly as energetic as some of the largest nuclear weapons ever detonated (~10¹ to 10² megatons).

As an example... It'd destroy London, and maybe some of its satellite cities like Luton, Oxford, and Cambridge, but the effects would be significantly diminished by the time the fireball radiation and the blast got to Nottingham.
I have no idea if technology like this will prove to be scalable, economically competitive, or even practical… but it does seem pretty dang cool as a concept
At first I thought this was some sort of joke or satire, like the Alameda-Weehawken burrito pipeline. Then I read the bit about rhino horn trafficking and I was like... well, shoot, that's actually a pretty good idea!
There will be times when the wind doesn't blow and the sun doesn't shine. Storage can come to the rescue if this is a few hours, but over much longer time periods will be a problem. It's rare, but not unheard of. Gas will be part of the solution for many years to come.
> I was floored at how _well_ NYC traffic moves in comparison

My criticisms of NYC traffic aren't based on the throughput efficiency for drivers, but the impact on the people who live there.

At least when I was in NYC, every attempt to charge market rates for parking, improve daylighting at intersections, get people to stop parking on the sidewalks, build protected bike lanes, stop making mountains of garbage bags on the sidewalk, etc were all met with fierce resistance. (Though I gather from this thread that things have improved in the last ten years or so.)

While the pedestrian fatality counts in NYC are breaking records, just across the Hudson River you have Jersey City and Hoboken prioritizing safe, pleasant streets for residents and have achieved "Vision Zero" with no traffic deaths.
Finally. VScode is a landing zone for malicious extensions.
I think this comment is a bit unfair. A lot of work goes into not having to do those things. Good immutability often means less need for babying a specific server.

It’s been a long time since I’ve had to do those things, so yes it’s becoming a lost art to me. However, on the rare occasion I need this sort of insight I do fine with JIT research.
Or what happened in my company where product managers were expected to take on a marketing role, and developers were the ones left with 3 roles or product management (usually left to the dev manager), development and QA on the individual developer. You’re left with product managers have no clue how the product works. They meet with 3-8 customers or other teams a day, and come back with a check-list of “must haves”. They have no idea how the existing product works, they just know that “customer is asking for X, what’s the timeframe for adding X?”. Then dev managers who have to take product management role, so they have no time for understanding how anything is actually built. Their time is spent defining timeframes, requirements, and expectations with other teams. “We trust our developers to do the right implementation”. Then developers who just get piecemeal requirements and are asked to implement it in the simplest fastest way. No time for a major redesign or refactoring of anything. Because from the PM prospective, there is a check-list of items we need and there are 2 unchecked boxes. From the dev manager prospective, we have X and Y, so having XY makes sense. Then from the developer prospective, just duct-tape them together instead of actually building Z which is what makes sense.
That's an unsourced and unbacked assertion, not at argument.

And I have seen no convincing argument for why this would be even remotely true.

As a counter argument, consider how poorly such predictions have done in the past (i.e. early 2023) [0]. For over a decade the IEA has been saying the same thing, and for every year in that decade they have been wrong, comically wrong.

So if you want to make your argument, you'll have to explain why the literally exponential curve is going to not just flatten, but go to zero.

[0]: https://stacker.news/items/581737 (original image from https://www.economist.com/interactive/essay/2024/06/20/solar...)
The Money Coup: What the fall of Chevron deference means for state capacity
Agreed. If we didn’t use kubernetes, we’d have to reimplement a bunch of its features. Back when we were getting started I tried docker swarm because it was supposed to be simpler, but I had weird issues with its networking.

The best part is multiple environments. I can run our full stack on my laptop with k3s and one call to make. We use the same yaml (with kustomize) for all three cloud environments.

It feels pretty boring, which is fantastic.
The solution to both problems is law, and the rule thereof.
I’m compelled to make a couple of comments:

1. I feel that one big and important aspect of devops that isn’t mentioned is that smaller releases are less likely to have killer bugs. If you can release one change a day rather than 100 changes a quarter then overall I think there’s a strong argument, not to be had here, that you’ll have faster releases and less bugs overall, assuming my next point. This doesn’t take away from the article, but it’s just something I don’t see discussed much.

2. I think a huge part of the problem is that business management keeps trying to abstract away engineering management. The most productive team I’ve ever been part of was when I was able to spend most of my time planning and coordinating the work, as part of an overall vision, while my peers did the implementation and gave me feedback. One side effect of this was that productivity was actually measurable. But the value of productivity is lost on business management who saw me as just engineer - one who had the authority, furthermore, to push back against stupidity and was therefore a pain in the ass. Technical management is not valued, because it’s not understood, and this is seen in the endless cycle of fads designed to make all engineers fungible.
> Time doesn't work inside black holes…

Time and space work exactly the same inside the black hole as outside, they just swap places. One dimension that was spacelike is bent into becoming timelike. Closer to the center becomes further in the future, and outside the event horizon becomes part of the past. The singularity at the center of the black hole is now the literal end of time. Nothing exists past the end of time; you hit that singularity and you cease to exist.

From the outside, all that we can detect is the mass of the black hole. Or rather, all we can detect is some gravity pulling us in, as if there were mass inside. Einstein proved that all gravity is just the curvature of spacetime. Your body is bending the fabric of spacetime right now!¹ When you dive into a black hole, the curvature you are causing is added to that of the black hole, so that the black hole grows exactly as if your mass still existed inside of it. But really you ceased to exist when you hit the end of time at the singularity.

But of course that is how we _used_ to think of it, up until a decade or two ago. As Susskind would say, ER=EPR. Spatial connectivity (which Einstein and Rosen wrote a paper about) is exactly the same thing as quantum entanglement (which Einstein, Podolsky, and Rosen wrote a completely different paper about in the same year). I won’t try to recapitulate one of his lectures (since you can just watch one; see <https://www.youtube.com/watch?v=31fVea8_OAw> for a recent example, but there are others), but the result is that the spacetime inside the black hole grows without bound, and you never actually reach the end of time. You cannot go back, but neither do you go splat. The matter that was once a star is somewhere ahead of you in that growing region of spacetime, forever in your future.

¹ Note all possible “yo mamma” jokes for future reference.
my guess, in short, is that black holes are equivalent to infinite loops, and white holes solve the halting problem
Wine 9.12 (Dev) – Run Windows Applications on Linux, BSD, Solaris and macOS
Requirements for Digital Preservation Systems
Exactly this! Fusion power is eight minutes away. Always has been.
Yes. Why do many people quote it as if something profound here (there are at least half a dozen of instances of this quote by different authors and some just repeat it in multiple threads)? This is the essential rule of law: nobody is above it. It appears that people posting this quote believe that the law should be different for different people? I mean, the original author was a monarchist and did not believe a democracy was good or just so it makes sense. Are people repeating this also all monarchists who believe the law for different classes should be different or just made up by the Crown for each situation?
The amount of assimilation was not homogeneous anywhere in Europe. In urban environments, some Jewish families were highly assimilated, and there was a great deal of interaction between Jewish people and Gentiles. If these dynamics are interesting to you, you might want to read about the haskalah:

https://en.wikipedia.org/wiki/Haskalah?useskin=vector

Out in the stetls (in rural towns), there was far less assimilation (although a lot of interaction). For example, in Poland prior to WW2, Jewish society was almost a parallel world. Polish Jews had their own religious institutions, shops, and, at various times, a parallel government. For centuries, Poland was like two separate worlds that inhabited the same physical space.

It's really too bad that it ended. I grieve for something I never even knew.

https://en.wikipedia.org/wiki/History_of_the_Jews_in_Poland?...
Not possible. The US is on the fast track to be humbled and humiliated by its geopolitical rival, China.
I know they are hackers. Unfortunately their minds have also fallen victim to all the political nonsense going on in our society.
The Google search deal started at around $50 million a year and has grown to a bit over $500 million a year. Let's estimate $5 billion total. It is typical to take 5% out of an endowment each year today, which means they would be have an income of $250 million a year if they had invested the money instead of spending it. Not bad!

On the other hand, the Google money accounted for around 85% of their income over the years, so if they hadn't been spending it they would have been operating on around 20% of the income for many years while the endowment grew, and likely would not have been able to keep up with competing browsers.

Also, for as much crap as she gets, Mitchell Baker invested over 20% of the Google money Mozilla received during her tenure, far more than was invested by prior CEOs. And before anyone brings it up, all that "woke activist" spending comes from donations, not Google money, which the IRS prohibits them from spending on browser development.
I'm guessing the reason why is that the Jews migrated northwards from the Levantine / Africa / Spain upwards through Italy, Austria and then Germany, Poland, the Baltics.

Are there any Italian or Piedmontese / Venetian traces in Yiddish?

Relevant? https://en.wikipedia.org/wiki/Judeo-Italian_languages
i have spent quite some time prowling windows system files,and letme tell you,
the windows system is set up to allow processes to pass data, and tags, and alternate execution streams out of band. Read the code for the winAPI and you will see it.

this above, and the corporate behaviour, is why im a not windows guy
In head lice outbreaks, 'selfies' may be a surprising culprit
https://archive.ph/BeuYX
> This argument makes zero sense.

It makes perfect sense: the livestock methane has merely supplanted the wildlife methane that existed for 50 million years. In 50 million years of geological analysis on climate change, we have not documented one case where biological methane has triggered large scale climate change.

> Thus, we know that these cattle, cattle that would otherwise not exist, are contributing to climate change.

In the absence of cattle and especially in the absence of humans, other ruminants will naturally propagate, as they have a number of symbiotic relationships with various plant and animal species.

Ruminants have roamed the earth for 50+ million years, and they have been widely propagated in the hundreds of millions to billions of total global population for that entire time.

The Great Plains were filled with 60+ million American bison, a species which trends larger than cows themselves, but which is still so close genetically to cows that they can still breed together. Deer, antelope, elk, moose, sheep, goats, etc also have similar digestive systems and also existed in larger numbers in the wild prior to modern human expansion.
I have worked at a company that has huge monorepos and bad tooling.

Tooling isn't the problem though, the problems are:

- multiple monorepos copying code from each other, despite that code should be a library or installable python package or even deb package of its own

- you will never understand the entire monorepo, so you will never understand what things you might break. with polyrepos different parts can be locked down to different versions of other parts. imagine if every machine learning model had a copy of the pytorch source in it instead of just specifying torch==2.1.0 in requirements.txt?

- "dockerize the pile of mess and ship" which doesn't work well if your user wants to use it inside another container

- any time you want to commit code, 50000 people have committed code in-between and you're already behind on 10 refactors. by the time you refactor so that your change works, 4000 more commits have happened

- the monorepo takes 1 hour to compile, with nothing to compile and unit test only a part of it

- ownership of different parts of the codebase is difficult to track; code reviews are a mess
It is more accurate to say that failure to build out enough housing, as well as other buildings, infrastructure, and industry, has made devastating poverty acceptable in Britain. https://worksinprogress.co/issue/the-housing-theory-of-every...

Meanwhile, people like this are like: "Increase supply? haha, best I can do is subsidize demand!"