Arttu
Hi, good to see you here! I call myself a software development consultant. The intent is to emphasise that although I mostly do coding, I also focus a lot on improving teamwork and processes. I enjoy improving how companies are building software.
I have worked full time since 2010. I've worked in a product company, as a contractor and as a consultant. Sometimes I'm a full time developer, sometimes a team lead, and sometimes something like a coach.
Interact on Mastodon: @arttuv or on LinkedIn.
My digital home is my arttuv.com website.
Arttu's work on this site
Arttu's latest comments
I like the practical nature of this definition of bad code: It takes the focus to outcomes. Farley is also conscious about the fact that what qualities the code should have is somewhat context dependent. Same as with processes, it’s too easy to start arguing about the details with very limited practical utility.
Naturally this is my view based on my experiences. Did anything sound surprising or ‘wrong’ in this article to others?
Bad Code
Oh yes, at least I remember I used to struggle with these definitions when I had less experience writing code. Like, ‘small functions are easier to read, split them up if they go over n lines’. You might get carried away with that kind of rules. Who am I kidding, I still struggle with these.