Mark McDonnell "Musings"

@Mark McDonnell  

 

The Word That Shaped IBM and Inspired a Culture 

 

Don’t Apologize for the Green Screen: Embrace it 

 

Special Edition: IBM i Adoption and the Quiet Influence of the Human Brain 

 

SMB Edition: IBM i Modernization: The Community Is More Diverse Than The Conversation 

 

SMB Edition: Why Some IBM i Modernization Narratives Don’t Always Resonate with SMB Organizations 

 

--------------------

 

#3 - Use an Accepted Style Guide to Help Call Objects and Actions Exactly What They are or What They Do. 

 

#7 - Set it and forget it. Historical Performance Data Collections  

 

#14.5 - What you may not have known about the IBM i Electronic Service Agent Auto PTF function. 

 

#15 - The History of IBM Call Home Technology - Chapter 1: The Early Days – From Manual Processes to Automation 

 

#16 - The History of IBM Call Home Technology - Chapter 2: The "Magic" behind late 1990s and early 2000's Auto Problem Detection and Reporting: Service Director Explained 

 

#17 - The History of IBM Call Home Technology - Chapter 3: Operating System Integration 

 

#18 - The History of IBM Call Home Technology - Chapter 4: The Hidden Cost of “Call Home” Technology 

 

#19 - When Did IBM i and its Interfaces Become “Outdated”?  

 

#20 - Demystifying Program Calls: Are You Unqualified or Qualified?

 

#26 - How Familiarity Forms in New Technology and Why It Really Really Matters for IBM i  

 

#27 - Why IBM i Is Better Than Other Enterprise Hardware Ecosystems  

 

#28 - IBM i Adoption and the Power of Involvement  

 

#29 - When IBM i Experts and IBM i Novices Don’t Speak the Same Language 

 

#30 - The First 5 IBM i Knowledge-Base Articles Every Shop Should Have 

 

#31 - What Not to Do When Teaching IBM i 

 

#32 - What Good IBM i Mentors Actually Do 

 

#33 - Why Knowledge Siloing Is an Operational Risk 

 

#34 - Why “We Don’t Have Time to Document” Is a Warning Sign 

 

#36 - Why Stability Can Hide Operational Debt 

 

#37: Teaching Judgment vs Teaching Commands 

 

#38: Why Modernization Fails Without Understanding 

 

#39: The Hidden Cost of “Just Let Me Do It” 

 

#40: Why Teaching IBM i Is a Strategic Capability 

 

#41: When Stability Becomes a Constraint 

 

#42: Why “Don’t Touch It” Is Not a Strategy 

 

#43: Building Adaptive Stability on IBM i 

 

#44: Why Untouched Systems Are the Most Fragile 

 

#45: Operational Confidence Is Built, Not Assumed 

 

#46: Why Familiarity Beats Heroics 

 

#47: The Quiet Risk of Silent Operators 

 

#48: Why Boring Operations Are a Sign of Health 

 

#49: When Confidence Turns Into Complacency 

 

------------------------------------------------------------------------------------------------------------

 

The Questions That Built IBM i 

 

#50: The Questions IBM Engineers Asked: A Rochester, MN Architectural Series - Introduction 

 

#51: Did Rochester Expect These Systems to Run This Long? 

 

#52: Should Operating Systems Be Designed for Programmers or Operators? 

 

#53: Why Should Applications Care Where Data Physically Lives? 

 

#54: Why Rochester Hid the Machine Behind an Interface 

 

#55: Why Did Everything Become an Object 

#56: Why This Architecture Survived Generations of Hardware

#57: Why This Architecture Almost Didn’t Ship 

#58: When Architecture Works Too Well