Five for Friday – August 3, 2018

Time again to share a few things I found interesting this week.

  • I’ve been reading Bad Blood (currently about 30% of the way through). So far, it’s a pretty damning investigative review of Theranos, but I’m still waiting for the plot twist :}. Wikipedia tells me that Jennifer Lawrence will star in the film adaptation.
  • Steve Denning is at it again with this article on Agile Is Not Just Another Management Fad.
  • A wonderful article on “Delivery Teams” from Janet Gregory.
  • This (yet another) article on the failure of open plan offices is making the rounds. Buried in the end of the article is this quote:

    “And probably least bad is small team rooms of fewer than ten people, preferably fewer than six. I’ve sat together with really small teams before and that’s been OK. Some people who don’t like the open office at all might even still enjoy this configuration.”

    This setup (a “team room”) has been, in my experience the hands down winner of the most productive work environment I’ve ever worked in – and I hate that it’s lumped into the valid arguments that go against barnyard style work seating.
  • Finally, a nice article on critical thinking and problem solving that I’ll probably re-read and refer to frequently.

Similar Posts

  • Mobile Application Quality

    I forgot to mention this before, but on Thursday, Jason Arbon from applause and uTest will be giving a practically free ($99) course on mobile application quality. Jason is a great teacher, and really knows his stuff in this area. More information at the SASQAG web site (scroll down a bit on the home page)

  • PBKAC?

    Yesterday, I read a mail sent to an email alias I’m on, where the author was asking why tool X wasn’t enabled on his latest build. The mail looked something like this (genericized to protect the innocent). foo.service doesn’t appear to be working Repro: I installed the build from <build_path> I verified the binaries existed…

  • Let it happen

    I come across this frequently enough that I’m sure I’ve blogged about it before, but context dictates that I do it again. The story I hear goes pretty much like this: My team really needs to improve X, but nobody is taking responsibility for it. The fix is obvious – we need our exec /…

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.