skysight-inc/HackerNews huggingface dataset:
The big advantage to deploying to prod constantly is trunk-based development.

Any system where you maintain a separate development branch is one where you're invariably going to be asked to cherry pick feature B to production but not feature A. This is a problem because you tested everything on a version of the code where B follows A, but now B needs to stand on its own. Can it? Maybe. But you didn't test that.

With trunk-based development you have one main branch that everything goes to all the time. If you need something to not go out to real users then you put it behind a feature flag. If something needs to go out to users today, then you merge a change on top of your main branch that unconditionally shows the feature to users.

This way all code that ever makes it into production exists at a point along a single linear commit history, each merge commit of which was checked by CI and is the same history that devs developed against locally.

In my experience eliminating cherry picking makes a huge difference in reliability, and the only way to do that reliably is to constantly deploy to prod.

And yes, my current $day_job does this.
They absolutely can apply the law to specific factual scenarios. They just can't necessarily apply new legal theories to new factual scenarios without getting challenged. The words "apply the law" generally do not mean "invent new legal theories."
China are currently building 27 fission reactors, and the construction time is 7 years.

If it takes 7 years to build something that is known and has been done a couple of hundred times before, I think it's safe to say it will take more than 4 years to build something of similar complexity that has never been done before.
That page is fricken fantastic thank you for sharing!
I think they've sorted that:

> The Indian conglomerate Tata has confirmed Bridgwater in Somerset as the site [...] Preliminary activity has started on the site and work to establish its foundations will begin in spring.

And the article's from February, so that's this spring just passed.
All credit to Conor White-Sullivan for making links cool again.

> unordinary direction

Hahaha, this is a very polite way to put that=) But I do appreciate it.
It's basically a prototype that industry ran away with. It leaks implementation details everywhere and pushes way too many config options up to the developer. Because industry ran away with it before it could be good, it takes projects like Cilium to push it in the right direction, but those take forever to get adopted and are really hard because they don't live in the product itself.

You'd need like 10 more Ciliums to make Kubernetes actually good, and they'll never all get adopted. The tech is a dead end that demonstrates some nice tech/patterns but got overhyped. It's like the Hadoop of containers
Which seems like an enormous power grab on the one hand but I can’t really see any other way for them to be a check on the other branches without that power. There needs to be some legal basis to declare a law invalid. The Constitution (with all of its vagueness at times) seems like the better way than simply vibes.
chef's kiss

This guy and the person that quit the bullshit industrial complex 6 months ago should get together and launch a startup.

Better yet, we should all go and join Jeremy Howard's answer.ai pro bono. Besides being miraculously headed by a guy who is Not An Asshole, it incidentally also had the most refreshing launch post (in the warm and fuzzy way) this side of the AI bubble.

The launch post concluded with this heading:We Don’t Really Know What We’re Doing.[0]

I mean, for the finest minds in our respective fields, what else is there left to say really?

[0] https://www.answer.ai/posts/2023-12-12-launch.html
I honestly don't remember the last time I used a terminal to edit files. I don't really miss vim that much since I still use vim shortcuts in VSCode. I briefly tried Emacs but a lot of the major modes for languages I used were too buggy and those were distracting me too much for it to be my daily driver (maybe I have ADHD, dunno)

For what its worth, VSCode also works over SSH. There's a collection of plugins for working remotely or in containers.

The main thing that drew me to VSCode originally was pretty good support for fonts and ligatures. And I think I also like some of the QoL plugins I use. The config is just JSON, and it's pretty easily tweakable to how I like it.

I've heard good things about nvim and zed though, and I'm tempted to try them. But there's a bunch of idiosyncrasies and quirks that you get used to, so switched kinda feels like a chore
Proof that it was installed and working correctly is super easy. Multiple airlines fly the same route. The airlines should be feeding the data to the government and the government can cross-validate that the data is legit for routes that have more than 2 airlines. + the jet stream is quite large so even not the exact same route should still be able to highlight airlines doing fraudulent data by. If they’re not sending data, that’s also super easy to tell.

At some point the cost of trying to lie and cut corners becomes worse than the cost of compliance and the airlines and airplane companies will just become good at doing a good job here.
Yeah, that's a bug. I'll fix it. Sorry.
EDIT: It's fixed now
Base load was a useful concept when steady output power plants with high capital cost produced energy at the lowest cost. It then made sense to use them as much as possible -- to handle the "base load" -- and cover the rest with more expensive to operate but lower capital cost sources.

But that's no longer the world we live in. The lowest cost energy is now from intermittent sources, and the optimal grid design will look very different.
The very very important stuff is hidden, and the only two examples anyone ever gives are core search ranking algorithms and the self-driving car.

Even the battle-tested hyper-optimized, debugged-over-15-years implementation of Paxos is accessible. Though I’m sure folks could point out other valuable files/directories.
Please don't cross into personal attack on HN, regardless of who the person is.

