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

re 1 - better design a program with no state beyond configurations.



Easier said than done, if you don't have any state you're probably not doing something all that interesting.

The trick is to keep your state in the right place, the answer usually being to punt state management to a database/message queue/etc. - you definitely want to avoid, say, stateful frontends.




Consider applying for YC's Summer 2025 batch! Applications are open till May 13

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

Search: