by shigemk2

当面は技術的なことしか書かない

2013-05-07から1日間の記事一覧

97 Things Every Programmer Should Know 63 Own (and Refactor) the Build

IT IS NOT UNCOMMON for teams that are otherwise highly disciplined about coding practices to neglect build scripts, either out of a belief that they are merely an unimportant detail or from a fear that they are complex and need to be tende…

97 Things Every Programmer Should Know 62 Only the Code Tells the Truth

THE ULTIMATE SEMANTICS OF A PROGRAM is given by the running code. With this in mind, ask yourself how clearly your code is telling you or any other programmer what it is doing. Treat your code like any other composition, such as a poem, an…

97 Things Every Programmer Should Know 61 One Binary

The rule is simple: Build a single binary that you can identify and promote through all the stages in the release pipeline. there are exceptions: you might be building for targets that have significantly different resource constraints, but…

97 Things Every Programmer Should Know 60 News of the Weird: Testers Are Your Friends

that's why I say testers are your friends. You may think the testers make you look bad by reporting trivial issues. But when customers are thrilled because they weren't bothered by all those "little things" that QC made you fix, then you l…

97 Things Every Programmer Should Know 59 Missing Opportunities for Polymorphism

polymorphism isn't simply about alternate implementations. Used carefully, polymorphism creates tiny localized execution contexts that let us work without the need for verbose if-then-else blocks. While there are cases where it's much more…

97 Things Every Programmer Should Know 57 Message Passing Leads to Better Scalability in Parallel Systems

PROGRAMMERS ARE TAUGHT from the very outset of their study of computing that concurrency—and especially parallelism, a special subset of concurrency—is hard, that only the very best can ever hope to get it right, and even they get it wrong…