Formal code reviews lead to confusion and wasted time. Pair programming, on the other hand, has regular, effective code reviews built into its framework.
Framework updates can require significant rework and expense. Nevertheless, the benefits of keeping technologies up-to-date greatly outweighs the costs.
Sudden changes in application behavior can often be attributed to reaching a limit or exceeding some quota; recognizing these can help with troubleshooting.
People are flawed and make mistakes on a regular basis. So how do we have any confidence that our software works?!
DevOps encourages better communication and collaboration between teams that are usually stuck in their own silos.
In this edition I’d like to touch base on some internal jargon that, as far as I know, we use specifically at Atomic Object