Frictionless Programming

It has been my plan for a while to start writing about all the things that make a software developer happy and active –  or loyal and productive, if you prefer to see it from a manager’s perspective.

When I am asked about my opinion on the topic, I usually mention that I need the right challenges, good colleagues, a decent work/life balance – and a fair compensation.

But if you have all that and you still feel frustrated every work-day, it might be because of what I intend to write about in future blog posts – too much friction.

Friction to me is everything that gets in the way when I need to get my work done. Friction to me is hour-long check-in times, processes that slow me down rather than helping me to get things right, using mind-sets, frameworks and tools that simply do not belong in 2018, and so much more.

At the end of the day, all I want is to look back and see that I actually managed to implement functionality that will benefit my users.

In future posts I will give examples as well as my opinion on what to do in order to achieve true frictionless programming.

One thought on “Frictionless Programming

  1. Pingback: If it ain’t broke, don’t fix it. Or, what? | Life, code and everything

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s