skysight-inc/HackerNews huggingface dataset:
> Rolling out API changes concomitantly with downstream changes to the documentation or the OpenAPI spec.

> Introducing feature-level changes and the blog post announcing those changes.

These are horrible reasons to use a monorepo. Commits are not units of deployment. Even if you're pushing every system to prod on every commit, you'd still basically always want to make the changes incrementally, system by system, and with a sensibly sequenced rollout plan rather.

To take one of the examples above, why would you ever have the code implementing a feature and an annoucement blog post in the same commit? The feature might not work correctly. You'd want to be able to test it in a staging environment first, right? Or if you don't have staging, be able to run it in prod behind a feature flag gated to only test users, or as a dark launch, or something to verify that the feature is working before letting real users at it and having it crash your systems, cause data corruption, or some other critical problem that would necessitate a rollback. But none of this pre-testing is possible if the code changes are really being done in the same commit as the public announcment.

And talking of rolling back... When you revert the code changes that are misbehaving, what are you doing with the blog post? Unpublish it? Or do some kind of a dirty partial rollback that just reverts the code and leaves the blog post in place?

The same goes for any kind of cross-project change[0], some of which appear more compelling on the surface than the "code and blog post in one" use case (e.g. refactoring an API by changing the interface and callers at the same time). Monorepos allow for making such changes atomically, but you'd quickly find out that it's a bad idea. There are great reasons to use monorepos, but this is not it.

[0] I wrote more about this a couple of years back. https://www.snellman.net/blog/archive/2021-07-21-monorepo-at...
Is 'cotton' racist as well?

How about 'train'? I heard that they used them in the holocaust.
what about jami? https://jami.net
> I’d argue he did better than Jobs would have done.

At making money? Possibly.

At making quality products. Definitely not.
I have often wondered if something like that is the physical basis of momentum, or at least contributes to it such that apparent mass is incorrect for charged particles.
It is not, because ice has a smooth surface and that probably the surface layer melts a bit because your shoes are warm?

That would be my reasoning, but it likely seems to be wrong, well why?
Star Labs is making what you're looking for with their StarFighter laptop, although you'll be paying MacBook Pro like pricing for it (and delivery would be in March at the earliest): https://us.starlabs.systems/pages/starfighter
You're talking about the "2D gas vs liquid" discussion?
The scariest bit to me is that if it detonates, the main product of that is nitrous oxide, which is rather… burny, and is its own source of oxygen.
Same - I really like seeing things like this.

Not only because it means we're about to learn some big stuff, but also because it would be completely *preposterous* if humans at our puny stage of development had already correctly figured out every last detail about insanely complex things like the exact size, age, and origin and age of galaxy-sized things that developed tens of billions of years ago, billions of light-years away from the tiny rock we stand on. Getting things wrong shows that people are actually doing science honestly!
I’m curious about the hierarchy between crypto scams and gig economy bathroom cleaning apps.

That aside, finding warm bodies to fill a position is usually not the problem, they need to actually help your product grow.

Focusing on the technology prominently is like hiring security guards by touting the big guns they’ll get. You’ll be rolling the dice on the people that come to you for the position.
While there is no inherent proof in actions, deleting data and denying access to labs and data does not inspire confidence when the WIV makes claims one way or another.
Earth came quite late to the party and it spawned life relatively soon after.

That's why it's strange we haven't discovered any Dyson spheres/swarms (in any galaxy).

Either life is indeed absurdly rare, or Dysons are impractical for some reason, or there is a way to mask heat.
The “narrative” example is pretty good, but the “conversational” example is rather unpleasant to listen to.

