Skip to main content

The Top 40 articles by Ronald Bartels on LinkedIn based on popularity

I started writing posts on LinkedIn in October 2014. Here are my top 40 articles since then:
  1. Born in the Sixties and my first taste of digital. Memories of my first encounter with digital technology. (631004)
  2. 6 things that will not solve problems in the workplace. The behaviours that will result in workplace problems. (331292)
  3. Boilerplate example for an IT SOP (Standard Operating Procedures). An article that shot to the top! (277911)
  4. Checklist for Change Management. Based on what pilots do but for IT. (111364)
  5. The IF THEN ELSE of SDWAN - reality versus the lab. Exception handling in SDWAN ecosystem. (108611)
  6. A checklist for troubleshooting network problems (22 things to catch). Old but obviously still well liked! (62717)
  7. Prestik, Scotch tape and barbed wire data centres. Data centres that cut corners are not where you need to store your data. (51156)
  8. A brief history of Madge Networks, My memories of a company who made Token-ring and had a philosophy of "Support without limits!" (31721)
  9. Learning from great leaders, Eddy Merckx. My cycling hero! (28234)
  10. Standby generator checklist. Boring but one of the most viewed articles. (21828)
  11. Learning from great leaders, Amundsen. Why Amundsen, a hero from the age of explorers, is a great leader. (21378)
  12. 5 practices that need to be taken into account when migrating to a more modern data centre. An article related to data centre migrations. (19146)
  13. Unforgettable work moments that will never find its way into my CV. Work moments not recorded in my CV. (13579)
  14. Great interview, poor performance. A great interview with a candidate does not necessarily mean that he will deliver great performances. (13301)
  15. Creating a leak detecting IoT solution. Detecting water leaks in a data centre and similar environments. (12128)
  16. 32 free Information Technology ebooks, Bibles and guides for Dummies. (10237)
  17. eTOM - the dinosaur of telecommunications. The dated framework whose time has expired (10102)
  18. Lessons from building large campus networks. Important considerations when building large networks. (9493)
  19. The business of SDWAN - from the top down. Don't double down on the technology! (8106)
  20. Learning from great leaders, Shaka Zulu (a military genius). Probably the greatest historical leader from Africa. (7911)
  21. Greyhounds (Greybrakke) - the legacy of the Governor General. About the history of my alma mater, Grey College. (6245)
  22. Installing NeDi on a Raspberry Pi 2. An article on the open source network management tool NeDi (5876).
  23. A timeline of major incidents (showstoppers) and milestones for Data centres and Operators in South - 2005. A summary of the crises that have happened in our neck of the savannah. (5700)
  24. Electronic tomstones - scattering the virtual ashes. What happens to our social media when we die? (5205)
  25. It's not about the uptime. Making the point that it is more important to analyse the downtime than to measure the uptime. (4801)
  26. Lessons from great leaders, Lovell, Kranz and Liebergot. And they appear in my favourite film Apollo 13. (4785)
  27. ITIL in the enterprise (the cart before the horse). We have solutions that go in search of problems. (4258)
  28. 5h1t h@ppens - understanding incident pyramids in IT. Circumstantial evidence meets IT. (2971)
  29. My life as a car. Analogies, nuff said. (2448)
  30. Work-life balance (and some help in cheating). Or why is whisky important? (2446)
  31. Craic. An explanation of Craic and why in our modern era where we are attached to our phones and broadband it is important. (2346)
  32. Installing RedMine on ubuntu 14. A write up on a difficult install. (2311)
  33. The difference between a local data centre and one that is offshore. Making the case to keep your data local. (2265)
  34. Flawed "ITIL aligned" Incident management. A story about Bob and Alice. (2243)
  35. An integrated approach to working with problems. A companion article to one of my top rated articles. (2239)
  36. Two words. Enough said. (2159)
  37. RIRA - Rapid IT Risk Assessment. Information Technology (IT) risk is a measure of the extent to which the IT landscape is exposed based on the exploitation of vulnerabilities by a potential threat. (2148)
  38. Why Madge Networks went titsup. A dot com crash to which I was a party. (2144)
  39. Dealing with showstoppers (the Major Incident Process). Wyle E, Coyote, a hero for all the wrong reasons. (1645)
  40. Checklists: FTW. Why the use of checklists has become important. (1531)
You can catch me on twitter here or read my blog, Thinking Problem Management here.
My articles on LinkedIn about the Internet of Things (IoT) are available here while my articles about software defined wide area networks (SDWAN) are available here.
* My personal favourite post was about Madiba (read it here).
** The famous Alpha to Zulu Guides. A work in progress.

Ronald Bartels Top 40


Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

Updated: Articles by Ron Bartels published on iot for all

  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all .  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all . Improving Data Center Reliability With IoT Reliability and availability are essential to data centers. IoT can enable better issue tracking and data collection, leading to greater stability. Doing the Work Right in Data Centers With Checklists Data centers are complex. Modern economies rely upon their continuous operation. IoT solutions paired with this data center checklist can help! IoT Optimi