To Blog or Not to Blog...
Mark Platte Born in January, 1984.I currently work as an IT architect in a hospital environment, with a career shaped by hands-on experience in application development, storage engineering, and infrastructure design. My roots are in software, but over time I moved deeper into system architecture, working closely with storage platforms, virtualization, and security especially in regulated and research-intensive environments. I have a strong focus on building stable, secure, and manageable IT solutions, particularly in complex environments where clinical systems, research data, and compliance requirements intersect. I’m especially experienced in enterprise storage design, backup strategies, and performance tuning, often acting as the bridge between engineering teams and long-term architectural planning. I enjoy solving difficult problems and still believe most issues in IT can be fixed with enough determination, focus, and sometimes budget. It’s that drive to find solutions that keeps me motivated.
To Blog or Not to Blog...
For the longest time, I wasn’t really into the idea of blogging about my work. Not because I didn’t have thoughts ,trust me, I have plenty , but because I often felt that what I had to share wasn’t all that groundbreaking. Scripts I wrote felt too specific. Ideas I had seemed too obvious. And let’s be honest, in a world already overflowing with content, it’s easy to wonder whether your own voice actually adds anything of value.
But recently I started to look at it differently.
Maybe it’s not about being first or having the smartest take. Maybe it’s just about sharing something that might help someone else. A script that saves time. A design decision that gets someone thinking. Or just a bit of frustration that makes someone feel less alone. Being honest about your own journey, especially the messy parts, can sometimes be more valuable than pretending to have it all figured out.
This blog isn’t here to show off polished expertise. It’s a place where I can write down things I’ve learned, mistakes I’ve made, and ideas I keep circling back to. Topics from the architect’s point of view, mixed with bits of code and hands-on fixes from my developer roots. If someone else finds it useful or relatable, that’s a win.
With a few new projects taking shape at work, and some unexpected issues popping up like what led to the delta disk post: deltadisk.hashnode.dev/the-hidden-delta-dis.. I felt that old spark again. While writing that script, it hit me: this solution didn’t exist anywhere. That got me thinking about all the tools and ideas I’ve built over the years that we still use today. Maybe they were never flashy, but they held up. Maybe they’ve been good enough all along.
So here I am, finally writing. Not to preach or pretend to have answers, but to share what I can, when I can. And if it helps you avoid a rabbit hole or rethink something, even better.
Feel free to leave a comment or share your own take. I’m always curious how others see it too.
For now I hope you’ll enjoy you time here.
Enjoy,
Mark
Note: This blog is the central place where I collect all my work. Some posts might also be shared in other communities if they’re a good fit, but this is where everything comes together. I have no idea how often I’ll post or if I’ll keep going. No schedule, no promises just whenever something feels worth sharing.
