I got a message today from a recruiter that included this line: "The firm believes in their product with such confidence, that they are willing to provide equity to anyone that comes aboard."

Ummmmmm..... Doesn't that mean the opposite pretty much??? Sounds like they are willing to liberally give up equity. Either way I though that was a really non-sensical thing to include.

One time I got an offer for a job I had found through a recruiter. When I wasn't sure if I was going to take the job, and it became clear to the recruiter that he wasn't going to be able to convince me, he had his "manager" get on the phone to try to tell me why I needed to take the job. One of the reasons was "because I was a recent college graduate and wasn't a CS major (I was a minor but had a lot of experience), this was the best offer I could get." It thought it was pretty sad that they resorted to insulting me to try to get me to take the job so they could get their commission. Sleeaaazzzyyy.

Trying to unit test legacy code with lots of static methods suuccks!

Sometimes they pay off...

I just had a flashback to the good ole days of using HTML tables for website layouts. Tables within tables within tables were pretty ridiculous, but they really got the job done pretty well back then. It makes me think about how technology changes and a principle that was once so widely used is now almost completely obsolete.

Never buy crappy, consumer-grade SSDs for use in production servers/RAIDs. This might sound obvious but at the company I used to work for, through a series of bad decisions by management and cheapness, we ended up with the cheapest consumer SSDs you can imagine powering all of our storage.

This turned into a nightmare spanning years of failed hard drives and a continues cycle of ridiculousness. Drive failed after a few days, gets taken out, sent back to manufacturer and then replaced with another equally crappy drive destined to fail within days/weeks.

Our ops people were going to the data center multiple times per week to replace failed drives. Lesson I learned: cheaping out on system-critical hardware and software can have long standing consequences and in the end usually doesn't end up actually saving money when you account for time employees have to spend dealing with issues that result from it.