Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I have a similar flow in a similar solution, when designing or reviewing a design, if I come up with thing that might be a problem later, I stop and think, if I come up with 1 solution within a minute, or 2 within 5, then it's not going to be a problem and I just go along thinking through the rest of the design. If it takes longer then there may be a big flaw there. I've saved times both ways with this, stopping working on a majorly flawed design as well as saving a lot of bike shedding. This is generally more for future proofing, things like "how do we make breaking schema changes"



Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

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

Search: