The best practice is not always the best?

Shaun.t
1 min readJun 22, 2022

In software development, there are always best practices for this and that, for instance, the best practices for:

  1. PM tool — Excel is the best & flexible tool for progress tracking.
  2. Workflow — back then, the SDLC is the best.
  3. Directory structure — HTML, Js, and CSS in a separate folder.

As time goes by, most of the best practices become irrelevant when someone found better ways of doing things. While some are still stuck with the “best practice”

  1. PM tool — Kanban board, Jira ticketing
  2. Workflow — Scrum, Agile, Water+Agile, or whatever works best for a single project/product.
  3. Directory structure — 😊

Real-life example

If I do styled-components in 2015/16, surely will backfire by the reviewer, ’cause it does not comply with the conventions. Maybe I’m just doing it under the “wrong” medium.

Be water, my friend

Adopt an elastic mind. Nothing is the same as always. If there’s a better way, just learn it. That’s why best practice is not always the best. Dare to challenge the best practice and try to keep learning & improving.

Conclusion

Sum up to this, keep learning is the best practice I have here. For everything else, just

--

--