Keeping the User in Mind

This week I found a short and sweet article on Code Simplicity by Max Kanat-Alexander (https://www.codesimplicity.com/post/developer-hubris/). The article is titled “Developer Hubris” and discusses the common notion among developers where they get the impression that the program they wrote is of vital importance and interest to the user simply because the developer put a lot of time and energy into ensuring that the program accomplishes its goal. This is usually never the case. According to Max, the user doesn’t care how the program works, what went into it or how long it took to write. They simply care that the program does what they need. He also goes into how some features of a program can be viewed as problems (i.e. pop-ups) because these features get in the way of the accessibility of their project. The user doesn’t care about the features that don’t have a direct impact on their work.

I agree with Max in that the developer should realize that not everyone is going to see their program as high and mighty as they do. A software developer needs to be realistic in their mindset and know that not everyone is going to love their software. The main attractant to a program is what can be done with it. A user will not have any interest in a piece of software that doesn’t satisfy a certain requirement. The main focus of the developer when writing their software should absolutely be the user and what they can do with it. That doesn’t mean that every user won’t care about the behind the scenes content. Some people are naturally curious and enjoy learning details like that, especially in this field of study.  

Certain pop-ups and options can be annoying to the user but that doesn’t tarnish or get in the way with the fact that the program does what the user needs it to do. In fact, I would venture to say that there are many programmers who would prefer these pop-ups. It allows the user to tweak certain options to his/her preferences. It actually seems that including more options for the user to change makes the program more user-friendly rather than not. To me, allowing for more flexibility is the true way to keep the user in mind.

要查看或添加评论,请登录

Martin Nesbitt的更多文章

  • Data Culture

    Data Culture

    This week, I read an article from Eric Brown (https://ericbrown.com/your-data-project-is-going-to-fail.

  • Estimating Task Completions

    Estimating Task Completions

    This week, I read an essay from Andy Hunt (https://pragprog.com/magazines/2010-11/guru-meditation) on estimating time…

  • Duct Tape Programming

    Duct Tape Programming

    Recently, I read an article on Joel on Software (https://joelonsoftware.com/items/2009/09/23.

  • Software Development Constraints

    Software Development Constraints

    Recently I read an article by Kevin Rutherford…

  • Code Readability

    Code Readability

    This week, I read an article by Max Kanat-Alexander, discussing the readability of code (https://www.codesimplicity.

  • Adjusting to Agile Development

    Adjusting to Agile Development

    This week, I read an article on Andy Hunt’s website (https://pragprog.com/magazines/2011-01/guru-meditation).

  • Agile, Test-Driven Development, and Pair Programming

    Agile, Test-Driven Development, and Pair Programming

    Recently, I read an article describing how a lot of companies that are transitioning over to agile development are…

  • Writing Maintainable Code

    Writing Maintainable Code

    I read a blog post on Code Simplicity (https://www.codesimplicity.

  • Agile and Agility

    Agile and Agility

    In February of 2001, 17 programmers met in Utah and developed an approach to software engineering known as Agile. One…

  • Refactoring HTML

    Refactoring HTML

    Recently I read an article on Martin Fowler’s website about the value in refactoring code; specifically, the value of…

    1 条评论

社区洞察

其他会员也浏览了