Cristian M. builds software that connects .NET applications with industrial automation, robotics, simulation, and AI tools. Their projects include C# libraries for industrial protocols and ROS, plus a digital-twin environment that brings simulation and robot-control components together.
Useful for custom technical collaboration on .NET integration with industrial automation, robotics, simulation, or AI tools.
Best for
Robotics software brands needing .NET bridges to industrial automation, ROS, or simulation tools.
Not for
Campaigns needing ready-to-book sponsored posts, published rates, or guaranteed broad consumer reach.
Key takeaways
They build C# libraries for industrial protocols and ROS to make capabilities accessible to .NET developers.
A MuJoCo walking policy runs in PhysX as a signal graph block, without retraining or Python.
On humanoid robots, they weigh flexibility against speed and repeatability of dedicated equipment.
Check first: Confirm sponsorship formats, availability, pricing, disclosure terms, audience demographics, and engagement on comparable technical posts.
Main ideas
New robotics and AI capabilities should plug into existing engineering software, not replace it · The digital-twin market is a set of excellent islands; what’s missing is a neutral, open graph · Understand the process before choosing the automation
Cristian M. builds software that connects .NET applications with industrial automation, robotics, simulation, and AI.
Their projects include C# libraries for industrial protocols and ROS, and Gemelli Studio, a digital-twin environment that brings simulation and robot-control components together.
Their posts pair hands-on engineering with a practical question: where should complexity sit—in the robot, the factory, or the software connecting them?
Cristian M. makes the promise and work of integration visible.
In a Gemelli Studio demonstration, a walking policy trained in MuJoCo runs in PhysX as a block in a signal graph, without retraining or Python.
They also describe the effort required to match the policy’s training conventions, a reminder that connecting tools takes more than making them look compatible.
Across their software projects, the same idea recurs: make capabilities such as industrial protocols, ROS, simulation, and AI accessible to .NET developers.
Their automation commentary is grounded in tradeoffs.
On humanoid robots in factories, they weigh the flexibility to reuse workstations or switch tasks against the speed and repeatability of dedicated equipment.
For a stable, high-volume process, a fixture may be the better answer; when products or demand change, flexibility can matter more than the fastest cycle.
They look beyond the machine to the process around it.
In a reflection on manufacturing efficiency, they argue that engineers should ask why each step exists before automating it: some steps compensate for inconsistent inputs or catch problems that could be prevented earlier.
And a family robotics build shows that practical engineering includes maintaining the tools that make the robot, not just assembling it.
Their posts describe work scaling automation systems at Symbotic and a subsequent focus on manufacturing. Ask for more detail on the scope of their career and other signature work.
Cristian M. builds software that lets engineers access advanced robotics, simulation, and AI capabilities from the tools they already use, mainly C# and .NET.
Read more
The posts consistently argue that integration matters more than migration, a neutral open layer is better than another closed suite, process understanding should come before technology selection, and hands-on craft — including maintenance and unconventional combinations — is how good engineering gets done.
New robotics and AI capabilities should plug into existing engineering software, not replace it
Cristian M. argues that Windows-based engineering tools already hold a great deal of useful industrial knowledge.
Read more
Connecting to them often means working with .NET, vendor SDKs, or COM interfaces that have been around for years.
The useful work, in this view, is making newer capabilities reachable from that existing software, so engineers do not have to move an entire application into another ecosystem.
The posts describe a family of C#/.NET libraries built on that principle, at different stages and with different dependencies and limitations.
The Friday Projects post lists EthernetIpSharp for reading and writing EtherNet/IP controller tags and implementing scanner and adapter roles; Mori.RosSharp and Mori.Ros2Sharp for ROS communication directly in managed C#, letting a .NET program take part in robotics workflows without a separate bridge process or a ROS installation on the same machine; C# wrappers around NVIDIA’s ovphysx and ovrtx physics and rendering engines; and LocateAnythingSharp for local perception inference, with image and camera demos.
The digital-twin market is a set of excellent islands; what’s missing is a neutral, open graph
Cristian M. respects the existing tool landscape — Siemens Tecnomatix, Rockwell’s Emulate3D, realvirtual.io, MuJoCo, Isaac, Gazebo, and FMI — and says the capability is already there.
Read more
The critique is about interoperability: each tool is a strong island, and getting off it is the hard part. Instead, the work is building a neutral, open-source environment in plain C#/.NET where a reinforcement-learning policy, a classic PLC control model, a supplier’s FMU, and a physics-accurate robot can all be blocks in the same graph.
Cristian M. describes the Signal Mapper evolving into a general block system for FMUs, SSPs, and ONNX neural networks.
A walking policy trained in MuJoCo for an Open Duck Mini v2 biped was exported and run in PhysX inside Gemelli Studio without retraining or Python, then steered live from the keyboard.
Matching every convention the policy was trained under took real work.
Understand the process before choosing the automation
In a reading note on Brian Potter’s The Origins of Efficiency, which examines how industries from steel and semiconductors to container shipping make production faster, cheaper, and more reliable, Cristian M. frames efficiency as accumulated engineering knowledge, not simply faster equipment.
Read more
Understanding why each process step exists changes the investment decision: it shows where automation helps, where the process needs redesign, and where a simpler tool is enough. Improvements also need to be captured, not left to one expert’s memory, so they can be repeated, taught, and tested.
Take a ten-step process.
Instead of buying equipment to speed up each step, ask why the ten steps exist.
Perhaps two compensate for an inconsistent input, one inspects for a problem that could be prevented earlier, and another is a handoff left over from a previous layout.
Cristian M. sums it up: a robot can repeat an operation, but whether that operation belongs in the process is still an engineering question.
Flexibility is worth paying for, but complexity should sit where it earns its keep
Commenting on Figure 02’s send-off and Google DeepMind’s Gemini Robotics 2 announcement, Cristian M. asks a question more interesting than the robot itself: how much of a factory should change to accommodate automation?
Read more
Engineers have made the world predictable for machines through fixtures, part presentation, and dedicated stations.
That investment buys speed, repeatability, and quality, and makes sense for stable, high-volume work.
But when products change often or volumes do not justify dedicated equipment, the same investment becomes a barrier.
A robot that handles more variation could change the calculation by reusing workstations, shortening changeovers, or moving between tasks as demand shifts.
Flexibility can be valuable even when it does not produce the fastest individual cycle.
Cristian M. also says they would not ask an expensive robot to solve a problem that a simple fixture could eliminate.
The real decision is where to put the complexity and what it will cost over the life of the process.
One question remains open: they are still not sure humanoids are the right form factor for factories.
Keep the whole chain visible, and treat maintenance as part of the craft
A family build-log post treats building a robot and maintaining the machines that make it as one continuous activity.
Read more
The method is slow, sequential, hands-on work, with the diagnostic reasoning made visible: open the tool, find the wear, explain why the upgrade addresses it, and note the maintenance that remains.
The point is educational as much as technical.
Nothing in the chain is treated as a black box, so a child can see the machine that makes the parts, the parts that make the robot, and the care each one needs.
The legs of an open-source 3D-printed biped were finished, and each motor calibrated one joint at a time, with every servo’s range checked before moving on.
The detour involved a Bambu Lab X1 Carbon, fitted with a CNC-machined aluminum extruder and metal gears to replace the stock plastic ones.
The plastic gearbox was packed with filament dust, and its gears had worn from abrasive materials, making the original grip inconsistent across flexible TPU, PLA, and tougher engineering filaments.
Unconventional combinations are an engineer’s edge, not a contradiction
A leadership post argues that traits people see as mismatched often produce results.
Read more
Cristian M. describes an unspoken pressure to fit a mold — the executive who only talks strategy, the engineer who only talks specs, the leader who is above getting their hands dirty — and says the people who change things bring something unexpected, such as an engineer who understands supply chain or a manager who can still solder. After 25 years in the industry, they observe that people who kept their edges built things that mattered while others sanded theirs down.
The listed background includes building furniture in a garage, naming a home automation AI after Norse mythology, reverse-engineering network protocols on Sunday mornings, teaching a child the Tetris theme through engineering, and leading the Autonomous Robotics Center at one of the largest automakers in the world.
In a separate post, Cristian M. closes what they call a chapter at Symbotic, describing years spent helping design and scale automation systems for logistics, including advanced robotics, AI, and real-time control in complex warehouse and supply chain environments.
They say the next chapter applies that experience to a new frontier in manufacturing.
Ask how the departure relates to the leadership role described in the other post.
Answers a newcomer’s first practical question: what does Cristian M. build, in which language, and for which industrial robotics and simulation problems?
Read more
Cristian M. lays out a connected set of C#/.NET projects: EthernetIpSharp for EtherNet/IP controller tag reading and writing and scanner/adapter roles; Mori.RosSharp and Mori.Ros2Sharp for ROS communication in managed C# without a separate bridge process or ROS installation on the .NET machine; C# wrappers around NVIDIA ovphysx and ovrtx; Gemelli Studio, a digital-twin runtime/editor with USD scenes, physics, sensor rendering, C# control, behavior models, and ONNX policies; and LocateAnythingSharp for local inference, with image and camera demos. The post says the projects are at different stages, with different dependencies and limitations.
For brands planning a campaign
Directly relevant to a robotics software company assessing .NET integration work. A consulting engagement could start with the existing libraries and Gemelli Studio, then establish supported protocols, ROS versions, simulation engines, dependency limits, and production-readiness requirements.
Shows the product thesis behind the libraries: not just wrappers, but a neutral integration layer competing on openness and mixed-model co-simulation.
Read more
Cristian M. describes Gemelli Studio’s Signal Mapper becoming a general block system for FMUs, SSPs, and ONNX neural networks.
A walking policy trained in MuJoCo for an Open Duck Mini v2 biped was exported, run in PhysX inside Gemelli without retraining or Python, and steered live from the keyboard.
The post names Siemens Tecnomatix, Rockwell Emulate3D, realvirtual.io, MuJoCo, Isaac, and Gazebo as strong but separate tools, and argues for a neutral, open-source C#/.NET graph that brings RL policies, PLC models, supplier FMUs, and physics-accurate robots together as blocks.
For brands planning a campaign
Gives a robotics software company a clear differentiation story and a concrete demo to evaluate.
It also identifies competitive alternatives and the integration promise.
Before repeating the no-retraining claim, test the repository, supported conventions, and reliability limits.
Explains how Cristian M. frames automation value: understand the process first, then choose the technology.
Read more
A reading note on Brian Potter’s The Origins of Efficiency.
Cristian M. treats efficiency as accumulated engineering knowledge, asking why each of ten process steps exists.
They suggest that understanding input inconsistency, inspection, and handoffs changes automation investment decisions.
A robot can repeat an operation, but whether that operation belongs in the process remains an engineering question.
Improvements must also be captured so they can be repeated and taught.
For brands planning a campaign
Useful for a robotics software company seeking consulting conversations about integration, not just tooling. The post suggests a services angle around process mapping, simulation, and knowledge capture.
Offers a plain-language view of the tradeoff between fixed automation and flexible robotics, a recurring issue for manufacturing readers.
Read more
Cristian M. questions whether humanoids are the right factory form factor while praising Figure 02’s send-off and Google DeepMind’s Gemini Robotics 2 announcement for whole-body control, dexterity, and multi-robot collaboration.
The central question is how much of a factory should change to automate it.
Fixtures, part presentation, and dedicated stations buy speed, repeatability, and quality in stable, high-volume work, but become barriers when products change frequently or volumes are low.
Flexibility can have value even when it does not produce the fastest individual cycle, but Cristian M. would not ask an expensive robot to solve a problem a simple fixture makes disappear.
For brands planning a campaign
A robotics software company can use this as a campaign theme around flexible automation and integration economics. For consulting, it suggests a discovery framework: identify where process variation justifies robot flexibility and where a fixture remains the cheaper answer.
Establishes the senior leadership context and hands-on engineering identity running through the technical posts.
Read more
Cristian M. says they lead the Autonomous Robotics Center at one of the largest automakers in the world.
They also describe hands-on engineering habits: building furniture, naming a home automation AI after Norse mythology, reverse-engineering network protocols, and teaching a child the Tetris theme through engineering.
The post argues these are not contradictions and that people who change things bring unexpected combinations rather than fitting a mold.
For brands planning a campaign
Relevant to assessing authority and fit for a consulting engagement. The post supports a senior-practitioner positioning, but it is a leadership essay, not evidence of specific .NET integration work; pair it with the project posts.
Provides career context for the warehouse and manufacturing interests in the other posts.
Read more
Cristian M. says they recently wrapped up a chapter at Symbotic, helping design and scale automation systems for logistics, with advanced robotics, AI, and real-time control in complex warehouse and supply chain environments. The post cites improvements in reliability, speed, and flexibility at massive scale and says the next chapter applies that experience to manufacturing.
For brands planning a campaign
Useful for a robotics software company evaluating large-scale automation experience and a manufacturing focus. Ask for details on the systems, roles, and results behind this transition statement; the post is not a technical case study.
A weekday series structure across very different subjects7
Building .NET bridges into robotics and industrial automation2
Gemelli Studio and the open-source digital twin argument2
Large-scale logistics automation and a stated move into manufacturing2
Efficiency as accumulated engineering knowledge1
Where flexibility pays: humanoids and factory redesign1
Hands-on making and maintenance as a teaching format1
Engineering leadership and bringing an unconventional background to the job1
Building .NET bridges into robotics and industrial automation
A large share of Cristian M.'s posts describe software libraries that let .NET applications access industrial protocols, robot middleware, physics simulation, rendering, and AI perception without leaving C#.
Read more
EthernetIpSharp reads and writes EtherNet/IP controller tags and implements scanner and adapter roles, with sibling projects in Python, C++, and Rust.
Mori.RosSharp and Mori.Ros2Sharp implement ROS and ROS 2 communication directly in managed C#, letting .NET programs take part in robotics workflows without a separate bridge process or a ROS install on the same machine.
C# wrappers around NVIDIA's ovphysx and ovrtx expose physics and rendering engines through .NET APIs, while LocateAnythingSharp connects a perception model and native inference engine to C#, with image and camera demos that run locally.
The practical motivation is that Windows-based engineering tools are long established in industrial automation and often require .NET, vendor SDKs, or older COM interfaces; these libraries let newer capabilities plug into that existing software.
Wrap native or vendor engines in managed C# APIs so engineers can keep their applications in .NET rather than move to another ecosystem. The posts are candid that projects are at different stages and have different dependencies and limitations.
For brands planning a campaign
This is the most directly relevant evidence for a robotics software company selling .NET integration: the posts read as a working portfolio of libraries built for exactly that purpose.
A consulting engagement could adapt the same pattern to a specific vendor SDK, protocol, or simulation engine.
Before promising a deliverable, ask which libraries are production-ready and which are demonstrations.
Gemelli Studio and the open-source digital twin argument
A digital-twin runtime and editor called Gemelli Studio recurs across the posts.
Read more
It combines USD scenes, physics, sensor rendering, C# control, behavior models, and ONNX policies.
Its ROS 1 topic connections let external robotics software send commands in and receive joint states, odometry, and simulation time.
The clearest statement of intent is an argument that today's digital-twin market is made of "walled gardens": Siemens Tecnomatix and Rockwell's Emulate3D for factory-scale twins, realvirtual.io in Unity, MuJoCo, Isaac, and Gazebo for robot learning, and FMI as the glue between tools.
The post says these tools lack no capability and respects them, but describes each as an excellent island that is hard to leave.
Cristian M. wants to build a neutral, open-source place in plain C#/.NET where a reinforcement-learning policy, a PLC control model, a supplier's FMU, and a physics-accurate robot are all blocks in one graph.
A walking policy learned in MuJoCo was exported and run in PhysX inside Gemelli Studio without retraining or Python.
The post presents this as proof that the block system generalizes: FMUs, SSPs, and now neural networks all become pins that can be wired like any sensor or drive.
Matching the conventions the policy was trained under took real work.
The critique targets interoperability, not competitors' engineering. The post says existing tools lack nothing and does not present the project as another suite to buy.
For brands planning a campaign
For a brief on simulation and integration tooling, this offers a clear, quotable position for content or a joint demonstration, especially the comparison between open block-based graphs and single-vendor suites.
A software partner could sponsor or co-develop integration examples.
Since the projects are open source, explain what will remain public.
A reading post works through The Origins of Efficiency by Brian Potter, drawing on steel, semiconductors, and container shipping to examine how production becomes faster, cheaper, and more reliable.
Read more
Cristian M. argues that efficiency is accumulated engineering knowledge, not just faster equipment.
In a ten-step process, instead of buying a machine to speed each step, ask why the steps exist: some compensate for inconsistent input, one checks for a defect that could be prevented earlier, and another is a handoff left over from an old layout.
Understanding those details changes the investment decision, showing where automation helps, where the process needs redesign, and where a simpler tool is enough.
Read widely, then apply the argument to robotics and AI decisions: a robot can repeat an operation, but whether that operation belongs in the process remains an engineering question. The post also argues for capturing improvements so they do not depend on one expert remembering an adjustment.
For brands planning a campaign
Useful to a vendor whose buyers are weighing automation against process redesign. The posts support educational content and workshop material that puts discovery work before hardware selection, giving a sponsor an intellectually credible frame rather than a product-first one.
Where flexibility pays: humanoids and factory redesign
A post on Figure 02's send-off and Google DeepMind's Gemini Robotics 2 announcement raises a question the author finds more interesting than the robot: how much of a factory should change to automate it?
Read more
The argument is that engineering effort has gone into making the world predictable for machines through fixtures, part presentation, and dedicated stations.
This buys speed, repeatability, and quality, making it the right investment in stable, high-volume processes.
When products change often or volumes do not justify dedicated equipment, that investment becomes a barrier.
A robot that handles more variation could change the calculation by reusing workstations, shortening changeovers, or moving between tasks as demand shifts.
Flexibility is valuable even when it does not produce the fastest individual cycle.
The post does not treat humanoids as the answer. It questions whether they are the right form factor for factories and says it would not ask an expensive robot to solve a problem a simple fixture makes disappear. The decision is where to put the complexity and what it costs over the life of the process.
For brands planning a campaign
A ready-made discussion hook for robotics vendors selling flexibility, and a good basis for a sponsored debate, webinar, or comparison piece. Align with the post's measured tone on humanoid form factors rather than expecting a firm verdict.
Hands-on making and maintenance as a teaching format
A family build-log post follows an open-source 3D-printed biped robot, finishing the legs and calibrating each servo's range one joint at a time before moving to the head.
Read more
It then turns to maintaining the 3D printers the build depends on.
The Bambu Lab X1 Carbon gets a CNC-machined aluminum extruder and metal gears in place of the stock plastic ones after the plastic gearbox was found packed with filament dust and the gears worn from abrasive materials.
The original grip was inconsistent across TPU, PLA, and engineering filaments.
The post's point is that maintaining the tools is part of the same craft, and that a child can see the whole chain from machine to part to robot, with nothing treated as a black box.
Slow, sequential hands-on work makes the diagnostic reasoning visible: open the tool, find the wear, explain why the upgrade addresses it, and note the maintenance that remains.
For brands planning a campaign
Reaches makers and small-shop audiences as well as industrial ones, suiting 3D printer, filament, and desktop-fabrication brands.
The discussion of material-specific wear gives sponsors a detail to build a technical demonstration around.
Large industrial vendors should note that this audience and tone differ from the factory-scale posts.
Engineering leadership and bringing an unconventional background to the job
A leadership post argues that traits seen as mismatched can produce results.
Read more
The listed background includes building furniture in a garage, naming a home automation AI after Norse mythology, reverse-engineering network protocols on Sunday mornings, teaching a child the Tetris theme through engineering, and leading an Autonomous Robotics Center at an automaker.
The claim is that people who change things bring something unexpected, such as an engineer who understands supply chain or a manager who can still solder.
After 25 years in the industry, the author says people who kept their edges built things that mattered while others sanded theirs down.
A first-person anecdote carries the argument and closes with advice to be the one who asks the unexpected question and changes the shape of the room.
For brands planning a campaign
Strong material for employer-brand, culture, and leadership content, and a way for a technical sponsor to reach an audience beyond tools coverage. Ask to verify the role descriptions before presenting them as credentials; they are self-described and not corroborated by the other posts.
Large-scale logistics automation and a stated move into manufacturing
One post closes out what it calls a chapter at Symbotic, describing years spent helping design and scale automation systems for warehouse and supply chain environments, bringing advanced robotics, AI, and real-time control into complex operations and improving reliability, speed, and flexibility at large scale.
Read more
It credits passionate engineers and operators and says the next chapter applies that experience to a new frontier in manufacturing. Read alongside the leadership post, the material shows a career centered on autonomous robotics in industry rather than on any single tool or product.
The two role-related posts are undated, so the order of the Symbotic departure and the description of leading an automation center is unclear. Ask to confirm the timing, employer and title.
For brands planning a campaign
Gives a brand the scale and setting of Cristian’s experience, which matters for briefs about warehouse or factory automation rather than only software libraries. Confirm their current position before building a pitch around it.
A weekday series structure across very different subjects
The posts share a naming pattern that turns unrelated subjects into a recognizable rhythm: Saturday:Family, Friday Ideas, Friday Projects, Wednesday Reading, Sunday Programming, and Monday Leadership.
Read more
The formats range from a build log and a project overview to a book discussion, a technical walkthrough, and a short personal essay. Long technical posts sit next to short reflection pieces, and most carry hashtags that match the series name.
A fixed slot per subject area, with technical posts carrying enough concrete detail, code-library names, and repository links to stand as reference material on their own.
For brands planning a campaign
Predictable slots make sponsorable series straightforward to plan, and a brand can attach to the one that matches its audience—for example, a programming or digital-twin sponsor on the Friday or Sunday posts rather than the leadership slot. The content formats vary, so match the sponsor to the tone of each slot.
The posts show one stated employment relationship and several working or positioning references to named companies.
Read more
Cristian M. writes that they had recently left Symbotic, where they helped design and scale warehouse automation systems.
Their open-source .NET projects wrap NVIDIA's simulation and perception software, and they name Siemens Tecnomatix, Rockwell Automation's Emulate3D, and realvirtual.io as established digital-twin tools their work is meant to complement rather than replace.
Ask directly about any sponsorship, affiliate, client, or investment relationships.
Symbotic
Employment
Cristian M. wrote that they had recently wrapped up a chapter at Symbotic, helping design and scale automation systems that bring robotics, AI, and real-time control into warehouse and supply chain operations.
Their .NET projects build on NVIDIA software: C# wrappers around NVIDIA's ovphysx physics and ovrtx rendering libraries, and LocateAnythingSharp, which connects NVIDIA's LocateAnything model to C# for local inference.
Uses a Bambu Lab X1 Carbon printer for parts in a family robot build.
Read more
They replaced the stock extruder with a CNC-machined aluminum one and swapped plastic gears for metal because the originals could not hold a consistent grip across flexible TPU and abrasive engineering filaments.
Cristian M. cites Rockwell Automation Emulate3D as a powerful factory-scale digital-twin suite that combines mechanical, electrical, controls, and robotics into one twin.
Read more
They point to it as a well-built tool that makes data difficult to move between platforms, part of the case for their own open-source C#/.NET alternative.
Cristian M. writes mostly about connecting advanced robotics, simulation, and AI capability to the C#/.NET tools engineers already use.
Read more
Their recurring weekday series covers distinct topics: Friday Projects carries project overviews and library walkthroughs, Sunday Programming covers the digital-twin runtime and simulator experiments, Wednesday Reading discusses engineering books and how their arguments apply to automation decisions, Saturday:Family shows hands-on robot building and printer maintenance, and Monday Leadership turns to career and management reflections.
Read a Friday Projects or Sunday Programming post for the technical substance, then a Wednesday Reading post for how they think about process before technology.
Longer explanations sit alongside short reflection pieces, letting readers choose practical material or leadership essays.
Cristian M. also explains industrial robotics and automation to a technical audience, including the hardware and software layers around machine tools and factories.
Read more
The posts walk through a Siemens CNC robot controlled through G-code and a digital thread that runs from design and simulation through machining and predictive maintenance, then point readers to a weekly robotics newsletter.
The Siemens posts are vendor-partnered showcases and newsletter-driven news coverage, while Cristian M. writes as the builder of open-source C#/.NET libraries and a digital-twin runtime, arguing for a neutral, open tool layer.
Writes about robotics and automation in manufacturing and logistics, including cybersecurity at the device level under IEC 62443-4-2 and the case that Canadian defence and industrial investment should build domestic production capability.
Read more
Both accounts connect factory-floor technology to buying and procurement decisions.
Cacciatore works from a manufacturing-strategy and industrial-base advisory angle, asking what buyers and country-level supply chains should demand, while Cristian M. writes from the perspective of someone implementing software and building integration libraries.
Analyses the physical-AI and robotics stack, including foundation models, simulation and physical-world data, dexterous manipulation, and where training data and deployment layers sit across China, the US, and Japan.
Read more
The pieces share Cristian M.'s interest in how simulation and real-world data feed robot capability.
Yan's lens is investment and market structure — funding, national strategies, and where value accrues — while Cristian M. focuses on hands-on engineering: library code, simulator experiments, and tool maintenance.
Treat this as a specialist technical audience, and pin down its makeup before committing budget.
Read more
Cristian M.'s LinkedIn profile had 15,921 followers on 9 October 2026.
The profile does not report followers’ location, age, gender, employer, job function, or seniority, so ask for demographic data or an audience survey covering employer type, job function, and seniority before deciding whether the following includes the .NET, controls, and integration engineers a robotics-software campaign depends on.
The dated posts show the kind of reader the content is built for.
They work through C# libraries for EtherNet/IP and ROS, wrappers around NVIDIA simulation and rendering libraries, an ONNX walking policy running inside a PhysX-based digital twin, and where to put complexity when automating a factory, alongside a leadership post about staying hands-on.
Selected examples — the digital-twin post and the .NET integration post — name specific libraries, dependencies, and limitations rather than summarising.
That depth suggests a practitioner-focused editorial approach.
Before placing spend, ask Cristian for engagement figures (reactions, comments, profile visits) on a technical post comparable in topic and depth to your campaign.
If the followers skew to practising automation, robotics, and simulation engineers, a consulting engagement announcement fits; if the audience is broader, expect reach without qualified inquiries.
None of Cristian M.'s posts describe a sponsorship product, rate card, or official partnership inquiry route.
Read more
Their published work is technical and open source: C# libraries for industrial protocols such as EtherNet/IP and for ROS (Mori.RosSharp, Mori.Ros2Sharp), wrappers around NVIDIA physics and rendering libraries, and Gemelli Studio, a digital-twin runtime and editor where FMUs, SSPs, and exported ONNX policies become wireable blocks in one graph.
Links point to GitHub repositories, not to a media kit, price list, or contact form.
There is no documented package to book, so an engagement would begin as a direct, custom conversation rather than a standard format.
A collaboration would likely focus on code integration, a reference implementation, or co-development around .NET, simulation, and robotics tooling, rather than a media placement.
Before committing budget, ask about sponsorship terms, commercial availability, pricing, disclosure practice, and the right inquiry contact.
Strong fit to explore a custom technical consulting engagement for a robotics software company that needs .NET integration with industrial automation or simulation tools.
Read more
Reasons
Cristian M. describes C# libraries for EtherNet/IP and ROS/ROS 2, wrappers around NVIDIA physics and rendering libraries, and Gemelli Studio, a digital-twin runtime and editor. This is direct evidence of work in the brief’s technical area. Ask whether the relevant projects are production-ready and support the buyer’s specific versions and systems.
A described Gemelli Studio demonstration runs a walking policy trained in MuJoCo inside PhysX without retraining or Python. The post says matching the policy’s conventions took real work, a useful signal for scoping an integration rather than promising plug-and-play compatibility.
Cristian M.’s process-improvement writing argues for understanding why work is done before choosing automation. That could help a consulting engagement assess whether the need is a software bridge, a process change, or both.
Suggested next step
Start with a paid discovery conversation after confirming availability and commercial terms. Ask for a walkthrough of the relevant repositories and demos, then define a small proof of concept around the buyer’s named protocol, ROS version, simulation engine, and deployment constraints. Agree on success criteria and ownership of any resulting code.
When to choose a specialist
Poor fit for a campaign that requires a documented, ready-to-book sponsored-post package or guaranteed broad consumer reach.
Read more
Reasons
Cristian M.’s posts do not say what sponsorship formats are available, and no rate card or official inquiry route is published there. Ask about placement options, pricing, availability, and disclosure terms before proceeding.
The posts demonstrate specialist technical subject matter, including C# integration, robotics, and simulation. They give a follower count but no audience breakdown; ask for audience data before assessing consumer reach or fit with a general-market target.
Cristian M.’s work describes projects at different stages with varying dependencies and limitations. A campaign that needs a polished, production-validated product endorsement requires technical and commercial checks before making that claim.
Alternative
If the goal is a standard paid post with confirmed audience demographics and booking terms, choose a creator or publisher that documents those details. Reconsider Cristian M. if the brief can be reframed as a custom technical collaboration and the missing terms and audience fit are confirmed.
A worked campaign example
Brief
A robotics software company wants to show how an existing .NET application could connect to a robot middleware or simulation workflow and is considering a consulting engagement.
Campaign angle
Build a small, inspectable integration demonstration: connect a specified .NET application to one selected robotics or simulation component, document what crosses the interface, and show one test that matters to the buyer. Frame the story around keeping useful engineering software in place while making a new capability accessible—not as a claim that every tool already works together.
Decision gate
Proceed only if the repository and demo review supports the target stack and the parties agree on scope and terms. The posts establish relevant work, not compatibility with a buyer’s unspecified system.
Proposed plan
Discovery: name the buyer’s target protocol or middleware, software versions, hardware or simulator, and use case. Check whether the relevant libraries and dependencies support them.
Proof of concept: agree on one bounded integration and a testable outcome, such as exchanging specified data or running a defined simulation control loop.
Public-facing output, only if separately agreed: a technical walkthrough showing the setup, observed result, limitations, and next step. Do not imply endorsement, sponsorship availability, or production readiness unless confirmed.
Before commitment: confirm commercial availability, scope, fees, disclosure terms, repository and code rights, and whether the work can be shown publicly.
Why this angle fits
This draws on Cristian M.’s stated aim of making robotics, industrial protocols, simulation, and perception capabilities accessible from .NET. The MuJoCo-to-PhysX policy example offers a concrete demonstration theme, while the post’s account of convention-matching work supports making constraints visible. The process-efficiency post also gives the project a reason to begin with the buyer’s workflow rather than a generic technology showcase.
When the buyer wants visibility with industrial automation and machine-tool audiences, a Siemens-adjacent voice could help.
Read more
Ziegler’s posts cover a Siemens digital-thread showcase for aerospace part manufacturing and a CNC robot programmed in G-code, with Siemens identified as a partner and the posts labeled as sponsored. For the same .NET integration consulting engagement, Ziegler is a better choice if the buyer prioritizes reaching engineers who already work with Siemens controls, CNC equipment, and mixed-vendor production environments—and wants sponsored or event-linked amplification of the integration story rather than code-level implementation help.
The tradeoff is that the posts are sponsor-aligned and market-facing.
They show Siemens software and CNC robot capabilities, but not .NET libraries, ROS integration, open-source software work, or a consulting practice.
A buyer seeking someone to design, build, and test a .NET-to-robot or .NET-to-simulation bridge would still need a technical engineer.
Ziegler can help frame where the integration fits in industrial production, but the posts don’t show implementation work.
When the .NET integration project sits within a connected-factory plan that networks robot controllers and automation equipment, and cybersecurity certification or Canadian manufacturing supply-chain context matters.
Read more
Cacciatore’s posts focus on IEC 62443-4-2 device-level security for robot controllers and Canadian defence spending as a manufacturing modernization opportunity. For the same consulting engagement, Cacciatore is a better choice if the buyer needs to reach Canadian manufacturers, address OT security in the purchasing conversation, or position the integration around secure, traceable production rather than software bridging alone.
The tradeoff is that Cacciatore’s material is standards and market commentary, not .NET or ROS implementation.
A buyer seeking working protocol libraries, simulation wrappers, or a tested software bridge would need to pair Cacciatore’s industry framing with an engineering consultant.
Ask for evidence of broader reach, audience composition, and commercial availability if those affect the buying decision.
When the buyer needs an investment or market-entry lens on physical AI and industrial automation rather than hands-on .NET integration.
Read more
Yan’s posts map funded embodied-AI companies in China, propose a physical-AI data flywheel for Japan, and trace AI-driven demand to industrial suppliers such as Generac and Modine. For the same consulting engagement, Yan is a better choice if the buyer wants to understand where capital and infrastructure demand are moving, frame a fundraising or partnership narrative, or identify adjacent industrial companies that may need integration work.
The tradeoff is that Yan’s analysis targets venture and strategy audiences, not software engineering, .NET development, or robotics integration consulting. A buyer seeking an implementation partner would need technical due diligence and a separate engineer; Yan’s value is in market thesis and deal context, not code or protocol work.
Cristian M.'s seven LinkedIn posts cover project writeups on C#/.NET libraries for EtherNet/IP, ROS and ROS 2, NVIDIA physics and rendering wrappers, and local perception inference; a digital-twin post about running a MuJoCo-trained walking policy in PhysX as a block in a signal graph; a reading note on Brian Potter's The Origins of Efficiency; commentary on humanoids and factory flexibility; a 3D-printed robot and printer-maintenance build log; a leadership essay; and a career-transition note after Symbotic.
The posts carry no publication dates, so they are grouped by argument and format rather than ordered in time, and the seven posts are a sample of the account, not a complete history.
Posts by Lukas M.
Ziegler, Anthony Cacciatore, and Joe Yan serve as comparators; each is a sample of that account, not a full history.
Cristian M.'s posts do not include sponsorship formats, pricing, audience breakdown, or an official inquiry route, so those points are left open rather than inferred.