Merad

It's not about looking at the body (in my area at least, funerals usually don't even display the body), it's about grieving and mourning. Or supporting other people who are going through grief and mourning, even if you don't feel it very strongly yourself. My mom died of cancer about a month after lockdown started in 2020 so we couldn't have any kind of service, but we had a "celebration of life" a year later. I'm glad that we did.

> LLMs should never do math. They shouldn't count letters or sort lists or play chess or checkers.

But these aren't "gotcha questions", these are just some of the basic interactions that people will want to have with intelligent assistants. Literally just two days ago I was doing some things with the compound interest formula - I asked Claude to solve for a particular variable of the formula, then plug in some numbers to calculate the results (it was able to do it). Could I have used Mathematica or something like that? Yes of course. But supposedly the whole purpose of a general purpose AI is that I can use it to do just about anything that I need to do. Likewise there have been multiple occasions where I've needed ChatGPT or Claude to work with tables or lists of data where I needed the results to be sorted.

If I understand the GP correctly, there's no notion of semver involved. Any difference in the schema results in a runtime error.

Unless you have some tricks up your sleeve that I'm not thinking of, an immediate consequence of this is that zero downtime deployments and blue/green deployments become impossible. Those both rely on your app being able to run in a state where the schema is not an exact match for what the app expects - but it's compatible so the app can still function.

That's not correct. He decided that the aircraft was out of control because his primary displays went out at low altitude - the manual says eject if out of control below 6000 ft. But in fact the plane was still flying and responding to controls just fine.

A big factor in this seems to be his overall lack of experience in the F-35 and not flying enough hours to really stay proficient. Highly recommend this analysis by two former naval aviators: https://www.youtube.com/live/g8PBA7k6vP8?si=o2DDBX1XqmM_x1gR

I haven't used it in 4-5 years but at the time we were generating html docs with it. IIRC it supports several other output formats.

LINQ is the name for the overall system. LINQ can be written using two different styles:

    // Method syntax
    var evenNumbers = numbers.Where(num => num % 2 == 0).OrderBy(n => n);

    // Query syntax
    var evenNumbers = from num in numbers
        where num % 2 == 0
        orderby num
        select num;

Method syntax and query syntax are both part of LINQ (query syntax is syntactic sugar). .Net developers tend to overwhelmingly prefer method syntax.

Sandcastle Helper File Builder has been around forever and started as an internal MS project IIRC, but for some reason few libraries use it.

https://github.com/EWSoftware/SHFB

I have a 6-7 year old Omron brand device that doesn't do this. I can always tell right away when my BP is running high because I can feel the machine squeezing harder than normal to get the reading.

I mostly live in the windows world, and since at least Win 7 its sleep and hibernate have been reliable enough that I use them regularly. When I'm deep into a project for work I can easily have a dozen apps open. Having to reopen them multiple times a days is (to me) just a waste of time when sleep works great.

Your birth is an event that happened at an instant in time, but very few systems concern themselves with that detail. The vast majority need to store birth _date_ and have no interest in the time or location.

ICE aren't going to go away any time soon. Battery tech has a long way to go before it can compete with the energy density of liquid dinosaurs, and if it did there are plenty of cases where ICE has major advantages over battery power. But even if say 90% of the vehicles on earth could be replaced with electric, should we really stop innovating on that last 10%?

I don't know the exact answer but when I worked there while in college 20 years ago the package cars were never connected to chargers overnight, nor did they receive any other special attention. I would imagine that they use heavy duty batteries and just spend an enough time driving and idling that it all balances out during the workday.

To "cross the line" means that you went too far, in this context meaning that someone revealed secrets or otherwise talked about things that they shouldn't reveal. So to walk up to the line means that the person was willing to talk about the topic or share their knowledge, but did so without "crossing the line."

Yes, I think this has been a huge missed opportunity. Making hybrids the standard car is a big win for fuel efficiency. Then shifting towards plugin hybrids with a 40-50 mile EV range has the opportunity to radically reduce emissions without giving consumers any concerns about range anxiety. Do this shift over the course of a decade or two, use that time to build out charger infrastructure, _then_ start pushing towards pure EV's.

Where are you getting 1500 Soyuz flights? As far as I can find the number is more like 150. It also experienced failure and loss of crew on two missions (Soyuz 1, Soyuz 11).

