If you have daylight saving time in your country, region, then the software can already handle leap hours.

At least in theory ... as the new leap hour will be probably put at a random place, this of course will have its unique problems.

It is actually not hard to test.

A crash from a leap year basically means something went seriously wrong in parsing.

Note: 23:59:60m this is time with a leap second, the 60. Except for leap second, it otherwise always is in the range 0 - 59.

So either the parser throws an exception about getting a number the programmer forgot to exist, or the 60 might be used to index into an array and be off by one, etc.

So, to test it, you basically only need test times with leap seconds.

The second critical part: to convert a Unix 32 bit timestamp into a printable string or similar higher level information, like splitting it into date, hour, minute and second, you need a list of historical leap seconds. Otherwise you simply miss them ... and get off by a second every few years.

In other words the "crashes" are often "malformed input" exceptions, which parses throw "in good faith", which do not get handled on upper layers, and terminate the process or thread.

Keep in mind, time is complex. To complex for a normal programmer, because he does not know anything about time.

When I have to do "time stuff", I just acknowledge, that I "know nothing" and read it up again :D

Concentration risk in lending is the potential for severe financial loss when a lender’s loan portfolio is overexposed to a single borrower, industry, geographic region, or loan product. Because the assets move or fail together due to a lack of diversification, a negative event in that specific segment can trigger widespread defaults. For example, if a large share of the portfolio is tied to a single business sector, such as commercial real estate, technology, or energy, an industry downturn or new regulation can hurt all borrowers in that group at once. (ncua.gov)

Someone is going to give this a go on a German Auto Bahn
That is a little bit misinterpretation. A huge deal of the auto bahn has speed limits.
I think the parts without are perhaps 10% or 15%.

Anyway, even the parts without speed limit have "a suggested" speed of 130km/h. If you are involved in an accident, above that speed, you are considered partial at fault, regardless if the mistake was on the other party.

On top of that, the stretches that are useable for mach 0.5 are many, but short. They are the emergency runways in case of war, about 3km stretches.

The second point is: if you can accelerate to that speed, you need a way to decelerate quickly. Except for the emergency/military runways, the straight looking paths are not straight. They go in meanders, to force drivers to adjust the course, in the hope it prevents them from falling asleep.

Well, I am a little bit old school.
I am still using ice.

I was more thinking about typical enterprise software.

But your example makes sense, too.

Since it's all a bunch of matrix math across ALL of the RAM,
No it is not. It is localized on the so called "experts". The stuff going on on one Mac has in generalnothing to do with what is going on on the other. At then you only have to gather the output tokens.

OMG!
Am I out of the loop and he is gone?

Party or 8760 hours of silence?

It is the same problem as having to change your password every x days or weeks.

I once used a Mayan calendar and used the English name for day and month when I changed it, and sent a screenshot of the pic to my own email.

But with modern AI, such a screen shot (was actually a photo from paper) would be easy interpreted.

It has nothing to do, or?

There always will be software jobs.

Or do you think someone fed Bosch's Anti Blocking Breaking System embedded software into an LLM?

Most people in "Computing" and AI look from the wrong angle.

The problem with software development was always: "in time", and "in budget", cornered by "defects" and "changed/obsolete requirements".

With AI programmers can boost their performance. The fact the "requirement" I implemented yesterday is obsolet today, is not as costly as it used to be. We just scratch it, and that is it.

Not sure how it works, but on my phones and tablets, I can simply download an *.apk, and install it with the file explorer.

Or, as it is a self written: I push it from the IDE to the device.

Probably just because debug mode and developer mode is active.

A vibe coder should "figure" how to activate those.

Funnily my banking app does not run, if it sniffs, debug mode is on, and a debugger is connected to the device.

Does not run, as in giving an error: disable debug mode first.

Unless they're secretly training on all your chats despite them saying they're not.

Perhaps you should try using an LLM.

Or simply join some news groups / mailing lists.

Most modern coding LLMs can code from random Jira (inert your issue tracker) tickets, better or on par with a human.

I guess once long ago you learned how to use a compiler, it is time to learn how to use an LLM, or stay using a compiler.

Well, perhaps the parent was thinking about green houses :D