Robert Schwegler

Often my employees and I need a development environment for C++ together with the installed GRPC. To reduce the time for installing and deploying the environment, I started making Dev Containers, which I give to my employees and they run them in VSCode. I hope it will be useful to someone else. https://lnkd.in/dCCQBpTt #cpp #c++ #docker #devcontainers

1

ICYMI, Google Cloud Platform and Technical Infrastructure Director, Jennifer Petoff, gave the opening keynote at DevOpsDays Zurich this year. You can check out the video here if you want to learn more about the importance of education in driving an SRE or DevOps culture.

3

The benefits of AI code assistants are still being evaluated, but here at Deutsche Telekom we are confident that our AI strategy to continually assess COTS products, as well as developing our own products and data foundation is the right approach to yield benefits in the future. Have a look at the post below from one of our leading developers on the topic It’s exciting to think about the capabilities of the product in only a few years from now; perhaps covering all aspects of the SDLC and integration to user stories, more context in relation to existing code repos throughout the enterprise (particularly useful for very large enterprises), models optimized for dialects of the languages (GoogleSQL vs PostgreSQL etc)….to think of a few examples Regardless, the developer experience will be greatly enhanced in the next few years and at Deutsche Telekom we’ve got a front row seat! 👏

16

1 Kommentar

It is quite good perspective to build enterprise platform. It is not just collection of shared service, but instead proposing that we should foster innovation and diversity at the application level while providing standardized foundations.  https://lnkd.in/ebiYjZ4x

3

𝐋𝐞𝐯𝐞𝐫𝐚𝐠𝐢𝐧𝐠 𝐂𝐥𝐨𝐮𝐝 𝐒𝐞𝐫𝐯𝐢𝐜𝐞𝐬 𝐟𝐨𝐫 𝐋𝐞𝐚𝐧 𝐚𝐧𝐝 𝐄𝐟𝐟𝐢𝐜𝐢𝐞𝐧𝐭 𝐓𝐞𝐚𝐦𝐬 𝐂𝐥𝐨𝐮𝐝 𝐄𝐧𝐚𝐛𝐥𝐞𝐬 𝐒𝐦𝐚𝐥𝐥𝐞𝐫, 𝐒𝐦𝐚𝐫𝐭𝐞𝐫 𝐓𝐞𝐚𝐦𝐬 Building on a previous post, which concluded that cloud services aren't more expensive than on-premises solutions (https://lnkd.in/d4c32w3b), let's explore how the cloud empowers smaller teams. In developing our online charging system (OCS) for telecom operators as a cloud-native application, we started with a handful of team members, proving large teams aren't needed with the right tools. 𝐓𝐡𝐞 𝐏𝐨𝐰𝐞𝐫 𝐨𝐟 𝐆𝐞𝐧𝐞𝐫𝐚𝐥𝐢𝐬𝐭𝐬 Cloud-native environments offer many services. While mastering all is impossible, generalists can quickly learn and use these services effectively. This adaptability allows team members to switch between container clusters, databases, and other services without deep specialization, maximizing cloud benefits. Prioritizing business value over infrastructure management allows teams to fully utilize available services. 𝐅𝐨𝐜𝐮𝐬𝐢𝐧𝐠 𝐨𝐧 𝐂𝐨𝐫𝐞 𝐁𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐋𝐨𝐠𝐢𝐜 Our product’s core—rating and charging—is highly complex. Utilizing serverless solutions and managed services like Lambdas, auto-scaling groups, load balancers, and step functions eliminates infrastructure management for necessary but non-core functionalities such as provisioning users. This allows our team to focus on implementing and enhancing core business logic, spending less time on infrastructure and more on adding value through innovative features. 𝐁𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐚𝐧𝐝 𝐈𝐧𝐝𝐮𝐬𝐭𝐫𝐲 𝐄𝐱𝐩𝐞𝐫𝐭𝐢𝐬𝐞 𝐢𝐧 𝐓𝐞𝐚𝐦𝐬 Balancing technical cloud skills with business and industry knowledge is crucial. While not every team member may possess deep business domain expertise, reducing infrastructure management allows them to focus on core logic development. This ensures our team is technically proficient and aligned with business objectives, fostering a product that drives business value. 𝐅𝐥𝐞𝐱𝐢𝐛𝐢𝐥𝐢𝐭𝐲 𝐢𝐧 𝐓𝐞𝐚𝐦 𝐒𝐢𝐳𝐞 𝐚𝐧𝐝 𝐃𝐞𝐯𝐎𝐩𝐬 𝐈𝐧𝐭𝐞𝐠𝐫𝐚𝐭𝐢𝐨𝐧 A key benefit of cloud adoption is team size flexibility. Projects can start with even one member, limited only by operational needs like on-call schedules and incident response. Integrating DevOps principles allows the same team to handle both development and incident management efficiently, ensuring responsiveness without larger teams. This maintains operational efficiency and reduces failure risks by preventing teams from becoming overextended. 𝐊𝐞𝐲 𝐓𝐚𝐤𝐞𝐚𝐰𝐚𝐲 Embracing cloud-native architectures enables organizations to maintain lean, knowledgeable teams focused on delivering real business value. By leveraging managed services and fostering a generalist skill set, companies can reduce overhead, minimize risks, and enhance operational efficiency. This strategic approach ensures teams remain agile and aligned with business objectives.

11

This is my new favorite #toiletreading (the book you read at... ehm... certain place 😁) I got from guys from Particular Software (authors of NServiceBus) at #NDCOslo. Rather short book, but full of great examples of why distributed systems are hard and why some problems, especially reliable communication, remain the same for centuries. If you would like to buy it, here is the link for Amazon: https://lnkd.in/dXtwdS_x

5

1 Kommentar

🚀 𝗥𝗲𝗶𝗺𝗮𝗴𝗶𝗻𝗶𝗻𝗴 𝗔𝗴𝗶𝗹𝗲 𝗳𝗼𝗿 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗦𝘂𝗰𝗰𝗲𝘀𝘀 – 𝗜𝗻𝘀𝗶𝗴𝗵𝘁𝘀 𝗳𝗿𝗼𝗺 𝗔𝗻𝗻𝗮-𝗞𝗮𝘁𝗵𝗮𝗿𝗶𝗻𝗮 𝗥𝗲𝘆𝗸𝗼𝘄𝘀𝗸𝗶 🚀 In a recent conversation with Anna-Katharina Reykowski, we dove into how Agile and Scrum can better align with a Product Operating Model. Agile’s rituals, while useful, can sometimes overshadow the real goal: delivering great products that bring long-term value. We discussed three key areas to focus on: 1.   𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗰 𝗔𝗹𝗶𝗴𝗻𝗺𝗲𝗻𝘁 𝗔𝗰𝗿𝗼𝘀𝘀 𝗧𝗲𝗮𝗺𝘀: Teams must evolve beyond just technologists and become Product Engineers, acquiring deep domain knowledge to align better with the product vision. 2.   𝗕𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗣𝗿𝗲𝗱𝗶𝗰𝘁𝗮𝗯𝗶𝗹𝗶𝘁𝘆: Predictable delivery timelines and costs are crucial for managing complexity in larger organizations. Refined estimates based on real-time data can help. 3.   𝗢𝘂𝘁𝗰𝗼𝗺𝗲-𝗗𝗿𝗶𝘃𝗲𝗻 𝗠𝗲𝘁𝗿𝗶𝗰𝘀: It’s time to debunk the focus on story points and velocity. Teams should be measured by their impact—customer satisfaction, usability, and business results. 👉 Read the full article to explore how we can refocus Agile on product outcomes and efficiency: https://lnkd.in/efU_6zPB #ProductManagement #AgileTransformation #ProductOperatingModel #Agile #Scrum #SoftwareEngineering #BusinessAgility #OutcomeDriven #AnnaKatharinaReykowski

1

