Patrick Mugabe

Systems Integration Architect | MuleSoft Delivery Champion. Passionate about API strategy, innovation, knowledge management & mentoring. Love coffee & golf.

[Patrick Mugabe @patmuga]

"Great Leadership is about Influence not Authority" https://t.co/iEXaFFIr3p by @mikekaeding

[Alex Xu @alexxubyte]

How does VISA work when we 𝐬𝐰𝐢𝐩𝐞 𝐚 𝐜𝐫𝐞𝐝𝐢𝐭 𝐜𝐚𝐫𝐝 at a merchant’s shop?

[Elizabeth McCormick, Motivational Speaker @pilotspeaker]

A boss has the title, a leader has the people. - Simon Sinek #Leadership #Pilotspeaker #Soar2Success

[Tendayi Viki @tendayiviki]

When it comes to innovation, do the hard things first. Don't invest all your time on the fun events and activities. At some point, you will have to account for the value you are creating for your company. This is when the fun stops.

https://t.co/KU0n4WdvKl
#piratesinthenavy

[Alex Xu @alexxubyte]

Have you heard of the 12-Factor App?

The "12 Factor App" offers a set of best practices for building modern software applications. Following these 12 principles can help developers and teams in building reliable, scalable, and manageable applications.

Here's a brief overview of each principle:

1. Codebase:
Have one place to keep all your code, and manage it using version control like Git.

2. Dependencies:
List all the things your app needs to work properly, and make sure they're easy to install.

3. Config:
Keep important settings like database credentials separate from your code, so you can change them without rewriting code.

4. Backing Services:
Use other services (like databases or payment processors) as separate components that your app connects to.

5. Build, Release, Run:
Make a clear distinction between preparing your app, releasing it, and running it in production.

6. Processes:
Design your app so that each part doesn't rely on a specific computer or memory. It's like making LEGO blocks that fit together.

7. Port Binding:
Let your app be accessible through a network port, and make sure it doesn't store critical information on a single computer.

8. Concurrency:
Make your app able to handle more work by adding more copies of the same thing, like hiring more workers for a busy restaurant.

9. Disposability:
Your app should start quickly and shut down gracefully, like turning off a light switch instead of yanking out the power cord.

10. Dev/Prod Parity:
Ensure that what you use for developing your app is very similar to what you use in production, to avoid surprises.

11. Logs:
Keep a record of what happens in your app so you can understand and fix issues, like a diary for your software.

12. Admin Processes:
Run special tasks separately from your app, like doing maintenance work in a workshop instead of on the factory floor.

Over to you: Where do you think these principles can have the most impact in improving software development practices?

--
Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): https://t.co/uc5M7CdXXC

[Patrick Mugabe @patmuga]

What a game!!! Good finish from the Boks and excellent execution.
#springbok #rugbyworldcup2023

[Alex Xu @alexxubyte]

How do companies ship code to production? The method to download the high-resolution PDF is available at the end.

The diagram below illustrates the typical workflow.

Step 1: The process starts with a product owner creating user stories based on requirements.

Step 2: The dev team picks up the user stories from the backlog and puts them into a sprint for a two-week dev cycle.

Step 3: The developers commit source code into the code repository Git.

Step 4: A build is triggered in Jenkins. The source code must pass unit tests, code coverage threshold, and gates in SonarQube.

Step 5: Once the build is successful, the build is stored in artifactory. Then the build is deployed into the dev environment.

Step 6: There might be multiple dev teams working on different features. The features need to be tested independently, so they are deployed to QA1 and QA2.

Step 7: The QA team picks up the new QA environments and performs QA testing, regression testing, and performance testing.

Steps 8: Once the QA builds pass the QA team’s verification, they are deployed to the UAT environment, where the QA team, dev team, and even the product owner perform UAT testing.

Step 9: If the UAT testing is successful, the builds become release candidates and will be deployed to the production environment on schedule. Here we might not want to deploy to all the users in one go to mitigate the change risks, so some techniques like feature toggle, canary deployment can be used.

Step 10: SRE (Site Reliability Engineering) team is responsible for prod monitoring. They leverage a bunch of log-analyzing tools and process-tracing tools like ELK stack, Prometheus, and Skywalking. They report production issues to QA and dev teams, and teams need to fix them based on defined priority.

–
Subscribe to our newsletter to download the 𝐡𝐢𝐠𝐡-𝐫𝐞𝐬𝐨𝐥𝐮𝐭𝐢𝐨𝐧 𝐏𝐃𝐅. After signing up, find the download link on the success page: https://t.co/0v29X0VLNt

[Patrick Mugabe @patmuga]

The KM strategy map - a visual link between KM and strategy by Nick Milton. https://t.co/9wfPRRalpj

[Real KM Magazine @realkmmag]

AI-based KM features for expertise discovery and dissemination [Generative AI & KM series part 5]

With thanks to Rachad Najjar

https://t.co/xYqVERXUfM

#km #kmers #knowledgemanagement #ai #artificialintelligence #generativeai #expertise #experts

[Patrick Mugabe @patmuga]

Great article on API security. @"API Security - Recommendations"https://t.co/KMuzvnTyDh on ⁦@LinkedInAU⁩.

[Patrick Mugabe @patmuga]

Leadership is a Practice, Not a Position of Authority - MEA HR & Learning https://t.co/uzvDTyt3Qd

[Bruce Boyes @BruceBoyes]

Getting to the heart of the problems with Boeing, Takata, and #Toyota (part 4): Embracing a different approach to knowledge management https://t.co/nvdFUX6B93 #boeing #complexity #km #knowledgemanagement #takata #xiaomi

[Stan Garfield @stangarfield]

10 ways to innovate key KM processes & tools to implement a KM strategy
- Article https://t.co/mhgsQDJYw2
- Step 11a in 12 Steps to KM Success https://t.co/maWyldaBQd
- Previous infographics https://t.co/4mXCcvRxBS
#infographic #KM #KMers #KnowledgeManagement #KMersIG #innovation

[Patrick Mugabe @patmuga]

@BruceBoyes You are doing some great work in this field @BruceBoyes. Always enjoy reading your articles.

[Java Guides @GuidesJava]

REST API Design Cheat Sheet:

[Carolina Campalans @c_campalans]

Using artificial intelligence to improve knowledge management in the construction industry https://t.co/01lNYCei0E #AI #knowledgemanagement

[CybersecInsider @Cybersecinsider]

Dispelling the Myths and False Beliefs of API Security https://t.co/K68WVbYSnr #CyberSecurity #Technology

[Patrick Mugabe @patmuga]

⁦@MuleSoft⁩ mega meetup in Brisbane. https://t.co/3B9lXMz9fD

[Java Guides @GuidesJava]

REST API Design Cheat Sheet:

[Paul Graham @paulg]

Mistakes become very hard to fix once they're embodied in jobs. The people whose jobs they are become highly motivated advocates for the continuance of the mistake.

[Patrick Mugabe @patmuga]

Thanks to ⁦@MuleSoft⁩ for the Delivery Champion certification. It’s time consuming but worth it. #deliveryChampion https://t.co/hVLFbrrz08