Software development quotes
No matter how hard you try, an occasional defect will escape to production despite your best efforts. Ideally, this is a rare event. When it happens, the defect is likely to be a devious problem that causes strange things to happen in other systems you didn’t know about during development. …
To avoid wasting time finding bugs that are not related to performance, it is important to have a stable application that has been thoroughly tested.
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.
