Everyone knows that when you have similar code repeated several times that you should consolidate into a loop or function, but changing discrete variables into arrays and adding loops can have a small readability cost, so sometimes it can feel like a debatable choice for something small just repeated two or three times.
Usually, optimizing for readability is positive, but a requirement to keep two separate things aligned through future changes is an “invisible constraint” that is quite likely to cause problems eventually.
Many years ago, I would casually copy-paste-paste-paste-modify 4D vector statements, but now I almost never even do two related statements like that.
The hazard is when you combine two things that are close, but not exactly the same, and the strain induces complexity.
Very pleased to share the first public work of the new @McKinsey Data Visualization Lab! It's a very non-traditional viz of a super complicated and highly bespoke data set outlining funding opportunities for states from the infrastructure bill /🧵
Enough with the renders! Let us introduce: The #Helix engine 🔥
Ready for some more information on this marvellous piece of #engineering and the chance to win unique polaroid pics of this beauty? ⬇️ (1/6)
#YurisNight
Altmaier: „ausser NRW gibt es keinen anderen Landesverband, der will, dass AL Kanzlerkandidat wird. „Viele werden enttäuscht sein, wenn Bundesvorstand genau das Gegenteil beschließt, was ihnen am Herzen liegt.“