Part 3 of 3: Operational Maturity In Parts 1 and 2, we explored Engineering Rigor and Architectural Integrity—the pillars of writing high-quality code and designing systems that last. But even the cleanest code and best…
Part 2 of 3: Architectural Integrity In Part 1, we explored Engineering Rigor—the discipline of writing clean, secure, compliant, and well-tested code. But great software isn’t just well-formed lines of code; it’s code that fits…
Part 1 of 3: Introduction and Engineering Rigor Over the last twenty years, nearly everything about how we build software at BTI360 has evolved—languages, frameworks, tools, platforms, and even the way we work. What hasn’t…
Next.js is a React framework that allows developers to better organize code and files in order to achieve single-page app like behavior, which still being able to access a number of server-only features. One of…
At BTI360, we recently spent a full day immersed in a Domain-Driven Design (DDD) workshop led by Paul Rayner. It was an intense, hands-on experience focused on understanding how to design software that reflects a…
In my last post, I discussed BTI360’s Clean Code 101 course, the importance of Clean Code, and three of my main takeaways from revisiting Clean Code as a Senior Engineer. Today I will conclude with…
BTI360 requires all new engineering hires to attend a six-session course called Clean Code 101, inspired in part by Robert “Uncle Bob” Martin’s book Clean Code. Created and taught by BTI360 engineers, the classes involve…
Close Form
Then stay up-to-date with our latest posts delivered right to your inbox.
Whether we’re honing our craft, hanging out with our team, or volunteering in the community, we invite you to keep tabs on us.