4 ms·

> I imagine this is only a problem at startups founded by students. I think you imagine wrong. > I've never worked on a team that didn't carefully consider th

> I imagine this is only a problem at startups founded by students. I think you imagine wrong. > I've never worked on a team that didn't carefully consider their schema from both a performance and extendability perspective. Count yourself very lucky.

zeroCalories 3y ago
Maybe you're the unlucky one? How does someone that doesn't know basic system design get put in charge of designing a system?
- renegade-otter 3y ago
  They murdered the Leetcode interview, so they must be good at everything else /s
- rapsey 3y ago
  Because people with experience expect a certain salary level.
- lowercased 3y ago
  Shortest answer is they're put in charge by someone who doesn't know that the appointee doesn't know. Either they don't know they're supposed to know that, or (ime) more often they don't know how to judge. As someone else replied, passing leetcode-style tests is taken as a mark of technical skill well beyond what it's intended to indicate. Glad to hear you've been part of well functioning competent teams of professionals. I know they exist - I've been there a couple times myself over the years, but it's not a given. I would probably say it's not even the norm if you include a wider range of places where tech/developer folks may be employed. A 'team lead' role is filled by someone who is dating the department manager's family member? Seen that happen. "Joe's been here longer, so he gets to make the final decision on things". OK, but Joe graduated high school last year, and he's cutting in to systems built by people with 20+ years of experience (both in software and in this domain), and Joe is replacing it with some cut/paste stuff he found on stackoverflow last week. I was going to produce a larger litany of dumb scenarios I've had to wrestle with, in painful detail, but unsure that would do much to convince you of anything. (venting does help me occasionally, but won't ATM).
dacryn 3y ago
I dare to say the opposite. Students still care and should have learned these principles in uni. They tend to overengineer and focus too much on the technical challenges In bigger companies, most IT people tend to be people who got the job because they started coding back in the day when you could get by using just common sense and gut feeling. Today we know those often lead to dark patterns and bad database design, but those people have now grown into architecture and management positions and have no clue what they are talking about. This is very prevalent in tech teams of non tech companies (e.g. manufacturing, banking, healthcare, CPGs,...)

zeroCalories 3y ago

Maybe you're the unlucky one? How does someone that doesn't know basic system design get put in charge of designing a system?

renegade-otter 3y ago
They murdered the Leetcode interview, so they must be good at everything else /s
rapsey 3y ago
Because people with experience expect a certain salary level.
lowercased 3y ago
Shortest answer is they're put in charge by someone who doesn't know that the appointee doesn't know. Either they don't know they're supposed to know that, or (ime) more often they don't know how to judge. As someone else replied, passing leetcode-style tests is taken as a mark of technical skill well beyond what it's intended to indicate. Glad to hear you've been part of well functioning competent teams of professionals. I know they exist - I've been there a couple times myself over the years, but it's not a given. I would probably say it's not even the norm if you include a wider range of places where tech/developer folks may be employed. A 'team lead' role is filled by someone who is dating the department manager's family member? Seen that happen. "Joe's been here longer, so he gets to make the final decision on things". OK, but Joe graduated high school last year, and he's cutting in to systems built by people with 20+ years of experience (both in software and in this domain), and Joe is replacing it with some cut/paste stuff he found on stackoverflow last week. I was going to produce a larger litany of dumb scenarios I've had to wrestle with, in painful detail, but unsure that would do much to convince you of anything. (venting does help me occasionally, but won't ATM).

dacryn 3y ago

I dare to say the opposite. Students still care and should have learned these principles in uni. They tend to overengineer and focus too much on the technical challenges In bigger companies, most IT people tend to be people who got the job because they started coding back in the day when you could get by using just common sense and gut feeling. Today we know those often lead to dark patterns and bad database design, but those people have now grown into architecture and management positions and have no clue what they are talking about. This is very prevalent in tech teams of non tech companies (e.g. manufacturing, banking, healthcare, CPGs,...)