I have learned a lot while working as a software developer for the last 15 years in both the public and private sector. There is one mantra that has really stuck with me as I have seen it hold true time and time again, and that is: "good, better, best." You may have heard of this before in the context of pricing model tiers for a service. The car wash up the street from me does the following: the "bronze" service gets you an exterior car wash, the "silver" service also cleans the interior of your car, and the "gold" service gets you fragrances and the promise that even dog hair will be thoroughly removed! Don't fall for that last bit - dog hair is&nbsp;furever (sorry, not sorry). But what does "good, better, best" mean in terms of software development? I am talking about code quality, and the order matters - start off with good code, then move on to better, and save the best for last. This may sound obvious, but I have seen many talented individuals (and teams) spend far too much time engineering complex solutions to simple problems.
Let's start off with the "good" code. Simply stated, good code is not great. It may not be the most performant, it probably isn't scalable, and it definitely does not have a high degree of unit test coverage&hellip; but it is&nbsp;solid. It is reliable, it does not have bugs, and it satisfies all of the specification's requirements. You know that new feature that you're working on - the one that is sure to be the "next big thing"? It might not be! So don't spend an excessive amount of time over-engineering it. Work with the business to determine what the minimum viable product is and build that as fast as you can. There is tremendous value in getting code into production quickly. The viability of the business idea can be tested by customers or clients, new features or requirements can be uncovered, and most importantly - you can beat your competition to the punch. If the original idea behind the code you are writing has value, you can take the next step.
Better code - but what makes it "better" than the good code discussed previously? Better code takes newly acquired domain knowledge into account to plan for a future state. "But wait," you might be thinking, "we should have done it right the first time!" That may have been true if you already had a thorough grasp on the problem that you are trying to solve and an understanding of the ramifications of every design decision facing you when you began the project. In my experience, this is rarely the case.&nbsp;Now&nbsp;is the time to start considering your design and architecture. Why? Because you have learned from the first iteration of the feature. Your decisions about where to focus development efforts are more informed at this stage than it was while you were writing "good" code.&nbsp;
So what defines the "best" code - how can it be quantified? This code takes into account every nuance and edge case in the knowledge domain to the point that it can and should be packaged and sold as a service. When do you take the time to write that code? You'll know because the feature will have already proven itself to be the "next big thing." Until you get to this stage of the game, think carefully about the amount of time and energy you are spending on the task at hand and remember that, in general, perfect is the enemy of done.

I have learned a lot while working as a software developer for the last 15 years in both the public and private sector. There is one mantra

A Pragmatic Approach to Software Development

I have learned a lot while working as a software developer for the last 15 years in both the public and private sector. There is one mantra that has really stuck with me as I have seen it hold true time and time again, and that is: "good, better, best." ...

Interviewing can be stressful, especially if you are just starting in your career, if you are re-joining the workforce after a long period or if you are just interested in seeking a different role. Below are five tips you should think about as you begin your journey.
Prepare Do your research. Understand the company you are interviewing with. Spend a few hours learning anything and everything about the company you want to work for by reviewing the company website, social media, and news releases. Talk to friends or contacts that can give you a sense of &ldquo;who&rdquo; the company is and how they operate. Also, look to see if the person(s) you are interviewing with is on LinkedIn. Review their profile to get a brief understanding of their background and experience so you have an idea of who you are talking too, and how you may relate to them.
Practice Review typical job interview questions employers ask and practice your answers. Strong answers are specific and concise that highlight your skills and experience that back up your resume. Your answer should highlight the skills that are most relevant to the position you are applying for. It is also important to listen during the interview to ensure your responses give the interviewer the information they are seeking. Role-play the interview with a friend or family member. Do it as many times as you can until you feel confident.
Be on time As an interviewer, this is a big pet peeve of mine. Never&hellip;be&hellip;late. I always follow the mantra, to be early is to be on time&hellip;to be on time is to be late. Always arrive five to ten minutes early for the interview. Know the location and how long it will take to get there. Give yourself extra time to pull yourself together, gather your thoughts, and calm your nerves. You don&rsquo;t want to show up disheveled and appear to be disorganized. You want to portray yourself as calm, poised, and confident.
Relax Interviews can be daunting, especially if you are in front of a panel of people. Always remember to make eye contact with the interviewer asking the questions. Your eyes are the windows of the soul. They show trust, distrust, fear, and uncertainty, but can also convey strength, thoughtfulness, and happiness. Employers are looking for unspoken clues about you as the candidate through all various means. Also, be aware of your body language. Body language speaks volumes and can help communicate a positive message to your interviewer. You don&rsquo;t want to come off as sloppy or stiff. Think about your posture. Sitting straight conveys you are comfortable and confident while slouching or being hunched over may give an impression of nervousness or low self-esteem.
Engage Know your audience and carefully read the room. Be energetic but not overconfident. Make sure to pay attention to all questions being asked using active listening techniques. Tips for active listening include interrupting a question, summarizing and repeating back what you heard, and just simply concentrating on what is being said rather than just &ldquo;hearing&rdquo; what is being said. Remember, believe in yourself&hellip;and smile.

Interviewing can be stressful, especially if you are just starting in your career, if you are re-joining the workforce after a long period o

Five Tips for Interview Success

Interviewing can be stressful, especially if you are just starting in your career, if you are re-joining the workforce after a long period or if you are just interested in seeking a different role. Below are five tips you should think about as you begin your journey. Prepare Do your ...

Team Member

Phil Rex

Learn HTML

Learn CSS

Learn Javascript

*UPGRADE IN PROGRESS* -- CareerCircle platform upgrades will occur between Monday June 27th 10PM Eastern Time through Tuesday June 28th 4AM Eastern Time.&nbsp; The system may be intermittently unavailable during this timeframe.&nbsp;&nbsp;

*UPGRADE IN PROGRESS* -- CareerCircle is upgrading its capabilities and as a result the system may be temporarily unavailable as we bring new capabilities and infrastructure online to better serve our members.&nbsp; If you receive an error during this timeframe please bear with us as we're working to improve our system and you may need to retry that operation at a later time.&nbsp; &nbsp;

Phil Rex

2

Articles

A Pragmatic Approach to Software Development

Five Tips for Interview Success

Tags

Career Path

Learn HTML

Learn CSS

Learn Javascript