Skip to content

Tag: habits

Design Over Functionality

Visual design is important. I’m not talking about making applications look pretty. (Which is never a bad thing.) I’m talking about how an the User Interface of an application is laid out. How the user interacts with the application. A good design will draw the user’s eye to the correct area and lead them through the application as you, the developer, intended. You should never need to read a manual or instruction guide to use the application. A well designed application is intuitive to the user and natural to use. The user, upon first use of the application, should be able to “just know”…

Your code is bad… Take care of it

  Refactoring is often not done. “There is not enough time”.  “Its not your responsibility”.  Look. Refactoring can only *help* you. You don’t need to devote hours and hours to it. Just make small changes. And over time your code will improve. And for the most part. Most of us are not writing NEW code. We are maintaining code. (And you probably should not be trying to write MORE code, but that’s another story). And its likely you will be working in the same code base for the duration of your employment, or will eventually be called to return to it.…

3 (Nearly) Effortless Ways to Keep Code Clean

Keeping code clean does not have to be a huge endeavor. Just do a little bit at a time, and your code will be shiny in no time. Consistency in naming variable. From the database, to the middle layer, to the user interface. If they are the same thing, do not change up the naming. It will make it so much easier for both you and other people to follow the code. Delete commented out code. If the build is working without the commented code, then you don’t need it. Maybe it’s someone else’s code. But if it’s been there…