https://news.ycombinator.com/newsguidelines.html
Jack Ma sounds odd at times but if you believe his story, he’s more self made than almost any of the US billionaires.

The title sounds reminiscent of Bill Hwang.
This particular asteroid is the size of a jet plane, so a nuke would probably have an effect.
> California has spent over $100bn to build 1600 ft of high speed rail over a decade. And it wasn't Republican obstructionists who caused that.

I'm not familiar with that specific situation. Was it taken to the federal courts and only allowed to happen because of Chevron?

> There are too many regulations.

I think many people cheering this ruling are just anti-regulation and they care a lot about that without thinking much about how this ruling will negatively impact their lives and the lives of their families.

I agree with you though. There really are too may regulations. That will probably always be true. As long as industry and corporations can write self-serving legislation and bribe people in congress to pass it, there will be regulations on the books that shouldn't be there. That said, regulation is the only reason you have safe electricity, clean air, and safe water (assuming you aren't one of the several millions of American's who currently don't have safe drinking water).

Regulations, like all laws, are just tools and they can be used to help improve our lives, preserve our health, promote the safety of the American people, and increase our freedoms or they can be used to stifle competition, funnel tax money into the pockets of private corporations, or restrict our freedoms. Like laws themselves (which there are also too many of) it would be foolish to abolish all of them because some of them are bad.

We should be paying attention to who is writing and passing regulations and who those regulations serve, then hold people accountable when they don't represent our interests. That's hard to do in our current system where people's votes don't mean much, so we might want to try fixing that situation first but being "anti-regulation" makes about as much sense as being "anti-laws". Laws are a good thing. Regulations are a good thing. Let's just try to make sure they are both serving the public good.
We'll let the space colonists worry about that. It provides no justification for anyone I know to pay for it.

Solar decreases as 1/r^2. Cube root? Where did that come from?
No, we’re quite aware the world outside has been catching up. There’s even a famous doc by a senior director about it…
The overwhelming majority of people do want a lot of things. Gerrymandering in the House and the fact that the Senate gives Wyoming and Vermont the same power as California and Texas prevents that.
They spelled it "correctly" there.

https://en.wikipedia.org/wiki/HTTP_referer

Etymology

The misspelling of referrer was introduced in the original proposal by computer scientist Phillip Hallam-Baker to incorporate the "Referer" header field into the HTTP specification.[7][8] The misspelling was set in stone by the time (May 1996) of its incorporation into the Request for Comments standards document RFC 1945[9] (which 'reflects common usage of the protocol referred to as "HTTP/1.0"' at that time); document co-author Roy Fielding remarked in March 1995 that "neither one (referer or referrer) is understood by" the standard Unix spell checker of the period.[10] "Referer" has since become a widely used spelling in the industry when discussing HTTP referrers; usage of the misspelling is not universal, though, as the correct spelling "referrer" is used in some web specifications such as the Referrer-Policy HTTP header or the Document Object Model.[3]
Untrusted by Google is what most laypeople will get out of it.
I just have to point out that the Vallée de Joux (namesake of the Valjoux movement) is a beautiful spot in Switzerland that is located such that very few foreign tourists ever go there. Definitely worth the visit.
Repealing and overturning are two completely different things done by two completely different branches of government.
Yeah I feel like the FAA should require the airlines to share some of the data so we get research into the jet stream that we can cross correlate with other data sources.
Honestly I don't know why they would go to the effort, especially when trying to sell the company. Surely the amount of $ saved is de minimus
here's my alternative 3d bin packer
https://3dpack.ing
Investment in renewables dwarfs that in nuclear now. Hell, it's exceeding investment in fossil fuels.
You know, maybe it's time to overturn Marbury v. Madison. An originalist like Alito should have no problem admitting that the constitution never granted the court these powers in the first place.

What's that I hear you say, he won't do it because it would hamper him personally? Well, bless his heart!
Your california bias is showing. Seattle and Vancouver BC (and Vancouver WA, the northern suburb of Portland OR, along with Portland) have even worse homeless issues than the bay area, and they don't have favorable climates for the unhoused. Try almost 300 days a year of rain, and winter temperatures that often dip to the 20s. Your arguments would imply that New Mexico, a poor blue state with a favorable south-western climate should be full of homeless people

It's the other factors you mention, and "Cascadia/The PNW" has more in common with each other than it does with the rest of its countries (This is bioregionalism and it's strong out here). The only reason you'd know you went to Canada when you arrived at Vancouver BC from WA state is that you'll see a lot of tim hortons around. SF bay area and Vancouver BC have the same exact problems despite wildly different weather. It's culture and laws.