(Especially if you know how well Meryl Streep delivers that monologue in the original: https://youtu.be/Ja2fgquYTCg)
Analog Chess – pieces are not constrained to a grid
Look, I'm not trying to start a holy war, I'm just relating my experience of more than just a toe being dipped in. Find the argument somewhere else.
More than google.com? Maybe, but it's close. Also, I'd be surprised if those behind NOTAM were all "professional engineers" since software PEs are pretty rare, relatively speaking. Especially in the US.
This makes perfect sense for founders/c-level people, and owners in general.

But here is the employee paradox: He may sooner or later shift his main focus from customers to his own career. So he reinvents the wheel building the next level hot js framework, start measuring his goals in Github stars and conference bookings...

In short, his tech stack IS the product, again.
Counterpoint: Slack
Writing a Vim9script to Lua Transpiler in Rust for Neovim [video]
I would pay $5 to have every one of these projects stop saying "alternative to ElasticSearch" unless they implement the ES API (as https://github.com/zinclabs/zinc at least claims) because if one just wanted some schemaless full text searching wizardry, there are about 10 of those projects. If one is trying to replace kibana or the damn near infinite log gathering tools that target ES, Sonic and Melisearch and and and are not going to get it done

q.v. https://github.com/zinclabs/zinc/blob/v0.3.6/docs/swagger.ya...
Most people who experience psychosis don't experience it as a perpetual
state,

Agreed.

and they aren't particularly more dangerous while experiencing or any more
dangerous while not.

Hard disagree. I have been in a mental ward. I have been in close proximity to people who have been undergoing psychotic breaks. Never have I felt in more danger for my safety, even though, ostensibly, nurses and other trained medical professionals were right there to deal with the issue. Being in close proximity to someone undergoing psychosis is a terrifying thing, and it's no surprise that traditional societies, in the absence of other mechanisms, would choose to exile people undergoing psychosis. And if the people never returned from their exile, well, that's a hard thing, but the great spirit must have had a different purpose for them.
We’ve been doing async standups and it’s been fine. The thing that really requires synchrony is if there’s a blocker which we deal with as they occur on an ad-hoc basis.
SEC Charges Genesis and Gemini
I'd rather have one idiot on the case than that idiot + a bunch of other, self-selected idiots prompted to show up by an app. At worst they will actually hinder police response and/or get themselves or others hurt.

Keep in mind that the user base of Citizen is not a uniform distribution of the population either - certain classes (for the lack of a better word) will self-select and are likely to have similar issues to the police itself. In fact you might have the kind of people who can't even make the cut to join the police itself, which is not a good thing when you see how low the bar for the police is to begin with.
A lot of products already have both printed on the package.
“Study in mice implicates changes to way DNA is organized, regulated rather than changes to genetic code itself”

What??
Ruby will be fine, this is more of an impact on Rails as the centerpiece for getting-to-MVP fastest. It once was the case, and might still be in some capacity, but everyone with that expertise is on years 10-15 in their career and don't come so cheap because they've put in the work to earn more and are well within their rights to say they aren't going to work all nighters.
That's a more mature and level headed take than what I suggested.
> “We hope these results are seen as a turning point in our ability to control aging,” said Sinclair. “This is the first study showing that we can have precise control of the biological age of a complex animal; that we can drive it forwards and backwards at will.”

Wow.
"Under construction now."

Wiki says: https://en.wikipedia.org/wiki/Australia-Asia_Power_Link

projected to begin construction in mid-2023

And:

In January 2023, Sun Cable went into administration, the equivalent of Chapter 11 Bankruptcy.
...the GNOME/Apple hacky way, that is rendering at an integer multiple and then downscaling as needed. It works, but it's not optimal, and won't ever be as sharp as it could be.
Like that recent post saying your tech stack isn't your product, your customers tech stack also isn't your product.
These guys have been doing tutorials, since the beginning.

What you’ll find with a general purpose platform like react-native. Is you’ll spend 80% of your time debugging. Just random issues that affects iOS or android. And you’ll still need to understand ios and android architecture. There is no silver bullet. Tradeoffs... Just an excuse for web developers to avoid learning another language.

https://www.kodeco.com/
let's go Uptown! One of the more colorful bars in the mission for sure :)

Their bathroom is fun
previously: https://news.ycombinator.com/item?id=33315237 (the blog post has also gotten some submissions, but nothing as compared to the github submission)
Maybe with some examples:

https://wiki.haskell.org/Zipper

https://en.m.wikipedia.org/wiki/Zipper_(data_structure)

To give you an example: the zipper of a list is two lists - one for the elements after the current one (the hole), another for the elements before the current one, plus the current element.
I'd trust a chair of Harvard physics over a anonymous HN commenter on this one. Not to appeal to authority, but there really isn't any other option here.
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
Which part of "No" are you falling to understand.
"Imagine a field that answers questions more often than it finds new ones; that'd be a pretty stagnant field to be in."

Funnily enough, that's what the science community of the ending 19. century thought about physics, before they started to look deeper.

Max Planck was advised against a career in physics, because:

"In this field, almost everything is already discovered, and all that remains is to fill a few holes."

He rather found some more holes.
Why is 3:2 better?
Experiment results that disagree with theory is EXCITING. I hope this contributes to progress and I'm giddy just imagining the model of the universe we have 50 or 100 or 500 years from now.
Previous discussion: https://news.ycombinator.com/item?id=33487598
I mean, not really? We usually measure air temperature but ground and water are much slower to change and are usually not the equal to the air temperature. I think Fahrenheit still wins here: There might be ice on the road when the air is as warm as 40f during a passing winter warm front. There is definitely ice on the road at 0f. That’s a useful 40 degree range of increasing levels of caution.
There's also a PS2 version, really cool stuff to see.

I don't know what schools are like nowadays but when I was in school I was taught Java and it feels like giving people ways to use that language in odd places is only going to bring about more good and fun projects to the world
It’s possible you’re doing it wrong. A bidet is a tool but it doesn’t do _the work_ for you.
The ethics around impersonating someone are pretty much absolute. It's not ethical. The degree of harm doesn't really factor into that.

They can likely do whatever they want with the account of course.
While not wrong, everything breaks at scale. Everything. Anyone that says otherwise is just not interested in talking about where what they built will break.

And note that this is more than just scale of use. It is also scale of development. Keep adding changes to something, and it will break. Stability of application requiring stability of development is just not something we care to admit, that often.

That is, don't hide when/why something will break. But also don't get blinded looking for how to avoid all breakage. If you can, find ways to isolate failures and block off entire sections.
"hey we identified every single bond we bought with the funny money we printed out of thin air, so no worries comrade."
If you accept the possibility of the multiverse as a "solution" to why the laws of the universe allow for life to develop in the first place (in quotes as it's not really a solution as it can never be proven), then it seems to me there is no reason to think that intelligent life can't be so rare that only in 1% of all universes that can support intelligent life, intelligent life actually develops.
CDC - Bird Flu Current Situation Summary :https://www.cdc.gov/flu/avianflu/avian-flu-summary.htm

Avian influenza : https://en.wikipedia.org/wiki/Avian_influenza
as far as we know spacetime is everything that exists
That's a false equivalence. MOND has made several predictions before they were observed (external field effect, linear Tully fisher relationship, early galaxies). I think LCDM's made fewer if any predictions.
That copper coil should do it on its own in some capacity. Drop a magnet or something through the coil. It should slow down passing through. Lenz's Law.
I dont know WiFi, but ethernet is now capped by my ISP plan: https://pasteboard.co/AGJiRV287mTA.jpg
Nobody cares if your warehouse is neat and clean. Your customers never go in there. They just receive orders that are shipped out of it.

But if your warehouse is a mess, if the aisles of your warehouse are blocked by crates strewn everywhere (that you've been meaning to put away for ages), then it does matter if your warehouse is neat and clean because it takes forever to maneuver your forklift in to retrieve products to ship them out. If your warehouse is disorganized, and you can't find anything when you need it, then it matters.

The real trouble, I think, is when people have reasons to choose not to keep the warehouse organized and functioning smoothly (like workers who see it as drudgery or managers who want workers working on something else) and they try to excuse it by saying, "Our customers never visit."

(I don't think the person above is doing that, incidentally. I think they're just agreeing with the keep your eyes on the prize message.)
It sounds like it subjectively _felt_ oversized, but objectively, it was undersized
Generally outages, deratings, and unavailable equipment have to be reported to the system operator. Not doing so and then claiming for lost revenue from broken equipment due to curtailment would be fraud.
I dunno, I felt like this was a huge cop out in the movie Men in Black
Ask HN: Protect REST API for mobile app without accounts
I currently develop a end-user iOS app which does not have any sort of account (and I don’t want to introduce them).

The app uses a REST API (provided by Cloudflare Workers) quite frequently. I’m currently thinking about ways to protect this API or my workers from malicious requests (especially Denial of Wallet attacks).
I thought about mTLS so publish the app with the bundled password protected .p12 file and obfuscate the password. Then block all requests that are not coming from the app via a mTLS rule.

However, I’m not really confident that this is really secure. So I would love to hear your thoughts on this idea and if there are better solutions given the constraints explained above.
Originally it was a play on words "a patchy web server"
Computer Science doesn’t get the pass, unfortunately. First of all because it’s a branch of maths, so in reality it doesn’t have any instruments to worry about.
Secondly, applied CS relies on an incredibly simple instrument: binary logic gates. The computers we have today are just a mesh of stuff that flips on and off with no intermediate states. That’s pretty primitive as a means of expression and computation compared with the rest of the universe
The letter says they’re removing “field” as in “field work” and “going into the field” and replacing it with “practicum”.
The extra vertical space is better for reading stuff, and looking at code. It also allows for smaller laptops with the same usable screen space - they don't need to be as wide.
“Closing the Gap: How AI Empowers Critical Thinkers in the Modern Economy”
> now MSFS is as good as the software in any of those sims

Are you sure? I'd expect the primary purpose of a pro simulator is to be a training aid in which case the simulation needs to be extremely accurate especially at edge-cases such as near/at stall speeds, various combinations of faults, etc - the dangerous stuff you'd actually want to train for and can't easily/safely replicate in a real aircraft.

I'm sure consumer-grade sims do a great job at replicating routine flight, but I'd bet good money a pro sim is much more accurate at replicating let's see a stall condition.
Strong disagree. It should always be surprising, and the people that designed and uphold the systems that allow for this should be held accountable. The world does not lack agency.
I recently started using a 1280x1024 display in a 5:4 ratio for my retro PC. I really like it. It's more square than 4:3 and feels very utilitarian.

On the other hand, I still prefer 16:10 over 16:9 for modern displays.
I'm not really sure that "expert" is objectively quantifiable. Plenty of experts have their own biases, especially when it comes to information that conflicts with positions they have long advocated for.

I'm thinking specifically here of the various stories that crop up when a grad student can't publish work that contradicts their advisor's own published work, but there are also plenty of examples in other fields as well.

At the end of the day, you have people who have either studied a thing or have direct experience working with it, and you assign them some amount of trust since they've done it more than you have. You don't need to know much about a particular sub field of biology to recognize that someone claims to have expertise in biology.

Knowing some yourself helps you see if they're making it up. Even if you don't know much, you can still pick up on whether they are open to new ideas, though.

All of this is to say that reducing "expertise" to a quantifiable binary answer is not an easy thing.
As an engineering manager, I'm sad for you. I believe in almost full transparency with my teams. The only things I keep private are personal items and things that are not yet ready to be shared.
I rock a 55" curved 4k TV (16x9) on my home desktop. To watch TV I move the desk chair and sit on my couch on the opposite wall. I can't explain how efficient this setup is in a small apartment.
It's your article, you don't have to justify anything.

That said, it still would've been nice to hear if Haskell has bought you anything that other languages don't do.

Would I have asked the same question for a JS article? Maybe I wouldn't have asked - I'm a bit more familiar with JS than I'm with Haskell - but a "and here's why I picked those tools" section would still have been interesting. I like hearing how people think about solving problems.

The fate of writing in public: people will always ask for more info on the parts that they're interested in.
That's your take away?

I think the point is that all the people in the world and all the various information they have received leads them to believe that a laboratory studying this very virus was responsible for its release.

You chose to side with those that would blind themselves to any information that doesn't conform to a narrative
> Vendoring/Versioning for discrete packages is a heavily invested in problem space for most tech stacks you'll come across.

100% disagree. The problem of "How do I define my dependencies and have a package manager reify that into a concrete set of versioned dependencies" may be a solved problem, but the tools for tracking dependencies across many repos and driving upgrades is neolithic. About the only company I've seen that does this well is Amazon, and they have yet to sell us version sets as a service.

> OP has such a tiny project that I'm not convinced they're even dealing with dependencies in a traditional sense. But well before you get to Google scale, you'll run into situations where you just want to change one thing and don't want to change every single downstream dependency which normally would have been isolated via a discrete package that doesn't have to change in lockstep. And then that exact same pain starts to exist for deployments and needs to be worked around.

As I alluded to above, the dual of this is that getting everyone to update their dependencies is orders of magnitude more difficult when you have a polyrepo setup, even if we're working under the ideal situation where repo setup is standardize to such a degree that a person can parachute into a repo and become effective within minutes.

> Nothing about the above has changed in the last 5 years, it's kind of the ground truth of monorepos via multiple repos: You're the first person I've ever seen imply monorepos don't offload complexity to tooling, even amongst proponents.

Both polyrepo and monorepo have complexity in scaling that is handled by their tooling. The difference historically is that OSS polyrepo tooling has been better and better integrated because that's just how most things are built in any language, but that has been improving over the past ~half decade

* Bazel maintenance complexity has dropped precipitously, and many of the initial bottlenecks you hit with it have been solved in OSS.

* If you're anti-bazel, gradle and cargo monorepo support is decently good. I believe the same is true in js these days, but I don't have hands-on experience

* Services for managing monorepos like sourcegraph for codesearch or mergify for submit queue now exist that make it easy to adopt the patterns that work well at large companies.

* Microsoft and others have invested in git to improve scalability of developing against large repos.

* you have OSS tools like git-branchless that further improve the experience of working in a monorepo

There are a bunch of companies in the O(100) - O(1000) developer range that are using this stuff and it works very well.
Not just SQL but MongoDB and Elasticsearch also seem horrible by comparison. The only other query language that IMHO is as intuitive as Cypher is Splunk.
This will end the Chrome/Blink monopoly.
We already have, they're now 'allow' and 'deny'. I drink my coffee denied, what do you prefer?
A simple set of dtos in the application layer, defined around their respective application services (use cases if you will) is ok. Required for most bounded contexts/microservices. You properly organize application and domain layers. It does not need to be verbose. The problem is when people define dtos on the http infrastructure, then similar dtos on the app layer, domain models (often with all attributes being public and behavior scattered elsewhere), then dtos for database schemas... AutoMapper looks useful in these scenarios, but it's the wrong solution for poor design.

While manual handling is required when you have proper domain models with controlled creation and change operations, these tools can be useful for other matters.
Put circulator fan to mitigate
It's incredible how Randall seems to be able to come up with an endless number of fun ideas even after all these years.
Twitter Employees Escorted Out of Singapore Office
Related ongoing thread:

Grayscale on 1-bit LCDs (2022) - https://news.ycombinator.com/item?id=34354213 - Jan 2023 (73 comments)