Databases have pretty robust access controls to limit (a sql user's) access to tables, schemas, etc. Basic controls like being able to read but not write, and more advanced situations like being able to access data through a view or stored procedure without having direct access to the underlying tables.

Those features aren't used often in modern app development where one app owns the database and any external access is routed through an API. They were much more commonly used in old school apps enterprise apps where many different teams and apps would all directly access a single db.

Pledging allegiance to the flag is a product of late 19th century sentiments that tie back to the US Civil War. This article has some backstory: https://www.bostonreview.net/articles/jack-david-eller-pledg...

I used to work in internal IT at a Fortune 500 working with different departments in the company to turn Excel spreadsheets and Access97 tools into web apps with real databases. The problem is that the companies/departments where this is the case all have their own workflows and business processes, and 99% of the time are completely unwilling to consider change. It'll be really challenging to develop software that can be sold to multiple companies even when they ostensibly do the same thing.

Many people store UUID's as text in the database. Needles to say, this is bad. TFA starts by proposing that it's bad, then does some tests to show why.

I'm not quite sure what all the links have to do with the topic at hand.

Best practice in Postgres is to use always use the text data type and combine it with check constraints when you need an exact length or max length.

See: https://wiki.postgresql.org/wiki/Don't_Do_This#Text_storage

Also, I think you're misunderstanding the article. They aren't talking about storing a uuid in a bigint. They're talking about have two different id's. An incrementing bigint is used internally within the db for PK and FK's. A separate uuid is used as an external identifier that's exposed by your API.

An int PK does not give you 4 billion rows. For example, in Postgres every time an insert transaction has to rollback, the id's that would have been used by that insert are discarded and gone forever. Likewise people often don't realize that Postgres' very convenient upsert syntax (insert on conflict do update) will consume id's from the sequence _every time it runs_. If you do an upsert with 100 rows, it will peel off 100 new id's just in case they're needed... if they aren't used, they're discarded. This can chew through 4 billion id's really, really fast.

Personally I would only use an int PK in a table where you know the bounds of the data with very high confidence. Like, at my last job the software involved working with our client's physical store locations. If we managed to capture the entire North American market for the type of business that we worked with, we'd be looking at about 50k stores.

The game actually does a pretty masterful job of tricking players and convincing them to go way, way overboard in their preparations. The submarine/mobile base and the robotic mining suit aren't even necessary to finish the game. The final levels of the game can actually be finished just by swimming freely with the seaglide. The rare material that's only available in those levels can be picked up as broken pieces laying on the sea floor, and IIRC you only need 6 pieces of it to finish the game.

For anyone who might not be aware, this is true for most companies. Any changes to your plan will usually require the removal of any grandfathered features, regardless of what the tier 1 CSR tells you.

It seems like GitHub is rejecting requests from affected IDE versions. We discovered this yesterday because PR integration was not working even though the GitHub login/token was correct. Issue resolved by upgrading the IDE to the latest version.

I'd recommend using Crockford base 32 [0] to encode the bytes. It makes the text more human friendly by eliminating case sensitivity, removing similar/ambiguous letters, and preventing accidental profanity.

And in most cases I think you're also better off just using a uuid and encoding its bytes as base 32, in which case you're basically doing type id's [1]. If the "slug" portion of the id actually encodes a uuid, then it gives you the option to store it in your database using an appropriate uuid type. This will make your database much happier than using long string PK's.

0: https://www.crockford.com/base32.html

1: https://github.com/jetify-com/typeid

Walmart. Walmart is totally the winner in this category. It has all of the grocery store things you mentioned plus mountains of clothing, household goods, mind blowing technology, medicines...

Show them all of these wonders - then tell them that this is where poor people shop.

Many of the migration tools I've worked with include the concept of scripts that are run every time migrations are applied, in addition to your standard migration files. So things like views, functions, SPs can go in these "every time" files rather than being duplicated in migrations every time they change.

> Canned food: if hermetic seal is intact, it's edible.

Definitely not a universal truth. Canned food can develop botulism, you do not want to mess with it. Any cans that are bulged or show signs of swelling should be discarded - don't even risk opening them.

There are guys on YouTube who explore old army rations (which were basically all canned food prior to the 1980s), and when they decide to open a bulged can "for science" they will often literally break out a gas mask. That said, it's also not terribly uncommon for them to find rations dating back to WW2 and older that are still partially edible.

Yep, you're walking in one of the voids that is largely ignored by modern front end web dev. Frameworks like React and Vue advertise that your can easily add them to any page and that's technically true... but when you have a real world app built with a backend framework and you want to integrate it with React/Vue in a sane way... good luck to you!

All the pieces exist to make it work, but you won't find much documentation to help you. You'll have to rely finding blog posts, but of course if the post is more than a year old most of the libs or tools they're talking about will have totally changed. Once you do get everything up and running you'll often find that the dev experience is less than great.