Continued from 2013/04/15/lessons-learned-as-a-scrum-master/ Here is my list of lessons learned throughout my tenure as Scrum Master, and I’m sure there are many more that I missed. These were notes directed to…
At SEP, we have very diverse teams, clients, and projects. With all of that variety and diversity, comes a lot of variation in how projects are run. Almost every project, in my experience, has used different processes and techniques.
I was recently inspired by one of my coworkers, Jennifer, by a letter that she wrote to herself describing her ideal job.
Given that we experience so much variety, I decided to try and describe my ideal project. I was not able to describe my ideal project, but I was able to come up with a list of my beliefs and things that I value.
Below, in no particular order, are the values of my ideal project.
This post is inspired by the recent blog battle topic “My favorite line(s) of code” and a recent line of code that I was, literally, Laughing-Out-Loud at. (I apologize for disturbing any of my neighboring SEPeers.)
Not the kind of laughing where you are like “man, what were they thinking!?!”. This was the kind of laughing like, “oh yeah, I’ve had to do some crazy stuff before…I understand what you were doing there.”
This simple, yet beautiful, line of code took me a minute to understand what it was _actually_ doing.
Yes, the readability was less than desired.
Yes, it was nearly impossible to search for in the code base.
And yes, it was flat out ugly (in a beautiful way).
But sometimes, you are so constrained, that you have to come up with amazing little tricks like this one. So, without further ado…