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…
Ask HN: How to study for system design that doesn't include front end/back end?
21–27 of 27 posts
Re: Ask HN: How to study for system design that doesn't include front end/back end?
#22There 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?
#23Re: Ask HN: How to study for system design that doesn't include front end/back end?
#24The 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?
#25https://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?
#26One 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.
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.
Re: Ask HN: How to study for system design that doesn't include front end/back end?
#27It has been said that a system is not the sum of its parts, but the product of the interactions between its components. I hope someone can remind me who said this.