Bugs are going to happen even to the best developer. That unexpected behavior is just part of this profession. But what sets you apart and defines you is your ability to problem solve. It’s about finding the root cause, that thing or things which are at the center of the problem, and then properly resolving it. In this daily tip, let me share with you my four (4) steps to problem solving. These steps are the same no matter if you are on the hunt for a minor issue to some intermittent, pain in the backside, wonky problem.
I’m often asked where you should start. How can you move from copy/paste to being able to build anything in code? You want to build your new skills incrementally, step-by-step. Each time you copy and paste a snippet of code, stop and dissect it. Go through the individual instructions. Look them up. Take the opportunity explore the code you are putting into your project.
A designer creates a complete visual branding and online presence for a client, including websites, logos, print and online media, advertising, swag, and more. The designs flow through all different types of mediums to create a consistent branding and visual package.
In today’s quality code tip, you will learn about removing the HTML from your business logic and putting it into a view file. In programming, you want to separate out your code by its intent and purpose. Let’s discuss the what, how, and why of view files. (Side note: I’m showing you the actual code on this website which is powered by Genesis.
Code Smell Alert: A common code pattern that I see is where the if/else logic and the if conditional is backwards. I call this the “if/else backwards code pattern.” This code pattern makes the code less readable, which decreases its quality. There are two clues to let you know that you have stumbled into this pattern: The if conditional is set off of a false state. Typically you’ll see a not operator (!) as your clue. The if logic is setting a default state. But that is the job of the else. Smelly Version This is the smelling code pattern: […]
I often hear how it’s difficult to make time for continuous learning. In this profession, we have to dedicate ourselves to staying current. That means we must give time to continuous learning. Here is a solution for you, a tip from me to you: Take one or two lunches per week, 2 hours total per week, and spend that time eating your lunch while you learn. I did this with my teams and staff over the years. It’s highly effective. The key is making sure you are spending the time learning from a teacher who helps you adapt the knowledge […]
When doing a conditional expression, it’s a smelly code pattern to then return true or false. Why? The conditional expression already returns a true or false state. Therefore, you do not need to be so verbose and hardcode a boolean return. Here is the smelly code pattern: Refactor this code down to one line to make it more readable. It’s less code too (skinny). Strive to reduce your code and make it more simple. If you see this pattern in your code, then refactor it. Remember, you want your code to be as skinny (as few lines) as possible.
Here is a master insight from me to you: the code building blocks empower you to build whatever you want in code. All code, no matter how simple or complex and no matter the language or technology, is built with a combination of basic building blocks. These are the foundation of computation and your ability to get that computer to do what you need it to do. Being able to build anything in code means you are proficient with the basic building blocks, i.e. the fundamentals of computation. Once you focus yourself on one language and become proficient with it, […]
Here is a master insight from me to you: Focus to make yourself invaluable. You need to marshall all of your energies and time to focus yourself. Proficiency in any business, and especially in software development, comes from focusing on building your craft and skills. Stop chasing the shiny new fads and efficiency tools. These make you more efficient but will not help you to write clean, quality code from scratch. They will not help you to be able to evaluate code, identify the strengths and weaknesses, and know how to integrate it into your project. These are efficiency tools […]