A Risky Way To Account For Changing Product Requirements
Accounting for a product requirements change is a challenging affair, but also part of the nature of software development. There's no avoiding it. There is one tactic for doing so that is growing on me, though it does come with some risks.
Philosophy of Technology
We often discuss the technical merits of libraries/frameworks/services we are evaluating. This is an obvious discussion point. Technology needs to have technical advantages. Yet, it is also important to consider the philosophy of those who build that technology when evaluating technology to use.
Page 1 of 18 Next Page
Get new posts when they are published