• 0 Posts
  • 60 Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle

  • At my last job I managed a team of developers in India (while residing in the US). It was pretty much necessary for me to be available outside of my company’s normal work hours. I always compensated myself for middle-of-the-night activity with time off during the day and nobody ever mentioned having a problem with it. I was eventually rewarded by being laid off with everybody else when my company was acquired by a west coast tech giant.



















  • c-suite

    CEO, CTO, CFO etc. In a '90s Internet startup like the company I worked for, the “C” really stood for “clueless”.

    giant printouts of insanely over-normalized databases

    Over-normalization is a database thing - a simple example of normalization would be a “People” table where instead of having the “Salutation” field just contain text like Mr, Mrs. etc., you have a separate “Salutations” table with all the possibilities listed and keyed with an ID (usually just a sequential number), and then the “People” table stores a Salutation ID for each entry instead of the actual text. It’s a valid and standard thing to do with database design, but it can be taken to extremes where absolutely every possible trivial thing that can be normalized is, producing an overcomplicated mess that is extremely difficult to work with programmatically.

    Printing out this over-normalized mess of a database on multiple sheets of paper which are then taped to the wall is utterly useless.

    How is a database a trick?

    The printout is the trick - it fools the bosses into thinking you’re doing something amazing and productive when you’re really just fucking around. It only works on the technically incompetent, of which there was no shortage in '90s Internet startups (or today).