Technical Practices Archives

Most Recent

Technical Practices

Code Reviews Are a Mistake – Try Pair Programming

Formal code reviews lead to confusion and wasted time. Pair programming, on the other hand, has regular, effective code reviews built into its framework.

Technical Practices

Three Reasons To Keep Your Frameworks Up To Date

Framework updates can require significant rework and expense. Nevertheless, the benefits of keeping technologies up-to-date greatly outweighs the costs.

Technical Practices

Diagnosing Problems: Limit, Threshold, and Quota

Sudden changes in application behavior can often be attributed to reaching a limit or exceeding some quota; recognizing these can help with troubleshooting.

Technical Practices

How Do We Know Our Software Works?

People are flawed and make mistakes on a regular basis. So how do we have any confidence that our software works?!

Technical Practices

DevOps – Software Delivery Done Correctly

DevOps encourages better communication and collaboration between teams that are usually stuck in their own silos.

Technical Practices

Atomic Glossary, Part 2 – Atomic & Software Industry Jargon

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

Technical Practices

Atomic Glossary, Part 1 – Software Terms

Being a non-tech person working for a Software Development company, I hear a lot of things around the office that sound like another language.

Technical Practices

Test Everything! (on Validating our Work)

Software quality assurance starts by validating our concept of the user, and continues even after the product is in their hands.

Technical Practices

5 Ways Atomic Object Keeps Your App Secure

Atomic takes security concerns very seriously and uses a number of patterns and practices to ensure that the software we write is safe and secure.

Technical Practices

6 Reasons to Build a Firmware Test Suite

Projects where firmware talks to software should have a high-level test suite written against the firmware's interface to the software.

Technical Practices

Technical Spikes – Rehearsing Your Software

A spike helps us solve problems without committing lots of time or resources. It lets us work out code's kinks and solve the problem.

Technical Practices

Why Vagrant? – Preventing Deployment Issues from Day One with a Virtual Machine

Vagrant virtual machines help developers prevent deployment issues by allowing them to write code in production-like environments.

Technical Practices

Resources for Clients category

Other Categories

Keep up with our latest posts.