ASIL-D Software Architect (Safety & Cyber) | AUTOSAR BSW & MPU/Timing Fire-Fights | Founder @ Thinking in Code
I had the opportunity to test GLIWA T1 4.0 recently. Thanks to Cristian Garzón and Germano Brunacci for the oportunity. GLIWA T1 4.0 is not “new.” It’s just less friction. And that matters. And honestly: it’s hard to improve an already great tool without just adding noise. This feels like the opposite, same fundamentals, fewer steps, faster loops. What stood out in my quick test: - Overall it feels faster (less waiting, quicker iterations) - A new page that puts the key information in one place, no more tab switching between cont / scope / … just to keep context - A very practical one: T1.flex across all functions at once, no more manual work selecting each function, starting measurements, repeating the same setup cycle Why this matters in real projects: timing/resource closure isn’t blocked by “lack of data”, it’s blocked by workflow friction. Reducing manual steps increases cadence and makes it easier to keep integration disciplined. What’s your biggest time sink today in timing analysis: setup/selection, running measurements, or turning results into decisions?
