Koodihommia

At the moment, I'm working in an organization where almost 80% of the Slack messages are direct messages. We have a low threshold on contacting others - in private. While it is obviously good to share information the method is not the best. I don't need to enumerate the drawbacks of DMs compared to messages sent to public channels. The most obvious ones to me are the increase of tribal knowledge and the further reduction of us into separate silos (devs, marketing, sales, etc...). We recognize that most of the DMs are casual conversation. Yet, these contain information gold nuggets and ideas which should be shared with everyone. We have a couple of ways how we are to stop direct messaging If someone DMs you, actively move the conversation to a suitable public channel. No need to be polite in this. Use more threads in public channels (yes, this is a bit controversial) Have channels for hobbies and chit-chat

I was working on the first part of the year on a project wherein the five-person team, there were members from Portugal and the US east coast. Since we were on the starting time zone, the workday went as follows: We started to work here in Finland, where the US left off. They left a descriptive torch pass message on what they were doing, and we continued from there. At some point in the afternoon, the Portuguese joined, and we worked together. Our day ended in the daily, which was pretty much our torch pass to the US part of the team. This resulted in pretty much 16-hour work cycles, or in other words, two shifts. It was very efficient for a couple of reasons Strong team. We were all capable of independent work and made decisions on the fly. Direction. We did not have detailed stories or Jira tickets, but the course was clear Strong PO and scrum master. They protected us, and we did not waste any time in pointless meetings. 5/5 would recommend working in a team ...

Given there is a chance, I'm eager to give a tech talk to any kind of audience which is willing to have a listen. Part of the fun of giving a speech is of course also learning something about the subject and also, improving myself as a speaker.  Two of the most recent talks I've held this year have been to the local university IT students. Having been one of them in the past, I knew that giving them something uninspiring to do would be something they are used to. The challenge would be to figure out something actually fun which can be accomplished in a matter of a couple of hours. There are countless blog posts and tutorials about how to talk to students, but I decided to ignore them and wing it. I gave two assignments to choose from. First one was to make a DVD screen saver with JS. There was a short-lived internet meme about it earlier this year, and I thought that hey this could be fun. It turned out to be quite amusing to watch at least especially when mixe...