lean thinking
Of course we all claim to hate complexity, but it’s actually just complexity added by other people that we hate — our own bugbears are always exempted, and for things we understand we quickly become unable to even see there is a potential problem for other people.
Luke Plant • No one actually wants simplicity
Nossa relação com a complexidade: só não gostamos quando é a complexidade adicionada por outras pessoas. Me lembrei da frase de Sartre, “o inferno são os outros”.
A lot of developers want simplicity in the same way that a lot of clients claim they want a fast website. You respond “OK, so we can remove some of these 17 Javascript trackers and other bloat that’s making your website horribly slow?” – no, apparently those are all critical business functionality.
In other words, they prioritise everything over spe... See more
In other words, they prioritise everything over spe... See more
Luke Plant • No one actually wants simplicity
Is simplicity your highest or lowest priority?
I think a good test of whether you truly love simplicity is whether you are able to remove things you have added, especially code you’ve written, even when it is still providing value, because you realise it is not providing enough value.
Another test is what you are tempted to do when a problem arises with some of the complexity you’ve added. Is yo... See more
Another test is what you are tempted to do when a problem arises with some of the complexity you’ve added. Is yo... See more
Luke Plant • No one actually wants simplicity
I think the legendary Bob Ross said it best:
He was talking about layering colors while painting, which in certainly more permanent than most software, but it still works wonderfully to guide us as developers. Tackle each task as you go, don’t increase your own overhead unless it... See more
Just remember that you can always add more, but you can’t take it away.
He was talking about layering colors while painting, which in certainly more permanent than most software, but it still works wonderfully to guide us as developers. Tackle each task as you go, don’t increase your own overhead unless it... See more
Deliver the Bare Minimum
Jim is an engineer and works for “THE COMPANY”. A client has requested a JSON file that contains all recent, Canadian buyers of their “PRODUCT ABC”. Jim can handle this task no problem, but thinks it is a little short-sighted. Jim thinks to himself, “What if they want to check buyers from the US? What if they want a shorter or longer time frame?”. ... See more
Deliver the Bare Minimum
Example of overengineering, a phenomenom which assolates IT development and impairs keeping things simple
An issue I tend to see in my travels through the world of software engineering is over-engineering. Shocking, I know. I’m not the first developer to point this out, nor will I be the last.
Deliver the Bare Minimum
Deliver the Bare Minimum
btxx.org
Excellent text on the need to keep things simple when talking about software development (although also applicable in other areas)
According to the “Just in Time” principle in the lean approach, these questions should be answered in order and should be defined on separate documents. First, the business requirements and user requirements should be defined and listed on business-case or vision and scope documents; then functional requirements, nonfunctional requirements, and bus
... See more