Klaus Häuptle recently announced the release of the 4th book supporting developer engineers in writing clean code: Clean SAPUI5 [https://lnkd.in/epmsdgWe]. This reminds me of what I learned 4 decades ago with ELAN. The programming language ELAN [https://bit.ly/47gR6W0] was widely used in school computer science classes and was especially popular in Germany during the 1980s and 1990s. It emphasized structured programming, clear logical thinking, and focused on modularity and algorithmic precision. With these principles in mind, even complex challenges can be broken down into maintainable and efficient code. Proof of concept was the multiuser operating system EUMEL [https://bit.ly/3Tks1ns] mainly based on ELAN.   Having ELAN, EUMEL and the 8 inch floppy disk in good memories, I wonder if anyone has had the idea to make it run on a Pi ;-)

12

💡 I am fascinated by the notion of a #100X #Product #Engineer Its amazing to see some companies churn out high quality products with a fraction of the engineering teams compared to other companies The 2023 state of #DevOps report by #DORA has great insights into what drives #high #performing #engineering teams. A lot of it is not unknown to everyone, but the sheer impact of focussing on each aspect can have a multiplying effect Also, it gives a great framework for #Engineering #Leaders to measure their team performance, impact and morale Summarising my key takeaways, although would recommend you read this yourself 💯 Holistic definition of "high performing" broken down into 1. #Organisational #performance - leading to more customers, revenue, profit 2. #Team #performance - adapt to change, rely on each other, work efficiently, innovate, and collaborate leading to more trust 3. #Software #delivery #performance - impact on key 4 metrics in Devops - Deployment frequency, Lead time for changes, Change failure rate, Failed deployment recovery time 4. #Operational #performance - Meet expectations of users from the product including availability & performance 5. Reduction of #Burnout, Increase in Job #Satisfaction & #Productivity The key technical factors impacting this are - A. Loosely-coupled #architecture - Substantially increasing all 4 performance factors mentioned above B. #CodeReview speed - coupled with trunk-based development & CI/CD C. Quality of #documentation - AI generated or otherwise D. #SRE practices - Investing in this early on as part of engineering process The biggest eye opener was how all of this fails without investing in "culture". Again, beautifully defined by - - #Westrum’s #organisational #culture:  generative, bureaucratic, and pathological - #OrganisationStability: How stable or unstable is the environment - #JobSecurity: How often employees worry about their job security - #Flexibility: when, where and how to work - #KnowledgeSharing: Probably the most undervalued trait in building a great culture - #UserCentrism: Focusing on the user leads to 40% higher organisational performance & 20% higher job satisfaction - #Work distribution and inclusiveness Do read the report and share your views. https://lnkd.in/gcUTYjbg

10

4 Kommentare

Read about how Paxos is using Bazel and BuildBuddy to speed up their builds! Their P99 runtimes for uncached builds dropped from 50 minutes to 10 minutes. https://lnkd.in/eEvPMQ9e

33

1 Kommentar

🚨I'm honored to be part of this year's FF PMC. Flink Forward is the place, where the #apacheflink community gets together every year, organized by Ververica | Original creators of Apache Flink®. Why Flink Forward? 👉 #apacheflink although around for years, has exploded in demand over the last ~2-3 years. And there is a good reason for it 😉 👉 Due to its nature and use from many early adopters and hyperscalers, you get to see the "what's and how's" of (but not limited to) #streaming problems; the biggest names in the market aim to solve. 👉 What's the next big thing for #streaming and #streamprocessing systems. ... and way way more. If you thought last year was a big show (even though we got our drones 🛫 jammed 😀 🙃 ), then you are up for a surprise as this year will be HUGE. It's Flink's 10th anniversary 🎉 , so it's only natural cool stuff is in place 😎 🌊 If you have a story to share and haven't done already make sure to submit your proposal: https://lnkd.in/dQjApM_d 🌊 If you feel reluctant or want more feedback, you can always reach out to any PMC; we are here to help 😉 🌊 Let's rock these streams 🤘 and look forward to seeing you all in Berlin. #dataengineering

52

🌟 Join me and Ravikanth Mogulla at DevOpsDays Berlin on May 7th-8th! Let's not just stop at the talk—let's connect and exchange experiences. See you there! 🚀 #DevOps #SRE #Networking #DevOpsDayConference #devopsdayberlin #devopsday

116

7 Kommentare

There is a new #PostgreSQL #Meetup group for the region #Stuttgart in Germany. First event takes place on July 11th, in #Tübingen. Two presentations, registration required. Sign up now. Speaker: Ilya Kosmodemiansky: PostgreSQL worst practices Sikandra Chaudhary: What's new in PostgreSQL 17

11

Friends, don’t miss this!! If you are an aspiring CIO/CTO/CDIO or already there, I know that my colleagues Aamer Baig and Delphine Nain Zurkiya are going to equip you with some fantastic insights on how to turn the promise of tech into real value (and get credit for it!) Register here: https://lnkd.in/evJ3nsAB #CIO #CTO #NeverJustTech #TechLeadership

12

Grayton Ward built a cool way to generate IaC for different environments, offloading the bulk of configuration management (including segmenting) to feature flag providers. We speak to a lot of devs who use feature flags to control feature rollouts etc. But on the DevOps side, the user experience of managing GitOps-based deployments and infrastructure hasn't really advanced past editing config files. It's an interesting problem to solve. Grayton has built FlagOps—a template engine that lets OpenFeature-compatible services act as inputs to generate GitOps and IaC repositories. Write-up below (using Flagsmith as the example provider!) https://lnkd.in/eiJnG8Jz #gitops #devops #iac #featureflags

15

3 Kommentare

As enterprises pull data from a large ecosystem of services, engineering teams continue to debate REST vs GraphQL to deliver the best experiences at the right speed and control. I am not dogmatic, so I say, when you can pick both, why choose?! A flavor of how this pattern could work. It makes sense if you can balance the strengths. Many leading technology platforms support both - The trick is in the application architecture and details. #graphQL #REST #BFF https://lnkd.in/eZ7Wfp4R

99

4 Kommentare