There's been a lot of work on the simulation itself over the past month, which doesn't lend interesting screenshots. Today I finally got to implementing good terrain decals, including normal mapping. I had to save the underlying geometry normals in a separate gbuffer attachment from the final visual normals. Perhaps there's a better way.
You need to use typesafe containers, which in C are built with macros. Sean Barret's stb library is perhaps one of the most famous implementations. My sti library (https://github.com/yzziizzy/sti) also has a variety of typesafe containers to take for example (or just use).
The core idea is that you can carry around type info by putting a pointer to the internal type inside some anonymous struct. This pointer can then be used at every function call (which are wrapped in macros) to get information like element memory size. Clever construction of the macros allow them to end up having the rvalue type desired. There are some other techniques, but that's the basis of it all.
Isn't there supposed to be a big jobs shortage in the US right now? People are posting online about how they applied to 800 jobs and didn't get a single call back?
The female mind naturally looks to get resources from others. This is normal, as the homemaker shouldn't be out trying to kill a deer or plow a field. The problem comes when they embrace feminism and reject family; there's nowhere to get free resources from except daddy government.
A) giant corpos that barely know you exist and expect about 1/20th of your maximum productivity capacity because that's the average of the tards they generally hire.
B) small companies with honest bosses who do respect you.
Bosses only care about shipping yesterday. Half the time they can't even tell if the thing you shipped is the thing they asked for because they can't even remember what they ate for lunch yesterday.
What you really need to get good at is convincing them that what you delivered is actually what they asked for. They don't understand what they want, so how would they know the difference? This is the enlightened path; trying to educate retarded clients is a fool's errand.
Professional LLMslop-fixer will be the new primary task of senior devs at any company not smart enough to ban vibecoding entirely. But, as you was, work is work. My entire professional career has been webshit of one kind or another.
I worked for a fintech startup and they were just as bad as any social media site. Execs don't give a shit. The only reason the banks move slow is because their systems are so old and glitchy that it takes eternity to do anything, and the Boomers that run the banks are too retarded, cheap, and boomery to do a green-field replacement of their 60 year old systems. Better to issue another dividend and go on more cruises, future be damned.
I once worked at a corpo place that had db partitions older than I was. Yes, partitions. It predated the general concept of databases being on filesystems.
CICD is a waste of time. You ship faster without it in practice because you never have to fuck around with it or get tripped up by some failure in the complicated deployment system. git push to prod, restart the server process. done.
Oh, it's a totally fucked mentality from the standpoint of a sustainable business model. 98% of software companies don't care though. It's all about getting the next funding round or scamming the stock price. Total Boomer mentality.
I never said anyone should care about the quality of corpo code. My argument is that good devs can ship garbage a lot faster than tard plugin cobblers.
That's what most of my jobs were. I was the dev getting rushed to ship everything out asap. It was shit code, but it got out there fast, sometimes even the same day.
What's not useful are tards who can barely code and only know how to cobble React plugins. The reason they're not useful is because they're slow, and hiring a swarm of them doesn't make them any faster, it just creates a much larger amount of shit at the slow pace.