Suggestions
Matt Gowie
CEO/CTO @ Masterpoint | Get control of your Infrastructure as Code workflows
Matt Gowie is the CEO and CTO of Masterpoint, a company focused on Infrastructure as Code (IaC) consulting.15 He is known for being a full-stack engineer with the ability to deliver quickly and solve complex problems across the entire technology stack.1
Professional Background
Masterpoint, under Matt's leadership, specializes in helping clients automate, migrate, and manage their infrastructure.5 The company aims to assist organizations in gaining control of their Infrastructure as Code workflows.2
Skills and Expertise
Matt is recognized for his:
- Full-stack engineering capabilities
- Problem-solving skills across the entire technology stack
- Leadership in Infrastructure as Code (IaC) solutions
Online Presence
Matt maintains an active presence on professional networking platforms:
- His LinkedIn username is indeed "gowiem"123
- He had accounts on Twitter for both personal and business use, but deactivated them in November 20233
- He has a GitHub profile where he shares his work and contributions5
Professional Interests
Matt shows a keen interest in:
- Open-source contributions, fostering such initiatives at Masterpoint2
- Cloud computing and infrastructure automation
- Sharing insights about technology trends, as evidenced by his posts on platforms like LinkedIn4
Matt Gowie appears to be a thought leader in the IaC space, regularly sharing his experiences and insights about various technologies and approaches in the field of infrastructure management and automation.
Highlights
One of our most read articles: "Crossplane: Why it Didn't Work For Us". If you haven't read this one, check it out!
https://lnkd.in/gDnytYdV
#terraform #opentofu #infrastructure #infrastructureascode #iac #platformengineering #platforms
A code smell in infrastructure as code: copying code or resources across directories as a means by which to elevate changes.
At Masterpoint, we're big fans of workspaces. But we also understand that not everyone is and that they like directory structures and managing their IaC through changes to their file system. That’s fine and valid. But that’s not fine if you’re just copying and pasting large sections of code to elevate those changes.
When practicing the directory structure way of managing infra, it is absolutely critical that you are heavily using local modules as a means by which to encapsulate the business logic, config, and resulting resources that you’re trying to deliver. Without that encapsulation, I believe that you are in a waiting game until one of the engineers on the team makes a (very justifiable) mistake in their copy pasta operations.
What do you think? Any good stories of poor copy/pasta operations? Let me know in the comments below!
#terraform #opentofu #infrastructure #infrastructureascode #iac #platformengineering #platforms
