Pierre Tempel

My colleague Richard Nordsieck had the opportunity to present at the recent #VDMA webinar “AI solutions for mechanical engineering – data strategy.” I think that his idea to use the Asset Administration Shell (AAS) as data provider for AI use-cases is particularly interesting. Using AAS as a foundation for structuring knowledge and data — enriched with semantic information and accessible via a well-defined standard API — shows how existing industrial standards can serve as an enabler for knowledge management and AI use cases. It’s a great example of how AAS can go beyond interoperability in manufacturing and become a technological fundament for data-driven innovation. Thanks to Richard and all contributors for sharing their perspectives! #AAS #DigitalTwin #AI #DataStrategy #KnowledgeManagement #Interoperability #VDMA #Mnestix #XITASO

3

if you think #Rust is still a niche programming language only for hobbiest, you need to catch up on the news. Ubuntu is replacing the `sudo` implementation with a Rust version. You cannot go more mainstream and security critical than this!

31

1 Comment

At my company we are currently experimenting 🧪 a lot to use AI for coding in more autonomous ways 🤖. With Cline we are achieving quite remarkable results so far and a lot of coworkers are astonished by the possibilities 🤯. In my opinion the AI space is such a fast paced environment that the most valuable learnings are different techniques, how to effectively use LLMs in the Coding lifecycle. And not get hung up over one tool over another. For example: - ⛓️‍💥 Breaking down bigger problems into smaller chunks, ideally cut vertically - 📸 Using state or context checkpoints to avoid repetitive common groundwork - ❓Make the model ask questions about the task to get deeper understandings apart from the visible context ... That list is not ordered and it's just a bunch of things that I use for my work. The hard part is having the whole company communicate about all the new learnings effectively so that these techniques are known to everyone! Your thoughts?

7

2 Comments

From idea to production in 10 hours. I wanted to see how fast you can actually ship something useful with AI coding in 2025. Not a demo, an actual product people can use. I have built www.smartzeugnis.de - generates German employment references. If you know German corporate culture, you know these are weirdly complicated. They use coded language where "zur Zufriedenheit" sounds positive but actually means "barely adequate." Perfect problem for AI. Stack: Codex + Claude Code, Next.js, Mistral AI, Hetzner. 10 hours of work spread over 2 days. What I learned: The breakthrough wasn't coding faster. It was meta-prompting – I used Claude to write prompts FOR Claude Code, then manually validated the output. This loop of prompt → build → validate is ridiculously fast. You stop thinking in code and start thinking in features. I know this sounds like hype, but most companies are still developing like it's 2019. Better tools, same process. That gap is only getting wider. Try it if you speak German: smartzeugnis.de and let me know your feedback. Curious how others are actually using AI for development – are you coding with assistance or orchestrating AI to build for you?

73

25 Comments

NOA stands for Next Open Automation from KEB Automation KG With Uwe Huber, Head of HMI and IIoT, and the CEO of the Austrian KEB, Markus Weissensteiner, I had another interview with one of the providers of open Linux-based automation platforms. If you look at the statements made in the interview, it is hard to imagine that there will be any well-known automation providers left in the future who will continue to rely on closed systems. The trend is clearly moving in the direction of Linux and open standards. KEB Automation is a good example of this. My interviewees also explained in the interview why openness not only involves a new form of competition, but also very great advantages and simplifications. It is well worth reading. The providers from the market overview are: Bosch Rexroth with ctrlX AUTOMATION, FLECS Technologies with FLECS, German Edge Cloud with ONCITE DPS, Hilscher Gesellschaft für Systemautomation mbH with netFIELD, KEB Automation KG with NOA, KEBA Industrial Automation with Kemro X, Lenze with Lenze NUPANO, Phoenix Contact with PLCnext Technology, SALZ Automation GmbH with SALZ Controller, TTTech Digital Solutions with Ubique, TTTech Industrial with Nerve, WAGO with WAGO OS and WAGO ctrlX OS, and Weidmüller Deutschland with u-OS and easyConnect. The public will be hearing a lot more about this sector in the near future. It embodies the opportunity that our economy has thanks to the innovative strength of the industry in German-speaking countries. Only here is this step towards a new, digital level of automation currently taking place. And this industry will network and make itself heard. Stay tuned. Find the link to the interview in the first comment.

