from my work as a developer
Posts tagged distributed team
what I learnt
Nov 25th
Do you remember my posts about the fourth question and fast thursday ?
Here is another constant behaviour for another day – friday with constant question: what you learnt (during this week).
Your answer can be related to your job or to hobby or to whatever you want. Give just one small example of what you learnt, it can be something small and funny or huge and very important 
It’s up to you, but share your knowledge, make other start wondering what to do next, maybe you’ll inspire others to do something like you. It’s very informative attitude, you’re expressing yourself, showing you aren’t just a nerd
Ok, so what I learnt ? I remember two things:
- below 0 degrees it’s hard drive a bike, not because it’s cold, but because a glass from the helmet freezes and you see nothing on the road
- at last I understood what’s the difference between @Inject (JSR-330) i CDI (JSR-299), CDI bases on @Inject, but you cannot put equal mark between them
There were probably more, but it isn’t important to say about all of them, just two is enough. Please try, share your knowledge!
And as usual some nice presentation from TED – be smart, play games
extend or not extend
Jun 14th
That’s the question!
When you are managing a project using the Scrum methods, each of your tasks must be grouped in sprints or iterations. The whole team is preparing a sprint, estimating the tasks and fitting stories in a given period of time – the Iteration.
As usual, the estimates are just estimates It’s always some kind of guessing … even if you spent a lot of time on the project and you know each line of the code and all the business behind (do you?). The problem is, there are many unrelated things that can happen. People can be sick, a build server can blow-up, a team member can left the company and so on and etc …
The reasons you cannot imagine and predict.
So, because of that should the sprint be extend or not ?
We can fail, we can move tasks and stories, we can spend hours trying figure out what was wrong … Or maybe extend the sprint for one, two more days, solve all the issues, close all the tasks. No one will be frustrated because of fail of sprint. We will not lost time for looking into the problems, we just passed over them. What do you think ?
At the end there should be a presentation from TED, but I didn’t get the newsletter yet, so I’m going to say how I work. As a member of highly distributed team which is working remotely, we use Skype to communicate. And because of that there is a drawback – you don’t know when someone just left the room and he / she isn’t at his / her desk. So, we use the short status messages (you can use “/me text” to change the status in Skype). The list is below, feel free to share it or extend!
- ś – śniadanie (breakfast)
- b – back (I’m back at the desk)
- brb – be right back (means I will be back in few seconds / minutes / hours)
- biab – back in a bit (means I will be back in few minutes / hours / days)
- bbiab – be back in a bit (means I will be back in few hours / days / years)
- o – obiad (lunch – in Poland not known)
- z – zupa (soup – if you eat)
- dd – drugie danie (second meal)
- out – out (means you finished the work for today and now you’re coding for pleasure)
Enjoy!
