Communication FAIL

Agile is about the development team being able to respond quickly to customer needs and enhancing developer-customer communication.

For my team, I think we need to take a step back and work on our own intra-team communication. I realize there are difficulties inherent to working closely with onshore/offshore contractors, but all the more reason to spend the time, make the effort, and reap the benefits.

Below is how most of our meetings, scrum calls, and sprint plannings conclude. Sigh.

SCRUM MASTER: Okay. Does anyone have anything else?
…
……
TEAM MEMBER #1: No.
TEAM MEMBER #2: Nope.
…
…
TEAM MEMBER #3: No.
…
……
SCRUM MASTER: Anyone?
…
SCRUM MASTER: <looks around questioningly>
……
…
SCRUM MASTER: No one? Well, in that case…
……
SCRUM MASTER: <looks around questioningly>
SCRUM MASTER: Have a nice day and talk to you guys later.
.
TEAM MEMBER #7: Wait, I have something.

Keyboard Failure. Press F1 to Continue…

I received the following error today while booting my computer with the keyboard unattached:

Keyboard failure
Press F1 to continue, F2 to enter SETUP

Are you serious?!

Cool Way to Get the Calling Method/Class in Java

I was looking for a graceful way of retrieving the class of the calling method. This isn’t half bad (found it here):

Class callingClass = new Throwable().fillInStackTrace().getStackTrace()[1].getClass();

And if you just want the name of the calling method:

new Throwable().fillInStackTrace().getStackTrace()[1].getMethodName();

Code Comments

My favorite takeaway so far from: Clean Code: A Handbook of Agile Software Craftsmanship

Every time you express yourself in code, you should pat yourself on the back. Every time you write a comment, you should grimace and feel the failure of your ability of expression.