Blog
  • devcrisis
  • 🔮Software atoms
    • Validating code Architecture with dependency cruiser
    • Actionable ways to use ChatGPT
    • Most courses aren't worth it
    • SQLite is❤️
    • Stabilizing Tests without fixing them
    • Interviews should copy Advent of Code
    • Rust is nice
    • Agile fatigue is rising
    • Documentation is needed after all
    • The Direction of the JS ecosystem is good
    • Zero configuration == <3
    • Make small pull requests
    • Good practices fade out
    • Rushing !== unmaintainable
    • Commit message readability
    • Universal Practices
    • More functions == good
    • Mocking Private Functionality
    • Lines of code != feature count
    • Different Software - Different Quality
    • junior2mid
    • Book alternatives
    • Courses
    • Type Driven Development
    • Latest and Greatest
    • Real Developers
    • 10x Developer
    • Books for beginners 1
    • Parkinson's Law
    • nest-cli architecture is nice
    • Incremental Feature Delivery
    • Self Healing Software
      • Typed Configuration
  • 💡Memos
    • 2022 Holiday code report
    • Complexity
    • Software Development Fundamentals
  • 🧱foundation
    • Junior2Mid
    • Books and resources for new developers
    • 🏔️Now
Powered by GitBook
On this page
  1. Software atoms

Different Software - Different Quality

Different software requires different quality.

Hobby projects, experiments and exploration projects simply need to work. Everything else is a plus.

When it comes to your professional work it may be hard to find the balance.

You are operating on company time. Your goal should be to bring as much business value as possible.

Should you spend the same amount of time refining and polishing your developer or internal tooling as you do the core of the solution ?

Many people may say yes: "If you don't trust your tools why have them in the first place" Yes. The code must work. It must be consistent. But it must not be perfect.

The point is that you won't add business value if your tools are ultra well designed or optimized. It will cost you more time. Time spent polishing tools can be used to bring more value to your business.

You should design just enough so that the tools are usable and easy to replace (if integrated).

Use your time wisely - there are always tests to write, techdebt to pay and documentation to write.

PreviousLines of code != feature countNextjunior2mid

Last updated 2 years ago

🔮