Sebastian Gebski

TL;DR - Sometimes I get an impression that there are people who got "promoted" to Senior Developer even before releasing anything to production ... Clearly the length of tenure is not the key determinant here, but neither should be the 100% memorizing of given framework's / library / language's full syntax. There are certain much important qualities that may be harder to assess, but in fact

Sebastian Gebski

TL;DR - These are not just great times to be a Software Engineer - it's even better to be a Software Engineering Manager. Plenty of open development opportunities help in shaping your own, individual professional profile. Physical world borders are far less constraining in that industry. True engineering expertise (& individuals who can apply it within whole organization) gets noticed & appreciated. And

Sebastian Gebski

TL;DR - 2016 in Technology failed to impress me; personally I missed building stuff (that matters), so I've quit (but not rage-quit ;>) my job few days ago. 2017 will be make or break.

It's January of 2017 already, everyone's making summaries, so how could I resist the overwhelming temptation of making my own one? :)

My 2016 in a (very) few numbers

  • 5 public
Sebastian Gebski

If you haven't yet, check the part I first.

Where were we? We've figured out that your job may wave you good-bye & go to Fareastan. But it doesn't conclude the consideration just yet ...

Is the growth inevitable?

Are we completely sure that software development is on permanent rise?

World is crazy about software, everyone wants to build new "digital" services, but if you

Sebastian Gebski

There are more and more open software developer positions in the market. And it's not just about quantity - breadth & variety of roles, technologies, platforms & languages continuously increases - to the satisfaction of all of us. But if you look carefully at the full spectrum of offers available, you'll notice that NOT ALL job offers are about ...

  • ... technologies / platforms considered "modern", "promising"
Sebastian Gebski

Our industry is batshit crazy. No point in denying. What we do (services based on pieces of software) is so multi-dimensional that sometimes it's damn hard to find a common denominator between two: people, projects, products, architectures, methods. Obviously, it's got its pros (let's leave them for another story ...), but there are serious cons as well - one of them is related to job