one_buggy_boi

Happy to see this. The push to RTO seems to just be a front for legal constructive dismissal of expensive employees. These jobs are immediately being backfilled by remote employees on the otherside of the world. The FTE to third-party ratio is growing exponentially, it's becoming way more common to see things like a 1:5+ fte to 3p ratio.

There are two established companies that I know of, Chinese Co. NetDragon Websoft (5k employees) has an AI CEO named Tang Yu and then there is a polish rum company called Dictador that did something similar. We'll see where it goes I guess.

Can anyone on the hiring side chime in on what you're seeing from applicants? Every job posting I see has 100+ candidates, I assume most are either international due to remote option or are part of this spray and pray phenomena. Is it obvious they're unqualified or is it actually difficult to separate the signal from the noise?

Are these models high risk because of their lack of interpratability? Specialized models like temporal fusion transformers attempt to solve this but in practice I'm seeing folks torn apart when defending transformers against model risk committees within organizations that are mature enough to have them.

Azure OpenAI still flags prompts that trigger their censorship rules for human review. The only way around that is to request a waiver which is generally reserved for regulated industries. That may have changed (hope so!) but at the time I know it was a non-starter for some privacy-minded clients.

What would be a good design pattern to put these dashboards behind auth? I suppose since they're static files you could just serve them with something like FastAPI or Spring Boot and have your CI/CD refresh the static files throughout the day on shared storage?

> When interviewing as a software engineer, for example, you’ll run into places that lean heavily on algorithms interviews. And don’t get me wrong, those interviews can be fun (in the same way that Project Euler can be fun), but it’s not very relevant for most jobs

I'm curious what changed around 2015-2016 that led to the current interview process. In the before times the interview was more of a technical conversation, sure they had some gotcha questions, but nothing too brutal. If you had real experience that you could talk about, maybe it was validated against references or a background check. People usually looked for a CS or adjacent degree, and that was enough. The quality of folks wasn't too different in my experience.

I really feel for those with a lot of experience that are being dropped into the fire, especially those with families who may not have the time to memorize patterns for 3 months, but are still very capable. Non-tech, low paying jobs now ask you to create a soduko solver or trap rain water within 45 minutes. There's not many places to go for those that don't 'adapt'.

Beyond the risk associated with using a ccTLD, I've noticed that several Fortune 100 companies are now outright blocking .ai domains because they host content believed to potentially leak intellectual property, especially within the financial services industry. This is something to consider if you're launching a new product targeting such customers and want to avoid having architects/engineers go through the hassle of requesting that your site be added to an allowlist.

Is modern Ceph appropriate for transactional database storage, how is the IO latency? I'd like to move to a cheaper cfs that can compete with systems like Oracle's clustered file system or DBs backed by something like Veritas. Veritas supports multi-petabyte DBs and I haven't seen much outside of it or ocfs that similarly scales with acceptable latency

One of my first projects was to interface with an IMS system using Python of all things, there was only one guy that really knew the system and I had to sit with them for hours to even begin wrapping my head around how a hierarchical DBMS worked, how space is managed, etc. I remember the first comment he made was that the database was created for use as an inventory system for the Apollo missions. The DB I had to work with was created in the 80's. This project was in 2021, so it's still out there, supporting critical infrastructure.