We care about our customers and want to ensure we keep meeting their needs even as those needs change. Engineers were building performance into our work naturally, but we knew we needed to do a lot more to coordinate our efforts and keep up with our increasing demand.
Upgrading Rails can often be difficult and risky! I'll be walking through the process my team took to safely upgrade to Rails 7.0. While this is going to be relatively Rails and Ruby specific, I hope you can take away something for software you are upgrading.
Many engineers, including myself, wonder what the end-to-end ownership of a feature looks like for a software company. I’ve had the opportunity to work on several projects with end-to-end ownership, and I wanted to share my journey
Many security teams operate like QA teams of yore. Testing was mostly absorbed into standard engineering practice - security is next.
How does a payroll engineering organization give the green light for a basal change to their tax system when the consequences reach many domains, features, and teams? With a decision matrix we were able to break down our options, clearly compare solutions, and find a path forward.
As someone who was recently promoted to senior engineer, this journey is still fresh in my mind. Here are some ways that senior engineers have helped during my career path from junior to senior engineer.
In part 1, we covered the goals and benefits of isolating the most sensitive customer data to a separate service, that we call HAPII - The Hardened PII store. Briefly, the isolation of the data, explicit retrieval API,
The ultimate goal of a growth team is to enable, activate, and retain paying customers on the platform who like the functionality so much, they’re willing to refer others to it—which creates a flywheel of satisfied customers and boosts revenue along the way.
