Lightor

I’m the CTO of my company and was just forced this week to downsize from 48 devs to 3… It was really hard. Telling everyone myself was even harder. Everyone was nice about it, understood it wasn’t my choice, but you’re impacting lives. To talk to someone having a normal day and then suddenly they’re reeling and trying to think of how they’ll survive.

I honestly think if our board has to be the ones to tell them it wouldn’t even register for them. It would be like ordering food. The people at that level only see money.

There must be something. I see so many comments and how horrible it tastes and honestly I can’t tell the difference. I sprinkle this stuff on my bran cereal and it tastes fine to me.

How?

You’re wrong.

What is asserted without evidence can be dismissed without evidence.

I think a full can of water would hurt more

Ahhh this line of logic. Yes, people can forego luxury items and save money while being healthier. You could never eat red meat, or drink soda, or have ice cream, sure, that would be much healthier and cheaper.

It’s important to me that I have no goal or purpose, and I will focus on making that come true no matter that.

My guess would be around your note. If someone mistakenly has two SSNs (due to fraud, error, or name changes), combining DOB helps detect inconsistencies.

Some other possibilities, and I’m just throwing out ideas at this point:

• Adding DOB could help with manual lookups and verification.
• Using SSN + DOB ensures a standard key format across agencies, making it easier to link records.
• Prevents accidental duplication if an SSN is mistyped.
• Maybe the databases were optimized for fixed-length fields, and combining SSN + DOB fit within memory constraints.
• It was easier to locate records with a “human-readable” key. Where as something like a UUID is harder for humans to read or sift through.