Honestly, our culture and laws which allow this to happen are super based and awesome, and having a large homeless population as externalities of booming economies, and lax drug laws is worth it. The rest of the world wishes it was the PNW, and being the "Prussia of the USA" is the position that California will naturally find itself in as a result of its northern half having the same factors which drive it to have so many unhoused.
This is so incredibly ignorant, which is fine. We're on a startup forum after all--not a conlaw round table. We aren't supposed to be experts. But to think you have some superior intellectual standing on this issue compared to any of the SCOTUS justices to too much Dunning-Kruger for me to just let slide.
Is there a regional aspect to it? I have been listening to a lot of Yiddish/Russian music lately and people say that there are a lot of Russian loan words and it is hard to understand for non-Russian Yiddish speakers.
> Exactly how do you write a law that has no room for interpretation?

Funny question in light of Fischer vs. US. The majority found that the text of a law didn't mean what they believed it should, so they threw out the text and went with their feelings. How can one write a law with no room for interpretation, to be understood by a court who can't be trusted to retain the letter of the law?
"should have ruled according to the text of the constitution"

The actual ruling was NOT an "textualist" interpretation at all.

Here's a summary with the linked ruling in case you're interested:

https://www.scotusblog.com/2024/03/supreme-court-rules-state...
Good now they can finally afford their own cards in their gaming rigs.
You have that backwards: the prospects for fusion looked so poor that there wasn't much stakeholder push for funding.

The argument "with funding, it will come" is cargo cult thinking, reversing cause and effect.
I'll start by saying that I think knowledge for knowing layers underneath the application is fading in some circles, and that makes me sad.

Having been a frontend guy some 10+ years ago, into a network engineer, then infrastructure engineering and now SRE. The amount of people on both sides of the developer circle and operations circle that do not want to understand what's going on is mind boggling.

I was around when VMs were hot, when treating them as long living pets was just toil that operations dealt with. The collection of shell scripts to make that toil go away was nice. Then puppet, ansible and the like.

Now we are in the golden ages of Kubernetes and orchestration platforms. We have a set of standards for how things can be operated. The terms are obfuscated sure, but the core concepts are still the same underneath the abstraction.

I agree that platform engineering is a good place to be, and honestly it needs to be understood more by all parties including executives. They were bought and sold cloud on the idea that it's all managed, but that cannot be further from the truth, wrinkles will show as scale grows and your use cases progress in any environment, at home or in the cloud.

Unfortunately good platform teams often aren't seen. A good platform just works, metrics just exist, logs just work, tracing just works out of the box. Things don't often go down. It's really only visible when things fail. If you do a great job implementing a self service platform you're often met with executives wondering why you're there because the cloud does it all!

Applications are highly visible to all, but so are the layers underneath and they all work together if done correctly, I wish that was more understood.

For context, I'm currently running multiple environments of Kubernetes, on premise and in cloud. Our team prides itself on using open source solutions utilizing the operator model. Prometheus, Thanos, Loki, Tempo, Istio, Cert-Manager, Strimzi Kafka, Flink operator, Otel collector etc. We do billions of requests a month and TBs of bandwidth with microservices. Have at a minimum 4 9's of uptime, and our cost footprint is extremely small. This comes from a 4 man platform team that also handles on call for all applications, security, cloud budget, and operations. It's not impossible.

I guess I can't emphasize enough that understanding what the orchestration systems, the tooling and the stack are trying to do makes everything easier. As a developer you can understand your constraints and limitations. You can build off of known barriers. As an operations or platform engineer you can build things that don't require constant babysitting or toil.. you can save hundreds of thousands of dollars not offloading your observability to data dog or the like, you can make an impact. The technology is already here.
Many linguists even call it Judeo-German (and Ladino, the Sephardic language, Judeo-Spanish)
Sysadmins provisioned and managed version control systems for years. CVS, Subversion, etc.
Partial check outs are standard because the entire code base is enormous. People only check out the parts they might be changing and the rest magically appears during the build as needed.

There are sections of the code that are High Intellectual Property. Stuff that deals with spam fighting, for example. I once worked on tooling to help make that code less likely to be accidentally exposed.

Disclaimer: I used to work there, but that was a while back. They probably changed everything a few times since. The need to protect certain code will never go way, however.
If you just want a feed of stuff where you choose who to subscribe to, where you can like and comment, no ads, and that's about it... that's Mastodon. If you want more topic-organized threads, that's Lemmy. There's not many people on the fediverse relative to mainstream social media, but there's enough for it have the Craigslist/usenet/BBS feeling.
Congratulations on moving fast! If possible ‘trunk’ is best.

Long lived branches are a problem if you are doing hot fixes to prod. The goal is the process avoids hot fixes and critical bugs.

Some industries would not allow software to be released more than every few months. SQA needs to sign off. Users need to UAT. 2-week notice, 15-minute notice to log off. Downtime needs to be communicated to multiple time zones. Software versions need to be auditable for regulatory.

