I’m still surprised by the number of people who don’t get this … Meetings are important and sometimes people have to be interrupted. But just keep in mind that the 5 minute chat will probably throw off people for an hour.
Source: CommitStrip.
I’m still surprised by the number of people who don’t get this … Meetings are important and sometimes people have to be interrupted. But just keep in mind that the 5 minute chat will probably throw off people for an hour.
Source: CommitStrip.
Stride is a new product from Atlassian. Â It is a re-branded and, hopefully, improved HipChat. Â I haven’t tried it yet, but our team account will be upgraded soon enough.
To be honest, I’m not that excited about this move, but I’ll give it a benefit of a doubt. Â I know there was a lot of hype about Slack recently, but I was really happy with HipChat. Â I tried Slack for three days, and ran away. Â But HipChat I can’t leave without. Â It’s a much simpler and cleaner user interface, and it just works – completely out of your way.
Judging by the screenshots, Stride is a user interface upgrade to HipChat. Â Atlassian has been moving to the new design recently with BitBucket and possibly other tools, so this part makes sense from at least their perspective. Â Stride also brings free video calls, voice calls, and screen sharing. Â HipChat had this option for the premium accounts (2$/month/user). Â We tried it for a month and reverted, as the quality of calls and video was horrible. Â And there were constant crashes and disconnections. Hopefully, Atlassian has put some work into these issues for the Stride release.
The most annoying thing about the upgrade from HipChat to Stride will be all the integrations. Â Atlassian is promising to migrate all the data – history, files, custom smileys, etc. Â But the best part about HipChat are the integrations. Â We have a whole lot of them – GitHub, BitBucket, TravisCI, Twitter, WordPress, Â Zabbix, and even our own custom ones, that we use for project deployments. Â All these will have to be reconfigured and setup for Stride separately. Â That’ll take a few hours here and there to get things back to where they were.
As far as the new features go, I don’t see too much yet. Â Apart from the already mentioned voice calls, video calls, and screen sharing, there are just a couple. Â Focus Mode is not really a big feature. Â HipChat, much like any other messaging application, already had the status (Online, Away, Do Not Disturb, etc). Â So Focus Mode is pretty much the same thing, with an extra time setting, so that you don’t forget to change you status back after a couple of hours.
Actions and Decisions is a nice addition. Â You’ll be able to mark any message as an action or decision so that its easier to find and follow up on later. Â But for us that’s not going to do much as we are already using Redmine for the project management. Â Actions go into Redmine as tickets, and can later be referenced in commit messages, linked to each other, etc. Â Having actions in Stride will probably work for very small teams with very few projects. Â For us, we have a separate room for every project, every team, every office, and then some. Â So searching for actions in a hundred-something rooms is far from perfect. Â But maybe Stride’s search will be more powerful than that one of HipChat. Â We’ll see.
Oh, and I’m guessing all the users will have to downloading and install new apps – for mobile, desktop, etc. Â That’s yet another thing to do.
As I said, I haven’t tried Stride yet, and I hope it’ll be a huge improvement over HipChat, even though I HipChat worked great for me. Â As I see it now, I think re-branding and the new design could have happened on the HipChat infrastructure. Â Moving people to the new application altogether has to be justified by some major improvements. Â And I’m not seeing anything major just yet.
Today is my third birthday as the Qobo CTO. Â Here are the summary posts for the first and second years, if you are interested.
I haven’t had a boring year at Qobo yet. Â And this last one was the most eventful and interesting, both business and technology wise. Â Let’s have a quick look at the business side of things first.
Since last August, here are some of the things that happened:
Now let’s have a look at technology a bit more. Â Last year I mentioned Qobrix, but I could give you any more details. Â Today, Qobrix is a real thing. Â It’s our own platform for building business applications rapidly. Â We developed it to a very usable state, and built quite a few applications with it, anything from custom processes, Intranets, and all the way up to the CRMs. Â The platform is being actively developed and is maturing every day. Â We have also started building a new website that provides plenty of information for it.
Big chunks of our development effort are being released as Open Source software – have a look at our ever-growing GitHub profile. Â We have also contributed to a number of Open Source projects in both CakePHP and WordPress ecosystems.
We are also getting much better at this whole cloud computing thing. Â Our knowledge of Amazon Web Services (AWS) is growing and improving. Â We have more servers now, use more services, and planning to expand even further.
Overall, as you can see, this was quite an intensive year, and it doesn’t look like things are slowing down. Â Quite the opposite. Â After three years at Qobo, I have to say that this is hands down the best job I ever had (and I had some pretty amazing jobs in the last couple of decades). Â I’m learning a lot every single day. Â I see the impact of my effort on the company as a whole, on the team, and on our clients. Â And I am still humbled by the expertise and virtues of people around me.
I’d like to thank everybody around me for all the wisdom, tips, hard work, and joyful moments during the last year. Â I’ll be raising my glass tonight for many more years like this one. Â Cheers!
Fedora 26 has been release about a month and a half ago. Â But I didn’t have the time to update my laptop until today. Â There was also nothing particularly exciting for me in this release, so there was no rush.
Here’s what I had to do today to update my laptop from Fedora 25 to Fedora 26:
# Let's get into root to save a few keystrokes sudo su - # Install all updates for Fedora 25 dnf update # Install dnf system upgrade plugin dnf install dnf-plugin-system-upgrade # Download upgrade packages for Fedora 26 dnf system-upgrade download --refresh --releasever=26 # Reboot and install Fedora 26 dnf system-upgrade reboot
If you need more help, have a look at DNF system upgrade wiki page.
The whole process took less an hour, but your mileage may vary. Â For me, the download itself was the slowest part. Â I had to pull down about 2.5 GBytes worth of packages, and given my office connection, it took about 35-40 minutes.
The installation itself took about 10-15 minutes, for which, I think, the solid-state disk (SSD) helped a lot.
One more reboot later, everything was up and running. Â Of all the changes pushed into this version, I think, the upgrade to PHP 7.1 is the one that affects me the most.
Joel Spolsky wrote “Fire and Motion” blog post back in 2002, but it is as relevant today as it was 15 years ago. It’s a good read on the subject of both personal and organizational productivity.
What drives me crazy is that ever since my first job I’ve realized that as a developer, I usually average about two or three hours a day of productive coding. When I had a summer internship at Microsoft, a fellow intern told me he was actually only going into work from 12 to 5 every day. Five hours, minus lunch, and his team loved him because he still managed to get a lot more done than average. I’ve found the same thing to be true. I feel a little bit guilty when I see how hard everybody else seems to be working, and I get about two or three quality hours in a day, and still I’ve always been one of the most productive members of the team. That’s probably why when Peopleware and XP insist on eliminating overtime and working strictly 40 hour weeks, they do so secure in the knowledge that this won’t reduce a team’s output.