Post #2445444

2023-09-21 06:55 UTC

@fallenhitokiri@social.screamingatmyscreen.com While I agree, such system can be easily built if management tells you we‘ll have lot‘s of users and we need to be able to massivly scale at some point. Doesn‘t excuse the bad way it‘s build to work with few users though.

Replies (3)

@DerMolly@toot.kif.rocks 2023-09-21 08:09

@fallenhitokiri@social.screamingatmyscreen.com In this vain: Maybe a companion book for management titled „How not to nerd-snipe your developers“ could be a good idea.

Open ##2445445
@weel@towns.gay 2023-09-26 04:02

@DerMolly@toot.kif.rocks @fallenhitokiri@social.screamingatmyscreen.com I worked at Facebook before the IPO. we had a de facto rule to never build a system to scale more than an order of magnitude beyond current needs. even though we knew we were growing. because we also knew that purely hypothetical requirements lead to bad code. if you can't test it how do you know it's even there?

Open ##2445448
@berkes@mastodon.nl 2023-09-26 06:28

@DerMolly@toot.kif.rocks @fallenhitokiri@social.screamingatmyscreen.com if management tells you "we'll have lots of users" the devs job is to ask "how many and when?". And then to answer "I'll guarantee that by the time we have N users, we can start scaling up within Y weeks to M users". No management will ever demand premature optimization. (Or if they do, it's so rare that quitting the job is probably the only possible decision)

Open ##2445450