Steve Massey’s Post

I am excited to be delivering a tutorial on Industrial DevOps at https://lnkd.in/eQwqkDXr Accelerating Space Missions with Industrial DevOps The space industry, with its complex, large-scale, safety-critical cyber-physical systems, is uniquely positioned to benefit from the adoption of Industrial DevOps practices. This innovative approach can significantly enhance the delivery and operation of spacecraft, satellites, and related technologies. By fostering a culture of collaboration between multidisciplinary teams, automating processes for efficiency and reliability, and implementing continuous feedback loops for iterative improvement, Industrial DevOps ensures that space missions can achieve their objectives more efficiently and effectively. Tailoring these practices to meet the stringent regulatory and safety standards of the space domain not only accelerates project timelines but also elevates the overall quality and safety of space systems. As the space industry continues to push the boundaries of exploration and innovation, embracing Industrial DevOps will be crucial for maintaining a competitive edge and successfully executing missions that expand our understanding of the universe. Dennis Ebersole Harry Koehnemann Dr. Suzette Johnson Hasan Yasar Leah T. Brown Mandy Rogers Tracy Bannon

So why are we an Ecosystem? Why Beloved Ecosystem? Because from First Principles, it is the optimal system to manage an environment of uncomputable complexity. Ecosystem's are essentially the Tesla, of organizational design. They have the capacity to achieve goals in environments of fast change and uncertainty. They are the ultimate Complex Adaptive system. They bridge structure and agility. See it in practice with a book recommended by Chike Aguh: Team of Teams: New Rules of Engagement for a Complex World by General Stanley McChrystal, Commander of the 2014 Joint Special Operations Task Force https://lnkd.in/eYZSi3Ke In more technical terms, Ecosystems are the best organizing system or best Entropy reducing system.

Top Deep tech news from the week! In focus: Lockheed Martin, John Deere, and Google. To know more about how BIS Research can help you have the market edge, contact us at hello@bisresearch.com #deeptech #weeklynews #newsoftheweek #lockheedmartin #google #johndeere #googleai #BISresearch

I am looking forward to this event!!! Sharing lessons and success patterns to deliver value faster. #industrialdevops

💡Thrilled to be included on Fast Company’s World Changing Ideas list for 2024! The list honors companies and organizations that are tackling some of our toughest challenges, and setting out to build products that improve the world. At Prewitt Ridge, we’re proud to deliver software that brings new levels of efficiency and collaboration to the engineering teams that are building world-changing technology, namely those designing and building complex hardware systems such as planes, satellites, and rockets. These teams are working on highly technical engineering projects, which require a multitude of tools for design and analysis. They rely on requirements to make those projects achievable, but these requirements and data are often siloed in these tools. At the same time, assessing the impact of any variation in those requirements on the whole system is a challenging and manual process that could result in mistakes, and those mistakes could bring delays, cost overruns, and even catastrophic system failures. Prewitt Ridge’s software helps engineers seamlessly access and distribute requirements across all of the toolsets that teams use. This boosts productivity, breaks down communication barriers, and ultimately speeds up system design timelines. In other words, it helps engineers move faster and break less along the way. Most importantly, this provides more space for the creativity that is necessary to build world-changing products. This recognition gives us more fuel to accelerate the development of high-impact hardware! Check out the full list at the link in the comments! #deeptech #engineering #hardware

It’s #NationalEngineersWeek! 👷 We are proud to have several talented engineers as part of our team, including Chief of Program Services Jeff Westhoven. Learn more about his engineering background and what he loves about being a part of our team! #TheHeartOfItAll

🌟🎧 What an enlightening conversation I had with Shadi Rostami, the SVP at Amplitude, on the "Big Ideas in App Architecture" podcast! 🛠️📲 We talk about Shadi's amazing career spanning across Palo Alto networks to Amplitude and dive into her leadership philosophy and engineering principles. It's a really fun conversations where Shadi is dropping golden nuggets on how to build successful engineering teams that are customer obsessed and outcome driven. Link : https://cockroa.ch/3FPJmxB 🎙️💼 #AppArchitecture #LeadersInTech #Amplitude #Podcast #Innovation #TechTalks #SVPInsights

What can the Soviet space program teach us about an iterative development methodology. The Soviet space program had its fair share of successes and failures, some more dramatic than others. We shall for comparison use the United States approach for achieving the same goals. Consider the scenario of building a class of orbital class vehicle. The US approach: Step 1: Heavy design --> essential since detailed designs of every component need to be share across multiple vendors to build their part. Step 2: Testing of each component individually took place at length with each vendor Step 2 - 1...n: Fix components till the are cleared. Step 3: Assemble all components together for the launch vehicle, assemble the launch infrastructure and see how the components now behave with each other (more like integration testing) Step 4: Once the kinks in the component interface are worked out, you may either end up with a successful launch or a failure of some component thereby requiring rework. The Soviet approach: Step 1: Design everything , nothing major in terms of difference with the US approach. Step 2: Assemble everything together, this meant the launch infra, the launch vehicle, the tracking stations etc. everything came together and was tested together. Step 2 -- 1..n: Fix components till ready. At this stage, not only have the components been tested, but we also have some clue as to how the individual components respond to each other and work as part of an end-to-end system. The crew already have a routine which for example test the launch infra, the fueling, the de-fueling and tracking components of the entire operation even if there is an issue found with the launch vehicle. This adds experience to the entire system working in cohesion. This literally translates into an empirical flow where you gain experience (not necessarily faster, but a wiser approach) as you move ahead. So, although Agile may have been coined much later, working examples of such approaches in some form or another were already available in the real world. Don't let the lack of commentary on the US approach assume bias, that approach in-fact got us to the moon, but that approach deserves its own post. #agiletransformation #empirism

Laura Tacho, CTO at DX, and Crystal Hirschorn, CTO at Zoa, are combining their extensive background expertise in this exciting upcoming discussion on best practices for establishing a strong platform engineering function. Too often platform engineers struggle with: - Team conflicts around tooling - Building the wrong thing - Not getting buy-in from the rest of the engineering org Tune into next week's webinar to learn the common mistakes platform engineers make that lead to these issues when developing a strategy to best serve their engineering organization. Afterward, you'll be able to recognize and avoid these mistakes but most importantly, know how to fix them.

We prove that absolutely continuous functions satisfy the integration by parts formula — hence proving that they are in the Sobolev space. https://lnkd.in/gb5HWf7e