Back in the VGA days, I worked for a video card maker, and one of them supported a multi-head configuration. You could stick as many as 16 into one machine, if it had enough slots. Thus driving 16 monitors at once. I was responsible for taking the stock Windows 3.1 display driver for the chipset and modifying it for multi-head support. That was a really fun and challenging project, and ultimately very satisfying. I am pretty sure there were a few customers who needed the full 16-card setup.
BTW this was done in the day when drawing pixels on a screen was all done via the CPU telling the card "draw /this/ pixel with /this/ color". Good times!
Someone tried this, I saw it one of the Reddit AI subs. They were training a local model on whatever they could find that was written before $cutoffDate.
"Your job is not safe" does not mean you should do everything possible to keep your job -- allowing yourself to be unfairly exploited and abused.
It means that you need to be responsible for yourself, and not allow thoughts like "I'm a valuable employee", or "I have too much seniority", or "my manager and I get along great" to convince you management won't lay you off or fire you or that they owe you anything.
As others have said, the employer-employee relationship is first and foremost a business relationship, i.e. transactional: you work and they pay you. When that relationship doesn't work any more for one side or the other, it ends.
It does often happen, of course, that professional friendships or even personal friendships develop. You are, after all, spending a lot of time with your co-workers. But don't think your good relationships or friendships will help if the business decides a layoff is necessary.
I've got some developer PTSD from a previous project where the solution architect decided to use CosmosDB for the entire domain model that was very relational and very transactional, all because "NoSQL is easy to learn and allows rapid development".
Yeah it is, until you're trying to manually create and maintain relations between documents in different schemas owned by different microservices.
I can almost guarantee you'll like it. Kotlin has this same feature and I've found it saves a good amount of boilerplate null checking when inter-operating with lousy legacy Java code.
BTW this was done in the day when drawing pixels on a screen was all done via the CPU telling the card "draw /this/ pixel with /this/ color". Good times!