Conversation

GitHub
@github
When you're faced with a BIG engineering effort, how do you approach development? Before we dove into code for contributing Scalar to Git, we solidified four 4️⃣ development principles that we used to guide our decisions. 🧵
Image
2
138
GitHub
@github
1️⃣ Code speaks volumes. An architectural design on paper isn't enough for solving problems at scale. Before committing to a decision, we would quickly build a prototype and measure its performance. 📈 2/6
1
20
GitHub
@github
2️⃣ Incremental changes > wholesale rewrites. We focused on small changes that solved an immediate need and optimized for reducing our technical debt and creating a better architecture. 3/6
1
23
GitHub
@github
3️⃣ Making any kind of software change adds risk to a project. That risk is mitigated when we have a large set of battle-hardened tests. With a robust test suite available, we were able to make significant changes to our architecture with confidence.
1
18
GitHub
@github
4️⃣ No surprises here--we value working in the open. Scalar was an open source project from day one, and was never intended to be a project only for internal use. So now we have a history of public code changes to talk about! 5/6
1
25