✳flâneur — a map of the web's best reading

Goodbye, Clean Code — overreacted

overreacted.io · 1,464 words · saved by 1 readers

My colleague has just checked in the code that they’ve been writing all week. We were working on a graphics editor canvas, and they implemented the ability to resize shapes like rectangles and ovals by dragging small handles at their edges. The code worked. But it was repetitive. Each shape (such as a rectangle or an oval) had a different set of handles, and dragging each handle in different directions affected the shape’s position and size in a different way. If the user held Shift, we’d also need to preserve proportions while resizing. There was a bunch of math. The code looked something like this: That repetitive math was really bothering me. It wasn’t clean. Most of the repetition was between similar directions. For example, Oval.resizeLeft() had similarities with Header.resizeLeft(). This was because they both dealt with dragging the handle on the left side. The other similarity was between the methods for the same shape. For example, Oval.resizeLeft() had similarities with the ot

Goodbye, Clean Code January 11, 2020 Pay what you like It was a late evening. My colleague has just checked in the code that they’ve been writing all week. We were working on a graphics editor canvas, and they implemented the ability to resize shapes like rectangles and ovals by dragging small handles at their edges. The code worked. But it was repetitive. Each shape (such as a rectangle or an oval) had a different set of handles, and dragging each handle in different directions affected the shape’s position and size in a different way. If the user held Shift, we’d also need to preserve propor

Explore this link on the map →

related reading