※Permission was granted by the artist to upload their works
YAGNI | にとり
seen from United States
seen from United Kingdom

seen from Malaysia
seen from Mexico

seen from Malaysia
seen from United Kingdom

seen from Ireland

seen from Malaysia
seen from Mexico
seen from Türkiye
seen from Aruba
seen from Canada

seen from Spain

seen from United States

seen from United Kingdom

seen from United States

seen from United States

seen from United States
seen from United States
seen from China
※Permission was granted by the artist to upload their works
YAGNI | にとり
"The mistake is treating both kinds of code the same: Glue code gets over-engineered. Core domain logic stays hidden in long services or handlers. Good architecture starts with noticing the difference."
"While that knowledge might keep me from making a terrible mistake, more frequently it leads me to create attributes, variables, and methods that I don't need yet, but that I KNOW I'll need."
"It's a solution in desperate need of a problem, and 8K looked to be a good candidate."
"If user stories are the units of work, each story represents a tiny iteration."
"Who’s McKinsey? **It’s a consulting firm.** Are they funny? **No.** Then I don’t need them."
I recently overheard two software engineers discussing a feature they were developing. They had two options: developing the feature specifically for the task they had at hand, or do something more generic that could fit future possible use cases. One engineer claimed that they only need a very specific implementation a
Regular reminder that YAGNI is not just about the effort to write the feature ...
Engineering Architecture - Jakub Kubryński