Other Driven Developments

Mental models within an industry, company, or even a person, change constantly. As methodologies mature, we see the long term effects our choices have wrought and can adjust accordingly. As a team or company grows, methodologies that worked well for five people may not work as well for 40 people. If all employees could keep an entire app in their head, we’d need fewer rules and checks and balances on our development, but that is not the case. As a result, we summarize things we notice have been implicit in our work.

Shopify logo
Shopify
•
John DeWyze
•24 min read•intermediate•
--
•View Original
JSONMVCRailsRubySingle Responsibility

Overview

The article explores various development methodologies, including Grep Driven Development, Copy/Paste Driven Development, Ego Driven Development, and Stickler Driven Development. It emphasizes the importance of adapting these models to improve team dynamics, code maintainability, and overall software development practices.

What You'll Learn

1

How to improve code searchability through better naming conventions

2

Why consistency in naming can enhance code maintainability

3

When to apply Copy/Paste Driven Development effectively

4

How to foster a culture of psychological safety within teams

Key Questions Answered

What is Grep Driven Development and how does it improve code quality?
Grep Driven Development emphasizes the importance of using expressive variable names to enhance searchability and maintainability of code. By ensuring that variable names are clear and consistent, developers can easily locate and refactor code, ultimately leading to healthier codebases.
How can Copy/Paste Driven Development be beneficial?
Copy/Paste Driven Development allows developers to quickly replicate functionality, which can be efficient in time-sensitive situations. It encourages leveraging existing code rather than reinventing the wheel, thus reducing development time while maintaining productivity.
What are the risks of Stickler Driven Development?
Stickler Driven Development involves rigidly following rules without understanding their context, which can lead to poor decision-making. It is crucial to recognize when rules should be adapted or broken to better serve the project's needs and foster innovative solutions.
Why is psychological safety important in software development teams?
Psychological safety allows team members to express ideas and take risks without fear of negative consequences. This environment fosters collaboration, encourages learning from failures, and ultimately leads to more innovative and effective solutions in software development.

Key Actionable Insights

1
Adopt Grep Driven Development by ensuring all variable names are descriptive and consistent.
This practice not only improves code readability but also enhances searchability, making it easier for developers to locate and refactor code in the future.
2
Encourage a culture of psychological safety within your team.
By fostering an environment where team members feel safe to share ideas and take risks, you can enhance collaboration and innovation, leading to better project outcomes.
3
Utilize Copy/Paste Driven Development judiciously to save time.
Recognize that while duplication can be seen as a negative, it can also be a strategic tool for rapid development when used appropriately.
4
Be mindful of the rules you follow in Stickler Driven Development.
Understanding the context behind rules allows for better decision-making and can lead to more effective coding practices.

Common Pitfalls

1
Relying too heavily on rules without understanding their context can lead to poor coding practices.
This often occurs when developers follow guidelines blindly, missing opportunities for innovation and adaptation that could better serve the project.