Dealing with unprintable characters is fine when you’re doing it on-purpose but, otherwise, I have just one thing to say about them.
One past issue with this blog is that people reading it would occasionally like to subscribe to the comments. When they subscribed to the comments, they never received notifications of new comments.
And yet again, for the third year in a row, GeoMetrick Enterprises has been given an award from GHP (Global Health & Pharma) magazine. This year, in the Biotechnology Awards 2018, the award is for “Best Laboratory Software Implementation Company – Midwest USA”: GHP Magazine’s Biotechnology Awards 2018 GeoMetrick Enterprises’ Individual Award Listing Gloria Metrick […]
I might have mentioned this but one of the tasks I’ve been doing quite a bit of, this year, is sitting in for missing LIMS system admins. For example, when someone’s LIMS System Admin leaves and you need someone to fill the gap – that would be me doing the filling.
We speak of the cost-benefit analysis to do before buying a system as if it really exists. It’s not as real as we pretend it is.
This roughly marks the start of GeoMetrick Enterprises. I started working on the company March 1st, 1996 and gotten all the insurance, registrations and such not long afterward. It’s strange to me to think that, this time last year, I had begun a W-2 job thinking I was starting a new phase in my life but, at this point, already knowing the job probably wasn’t going to last and that I would likely return, here. Here are some thoughts and observations based on these years in business.
In my last post, “Notes on Software Testing Habits,” I ran through a few thoughts about how to look at your software testing habits. Regulated or not, there are many commonalities.
In LinkedIn, I recently forwarded a post by Martin Lush entitled “Don’t Blame the Person – Fix the System!” One outcome for me from that is that it started a variety of side conversations with other people in the industry. One area of conversation that came up is that of testing, as a general topic and, today, I want to share my own thoughts on testing.
Some time ago, I made a post here about the levels of configuration and the misconceptions around them. What led-up to this post were conversations with customers and the continued realization that customers are still not being educated on what the term “configuration” means in our industry.
In a past post, I mentioned systems that let themselves become non-compliant. The issues I spoke about are actually issues for non-regulated systems, as well. All systems need some amount of maintenance and proper usage. However, there are other symptoms I hear among those groups who aren’t properly maintaining or using their systems. Here are some warning signs.