Crafters seem to have “stashes” – a pile of material collected that they intend to use “some day” but that continues to grow to the point where they have too much money and space invested in materials that they haven’t used. Occasionally, crafters come up with “stashbusting” projects that “bust” the “stash.” If you think of your project that way, where you have too many things on the list of tasks (i.e., where you’ve run into “critical path” issues and/or resource blockages), it’s a little bit like that – it’s a pile of something that needs to be conquered.
When I first started my business, I knew there were quite a number of projects that had resources who couldn’t finish their work. I don’t mean that they couldn’t finish in a reasonable time, but that they literally couldn’t finish anything, at all. I knew this partly from working with these projects but also from running into customers who told me about their projects at user group meetings or on the phone. I thought this was the best source of revenue I could find. I was wrong on that account.
If you’re looking for product reviews, this blog isn’t the place to look. Every once in a while, one person or another will suggest this to be a good task for me to take on in this blog. That’s not likely to happen. Keep reading for more about why that is.
In the last post, I talked about how micro-consulting can be useful for customers. While there might be advantages in using the largest firms, there are just as many disadvantages. One disadvantage is that using the larger firms can be more expensive. Here are three reasons why a micro-consulting firm is less expensive.
These days, it seems as if we can get micro-anything-we-want. We can get micro-greens, micro-brews and micro-distilling, just to name a few. In any case, I knew that micro-roasting (of coffee) was a “thing” but I was quite surprised, the other day, when I ordered coffee and each bag I received had information not just about what coffee was in the bag, but it said it had been specifically brewed for me (it had my actual name on each bag) and gave the date and time roasted.
A few people had noticed that there was a new picture on my blog but that it was not a picture of me. This is one of those situations where I accepted an upgrade, it had unintended consequences (the picture of someone else popping-up on my blog) and I decided not to roll it back – that there are more good features than problems and, also, that I didn’t currently plan to devoting time to kicking that person off my blog, being busy with other things. And, in that, it’s the same issue we face with LIMS, ELN and LES upgrades.
Some of the customers who read these posts are working to do as much of the actual work on their system, as possible, to include LIMS/ELN/LES System Administration, configuration, programming, etc… Others have decided that they don’t need to build some or all of these skills in-house and are asking their software vendors or other outside consulting firms (such as the premier GeoMetrick Enterprises) to do the work, instead. In doing this, while you do avoid having to build the skills in-house, you do not abdicate yourself from the potential issues that can come from this.
In my last post, I suggested to customers interested in running mobile apps for their LIMS, ELN or LES that they consider writing their own or having someone write one for them. I suggested writing them specifically for the devices that they will use. But some clever folks are still thinking they’re going to write one generic app that works for everything. They think if they do this that, if they switch devices, they can just swap the new devices in. Here are two more considerations.
These days, a criterion of looking for a new LIMS, ELN or LES is more and more commonly that it have mobile capabilities or some other mobile factor. More customers are looking for this. Yet, how critical is this on your requirements list?
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.