5

1 Comment

Who needs self-service? In this article, Conduktor’s VP of Engineering, Matt Searle, talks about his own experiences attempting to balance developer autonomy alongside platform stability. His key insight? Govern Kafka, or risk havoc. Read his latest blog—and learn more about how Conduktor can help you implement self-service with guardrails. https://lnkd.in/ejWTRctu

14

“Efficiency and transformation are really changing the way we are working.” That’s how Helmut Schuller, Managing Director at @SCHULLER & Company GmbH, summed up the momentum we’re seeing across industries. As one of our long-standing partners, he joined us at #AVEVAWeek 2025 to share how joint projects with AVEVA are helping customers modernize operations and unlock new potential. 🤝 Hear more about how strong partnerships drive real-world innovation—with measurable impact.

33

1 Comment

I’m excited to share that I’ve been invited to speak at this year’s workshop of the German Interest Group in Operating Systems (https://lnkd.in/d2WGUQM3), hosted by Heinrich Heine University Düsseldorf on 26/27 February. In my talk, “Using AI to Fight GenAI Fraud at Scale,” I’ll explore how generative AI is reshaping the fraud landscape — from synthetic identity creation to industrial-scale deepfake attacks — and what it takes to defend against it effectively. Beyond detection models, I’ll dive into the engineering side: what enterprise-ready, cloud-native architectures must look like to handle millions of verifications per day, process billions of events per month, and scale dynamically while maintaining reliability and observability. Looking forward to discussing the intersection of AI and large-scale systems with the operating systems community.

57

Your CI pipeline takes 35 minutes. The actual tests? Only 20. What's eating the other 15 minutes? One test. One webhook. One painful wait that blocks your entire team every single run. You submit a quote. A third-party system processes it. The webhook arrives... eventually. 15 minutes later. Meanwhile, 280 other tests sit idle, waiting their turn. Your devs stop trusting the pipeline. PRs stack up. Sprint velocity tanks. You can't skip the test. The wait is real. But you can stop letting it hold everything hostage. The fix: trigger the webhook in global setup, let it cook in the background, then validate after your suite finishes. (Check Below 👇) Now your 280 tests run in parallel while the webhook processes behind the scenes. By the time validation runs, the response is already waiting. 35 minutes becomes 20. Same coverage. Zero compromises. #Playwright #TestAutomation #CI #QA #E2ETesting

6

Check out this newly published Manifesto on Technical Debt! My wonderful colleagues Brigid O'Hearn and Ipek Ozkaya are part of a world-class group of researchers who came together to reframe the field of technical debt. The post below features a one-page summary, and you can click through to download the full report from Dagstuhl Perspectives Workshop 24452. DoD Acquisition friends, I'm curious: how do you measure/track technical debt in your software programs? Brigid O'Hearn Ipek Ozkaya William Nichols Rita Creel Christina Rhylander

7

Dear Jensen Huang, at the most recent “Tag der Industrie 2025” with chancellor Friedrich Merz, you claimed that we Germans are unable to develop software because we are too “precise.” 𝗜 𝗱𝗶𝘀𝗮𝗴𝗿𝗲𝗲: 𝗽𝗿𝗲𝗰𝗶𝘀𝗶𝗼𝗻 𝗶𝘀𝗻’𝘁 𝗮 𝘄𝗲𝗮𝗸𝗻𝗲𝘀𝘀. 𝗜𝗻 𝗼𝘂𝗿 𝗰𝗮𝘀𝗲, 𝗶𝘁’𝘀 𝗮 𝗿𝗲𝗾𝘂𝗶𝗿𝗲𝗺𝗲𝗻𝘁 𝗳𝗼𝗿 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗮𝗻𝗱 𝗱𝗮𝘁𝗮 𝘁𝗵𝗮𝘁 𝗹𝗮𝘀𝘁𝘀. I got your point, Jensen, but please take into account: Someone who works accurately can always botch things up at any time. A bungler, on the other hand, can never work accurately. “Doing the right thing right” is a challenge and a vision, but it is the only possible position - it is the only sustainable way in our branch out of digital chaos. We’re even willing to sacrifice our short-term gains (profits) to get there. We see it every day: if wrong software is used or software isn’t built with care, users often end up with messy, inconsistent, unstructured data. That’s not value - it’s data waste. 𝗧𝗵𝗶𝘀 𝗸𝗶𝗻𝗱 𝗼𝗳 𝗱𝗮𝘁𝗮 𝗰𝗲𝗿𝘁𝗮𝗶𝗻𝗹𝘆 𝗶𝘀 𝗻𝗼𝘁 “𝘁𝗵𝗲 𝗻𝗲𝘄 𝗼𝗶𝗹”. Only 𝘷𝘢𝘭𝘪𝘥 data is. And so this might create the demand for more processing power, but it’s hardly progress. Real progress means creating clean, usable data right from the start. But don’t worry - we are using NVIDIA chips in a much smarter way than just fixing “data chaos” with the help of AI. At primtech, we develop 𝗱𝗮𝘁𝗮𝗯𝗮𝘀𝗲-𝗱𝗿𝗶𝘃𝗲𝗻 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗳𝗼𝗿 𝗰𝗿𝗶𝘁𝗶𝗰𝗮𝗹 𝗶𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲. There’s no room for “move fast and break things” when the cost of bad data is real-world damage. In other industries, this might work. In many use cases, it would be fatal. We use AI to build valid Digital Twins of existing HV substations. Of course, even our German employees are able to deal with chaos and faulty data. But if we have a chance, we do it right from the start - with precision, and care, and valuable data. Our customers don’t need more silos, they need clarity and consistency. “German thoroughness” isn’t a bottleneck. It’s a strength. Especially in the energy sector, where many global engineering and software leaders come from Germany - built on deep expertise, long-term thinking, and quality by design. That’s also how we work at entegra gmbh. People from over 17 nations contribute their skills and knowledge to build software that delivers on its promise. Immigrant expertise is part of our success. We employ industry experts - not just to build the product, but to support it. People who understand the project, the industry, and the real challenges behind the screens. If you think precision slows things down, you might be misunderstanding what digitalization is actually about. PS: Funny enough, you also advised young people to focus on physical sciences instead of software. Seems like you know that real-world impact still relies on precision and expertise. Welcome back to reality. #Innovation #DigitalTransformation #AI #BusinessModelInnovation #Germany

41

5 Comments

TYPO3 CMS Migration framework In 2025 I worked on a big migration and upgrade project. It was a website based on TYPO3 CMS, that needed a major technical overhaul. During the upgrade process I migrated over 100 content elements from DCE to Content Blocks and Container. On the TYPO3camp Hamburg 2025 I presented my approach to a handful of people. Some of them approach me afterwards asking about a similar migration for Flux based content elements. Matthias Krappitz put in some effort and found 4 companies including his own to sponsor the development of the Flux to Content Blocks migration. The result is not only a Flux to Content Blocks migration. It is an extensible migration framework for content element migration. The core uses Content Type Providers, that provide normalized configuration and data of the source content elements, Content Type Builders, that build the configuration for the target content type and Record Data Migrators, that take the source data and return the data structure for the new content type. Based on the structure it is possible to migrate from one content element strategy to another. It would even be possible to migrate plugins or core content elements with this, if someone built content type providers for that. Currently there are extension with Content Type Providers for DCE and Flux available, as well as Content Type Builders for Content Blocks and Container: * https://lnkd.in/eg-pirJD: Migrator core * https://lnkd.in/ezGYBXnw: DCE Content Type Provider * https://lnkd.in/eRkUDCPx: Flux Content Type Provider * https://lnkd.in/etgSH_qZ: Content Blocks Content Type Builder * https://lnkd.in/etiDADVs: Container Content Type Builder If you think this could be relevant for you, please start with reading the documentation (README) of the migrator core, as it describes the core concepts and components. If any questions arise please message me here on LinkedIn or send me an email to thorben@webcoast.dk. This the first version, which still needs some testing. So if you're interested, please give it a try an provide feedback. A big thank you goes to aemka, Apart Design Studio, Homepage Helden GmbH and Henrik Ziegenhain for sponsoring the development. Another thank you goes to Nikita Hovratov (https://lnkd.in/efiDk59H) for his work on Content Blocks and b13 GmbH for their container extension. #typo3 #cms #dce #flux #contentblocks #container #sponsor #community #opensource

8

Every engineering leader says they care about velocity. But velocity doesn’t die in the IDE. It dies in: Review queues Approval loops Dependencies across 3 other teams The fastest teams don’t code faster. They unblock faster.

1

🎙️ New episode with Sebastian Gerhardt is live. In this episode of Build by People Leaders, I speak with Sebastian Gerhardt, founder of Flee, about improving developer experience in modern software organizations. One key idea: Developer productivity cannot be measured by output alone. We explore: • Why output-based metrics often fail engineering teams • How organizational structure and team culture shape performance • The role of psychological safety in high-performing teams • How feedback systems and survey-driven insights reveal hidden friction • Engineering leadership in remote and distributed environments For CTOs and engineering leaders, this conversation offers practical insights on identifying friction points, fostering open communication, and building resilient, high-performing teams. 🎧 Listen here: https://lnkd.in/dKV3ZtFW

3

Your CI/CD bill is not exploding because of “expensive runners,” it is bleeding out through flaky tests, over-parallelized jobs, and slow feedback loops that quietly tax every deploy This piece shows you how to redesign pipelines so you cut compute waste, shrink queues, and speed up developer flow without adding yet another approval gate or YAML religion Full breakdown in the comments. #DevOps #CICD #PlatformEngineering

8

1 Comment

Two major events today: 1️⃣ Launch of the yearly SPS in Germany 🏭 2️⃣ Release of Claude Code Opus 4.5 ✨ This morning I am keeping half an eye on my LinkedIn feed showing posts from SPS, while I test the capabilities of Opus 4.5. Such a crazy time to live in, where every x months coding models become y % better. And there are no signs that things are slowing down. But industrial automation is stuck. We can't use the modern coding workflows with the 'legacy' automation IDE's. Yes during SPS multiple vendors are presenting some kind of solutions. But here are the problems: ❌ Coding agents have no direct access to the code, everything runs through API's/MCP/... ❌ No git for tracking the agents. (Or worse: broken git) No granular commits and reviews for what the agents are doing. No diffs. No SDLC. ❌ No or limited BYOM (Bring your own Model). ❌ Separate licensing for the coding agents WITHOUT the model. ❌ ... ? The root causes are: 1️⃣ Legacy IDE's that shield the code from direct access 2️⃣ No CLI commands for things like code compiling (coding agents need feedback loops) 2️⃣ Fragmented IEC-61131 dialects (yes most automation engineers stayed in a single vendor ecosystem, but agents are general, and will be massively confused by this) But at least there's good news: next-gen IDE's are coming! This is what has already been announced/released: - Simatic AX - Beckhoff PLC++ - Codesys Go! - B&R Automation Studio Code ... and more coming that are not announced yet. My recommendation? Stop putting effort in legacy IDE's. We'll need to transform our coding workflows. It will take effort. Using coding agents with legacy IDE's will be almost impossible to control. Spend the effort by taking the opportunity to switch to a next-gen IDE. Talk to your vendor. Don't take 'not ready' for an answer. (Send me a DM if you don't know which person(s) to talk to) And if you're one of the automation vendors? Well we have been asking to fix the IDE's and toolchains since many years. At least some of you realized the need and took action a while ago. But there is no way to hold this back. We are losing competitiveness, speed and talent. Things still feel like they are moving relatively slowly. Yet soon it will be suddenly. How about the DCS system? Well ... you all know that I live and breathe process automation. There also is a viable path forward there. But no vendor seems to see the path through the trees yet ... 🤷‍♂️. I am not at SPS, so add a comment if I missed something ... 🫵 👇

28

2 Comments