Introduction to This Experiences Blog

(picture of Garry Flemings)
Garry Flemings

Hi! Welcome to this Experiences blog.

I’ve worked in information technology (and lots of software development) for over 20 years. In this blog, I’ll write about my professional experiences. I have some bio information at Garry Flemings bio. And at Garry Flemings on LinkedIn. (blush) Enough about me.

I hope my writings will prove useful to you, the reader. And I hope you’ll come back. (Yeah!) And I hope you’ll always feel free to comment. (Yeah more!) The more often you come back and the more you comment, the more a part of the community you are! No matter how often you return and whether or not you comment, you’re welcome here.

No matter what else: if you see a problem, please let me know at (or

On June 19, 2016, this blog moved from to I’m a project manager (the first site). I’m a software developer (the second). I’m eager to concentrate on software development, so I moved the blog.

Let’s keep all content here suitable for children of all ages and … well … there’s a little more information like that in the expectations section below. Let’s all keep it reasonable!

I’ll post now and then. My previous attempts to post weekly proved ambitious. In return, my posts will typically be longer than a paragraph and more laden with helpful meaning.

You (and I) are free to post or comment any time 24 hours by 365 days (hint hint)!

For readers new to this software: the blog depends on an open source software development effort called WordPress. WordPress maintains two lists of contributions to the blog, “posts” and “comments”. Often authors (that’s you!) use comments to respond to either. You can enter either any time.

It’s good practice to create realistic expectations. In that vein:

  • Let’s each decide to keep all content here suitable for children of all ages and otherwise professional and respectful. This is, after all, a pretty public place, potentially world-wide.
  • WordPress asks your browser to store “cookies” on your computer. My web reading tells me their purpose for using cookies is to make your experience easier with this blog; see the sub-bullet for more detail. (Skip it if the detail might make your eyes glaze over. (he he) And that’s okay.)
    • Cookies in WordPress: When you first sign in, the WordPress software generates a number from the information you give the blog about your account (it could use your name and email address, for example). The blog asks your browser to store that number on your computer; the file storing that number is the “cookie”. When you come to the blog later, your browser reads the cookie and sends the number to the blog; the blog computes the number again. If the two numbers match (the one the browser sends and the one the blog computes), the software might not ask you to log in. I got this information from a quick web search; perhaps you’ll find more detail with a search of your own!
  • Your privacy is important. I intend not to use any information from this blog to create unexpected information about you. I intend not to use names and email addresses this blog collects as a basis of a sales campaign. I intend not to share names and email addresses this blog collects with anyone or for profit.
  • If you have a privacy concern with this blog, it’ll be our community’s loss that you decide not to participate, but we respect your choice. (Feel free to come back as often as you like to read our work!) If you care to inform me about your concern, I intend to address or explain the concern.
  • As far as I know, I’ll know about your account (and you) only what you typed when you created your account on this blog, plus the date and time you entered the information. This blog won’t record and I won’t know how often or when you return. If I learn otherwise later, I intend to change this text.
  • I will have access to the clear text of your password here. I don’t foresee need to use it; I intend to never use it outside this blog. If you use a password here that you also use on another site, I won’t know about your use elsewhere; I won’t seek to find out.
    • Oh! But none of us would ever do that, right?! We all know that’s a bad practice, right?! We all know that administrators on many web sites and systems we use have access to our passwords for that site or system, right?! We all recognize the ease of protecting ourselves from the possibility of bad actors in any population, even administrators, right?! Any questions? Feel free to contact me!
    • If you use your email to register here and use the same password here as on gmail, I can’t help but know you have an account both here and on gmail. If I turn to the dark side, I could access your gmail. I won’t. Thanks for the trust.
  • If you register here, please expect that WordPress will deliver the community all the same information about you that you see about others. (I’ve only seen that the blog shares your name; I haven’t found anyplace that it shares your email.) If you want to un-register, feel free to contact me. (And … there may be a WordPress function to do that … I haven’t found it yet …)
  • WordPress supports a moderator. I have moderator permission; for now (maybe always), only I will have it. I intend to moderate sparingly and always in the best interest of the community. I intend to avoid editing text others wrote. That said …
    • Before WordPress accepts a post from you (not before it accepts a comment from you), it will ask you to register. That means  1) The blog will ask you to enter your name and email address.  2) WordPress will send you a password via email.  3) The blog will expect to get that password from you for future log-ins.
    • There are spammers out there looking for blogs that don’t use this basic protection. Uncontrolled spam on the blog doesn’t seem in our interest! I could get rid of the spam after we all see it, but maybe we’d all prefer to avoid it from the start. (I know I would prefer not having it on the site!)
    • Before the blog makes your post available to the community, a moderator (yup, that’s me) must approve the post. When you leave the post, I’ll get an email. It’d be great to start getting those emails!
    • If you don’t log in before you leave a comment, I’ll get an email and I’ll need to sign in with a moderator account to approve your comment. If you log in, the same applies to your first comment; after that, your comment is immediately available.
    • The moderator can remove posts or comments.
  • There’s no guarantee here. Please depend on your best judgment before applying advice you find here to your (and your stakeholder’s) situation. Feel free to ask me for more information!
  • Your participation here is your acceptance to hold Garry Flemings, Midwest Project Management, Inc., and Program harmless from results of your participation in this blog and from any information here.

Happy blogging here! And … feedback is always welcome …

2 thoughts on “Introduction to This Experiences Blog”

  1. This is an example comment. Garry Flemings wrote it after I used the blog screens to register as a new contributor (the same screens you can use!) The blog shows the user name “Garry Flemings contributor” when I log in with this account.

    The registration process was easy. I recorded my name and email address. WordPress sent me an email with a password. I signed in.

    Very easy … Only have to do it once …

  2. This is an example comment. Garry Flemings wrote it after I learned how to use a WordPress setting that makes it even easier to enter comments. Now, you don’t have to register or log in to participate in this blog.

    I like improvements, even the small ones …

Leave a Reply

Your email address will not be published. Required fields are marked *

Comment moderation is enabled. Your comment may take some time to appear.