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.
We, software developers, tend to have some bias towards cutting edge technologies and, in a perfect world, we’d only use them. It’s efficiency driven so that’s great but sometimes we forget that the code we write is written first to benefit the human and only second for a computer to understand. And that’s why we
We all want to be rich, lean, fit, have a good job, a happy life and all that stuff we aren’t or don’t have. But then, quite often, we are safe in our comfort zones and don’t really want to change that because we fear we may not succeed. Or we decide to change and
We, software engineers, tend to be protective of our work.
We get anxious about showing our code.
Unfortunately, the wall we build around “our” code is a perfect formula for a disaster.
Luckily, doing the things that scare us more often makes them less scary.
Everyone needs a software right now. To be more efficient, faster etc. And here we come: software engineers doing our best to make people’s lives easier…
How do you call yourself?
Software developer? Programmer? Coder?
Or, like me, software engineer?
Ok, I get it. You are a software engineer… And you probably decided to be a software specialist because you enjoy programming. so why is it that you ought to know the business side of the project?