CommentComment

I'm going to start this week with something that's been on my mind for a while now, but after reading The Churn by Robert C. Martin this week I want to briefly write some thoughts about it.

First of all, read the article.

There is a balance to be struck when considering this problem. I don't really agree that software development is at the point of diminishing returns and I do still think that we need people working towards pushing development practices forward. But in iOS development, do we see more writing about the language and CS techniques? Do we see less about actually building the apps that end up in the hands of our users?

Introducing a new language, especially one as flexible and complex as Swift was always going to trigger a lot of writing about lower level topics, but it's easy to fall into some of the traps Bob mentioned if if you listen too closely. I love Swift and I'm happier writing code with it than Objective-C, but what matters most to me is still the apps that we ship, and how they work for our users.

It's worth bearing in mind that is an issue mainly focused on writing about building apps, rather than actually building apps. There are a thousands of apps shipped every single day, but we do view iOS development through a lens of what's being written about it in our community and it does have an effect on getting things done. I'm also aware that in giving you things to read every week, I am part of the problem! I do actively try to keep things balanced where I can though.

I think what I'm trying to say is that it's OK to focus on getting apps built and shipped. You don't need to be an expert on how a language is created, or every new development technique, or rewrite working code because you saw a potentially better solution in a blog post.

Dave Verwer

News


Tools


Code




Design

Business and Marketing

Videos

Jobs



And finally...