2 ms·
Everything else in a software project changes frequently, especially during the early days. "Fundamentals" don't help you know more ahead of time and it's reall
by mrkurt 15y ago
Everything else in a software project changes frequently, especially during the early days. "Fundamentals" don't help you know more ahead of time and it's really nice to be able to quickly adjust when you come across something you hadn't anticipated.
I tried building a small side project with Postgres about 8 months ago (after not really doing rdbms stuff for 18 months before) and was amazed at how inflexible it felt, and how much frustration used to seem normal.
- lwat 15y agoCould you elaborate please? What were you doing and what made it feel frustrating and inflexible exactly?
- einhverfr 15y agoThat's what prototyping and peer review are for, I write up a schema, send to everyone else on the team, get feedback. If users are invovled get it from them too.... take in all the feedback, write up a new draft, wash, rinse, repeat until running out of shampoo (i.e. feedback)..... Once things are pretty stable, do a prototype, address any oversights, do the real thing. It's not rocket science.