Tom Gauld on Kafka’s book for toddlers

I do enjoy some Kafka-adjacent humor on a Sunday morning.

Ask Me a Question

The last few posts have all been questions I’ve been asked. This is one of my favorite ways to generate a blog post, as quite frankly what I am obsessing about all day at work is stuff I can’t easily turn into blog posts without running it through legal. Better to stay at a specific level of generality in these things.

So, I’m throwing open the door. Send me your questions on quality related matters or the other topics I like to write about on this blog and I will try to answer them to the best of my abilities.

← Back

Thank you for your response. ✨

Stop it with the 4.0 stuff

Industry 4.0, Quality 4.0, Validaiton 4.0. It is all absurd, so cut it out. Old man rant out.

Seriously though, let’s have a chat about this and why it is a bad practice.

When we put a number after something, we denote a version number. Version numbers have meaning, and individuals react to them in a certain way.

Understanding Version Numbers

A version number is a unique identifier assigned to specific releases of software, hardware, firmware, or drivers. It helps developers and users track changes, improvements, and updates in the product over time. Version numbers are crucial for maintaining software, ensuring compatibility, and managing updates effectively.

Structure of Version Numbers

Version numbers typically follow a structured format, often in the form of major.minor.patch or major.minor.patch.build. Each segment of the version number conveys specific information about the changes made in that release.

Major Version

Indicates: Significant changes or overhauls.
Example: Going from version 1.0.0 to 2.0.0 might indicate a complete redesign or the addition of major new features.
Impact: These changes might not be backward compatible with previous versions.

Minor Version

Indicates: Addition of new features or significant improvements that are backward compatible.
Example: Updating from version 2.1.0 to 2.2.0 could mean new functionalities were added without altering existing ones.
Impact: Users can expect enhancements without losing compatibility with previous minor versions.

Patch Version

Indicates: Bug fixes and minor improvements.
Example: Moving from version 2.2.1 to 2.2.2 might mean minor bugs were fixed.
Impact: These updates are usually safe and recommended as they resolve issues without changing functionality.

Build Number

Indicates: Specific builds or iterations, often used internally.
Example: Version 2.2.2.45 could indicate the 45th build of this particular version.
Impact: Helps in identifying specific builds, useful for debugging and internal tracking.

Semantic Versioning

One of the most widely adopted systems for versioning is Semantic Versioning (SemVer). It uses a three-part version number: major.minor.patch. This system provides a clear and standardized way to communicate the nature of changes in each release.

Major: Incompatible API changes.
Minor: Backward-compatible functionality added.
Patch: Backward-compatible bug fixes.

Importance of Version Numbers

Tracking Changes: Helps developers and users keep track of what changes have been made and when.
Compatibility: Ensures that users know whether new versions will work with their current setup.
Support and Maintenance: Facilitates efficient troubleshooting and support by identifying the exact version in use.
Update Management: Allows users to determine if they need to update their software to the latest version.

Why I Dislike Quality 4.0, Validation 4.0, and the Like

It is meant to denote a major version, but it’s not, for a lot of reasons:

These concepts are more growth of design boxes than major changes. To use version control lingo, there is a lot of backward compatibility.
They are not definitive. There are absolutes and best practices and onward progression.
Each company tends to be in different places in different ways, and there are many maturity scales, not just one.

Maturity models are a better option. Each of these buckets has multiple scales, each of which needs to be evaluated and improved.

This is why I like cGMP

The “c” in cGMP stands for “current,” which signifies that the Good Manufacturing Practices (GMP) being referred to are up-to-date with the latest standards and technologies. This differentiation emphasizes that companies must use the most recent and advanced technologies and systems to comply with the regulations set forth by the FDA. The term cGMP ensures that manufacturing practices are not only good but also current, reflecting ongoing improvements and updates in the industry.

Working on Silence

I’m working with my therapist to become more comfortable with silence, which has never been one of my strengths. I’m researching and writing to figure out how to address this. Here are some thoughts on how I plan to incorporate this at work.

Why Silence?

Enhanced focus and reflection: Silence allows team members valuable time to process information, reflect on ideas, and formulate thoughtful responses, leading to deeper understanding and more insightful contributions.
Improved inclusivity: Silent periods level the playing field for all participants, giving everyone an equal opportunity to contribute regardless of personality type or language proficiency. This can help draw out insights from quieter team members who might otherwise struggle to be heard.
Increased efficiency: Silent meetings or periods of silence within discussions can be more time-efficient by eliminating unnecessary chatter and keeping the focus on the agenda.
Higher quality discussions: When participants have time to reflect silently, they often formulate more articulate and considered responses, leading to higher-quality discussions when verbal communication resumes.
Better idea generation: Silence can be particularly effective for brainstorming and ideation. Research suggests that silent brainstorming can yield more and better ideas compared to traditional verbal methods.
Improved listening: Periods of silence encourage active listening, allowing team members to fully absorb what others are saying without immediately formulating a response.
Reduced dominance by vocal members: Incorporating periods of silence into discussions can prevent a few voices from dominating the conversation. This can lead to more balanced and diverse input from the entire team.
Enhanced creativity: Silence allows for diverse perspectives and unexpected ideas, fostering innovative solutions.
Better decision-making: By allowing time for reflection and careful consideration, silence can contribute to more informed and thoughtful decision-making processes.
Improved emotional intelligence: Strategic use of silence can help team members become more aware of nonverbal cues and develop a better understanding of group dynamics.

Okay, so based on this, here’s my plan to effectively incorporate silence into team discussions. I chose team discussions as it seems like a good place to start.

Explain the purpose and benefits of silent periods to the team
Use collaborative tools for quiet idea sharing and note-taking. This will require some alignment and effort to implement as I think my team needs work here to be truly comfortable. Been meaning to do this more.
Plan to take some time to reflect after important points or before making major decisions.
Encourage a culture that values thoughtful pauses and reflection.

State of the Blog

I’ve always been clear to folks when I describe my blogging that I do this for a few reasons:

As a way to clarify my thoughts on a topic, usually before or after a difficult conversation on the topic
To rant about something that is on my mind without causing folks at work to start scurrying to address my ideas as requests for immediate action (has happened more than I would like to admit)
As a way to give back to the profession that has been so good to me
As a way to push the conversation in a direction and help further the profession.

While it is often good for 1+2, I don’t get enough comments and feedback to know about 3+4.

Additionally, my writing is often linked to my mental health and happiness at work. Miserable? I disappear for months. Feeling good about things? I write a ton.

I set myself a goal this month to write a little every day. The funny thing is, it didn’t move the needle in metrics at all.

I don’t have any comparisons, so I have no idea if this number of views is good. But seriously, a blog post I wrote 3 years ago (that needs to be cleaned up) is my most viewed post month after month.

I’m considering what to do after my little month-long experiment wraps up soon. No matter what, I think the blog’s public-thinking nature will continue. But I am asking myself, “Do I want more out of the blog?”