The only point I was trying to make is ‘publishing’ multiple times per day with a team of developers requires ‘devops’ and that release does not always mean to prod. The same setup for releasing to prod multiple times per day is the same as releasing to develop multiple times per day.

Long live DevOps
My experience with T Mobile is them always trying to upsell me on more expensive phones.

I know exactly how much I want to spend.
The gas can be hydrogen, produced with renewable electricity by electrolysis.
The article exists because of several recent high profile CAT incidents.

It cites data from several years ago (before the recent spate of stories) that only talks about increases in CAT-conducive conditions, but says nothing about increases in actual incidents. The article leaves maybe the impression that any recent spike in high profile turbulence events might be a result of the changes in jet stream activity but doesn’t actually provide much justification for that. Other posts on this thread point out that there was no actual increase in reported CAT encounters that correlates with the proposed mechanism so… unclear if the article’s data says much if anything about recent media-reported CAT events.
> Not sure where the idea that software is released to production multiple times per ever came from.

UX-focused development. Your concern is mainly about user journeys, acquisition tunnels, etc. So you rely on user feedback a lot. So you ship, A/B test, iterate.

Also, if your service consists of lots of microservices, you don’t want to wait to ship them all at the same time.

The most fitting example to both is probably Netflix. I guess they ship to prod every day a lot.
Theia platform is the foundation to build custom IDE.

TheiaIDE is one, dare I say official, implementation of an IDE on the platform.

To me, that seems congruent.
Man, this is such a downer. I think most rational people avoid a professional sports career unless they “have that special something,” but so few do. To scrape and struggle for years on end all alone during it must absolutely gut a person.
They have swung full Trumpist. There is no room for both siderism here. They are against the peaceful transfer of power.
I'm in integrated circuit design and one of the most rewarding aspects is brainstorming with coworkers on a white board. When someone asks a question about a bug in the flow and you have the answer it feels good to help and vice versa when someone else helps you. Sometimes the job sucks when the deadlines are approaching so its nice to be able to complain about the stress with coworkers while getting a beer. In many ways a good team at work is similar to a sports team at least from what I remember in school.
Yeah, unfortunately the world is super into c and c++ tot he point that billions have been spent on making it safe via frama-c, astree and friends rather than in funding an actual safe language.
Right… that’s exactly what I said but thanks for repeating it.

Either you want to do it or you think you have to do it.
I think that's the issue, it's not the tooling. Kubernetes is great... unfortunately people are awful at unpacking the underlying layers.
Is it? In the US the majority of my coworkers just drop in (virtually or not) to ask questions without saying hi (even at the start of a sentence containing the question). That's not true for other countries.
Microsoft pauses Windows 11 update as it's sending some PCs into infinite reboot
I see what you mean. Yeah it's extremely difficult. I guess I learned that the hard way. Thought everything would proceed smoothly if I just showed up with the code already working. All they had to do is review it and apply it if they found no issues, right? Not so.

I've also filed a few bugs and feature requests on the LLVM issue tracker and GNU mailing lists. LLVM has like a trillion open issues, it's like shouting into the void. GNU almost always tells me the existing stuff should be enough and that I don't really need whatever it is I'm asking for.

For example, I requested a way to make the linker add extra PT_NULL segments to the ELF output file so that I could find and patch those segments later. LLVM has yet to respond to the issue I created, and GNU says the arcane linker scripting is enough even though the example they gave me didn't work. Only person who responded favorably to me was the maintainer of the mold linker, he added a couple lines of code and suddenly I could easily patch ELF segments. As a result, I fully integrated the mold linker into my makefile and switched to it.

My point is this:

> I am not so excited about comments such as "the standards committee should simply"

I can relate with that feeling. It's just that we're also not so excited by comments along the lines of "pull requests welcome". That's a direct challenge to rise up and directly participate. When we do, it often happens that we are not even given the time of day. To say it's frustrating would be an understatement.

I'm not going to enumerate every negative experience I've had, better to leave it all in the past. However, I've concluded that many times effort does not equal reward, and that it might just be easier to ask the insiders to change things instead and leave things be if they don't seem convinced. Change is difficult enough for the insiders to make, for an outsider it's orders of magnitude more difficult.
Perhaps they make more than that just by using the tooling internally and creating/maintaining other stuff with it — that’s a major competitive advantage
Also see “poptrie” [0] for an efficient way to do routing table-style lookups for CIDRs (longest prefix match). They basically use the “popcnt trick” to implement sparse arrays, use “direct indexing” for the first however many bits to reduce the number of indirections, and have a cool optimization specific to longest prefix match (“hole punching” in the paper).

[0]: https://dl.acm.org/doi/10.1145/2829988.2787474
A lot of people think I am Mexican.