AlexanderStein (Pixabay)

Who would have thought that a game about paperclips would be so addictive?  But it is.  Paperclips is, at its heart, simple resource management.  You make one paperclip and sell it.  You make another and sell it until soon you can afford to buy machines that will make paperclips for you. And then big bigger machines.  And but the metal spool automatically.  But wait, there’s more! Continue reading “Paperclips”

How Many Environments Do You Need?

Let’s assume that you are part of a project team creating a new product – The Whizbanger – and you’ve just completed your major release.  It’s in.  It’s complete.  What’s next?

Well, in some organizations, the product is passed off to the maintenance team.  But you’re in a progressive organization where the product team does everything:  all major releases, minor releases and bug fixes.  So the next step is obviously to fix bugs and work on the next release.

Oh, you’re not in progressive organization?  That would mean that you are handing off the application to a maintenance team that will do bug fixes and perhaps minor releases while your team … works on the next major? Continue reading “How Many Environments Do You Need?”

Why is anyone using HTTP?

HTTP = Hyper Text Transfer Protocol.

HTTPS = Secure Hyper Text Transfer Protocol.

(For more details look at this article on LifeWire)

If invoking HTTPS is as simple as HTTP, why would anyone use HTTP?  In Google’s opinion, no one should be.  When Chrome V63 is released a new feature will be running that is going to scare a lot of people.  When you visit a website that contains Form fields, but is not running HTTPS then it is going to tell you that the site is Not Secure.  Will it scare you?  It should.

Continue reading “Why is anyone using HTTP?”

Bandages for Applications

At what point does a “data fix” do more harm than good?  For that matter, what is the tipping point between doing a data fix and fixing the application?  A data fix is merely a bandage for an application.  It treats a symptom, not the problem.

There are many debates about this very topic but let’s get things settled at the beginning:  one data fix is too many.  Yes, that seems rather draconian, but if you need to go into the database and manipulate the data to achieve the correct business results then there is a failure somewhere in the process.  Perhaps it was in gathering the requirements.  Perhaps it was in not providing the correct testing.  Or perhaps it was an unforeseen circumstance.  (The users got access to the applications.  It could happen.)

Continue reading “Bandages for Applications”

DevOps is complex

Does DevOps make things simpler?

That all depends on which side of the fence you are standing.  If you are developer things are simpler.  If you support DevOps, if you are one of those people that is trying to automate processes or make things simpler for others, then your life is more complicated.  Instead of one tool you’re dealing with many tools all hooked together with bubblegum and twine.

Continue reading “DevOps is complex”

Our IT Security Duty

There have been a number of security … questions/concerns … that I have had recently that have caused me to initiate different actions.  I won’t go into details about the specific items other than to say that it caused me to look at a bunch of different sites that I thought you might be interested in:
Continue reading “Our IT Security Duty”

Agile Framework

See if this tickles your fancy:

Lean-agile portfolios differ from traditional IT portfolios in several ways. They allow an agile enterprise to balance supply, demand, and cost in an effort to optimize IT output.

Continue reading “Agile Framework”

Deliver Fast

Embed from Getty Images
Back in the “good old days” when IBM 3270 was meaningful and everyone did waterfall there was kind of a set “project management” overhead that was associated to the project.  For most projects I worked on at Accenture (over fifteen years ago) we charged between 10% and 12% depending upon the size of the project and the technologies we were doing.  (Hint, the larger the project the higher the overhead.  See my other articles on communication costs increasing based on the number of people in the group.) Continue reading “Deliver Fast”

Rebuild To Make It Better


Trust is an interesting thing.  Our society, by the way, we have designed it, places a lot of trust in people doing their jobs or doing the right thing.  For instance, have you thought about how many people you are trusting when you buy your coffee in the morning?  The grower, all of the people involved in the transport, the people at the processing plant, more transportation, the workers at the distribution centre, more transportation people and all of the employees at the coffee shop.  Hundreds, if not thousands of people had the opportunity to taint your coffee, to add something to it or do something wrong so that it wouldn’t be the coffee you expected.

But none of them did it.  You implicitly trusted them. Continue reading “Rebuild To Make It Better”

Decomposition (not that kind)

Wikimedia Commons

OK, this note is technical in nature, but the lesson is applicable to virtually everything that we do.  So, if you can muddle through the geek speak I’ll have a present for you at the end.  Well, maybe not a present.  In the end you may know the answer already and I’m just repeating what you are mumbling in your sleep every night.  Not that I’m listening to you mumble but as long as you play Candy Crush just before going to bed … oh, never mind. Continue reading “Decomposition (not that kind)”