Hacker News new | comments | show | ask | jobs | submit login

how to better architect systems

I beleive that there is one answer to this question which does 80% of the job, it is easy to express and yet in the same time impossible to grasp for so many programmers/managers which leads to so many awful codebase.

As the post says very well: start by thinking about what you would do if you had infinite resources. That's the ideal case. Find a real bottleneck (money, cpu, memory, ?) and rethink your architecture accordingly, find the next real bottleneck and so on.




This is gold. I remember a quote from a prominent game programmer, I think it's John Carmack but I'm not sure, that when thinking of an approach to a new game engine he would start on the basis of an imaginary computer with instant CPU calculation and infinite memory. I can see the parallels here.




Applications are open for YC Winter 2019

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: