Pair Programming, Code Review, The Great Migration to Mastodon, Clean SAPUI5
Hi colleagues,
In this edition of the engineering ecosystem newsletter, we are switching to a curated format that features a selection of different topics. Our plan is to alternate between this format, which provides an overview of several subjects within the engineering ecosystem, and a format that focuses on a single, in-depth topic. In this curated edition, we will be covering a range of subjects:
Benefits of doing Pairing and Mob activities over Code Reviews: Dragan Stepanovic explains in the blog From Async Code Reviews to Co-Creation Patterns the cost of asynchronous reviews and advocates for pair and mob programming for higher throughput and better quality if the situation allows.
Reducing Pull Request Wait time: Facebook improved the mentioned cost of asynchronous reviews by introducing optimized tools to lower the wait time for a code review. In the blog Move faster, wait less: Improving code review time at Meta they explain their findings and how the tool helps. So far they implemented two features (next reviewable diff and reviewer recommendation) and more is on the roadmap.
The great migration from Twitter to Mastodon:
Recently there has been a growing trend of users and businesses moving away from Twitter towards other social media platforms, such as Mastodon. Mastodon is a decentralized, open-source platform that has gained popularity among users who are looking for a more community-focused alternative to Twitter. Unlike Twitter, Mastodon is not controlled by a single company, but rather a network of independent servers that are run by volunteers. This decentralized structure allows users to have more control over their data and the content they see, and also makes it easier for communities to form around shared interests.
Why I left algorithm based social media Interesting blog post on the need to move away from attention grabbing social media algorithms I found when I moved to Mastodon.
My personal experience with Mastodon has been very positive. I recently opened an account on the platform and have been pleasantly surprised by the relevance of the feeds I've seen so far. Most of the colleagues I follow on Twitter are also on Mastodon, so it's been easy to connect with them and continue following their content. If you're looking for a more community-focused alternative to Twitter, I highly recommend giving Mastodon a try. You can follow or connect with me using the link: https://saptodon.org/@klaushaeuptle# I look forward to connecting with you on Mastodon and seeing what the platform has to offer. Let's explore the possibilities together!
Clean SAPUI5: I am excited to announce that the book Clean SAPUI5, which applies clean code principles and practices to SAPUI5 and JavaScript code, is now also available in hardcover format in Germany. This updated edition allows readers to enjoy the book's valuable insights and guidance in a more durable and convenient format. Whether you are a seasoned developer or just starting out in the field, "Clean SAPUI5" is an essential resource for anyone who wants to write readable, testable, and maintainable code using SAPUI5 and JavaScript.
Thanks and Regards,
Klaus
Why: More on my motivation to start the newsletter can be found in Collaboration on Improving: Why I'm starting the Engineering Ecosystem.
About me: I am Klaus Haeuptle an engineer and architect at SAP, the author of the books Clean ABAP and Clean SAPUI5, a coach for agile software engineering and a community servant leader for a large SAP internal grass roots community on improving tools, technologies, practices and culture, with more than 3000 participants from all locations and departments. Views are my own - the content published on this channel reflect my opinion and engineering principles.
Subscription: If you want to get updates, you can subscribe to the free newsletter:
Mark as not spam: : When you subscribe to the newsletter please do not forget to check your spam / junk folder. Make sure to "mark as not spam" in your email client and move it to your Inbox. Add the publication's Substack email address to your contact list. All posts will be sent from this address: ecosystem4engineering@substack.com.
✉️ Subscribe to the newsletter — if you aren’t already.
❤️ Share it — The engineering ecosystem newsletter lives thanks to word of mouth. Share the article with someone to whom it might be useful! By forwarding the email or sharing it on social media.