Live data from Hacker News

Ask HN: How to study for system design that doesn't include front end/back end?

news.ycombinator.com

21–27 of 27 posts

Re: Ask HN: How to study for system design that doesn't include front end/back end?

#21

There are two aspects to systems design. * Flow control - This is the logical path the software takes from input, through computation, to output. * Division of effort - This isn’t your division of labor but the organization of parts to account for reuse, documentation, testing and so on. With enough practice writing and refactoring original software you just build a vision for it through repeated practice. If that is…

Can this insight be applied to human resources or business organization?

Re: Ask HN: How to study for system design that doesn't include front end/back end?

#22

There are two aspects to systems design. * Flow control - This is the logical path the software takes from input, through computation, to output. * Division of effort - This isn’t your division of labor but the organization of parts to account for reuse, documentation, testing and so on. With enough practice writing and refactoring original software you just build a vision for it through repeated practice. If that is…

Can this insight be applied to human resources or business organization?

Business organization is similar but people management is different. With people management you are attempting to ascertain their goals and constantly reading their communication to determine their motivation. As a leader it is up to you to set expectations and it is up to them to rise to those expectations. As for business organization the chief difference is with subordinate leaders, to put the right people in the right seats.

Re: Ask HN: How to study for system design that doesn't include front end/back end?

#24
Most of the time the interviewer is determining how you think, whether they can interact with you easily, how you react to uncertainty, how you react to feedback, how you react to a superior saying “I don’t know”, your resilience in the face of incomplete information, your calmness under stress, and then finally, your final solution given the time constraints and pressure you are under.

The goal is not really to get an A+++ on the final product (although that’s nice) but the goal is to communicate that you work well under non-ideal conditions and you’re not a total F*ing nightmare. So take a big breath and engage that lovely neocortex and let your intellect be driven purely by curiosity, a desire to do good, and kindness, and you will get far.

Re: Ask HN: How to study for system design that doesn't include front end/back end?

#25
System design has tonnes of YT videos. Watch them.

https://m.youtube.com/@SDFC

https://www.youtube.com/@jordanhasnolife5163

Pricer would have some kind of human interface. Even if just CLI that called API endpoint using some kind of SSO staff authentication. Then it is just a back end.

Re: Ask HN: How to study for system design that doesn't include front end/back end?

#26
post #7

One general tip is to always ask (credible) clarifying questions. A lot of interviewers look out for this - they want to see you dissect the requirements a little bit, not just jump straight to solving the problem based on a bunch of assumptions you've made that might not be correct.

This is big. Often will be on the senior plus rubric. "Did they ask clarifying questions?". Tick.

It also gives you constraints. Which are your friend.

I can't find it now (I tried but it was a year ago) but on YT there are some excellent example system designs where someone does it and then they talk about it. What was good. Why it was senior vs junior or senior vs principal.

Post reply on HN