4 ms·
This is great advice as long as you know the difference between a detail and an issue. They are often easy to confuse. Detail: What font should we use on the p
by edw519 14y ago
This is great advice as long as you know the difference between a detail and an issue. They are often easy to confuse.
Detail: What font should we use on the payment page?
Issue: Should the customer's credit limit be for our division or for the entire company?
Ignore the former and make faster progress.
Ignore the latter and be prepared to redesign your database and rewrite your app if you made the wrong choice.
- deleted 14y ago[deleted]
- notimetorelax 14y agoExactly what I thought. If you're designing backbone of your application then being sloppy can be very expensive in the long run. Of course you still need to see the difference between essential elements and those that can be tackled later (usually parts of functionality that have nothing depending on them). Personally I find it very hard to do software design on initial stages of a project. It is similar to deciding on the laws of chemistry when building a tree, if you chose wisely it will grow naturally, if you make a mistake project completion may become impossible.