John RegehrFeb 27
today in "draw the rest of the fucking owl"
Show threadSnoopJFeb 27

@regehr "find the seams" is much harder advice to execute on when dealing with code that may not even have seams because it was not constructed with any intent but rather is a gooey blob of gunk secreted from a statistics engine

glhf needleworker, you shit your bed now you can lie in it

Show threadderptronFeb 27

@SnoopJ @regehr

The more shit changes, the more it stays the same.

https://archive.org/details/working-effectively-with-legacy-code

Working effectively with legacy code : Feathers, Michael C : Free Download, Borrow, and Streaming : Internet Archive

Code without tests is bad code. It doesn’t matter how well written it is; it doesn’t mat- ter how pretty or object-oriented or well-encapsulated it is....

Internet Archive
Show threadSpagbol
@crazyeddie @SnoopJ @regehr
Thanks for sharing that book! I have been looking for these type of ressources!
Feb 27 at 6:46pmMastodon for Android
Show threadSnoopJFeb 27
@Spagbol14 @crazyeddie @regehr it's an awesome book 🙌
Show threadderptronFeb 28
@Spagbol14 @SnoopJ @regehr It's an important one to have or at least be aware of some of the content. You could add "Refactoring" to the list--maybe its workbook too but I didn't end up ever doing any of the exercises it contains.