Profile_bird

Hey there! pgfarley is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What's happening? Join today to start receiving pgfarley's tweets.

Already using Twitter
from your phone? Click here.

pgfarley

  1. Sometimes a colleague or client will complain of thirst as they run, fast as they can, towards a cliff. Fetching them water is a cop out.
  2. Mike DeCleene: Your main job at stand-up is to listen. If you give a CYA report and tune out, of course you will find it to be low value.
  3. It's never a good idea to DRY your code with a blowtorch
  4. The point of bespoke SW is that it's specific to a firm. Buy package SW if you can, but if you can't, don't build it as if it's for sale.
  5. YAGNI isn't "you're always wrong". It's "A few incorrect speculations can be costly. Many correct speculations tend to save just a bit."
  6. Ever notice that programmers and GoF patterns are a little like Pygmalion and Galatea?
  7. Not every test worth writing is worth keeping
  8. With re: to performance issue debugging, hunches seem mostly to be a false friend, out to screw me. Evidence, now there's my real pal.
  9. Programmers program. Supporting production will intervene. If programming isn't what most of the team does all day your project is broken.
  10. If you spend more than 60 min a week, configuring, copying, refreshing data, or just plain waiting, your project is broken.
  11. shane harvie says: "generally... If you aren't using the class polymorphically today, don't write an interface today." damn straight.
  12. When the little index card TODO list I carry around with me starts to feel too precious, it means I'm irresponsibly hoarding responsibility.
  13. Seems like SW would be a lot better if we paid more hypothetical runtime costs and fewer real design time costs.
  14. post-mature optimization...
  15. I'm now a twit.