The quantity of immobilized code due to unnecessary complexity built up in name of false perfomance is enormous. Those proclaming performance trumps architecture and clean code are absolutely wrong. They're now probably building the next (may be fast) immobile legacy code
A team that has created an exhaustive suite of tests to reduce number of delivered bugs and now they're thinking about deactivating tests because are failing due to structural or unrelated changes on the production code has just unveiled its new bottleneck: lack of design
Planilandia es un texto que ayuda a entender y explicar los conceptos de múltiples dimensiones.
El narrador llega a entender el concepto de dimensión tres cuando recibe la visita de una esfera tridimensional que atraviesa su mundo.
https://t.co/P8NIQskf8M
After enjoying the testing workshop of @XaviADev where a lot of techniques were shown, I have the challenge of thinking about them and try to apply some in the embedded world! #embedded#testing#QA
Some of us agree on this sentence:
"The only way to go fast is to go well"
I have been realizing that it seems to have this addendum corollary:
"The only way to go well is by hiring correctly"
If we treat software as liability, then every single piece of it must have a really good reason to exist: provide an external noticeable and valuable behavior. Being so, which are the reasons for accepting even a single line of code without coverage? 🤔
From Code Complete @stevemconstrux: "Complicated expressions make for code that has to be figured out rather than read".
Great quote that encourages us to write intent-revealing code. Reminds me of a famous quote from the Refactoring book @martinfowler