13
wojtek322
44d

Who the fuck thinks that giving the user the possibility to delete/create any DB column is a good idea on a table that should have 100k+ records.

Why does this senior guy not realize how bad this is.

Comments
  • 6
    Bad enough watching idiots trying to use a spreadsheet as a database. Using a database as a spreadsheet is next level.
  • 2
    Is it even possible to be that shitty of a dev???! Is this a true story? Bc that’s an impressive feat, you have to really try to be that fucking bad. Tbh you can be a bad dev without being a total dumbass in general but he ticks both boxes
  • 2
    @TeachMeCode For more context, the application would be used internal by 8-ish users. But they are responsible that the whole dataset is correct It's a lot of work for them and management wants to move a few of them to a different project (hence the project + cost price of that existing product). The tool that they used was generic but heavily adaptable and very powerful for their use-case. They want the same (overkill) use-cases
  • 2
    > 'Who the fuck thinks that giving the user the possibility to delete/create any DB column is a good idea'.

    He just wanted to let the users feel the power between their legs.

    https://youtube.com/watch/... .

    /jk
  • 1
    I don't even want users to access a database to extract data by hand (sqlite). So I write export functions.
  • 0
    Ask him to delete the database and backups and be done
  • 0
    @wojtek322 ok not as scary with that extra stuff you added. got guardrails so they don’t do anything nuts?
  • 0
    Well if it's an internal tool, then that's a horse of a different color, especially if all 8 people are also responsible for maintaining the database.

    There should still be a prod and dev environment though, and there should still be a promotion process for database changes from one to the other.
  • 0
    @TeachMeCode It was discussed and senior said that it will be their problem if they fuck up. But they had previously an unhappy employee that was fired that did unwanted changes in their old application.

    @AlgoRythm I would love that but I'm doubtful that we will get this in v1.
Add Comment