Disagree - the timelines are completely reasonable for an actual software project, and that's what the training data is based on, not projects written with LLMs.

Yes, this is my experience as well.

With a comfortable spread out my hands are 9.5 inches from pinky to thumb, a thirteen inch laptop is so painfully small I can barely use it.

hash your thing you want to do and see if you did it recently or in order by hashing each thing you wanted to do in order to get a new hash of all the things you did in the order you did it in one value.

If you need "transactions" with microservices the traditional answer is sagas - eg multiple transaction boundaries that dont fully commit until their entire set of things is complete by passing a message or event to the next system, and having the ability to rollback each thing in a positive manner, either by appending new correct state again or "not ever adding" the original state.

The problem with sagas is that they only guarantee eventual consistency, which is not always acceptable.

There is also 2 phase commit, which is not without downsides either.

All in all, I think the author made a wrong point that exact-once-processing is somehow easier to solve than exact-once-delivery, while in fact it’s exactly same problem just shaped differently. IDs here are secondary.

I'd agree with that - two phase commit has a bunch of nasty failure cases as well, so there's no free lunch no matter what you do when you go distributed. So just ... don't, unless you really really have to.

You can't avoid distributed unless your users live inside your database.

What's the best way for a lawyer more familiar with other parts of the law to break into immigration?

Join AILA, attend AILA local chapter meetings, and attend the annual AILA conference. And get a mentor if possible.

There's very few people whose brains work like this, it requires constant maintenance and people are ready to fall into the trap easily because they are held accountable for the outcomes, and its easy to pretend your ideas would have saved you from the certain disaster your fellows brought you to.

Just like every league of legends game, it's not possibly your fault!

Then it sounds like you need to train them and also pay them better. Most people just want to stay at one company and not do the grind, but the lack of raises, poor treatment, and much better pay other places is blaming juniors for your companies problems.

Nothing the GP said had anything to do with taking away people's voice because they are rich, they are saying just because they are rich they don't automatically deserve a microphone.

HN seems very ready to defend the rich and powerful from attacks that don't even exist and its weird to come here and say how great he is while also seeing what his efforts have actually wrought - nothing positive on education or government overreach via the Trump admin. Paypal may have been ok at one point, but is generally considered to be a terrible company to work with, Palantir is a murderer for hire, and SpaceX burns billions to get us not very much with its continued explosions in the sky with hilarious mars shot promises regardless of its other commercial successes.

> how to not give these people a microphone

Yes, the word is give, as in "we are all giving our time away listening to this dumbass" - nothing about pointing my ears in a different direction is taking away anyone's ability to speak.

https://www.youtube.com/watch?v=Ruf-cLr2PZ8 I always think of this when thinking about the gracefulness of a hammer.

Turns out it’s the skill of the person handling the hammer that matters most. Enlightening! Appreciate the link!

Upholstery tacks are sold sterilized for people holding them in their mouths. Now I wonder the same about drywall nails!

Thanks for the link; that is absolutely masterful work.

Wow, thank you for this gem!!!

This is interesting, and I guess for portability not having a calendar table makes sense, but imo a calendar table and a numbers table are great additions and making yours arbitrarily complex for your use case makes a lot of this type of stuff (if you are not implementing an entire calendar solution itself) a lot easier.