Or how some people have a hard time believing that they are not infallible.

Photo by Paul Carroll on Unsplash

I’ve seen this in various software development organizations. One of the developers in the team (possibly more than one, but then, I really pity you) is supposedly a “very knowledgeable” developer. A guy who really “knows a lot”. Pretty soon, you figure out that his word is law: if he has said it, then it is the end of the discussion, if there was even a discussion. Because he is never wrong, even when he is wrong. He is the “pope” of your development team.

Let me make a clarification at this point. I use “pope” in quotes because, evidently…

Or why an often overlooked part of software development can be more important than you think.

Photo by visuals on Unsplash

Warning the user about an error in an app is a part of the job that most app developers do not like or do not care enough. After all, most app developers want to write code that works, and not code about dealing with what happens when things do not go well.

That behavior is exacerbated by how development teams are structured. We spend a lot of time discussing how features in our apps will work, but rarely we talk about what to do in anomalous situations. That’s understandable: we all like to provide our users with cool new features…

Photo by Ehud Neuhaus on Unsplash

At this point, the concept of technical debt has been thoroughly disseminated among developers. Just as a refresher, technical debt is what happens when developers, usually under pressure to finish quickly, cut some corners, take some shortcuts, hack something to make it work. In other words, compress development time at the expense of code quality. But the best way to illustrate this concept is with an (all too common) example.

We have all been there: you are trying to finish a project in time. But then an urgent business need comes around. You have to create a feature in your…

Photo by Kelly Sikkema on Unsplash

In a previous article, I described a useful programming idiom for passing parameters to an Activity in Android. As I said then, I believe that idiom would help when refactoring some old and large Java codebase, in which you have an Activity with lots of parameters spread all over the code. However, as we all know, Kotlin is quickly overtaking Java as the language of choice for Android programming. I think that this idiom is useful for new codebases as well, so I’m giving its implementation here in Kotlin.

Kotlin makes the idiom even easier to write. For starters, you…

These days, Android development is switching fast to use Kotlin as the standard programming language. However, there is still a lot of Java code written for Android and developers face the challenge of modifying (and hopefully improving) big codebases written in Java. In this article, I would like to show an idiom that can make the code for starting Activity objects a little easier to to deal with, and help you cope with some old Java codebase.

As Android developers know, in order to start an Activity, you have to create an Intent object. In that object, you can pass…

Nelson Leme

Principal developer, with a passion for writing code. I love my little objects and high order functions! 👨‍💻 (https://www.linkedin.com/in/nelson-g-m-leme/)

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store