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

help-circle


  • 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).








  • I feel like that’s the same underlying issue: The requirements are not understood upfront.

    Actually on most of these failed projects the requirements of the original customer were pretty clear. But the developers tried to go far beyond those original requirements. It is fair to say that the future requirements were not well understood.

    the alternative is building a prototype, which you’re allowed to throw away afterwards

    Lol I’ve done many prototypes. The problem is that management sees them and says “oh, so we’re finished with the project already? Yay!”




  • I (white boy) visited India in the early '90s and brought back a bunch of rolls of half-Rupee coins as souvenirs. Turns out they were the exact same weight and diameter as US quarters (even down to the number of ridges, which makes me suspect India bought a bunch of used US minting machines to make them), so I started using them at laundromats. The exchange rate at the time was 35 Rs to the dollar, so a load in the US that normally cost $1 was costing me less than 6 cents. I do feel bad for the harassment that actual Indian customers probably ended up receiving, although possibly the owners never noticed or cared.



  • My small tech company (which I really liked working for) had < 100 employees. We struggled through a few near-death experiences because of slow sales and panic from our original investors, then we got saved for a few years after being purchased by a larger company (with around 1000 employees). Then that larger company (a small player in the networking equipment genre) got bought by probably the largest player in that space, and within six months everybody from the 1000-person company (excepting a few c-suite types) were laid off - the company had only been acquired in order to eliminate a very minor competitor. There is no safety in small.






  • I had a coworker who did exactly this back in the '90s. He was an expert in a really obscure programming/database platform/language from the 1970s (called “Cyborg”) that only had a few people left that knew anything about it. It took literally hours to compile even the tiniest code changes so his job mostly involved sitting around doing nothing waiting for the compiler to finish. He managed to eventually get a WFH situation (with dialup lol) that paid him $300 an hour, then went out and got two other similar WFH jobs that paid the same since his actual work load was just a few minutes per day for each. $900 an hour in the 1990s.