Is it always a good idea to use the latest software updates or features in an application? Check out the discussion in the video Should We Use the Latest Features/Updates In Development. As we learn, this question is one that we should reflect over because there are situations where the latest may be a wise choice or cause problems that we didn't expect.
Some questions related to the discussion that are answered in the video are:
For mastering data transformation from one form to another form, check out the highest-rated Automating ETL course on Udemy. For a coupon to the course, check out the trailer video on the channel SQL In Six Minutes.
A colleague once shared a story with me where their team had chosen to use the latest feature in software without reflecting over the effects. When they deployed the changes, they discovered that the new feature wasn't compatible with some of the software they were using causing an outage. This issue wasn't detected in development or QA because the software was rarely used by customers and they had failed to design tests which used it. In addition to highlighting the point of thorough testing, it served as a reminder to be careful about always using the latest software features - it may have effects you don't anticipate.
One regular point I like to remind my audience, especially as of recent: we can often solve the same problem with a variety of techniques. While we look at one or two ways to solve the problem, these aren't the only ways we can approach this problem. The most appropriate solution to a problem is one in which you can troubleshoot quickly in the future and one in which you understand. Be careful about applying solutions that solve a problem, but introduce new problems in the future.
SECURITY ALERT! Want to know the latest in security? Check out the subreddit Security Testing for the latest information, tools and courses that will help you strengthen your personal security and your company's security. Best of all, we're a subreddit created by security professionals for security professionals and individuals interested in security.
A great re-occuring example of this is my discussion on alerting best practices. There are a variety of alerts everywhere for everything in today's development environments, but many of these alerts cause more issues than they solve (one of which is creating a distraction). Be careful about "easy" solutions which introduce bigger problems. Know your environment and where to apply the best solution. Of course, all these being written, it is helpful to learn new techniques to solve problems because they may be useful in the future.
SQL In Six Minutes | Automating ETL | T-SQL In 2 Hours | Consumer Guide To Digital Security
