Due to some recent events in BJ's life that have made him re-evaluate some of his goals for this year we've decided to look in on our goals and do a mid year review.
It's important to understand the grieving process. Not only is it part of being an adult but understanding how people process grief is also crucial to avoiding situations that make it worse.
In any field, there is a lot of hard-won knowledge that the more experienced attempt to impart to those with less experience. Depending on the field, these things may be expressed as old sayings, or laws. They typically aren't really hard and fast rules, but rather are general tendencies that have been observed over time.
If you regularly do software development in a higher level language, you'll eventually run into a situation where you have to deal with the sort of problems that higher level languages are built to avoid. These problems may cause application crashes, data corruption, or performance problems until you get them sorted out. Worst of all, your experience in the higher-level language can often work against you in a lower-level one.
No matter if you are a morning person or a night person or if you get up early or stay up late and sleep in you have to start your day at some point.
Everyone should be continuously learning to improve their skills. This is not just something for junior developers. Even senior developers can get left behind if they don't keep up.
Dani Heileman is a marketing strategist, designer and front end developer who's working as the Marketing Director for Music City Code.
A lot of us would like to do more with our lives, but find ourselves getting blocked by our own laziness, lack of motivation, or simply not being sure which thing to do first. While these skills apply to your career as a software developer, they are also broadly applicable across your entire life.
Getting started can be a little intimidating, so it's important to go over the basic requirements to get started learning how to code through experience.
The idea of code smells is they are patterns or anti-patterns that are easy to identify and show the code needs to be reviewed in that area when refactoring your code. Research by Tufano et al. found that there is empirical evidence for the consequences of "technical debt" but only anecdotal evidence as to how, when, or why this occurs.