14.01.2019 by Jens in Learning
Yep, I said it. Right in the headline. And I mean it. Don’t use that pattern. To make it clear from the beginning, I am not against it, but like with any other decision do proper analysis before.
I’ve been on training for mindful coaching recently, and almost a day in, I started wondering on how to apply what I learned to coding. How could a team benefit from combining the two concepts? How could mindful coding help to ease the pains of building software?
Sick of deadlines? Sick of project managers, boss, customers or whatever? Coding was once a dream of yours and now it drags you down. Each time you even think about it? Dreading Mondays? Thinking, why am I doing this shit?
Somehow complexity attracts devs like light attracts moths. They can’t resist, we can’t resist.
I was giving a Spring Boot training last week and during the course, I made some observations, which I like to share with you over this week.
Plans never work out.
Let’s take the neverending discussion of testing vs no testing.
Yeah, for your passion of course.
I’m having a problem with this passion word and thing for a long time. Passion is bullshit. I read it again a few minutes earlier where a fellow dev proudly states he’s passionate about unit testing. Yeah, I am passionate about hammers too. And chainsaws. Especially last Friday (13th).
I’ve recently listened to the Freelance Transformation Podcast Episode with Alan Weiss and I think there are some gems in it even when you are an employed dev.
Don’t let names or his books fool you into thinking it doesn’t apply to you. Yes, it is focused on consulting and self-employed people. But in today’s crowed dev world (and stupid interview processes), it will help you too to tune out from the typical dev point of view.