Write Once. Read Many. The cost of avoiding shortcuts when writing code is far exceeded by the benefits you'll get when reading it.

What's the state of Microsoft Access in 2021: thriving, alive, dying, or dead? If you only know Access by reputation, the answer may surprise you.

Did you ever think to yourself, "I wish there was a way to make my back-end data less flexible *and* less powerful?" Good news; your wait is over!

Hey! Wouldn't it be great if Access was version-control friendly out of the box? If you agree, head over to the Access feedback portal and vote for my request.

The key to becoming a better developer is to make it so The Right Way is also The Easy Way.

The most reliable software holds the potential to cause the greatest harm. Examples abound, from my own $86K mistake to a devastating Russian hack.

Beware of strawman arguments against Microsoft Access.

Before you commission that custom web application project, it pays to validate that the business process even warrants such a significant investment.

There are two problems with clever code. 1) The next person might not know what you were doing. 2) They might not know if *you* knew what you were doing.

The dual nature of Access–and the ignorance of this reality–is a major source of the shade that "real programmers" throw its way.

I will be presenting the about-to-be-released TwinBasic project from vbWatchdog developer, Wayne Phillips. Join me on April 22-23.

Not all bugs are created equal. Avoid the expensive ones by making more of the ones that are easy to find and fix.

Access just crashed while you were writing code. When you last saved will determine how long it takes to recover, but it's not a linear relationship.