It’ll be short today. And a little bit more personal 😉 I’m attending Devoxx Poland again this year – that was my first conference ever and I have to say that: it changed my career, showed me new paths, encouraged to learn things again. I think that’s what conferences are for. They encourage conststant learning and
Imagine what happens when you approach the developer in a middle of that task? Now, if you think he/she can pick up where he/she stopped you couldn’t possibly be more wrong.
When your dev don’t want to follow the process he’s incompliant, isn’t he? But what if the process is killing creation and innovation?
Imagine yourself sitting in front of a compiler, tasked with fixing a small bug. But you know that as soon as you say “I’m finished,” another developer – or worse, your boss – will be examining your work. How do you feel? Anxious or encouraged? As software engineers, we take pride in our work (as well
My company uses IBM DOORS connector for JIRA to simplify requirements tracking process. However, the way requirements are transferred to JIRA from DOORS makes it hard to say what the requirement is about. So when I was looking for a way to view the actual requirement my project manager told me about a possibility to
Recently I wrote how to deal with requirements in the process of a software development. Requirements are often customers expectations but those aren’t always the same. And not only your customers have expectations. In reality, every person included or interested in a software project has her/his own interests and expectations. And even as a simple developer you
Have you ever worked on something for a long time, only to realize in the end that you’ve completely missed the point? Probably. this is how to ensure you know what’s about to be built.
We didn’t become programmers because we like working with people. But most of a software is created by teams. So like it or not, you must effectively communicate with others.
Here I go creating 2-people Kanban board for our current project efforts so that we can easily see how our work goes and share it with my Junior (he’s a Junior Dev, but he’s got more IT experience than I in fact… he did a career sidestep just recently). And the first thing I hear is:
On every project, there are things you know and things you don’t know. When it comes to the difficulty of the unknowns, you can make progress only thanks to assumptions. Without assumptions, you’d never get anything done because you’d be frantically proving everything before you’d move on. However, when they end up being false, they can affect your project outcome significantly.