No, I didn’t die, I was just too busy to change more or less…everything in my life.
Long story short: I had to stay one year in London, but when the end of the year came I realized that maybe one year wasn’t enough for a lot of different reasons.
So I changed plan.
In 2030 a massive project were kicked-off in order to colonize new planets.
The name of the project was International Space Program.
A lot of planets had been probed looking for the best candidate of the first mankind settlement in the space.
At the end Mars won and a bunch of settlers were chosen to colonize it.
The main reason for the colonization of space was the research and the harvesting of an important resource missing on Earth: “Whatsoever” (on periodic element table: WH)
What you could achieve using the “Whatsoever” was limitless, so a lot of Companies invested on the International Space Program.
The settlers were sent on Mars in 2032 and an interspace link granted the quick send of designs, prototypes useful to build objects on Mars.
The name of this link was: New Universal Gate for Extraterrestrial Transport or N.U.G.E.T for short.
Few months ago in the office we started a discussion about testing.
The original topic was “how to implement a continuous integration/continuous delivery workflow”, so “how to test” became immediately a requirement and a parallel important topic.
My suggestion was to start coding in TDD of course, but like every office we had a lot of legacy code to deal with.
In order not to be stuck by that, we decided temporarily to focus on new (or almost new) projects and apply it to them.
So the point became to find a way to have all the developers, regardless on the seniority and the project, on the same page about the topic.
After the first implementation of the game, my friend and I compared our versions.
He focused on the deck model instead of the dealer like I did.
This simple choice drove his design to a complete different path.
He put a lot of effort trying to replicate a realistic deck, implementing the shuffle logic and making impossible to draw the same card twice.
This hypotheses never came up to my mind because I knew that in the real game there are multiple decks in order to make almost impossible for the players the calculation of the drawn cards.
Speaking to a friend a couple of weeks ago, he told me about an interview he did where one of the challenges was to create the blackjack game.
The algorithm itself is not too complicated, but it’s a good test to practice TDD and having never tried it in AngularJs I decided to give it a shot.
Along this year in London I’m learning how the projects are managed here, how teams are formed and dismissed, how to deal with the day-to-day activities, how to create roadmaps for projects…and a lot of other things.
Needless to say that the environment in the London office is more fluid and working with Projects is very very different from working with the Products.
I’m attending a few business classes focused on Communication and Management, nothing specifically Agile related, but very focused on the Business and the Company.
An important concept that I Iearned in these months and I’m using to re-analyze how I did before is “be sure to set and clarify the expectations”.
If you read the introduction to angularjs, it’s stated clearly that angularjs can be not the best choice to create games.
I can imagine the reason easily: the performances can be very problematic, mostly if the game requires a complex DOM.
Moreover a lot of good frameworks exist to create amazing games in html5 (have you ever heard about impactjs?).
Nevertheless I have found very fascinating the idea to manage via directive a level design instead of a classic multidimensional array as I did in the pawn and tiles experiment.
When we started 4 years ago using Scrum the PO decided to use PivotalTracker to manage the Backlog and the roadmap.
We also had a physical board for the current sprint, but we found very useful to have the virtual one.
My “wall” in Turin a couple of years ago, before we moved in a newer room.
I will discuss about my generic approach in refactoring in a specific post, but a few weeks ago I found an old code and I remembered what was happened that specific time.
Like in every nightmare, everything started with a simple request
“Could we re-arrange few lists of categories in a different layout?”
More in detail, the task was to rearrange in a different rows-columns layout four lists of categories sorted and grouped by macro category.
In theory pretty easy so the answer was “of course!”