This content originally appeared on Go Make Things and was authored by Go Make Things
In response to my article on under-engineering, reader Caleb Stauffer responded (shared with permission)…
This is the same thing we talk about with dev experience: fewer building and tooling is nearly always better, easier to implement, easier to maintain, less likely to break, and less confusing to future developers.
Absolutely!
That doesn’t mean “use no tools at all,” of course. The right mix of tools can be incredibly helpful at automating complex, repetitive tasks.
I think we have a tendency as an industry, though, to approach development with an “if some tools are good, more tools are better” mindset that doesn’t actually play out that way in reality. Typically, more tools means more work to get started, more things to break, and so on.
It reminds me of a quote often attributed to Einstein…
Everything should be made as simple as possible, but not simpler.
Level-up your team’s core JavaScript skills. I offer project-based courses and workshops designed to fit around your team's schedule. It's perfect for remote and distributed teams.
This content originally appeared on Go Make Things and was authored by Go Make Things
Go Make Things | Sciencx (2023-02-10T14:30:00+00:00) As simple as possible (but no simpler). Retrieved from https://www.scien.cx/2023/02/10/as-simple-as-possible-but-no-simpler/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.