Several Short Sentences About Writing A Book by Verlyn Klinkenborg www.goodreads.com Here, in short, is what I want to tell you. Know what each sentence says, What it doesn't say, And what it implies. Of these, the hardest is knowing what each sentence actually says. Sonorisms VBoth models are completely uselessThe shape of the sentenceThe Anxiety of SequenceYou can get anywhere from anywhere+18 More Wittgenstein's MistressWrite SimplyThe most important thing you do writing
Feature parity An Article martinfowler.com Whilst Feature Parity often sounds like a reasonable proposition, we have learnt the hard way that people greatly underestimate the effort required, and thus misjudge the choice between this and the other alternatives. For example even just defining the 'as is' scope can be a huge effort, especially for legacy systems that have become core to the business. Most legacy systems have 'bloated' over time, with many features unused by users (50% according to a 2014 Standish Group report) as new features have been added without the old ones being removed. Workarounds for past bugs and limitations have become 'must have' requirements for current business processes, with the way users work defined as much by the limitations of legacy as anything else. Rebuilding these features is not only waste it also represents a missed opportunity to build what is actually needed today. These systems were often defined 10 or 20 years ago within the constraints of previous generations of technology, it very rarely makes sense to replicate them 'as is'. softwarefeaturesrepair