Software development quotes
Before agile many companies and teams considered a three month release cycle as aggressive, an annual release was more common. Agile started to ask teams to make fortnightly releases, or at the very least be able to release every two weeks. Being releasable was more important than actual releasing because …
Despite that fact that architects and developers know that tight coupling leads to increased complexity, we experience large object models growing out of control on an almost daily basis. In practice, this leads to performance problems and lack of transactional integrity. There are many reasons why this happens: the inherent …
I know plenty of teams that do all the right research activities, but these activities don’t influence their product decisions. They set out to build the same solutions they intended to build before they did their research activities.
Most of the complaints you hear about monolithic architecture can be traced directly to poor and/or accidental design. if you leverage similar design practices to create a distributed system, no amount of observability will save you.
Too many developers have an unrealistic view of the relationship between the quality of their software and the time and cost of creating it. The received wisdom is that more reliable software takes longer to write.
Traditional testers often don’t like agile because without detailed specification documents they are suddenly unable to do their jobs. This is because they consider their job being to compare the working system to the specification, and report where there are discrepancies. If you think about this for a second, the …
