[{"_1":2,"_42":-5,"_43":-5},"loaderData",{"_3":4,"_10":11,"_40":-5,"_41":-5},"root",{"_5":-5,"_6":-5,"_7":-5,"_8":9},"user","shoppingCartId","toast","locale","en","routes/_store+/_readers+/email_author.$slug/route",{"_12":13,"_39":-5},"book",{"_14":15,"_16":17,"_18":19,"_20":21,"_22":23,"_24":25},"id","Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvNjc5NzA","title","The Other Half of Coding","state","published","contactAuthorMethod","email","aboutText","

It doesn't have to be this hard.

Ever wonder why software systems seem to decay over time? Even when teams follow the best practices — TDD, Design Patterns, DDD, Behavior-Driven Development, and so on — it seems like the system always gets harder to work with.

It's not that the best practices don't work. It's just that they only address half the problem. All of these disciplines make the promise \"If you do this today, things will be easier tomorrow\"... but none of them actually give much advice about what to do when tomorrow comes (as it does every morning).

That's the other half of coding: not what you code, but how you code it.

The Other Half of Coding will show you what’s been missing all along — why software decays, how to stop it, and how to complete your skill set so you can write code that stands the test of time.

","authors",[26],{"_14":27,"_28":29,"_5":30},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci83MjI3NA","name","Max Guernsey, III",{"_31":32},"avatar",{"_33":34,"_35":36,"_37":38},"url","https://d308did4coypzi.cloudfront.net/avatars/171891/medium/Picture_016.jpg?1752789467","styleName","medium","exists",true,"currentUser","routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Email the author