Spending too much time upfront thinking about the perfect data structure is a bad idea.
Long walks on the beach and fasting is not going to deliver your perfect data structure.
People (other than yourself) using your product and observing evolving requirements over time will reveal an optimal data structure.
Rapid iteration and real-world usage is the key. I can’t count the number of times I thought I had the perfect design only to implement it and not find it useful to myself - after having thought so long about it.
> node
Node is great. And it’s great at iterating quickly which should be the goal of any project.
The post comes off very naive and a classic grass is always greener vibe.
> And it sounds like the exact kind of algorithmic kludge a programmer would introduce if her underlying foundation had a few flaws.
Why use a gendered pronoun here? It’s a bit unfair that the only non-specific gendered pronoun relates to a bad programming practice.
Spending too much time upfront thinking about the perfect data structure is a bad idea.
Long walks on the beach and fasting is not going to deliver your perfect data structure.
People (other than yourself) using your product and observing evolving requirements over time will reveal an optimal data structure.
Rapid iteration and real-world usage is the key. I can’t count the number of times I thought I had the perfect design only to implement it and not find it useful to myself - after having thought so long about it.
> node
Node is great. And it’s great at iterating quickly which should be the goal of any project.
The post comes off very naive and a classic grass is always greener vibe.
> And it sounds like the exact kind of algorithmic kludge a programmer would introduce if her underlying foundation had a few flaws.
Why use a gendered pronoun here? It’s a bit unfair that the only non-specific gendered pronoun relates to a bad programming practice.