Join my daily Newsletter

Subscribe to get my latest content by email.

    I respect your privacy. Unsubscribe at any time.

    preloader
    Elevate Your Embedded Systems Development

    Elevate Your Embedded Systems Development

    Are you facing challenges in your embedded systems projects?

    Modern development practices can revolutionize your approach.

    I’m Luca Ingianni, your embedded systems consultant.

    I help engineering teams adopt agile methodologies and efficient practices, tailored for the unique demands of embedded systems.

    Explore How I Can Assist You

    Key Challenges in Embedded Systems Development

    Through my extensive experience in embedded systems and interactions with numerous CTOs and tech leaders, I’ve identified common challenges in the field. These insights come from both my consulting work and the conversations I’ve been able to lead as a co-host of the Agile Embedded Podcast. Do these resonate with your experience?

    Hardware-Software Integration

    Many teams struggle with seamlessly integrating hardware and software components, leading to delays and unexpected issues in development.

    Real-Time Constraints

    Meeting strict real-time requirements while maintaining system reliability is a constant challenge in embedded systems development.

    Resource Limitations

    Working within the constraints of limited processing power, memory, and energy consumption is a key challenge for embedded systems developers.

    Safety and Reliability

    Ensuring system safety and reliability, especially in critical applications, is paramount and often requires rigorous testing and validation.

    Agile Adoption in Embedded

    Many teams find it challenging to adopt agile methodologies in the hardware-dependent world of embedded systems.

    Toolchain Complexity

    Managing complex toolchains for cross-compilation, debugging, and testing can be a significant hurdle for embedded teams.

    Long Development Cycles

    Embedded projects often have longer development cycles due to hardware dependencies, making it challenging to iterate quickly.

    Keeping Up with IoT and Edge Computing

    The rapid evolution of IoT and edge computing presents both opportunities and challenges for embedded systems developers.

    Fabian Appel, DevOps Engineer

    Fabian Appel, DevOps Engineer

    Luca is a great trainer making the DevOps training worthwile and explaining topics in a very comprehensive way supported by good examples and leading valuable discussions within the training group.

    Oana Moldovan, project lead

    Oana Moldovan, project lead

    Just wanted to say that I have been in several on-line courses during the last year and this was by far the most interactive and interesting one :-) I enjoyed how you moderated the discussions and that we had fun while learning new concepts or remembering what we had pushed to the back of our minds. Thank you for these past 3 days

    (anonymous), DevOps Engineer

    (anonymous), DevOps Engineer

    Luca strikes me as a person who is genuinely intersted in DevOps. He is not selling you are producd but rather trying to show you what you can use in your company/team in order to be more productive.

    GB, Enterprise Product Owner

    GB, Enterprise Product Owner

    Luca is an excellent trainer who try to keep the audience engaged with his unique style of training. He believes in more practical discussions rather than just rushing through the presentation unless necessary. With such practical approach, he keeps the audience engaged. He listen patiently to the queries & try to answer them appropriately without sugar coating. I like the honesty of accepting if he’s unsure of any answers

    Do you want to level up as an embedded systems leader?

    Take a look at my catalog of training, consulting and coaching options – there’s surely something for you!

    buy a consultation or training

    Latest Appearances

    DevOps auf die Ohren und ins Hirn

    DevOps auf die Ohren und ins Hirn

    Folge 50: DevOps Skalieren 1/2

    Open Source Summit Europe 2019

    Open Source Summit Europe 2019

    You Mess Up, People Die: Dealing with Failure in High-Risk Environments

    Czech DevOpsDay 2020

    Czech DevOpsDay 2020

    Don’t make success a negative: Error-based vs. Success-based metrics

    DevOps Paradox Podcast

    DevOps Paradox Podcast

    Luca at DevOps Paradox – DOP 113: Are Specifications still Relevant?

    Tiny DevOps

    Tiny DevOps

    Luca at the Tiny DevOps podcast: Does DevOps make sense for embedded systems?

    DevOps auf die Ohren und ins Hirn

    DevOps auf die Ohren und ins Hirn

    Folge 48: DevOps und OKR

    The Agile Embedded Podcast

    The Agile Embedded Podcast

    How to Speed Up Safety Critical Processes

    The Agile Embedded Podcast

    The Agile Embedded Podcast

    How to Speak Agile to Hardware Folks, with Mojtaba Hosseini

    Handbuch IT-Systemmanagement

    Handbuch IT-Systemmanagement

    Das Kapitel “DevOps” des Buches “Handbuch IT-Systemmanagement” des Hanser Verlages

    Latest Posts

    Image

    Team Topologies: My Reading Journey

    I love the book “Team Topologies”.

    It’s one of those annoying books that’s so full of good stuff that if you highlight what’s worth remembering, you end up highlighting the entire book (and then you think to yourself: “well, that was useless”. Or is that just me?).

    What I like so much about the book is that it puts into words several things that I had kind of figured out, but hadn’t processed deeply enough to have words for some of my thoughts, much less shaped a well-rounded whole.

    Read more
    Image

    When to Rewrite

    One of the hard questions of an engineering manager is how to deal with technical debt, especially of the crippling variety.

    Three bad choices

    Do you throw out the existing product, and rewrite from scratch? Everybody who has tried that has learned painful lessons. Rewrites are always harder than you expect.

    Do you gradually refactor? That means fighting an inadequate product for a long time, painfully juggling old-style and new-style parts of the product, and perhaps not being able to excise all the unpleasant aspects of the old system (after all, the parts that bug yo uthe most are probably also the ones hardest to change).

    Read more
    Image

    The Three Ways and Conway's Law

    First, a quick refresher about those terms I used.

    Hang on, what ways?

    If you’ve read some DevOps literature, you’ve certainly come across Gene Kim’s Three Ways, his core principles underlying the DevOps approach. These ways are

    • Systems Thinking: always considering the system (e.g. your product) as a whole, not just the fraction of the whole you’re concerned with
    • Amplify Feedback Loops: actively seeking out and creating feedback loops, carrying information from “right” to “left”, upstream in the development process
    • A Culture of Continual Experimentation and Learning: well, exactly that: actively finding and welcoming opportunities to try new things – and accepting the occasional disappointment

    And what abut that Mr Conway?

    Conway’s law states that organisations always create products whoes architecture is similar to the organisational structure itself.

    Read more
    Image

    The people you hire are your architecture

    If you’re starting a new company, or a new team, something critical will happen: the people you hire, their skills and interests, will define how they work together… and that will invariably shape your architecture.

    So for budding organisations Conway’s law extends to hiring: you’ll end up with exactly the architecture your first few engineers dictate.

    In a very real sense, your first hires will be your architecture.

    Read more
    Image

    Dunbar's number in remote teams

    Excuse me, what number again?

    Maybe you’ve heard of Dunbar’s number. It’s the maximum number of people you can have a stable social relationship with: the kind where you know the other person, at least somewhat. Dunbar guesstimated this number at about 150 people, for humans.

    Dunbar’s number is important because it puts a cap on the size of departments, or teams-of-teams, or other organisational structures. Once the group becomes too large, it breaks down and splits into subgroups; you won’t know all the people in your organisation, only about 150 of them.

    Read more
    Image

    DevOps in Aerospace

    DevOps in Aerospace

    DevOps is for software companies. You’re an aerospace company.

    …are you sure you’re not a software company?

    Because when I look at aircraft, they have lots of software in them. From avionics to in-flight entertainment, from flight-critical to luxury.

    And let’s not get started with all the software that’s driving processes on the ground: during design, manufacture, maintenance and operation.

    (And remember, I’ve got a degree in Aeronautical engineering, as well several years’ experience in avionics development – I know this first-hand.)

    Read more
    View All Posts

    Contact Me

    I love to encounter new people. Please don’t hesitate to get in contact with me for any reason!

    Meet me in person in Munich.
    Meet me virtually, anywhere in the world!