Vlad Mihalcea’s Post

Software choices are starting to matter as much as implant systems. See why in our latest short blog 👉 https://lnkd.in/gKFrZjwY

Wow! We are entering a period of significant transition where the role of static documentation is changing, though it is unlikely to become completely obsolete. The future of software documentation is shifting from a static "book" format to a "dynamic layer" that lives within the product and evolves in real-time with the codebase. https://lnkd.in/grKyeqk4

Software is visible. Systems are not. But systems determine speed, quality, and reliability. If the tool is doing “everything,” your system probably isn’t doing enough. More context here: https://lnkd.in/grUUKDHM

Software issues come in all shapes and sizes 🫟 Here's the story about how Skimmer, the leading pool management software, cleaned up their issues by consolidating on Sentry — cutting issue resolution from days to minutes while growing 50% YoY https://lnkd.in/gizhu3hp

Day 66 : Can test metrics guarantee software quality? Answer: No. Test metrics support decision-making, but they do not guarantee quality. They must be combined with skilled testing and good processes

The blueprint for software-native organizations: 5 principles that form the operating system.From constant experimentation to real-time adaptive systems���this is how you build organizations that adapt at software speed. Episode 5, the series grand-finale 👇 https://lnkd.in/dHb9Nz7u

DPI is a software execution governance research model focused on defining and enforcing allowed system actions at runtime through declared rules.

The blueprint for software-native organizations: 5 principles that form the operating system.From constant experimentation to real-time adaptive systems—this is how you build organizations that adapt at software speed. Episode 5, the series grand-finale 👇 https://lnkd.in/d6Etke92

GWM is a standalone software package implementing "A greedy algorithm for wavelet-based time domain response spectrum matching" (Nie, Graizer, and Seber, 2023) https://lnkd.in/gehBAYsi

Can you please remove this field? Happy to, but let’s first check what it’s really connected to. Because removing a field sounds simple… But in real life? It might be: Used in 4 Flows Part of a validation rule Visible in 3 record types Referenced in reports Synced with an external system So when I get that request, I don’t ask just "Where is it used?" I ask: 🧠 "Where do people think it’s used and where is it actually used?" That’s how you avoid turning "quick cleanup" into a broken deployment.