Mazda Toyota Manufacturing’s Post

👉When the members of IPN were faced with difficulties in the business climate, we partnered to help them navigate through it. The business development support program led by Ricoh delivered: achievable ✅, realistic 💡and measurable 📏results. 🎞Jeroen Beckers, the General Manager of IPN, explains in the video, how members became better able to adapt to the unparalleled challenges of this extreme period thanks to our partnership. ▶️Take a look: #BusinessDevelopment #DigitalExperience #LeadingChangeAtWork

It’s the start of a new month, last month of the 1st quarter of the year. How far have you gone with the goals you’ve set for this year? You might have had a few setbacks and hangups but that’s okay. This is another chance to re-strategize and take action on your plans and let’s #marchforward #pdic #industryintel #happynewmonth #manufacturingindustry #manufacturingconsultancy

Here we grow!!!! #practicalbuildings #practicalmetals #pemb #metalroofing #metalbuildings #steelbuildings #standingseam #standingseamroofing #clientfocusedsteelsupply #rollforming #jobsiterollforming #commercialroofingsupply #sdvosb #service #disabledveteranowned

Curious about how our solutions can streamline your revenue cycle and enhance efficiency? Swing by and say, "Howdy!" to Ashley Sanders, MBA in booth #2 at the HFMA Texas State Conference to learn how we can help you #RecoverMore! #HFMATexas

#Digital_Engineering Finally ANSYS Simulation World 2024 Conference ( #SIMWORLD24) is coming. I encourage to attend my lecture that was recorded last July as Director of Engineering and Shipbuilding in the Spanish Navy. Title: Digital Engineering for Navy Systems: Digital Thread to improve LifeCycle Support. May, 24 @ 1120 EDT It is about Digital Engineering in the shipbuilding process, from requirements definition to design, production and life cycle with emphasis in MBSE and digital twin development and enrichment. Digital engineering is a MUST for complex proyects and it will facilitate and accelerate the fielding of current and next generation warship programs.

Great insights from Simon Heliso Kuka @ the 3rd SBC Summit! Do we often overlook the future consequences of our decisions, focusing solely on immediate needs? Dr. Heliso's stance on #sustainabledevelopment challenges us to think beyond today. We need to start making decisions that "meet our present needs without compromising future generations." Let's reflect on our choices, ensuring they pave the way for a sustainable and thriving future for our children and #futuregenerations to come.

Join the leaders of DCT - David Coman, Michelle Longmire, Anthony Costello, Derk Arts, MD PhD, Steve Rosenberg, Ryan Jones, AMIR KALALI, MD, and Craig Lipset - as they discuss the current state of DCTs beyond the hype #CNSSummit2023

In this month's #AUGIWORLD, Mark Kiker continues his running series, Secrets that Tech Managers Keep. This month is about decision fatigue and the toll it can take on a Tech Manager. Page 12 here: https://smpl.is/8naiw #AUGI

Just as models should be iterative, strategic design should change when the context and our understanding of the problem evolve. As a model grows to solve more problems, it becomes less supple in its ability to evolve. Tensions arise within the model that struggles to stay coherent. Eventually it reaches a critical mass and becomes a big ball of mud. Watch this talk with Julien Topçu and Josian Chevalier from DDD Europe 2023 and join us for more talks at https://lnkd.in/emU28ezw

Let's talk about this microservices mess we all have done and may be still doing 💥 The microservices trend pushed many people to oversplit ✂️their software into multiple services, falling into the hell of distributed monoliths. As a result, each time a feature is implemented in the system, several microservices must be changed and delivered together, even though this is against the microservices philosophy 🤯 All those things happen because although those microservices are technically decoupled, they are still conceptually coupled🔗from the business domain perspective. After a decade of microservices in production, the industry is taking a step back and realizes that splitting too soon will generate important scale costs : 🕸️Network calls instead of method calls (increased debug cost, and cognitive load, intermediate technical services such as message brokers, circuit breakers...) 🧑💻 Code over-duplication (more than needed) across the microservices 🎢 Scaled technical debt (instead of having one instance of a technical stack to updated, you need to update it for each microservices) On the other hand, under-splitting the software by stacking evolutions without a modularization strategy will end up creating coupling between all the responsibilities🔗 It then turns the system into a hell of legacy spaghetti monolith 🍝: a Big Ball of Mud (code immobility, high cognitive load, high maintenance cost...) Even though those problems seem different, they are two sides of the same coin🪙: the business model should drive splitting strategies. It is quite complicated to find a pattern which helps people split a model in place while they have to ensure the stability and evolution of the application over the duration of the process. We lack heuristics to make decisions to spawn a new model and patterns to decide on the boundaries of the system. In the early stages of the split, the complexity is generally not sufficient to draw the boundaries🚩without overlap. After several years of experimentation⚗️, Josian Chevalier (Shodo 🈹) & I found a dynamic pattern to split progressively while limiting the coupling between the emerging models. This pattern help you to avoid falling into the Distributed Monolith and Big Ball of Mud Hells🔥 By combining strategy patterns from Domain-Driven Design, we coined the Mitosis Pattern (as an analogy of a cellular mitosis 🧬). We had the chance to present it during Domain-Driven Design Europe 2023, and the talk is now available on YouTube: https://lnkd.in/eNx5zQ4F Note: Beware of the reluctant and passive-aggressive AI we are using during the talk 🤖