Do you have a software project littered with now-old items named "XxxxNew"? If you're determined to avoid doing it the right way, here's a less terrible approach.

Microsoft Access or SQLite: Which one is more secure? The answer may surprise you.

"Three properties determine the complexity of an environment. ... The greater the multiplicity, interdependence, and diversity, the greater the complexity."

Hey, who wants to maintain this legacy code? Beuller? Beuller?

Once is a fluke. Twice is a coincidence. Thrice is a pattern.

VBA may never be a GitHub heavyweight, but it holds its own among other top languages in terms of Stack Overflow popularity.

The act of writing end-user documentation before software development offers a host of surprising benefits.

The fewer items you need to mentally track the less likely you are to make mistakes or generate bugs.

The Zen of Python is the famous philosophical foundation of one of the world's most popular programming languages. And that's no coincidence.

Many of the things I thought I knew about writing software were not only wrong, but often the exact opposite of the truth.

It doesn't matter which context you are working in–VBA or queries–the key is to pick one and stick with it.

Copy. Paste. Modify. Repeat. Writing and maintaining boilerplate code is a necessary evil in VBA.

Writing code is like juggling. But mixing code, queries, and global state is like juggling balls, bowling pins, and running chainsaws.

Even the world's worst programmer knows more about programming than most small business owners or department managers.

Getting ready to start a complex project? Stressing about what might go wrong? Here's some advice to help lower that stress level.

VBA-enabled documents are commonly used to open the door for more virulent malware.

Microsoft has embraced the mantra of "move fast and break things." For Access, though, Microsoft is only delivering on the latter part of that promise.