# Make it

2018-07-08

> I always interpreted this phrase in terms of business needs, not coding standards.

> 1. Meet the minimum requirements for the business to call project a success. (Make it work.)

> 2. Add bells and whistles to make the program less prone to error and more feature rich. (Make it right.)

> 3. Find and eliminate waste in the process. Some assumptions from the start will have been incorrect. Remove unnecessary business logic. Included in this step is to improve code for better performance. (Make it fast.)

> Make It Work Make It Right Make It Fast (cache)

0. Understand the ethical implications of your work and your responsibilities acting for a future you believe in. (Make it for good.)

Other articles in English: On caching links, Bushcraft retrospective, Into the Raft, Into the Bugs, Meritocracy crisis, The Seller, the Teacher and the Wise, Into the Good, Into the Mice, Into the Camp, Into the Wind, Into the Snow, Into the Cold, Async Python Frameworks, Distributed teams, Into the Wild, Without JavaScript, Inclusive Python, Micro-cultures and governance, Resilient Web and Tools, Bitcoin and energy, Team building, Inclusive developer, Cultural Intimacy, Tools and teams, Senior developer, Slow Data, Inclusive communities, Delivery and value(s), Collaboration debt, Communities and leadership, Specifications and APIs. Oh, and most of the 2018 thoughts.