The Inertia of Names

Our team of talented, friendly people are here to help you make your business even better – give us a buzz!

President Armen Stein has earned the Microsoft MVP Award every year since 2006. That tells you something about his passion for technology.

Did You Know?

The “spread spectrum” technology that actress Hedy Lamarr helped to invent would galvanize the digital communications boom, forming the technical backbone that makes cellular phones, fax machines and other wireless operations possible. Read more


“Names have inertia. Once a system is deployed, changing names is much more difficult.” ~ Armen Stein

The name of something is very important, for clarity and consistency. This is especially true when designing a database system and naming items including tables, fields, and labels. The names you choose are difficult to change later!

That is why we take great care in naming items when designing and building custom systems. We start with best practices and standards for naming the structures, and we make sure that we use clear, consistent, and useful names. Spending the extra time up front pays off later.

We’ve all seen systems where fields are misused to store different kinds of data, or labels that don’t accurately describe their values. Those problems make those systems hard to understand and give users a perception of poor quality.

Bottom line: We make sure to name things correctly (both visible and under the covers) in your database application so that your application is high-quality and will last a long time.
Contact us for a free consultation – we’re here to help you!

Meet The Team: Joe Kane
Software Design Analyst

Joe evaluates our clients’ business needs and collaborates with our development team to design powerful, intuitive applications.

What else? Joe’s other interests include books, photography, road cycling, and architecture.

Share this post

Related Articles

Man and woman shake hands at desk.

Can You Take Yes for an Answer?

Working with hundreds of potential clients over the years, I’ve learned that reaching an agreement requires both timing and confidence. When a conversation is going well, you must recognize it and lead the client to the next steps without over-explaining. Once the client says “yes”, it’s essential to take that answer and move forward rather than offer more reassurance when it isn’t needed. A specific example is references. Sure, we have a bunch of them – but we don’t offer them when the answer is already yes!

Read More »
picture of puzzle pieces - How Do You Solve Problems

How Do You Solve Problems?

Here at J Street, we say that we build and support database applications. But really, what we do is solve problems. Every day. That is our job. And it’s a skill that we’ve developed.

Read More »