Complete Developer Podcast

Podcasting has definitely been a journey for both of us. When we started BJ wasn't even a developer and Will was working for himself. Now 8 years later BJ is leading a team of developers and Will is back working for himself. It has been an amazing journey with you all this past years. We have both learned a lot about ourselves, programming, leadership, and audio engineering (well Beej learned about audio). However, like all things, it can't last forever. Sometimes you just hit a point where you realize that you can go on, but your heart really isn't in it any more. That's kind of where we both are. We've enjoyed our time podcasting and it's been a very memorable eight years. The podcast has changed us both a lot, and that's the real reason we are stepping away from it. We've both gained many new skills, and more comfort with more difficult tasks. And now we both have goals of our own that don't really mesh well with the podcast. LINKS JOIN US ON PATREON [HTTPS://COMPLETEDEVELOPERPODCAST.COM/?FEED-STATS-URL=AHR0CHM6LY93D3CUCGF0CMVVBI5JB20VQ29TCGXLDGVEZXZLBG9WZXJQB2RJYXN0&FEED-STATS-URL-POST-ID=4215] LEVEL UP FINANCIAL PLANNING [HTTPS://COMPLETEDEVELOPERPODCAST.COM/?FEED-STATS-URL=AHR0CHM6LY93D3CUBGV2ZWX1CGZPBMFUY2LHBHBSYW5UAW5NLMNVBS8%2FY2RW&FEED-STATS-URL-POST-ID=4215] [https://completedeveloperpodcast.com/?feed-stats-post-id=4215]The post A Farewell To Our Fans [https://completedeveloperpodcast.com/a-farewell-to-our-fans/] appeared first on Complete Developer Podcast [https://completedeveloperpodcast.com]. Hosted on Acast. See acast.com/privacy [https://acast.com/privacy] for more information.

Simple systems fail simply. Complex systems also fail simply, but their interconnectedness with other systems makes mitigating failures much more complex. Past a certain level of complexity, system failures are an emergent property of the system – that is, the set of system parts has a set of failure cases that the individual parts do not have by themselves. This means that it is more difficult to predict what can go wrong with a system. At some level, prediction is nearly impossible. However, you can predict many of the things that are likely to cause problems, simply by engaging in a few fairly simple thought exercises, you can greatly reduce the number of unexpected problems that your system encounters. While it can be tempting to wait until a problem occurs to try to mitigate it, this is unwise in a production system that other people are dependent on. A system failure usually costs money at a minimum, and the problems can be far more severe than that. As a result, it's common for software services to include a Service Level Agreement or SLA, that dictates expectations about the frequency of system outages, response times, and time expected to complete work. Even if your system is engineered so that it doesn't completely fall over when a problem occurs, it can still violate an SLA and cost money. The consumers of your application probably have their own clients who have their own expectations. SLAs tend to bleed inward from clients to the services that they use and then to the services that those services use. In contrast to SLAs, systemic problems, including both errors and latency tend to bleed outward from one service to its clients and then to the clients of that service. As a result, when you are thinking about how to find potential systemic problems, it's often best to think of these problems from two different angles. That is, you need to consider how errors and latency will bleed out as a result of a problem, while also considering how SLAs bleed in to put more stringent expectations on your system than you might expect. In effect, you are dealing with a balance between tolerance for errors and difficulty in error mitigation. Depending on how critical your system is to your clients, these expectations will vary. You can't prevent every problem in a system, but you can usually prevent a large percentage of them by planning ahead. However, until you've encountered enough unexpected problems, it can be difficult to envision how something can go wrong, or even have a realistic thought process for thinking about what can go wrong. However, if you go through the thought exercises we've outlined here, then you have a good chance of preventing most of the problems that will plague a complicated application. While this doesn't fix everything, it can give you enough breathing room to fix the truly unusual problems that you'll occasionally encounter. LINKS JOIN US ON PATREON [HTTPS://COMPLETEDEVELOPERPODCAST.COM/?FEED-STATS-URL=AHR0CHM6LY93D3CUCGF0CMVVBI5JB20VQ29TCGXLDGVEZXZLBG9WZXJQB2RJYXN0&FEED-STATS-URL-POST-ID=4210] LEVEL UP FINANCIAL PLANNING [HTTPS://COMPLETEDEVELOPERPODCAST.COM/?FEED-STATS-URL=AHR0CHM6LY93D3CUBGV2ZWX1CGZPBMFUY2LHBHBSYW5UAW5NLMNVBS8%2FY2RW&FEED-STATS-URL-POST-ID=4210] [https://completedeveloperpodcast.com/?feed-stats-post-id=4210]The post Preempting System Issues [https://completedeveloperpodcast.com/preempting-system-issues/] appeared first on Complete Developer Podcast [https://completedeveloperpodcast.com]. Hosted on Acast. See acast.com/privacy [https://acast.com/privacy] for more information.

Feedback is any information, observation, or even opinion about the performance or behavior of another individual our group. It can be formal as in performance or peer evaluations or informal such as with mentoring a junior developer. It is a form of communication designed to provide guidance that helps the other person to grow and achieve their goals. Providing feedback gives insights and identifies areas of improvement. Often it is used to guide those you are leading toward personal and professional growth. To the person receiving the feedback it can be stressful, especially if it is not all positive. It can also be very stressful to the person who is providing the feedback, especially if they are not a confrontational or naturally assertive person. Having a plan of action when providing feedback not only helps the person receive it better but also helps the person providing the feedback. As feedback is a way to help achieve goals the technique for creating effective goals (SMART) can also be applied to providing feedback. To review, SMART stands for Specific, Measurable, Attainable, Relevant, and Time-bound. Applying SMART to feedback will better define what you are getting across and make it more actionable. SMART (Specific, Measurable, Achievable, Relevant, and Time-bound) is a framework most often used in goal setting. However when applied to providing feedback it will enhance the abilities of the person providing the feedback and allow the recipient to better understand what they need to do to achieve their goals. Using this framework ensures that the items coming from the feedback are actionable, well defined, and focused on the issue or goal at hand. Whether you are doing performance plans for those working for you, peer or code reviews, or just mentoring someone who is not as far along as you apply the SMART framework to your feedback and see the improvement in reception and accomplishment. LINKS JOIN US ON PATREON [HTTPS://COMPLETEDEVELOPERPODCAST.COM/?FEED-STATS-URL=AHR0CHM6LY93D3CUCGF0CMVVBI5JB20VQ29TCGXLDGVEZXZLBG9WZXJQB2RJYXN0&FEED-STATS-URL-POST-ID=4207] LEVEL UP FINANCIAL PLANNING [HTTPS://COMPLETEDEVELOPERPODCAST.COM/?FEED-STATS-URL=AHR0CHM6LY93D3CUBGV2ZWX1CGZPBMFUY2LHBHBSYW5UAW5NLMNVBS8%2FY2RW&FEED-STATS-URL-POST-ID=4207] [https://completedeveloperpodcast.com/?feed-stats-post-id=4207]The post SMART Feedback [https://completedeveloperpodcast.com/smart-feedback/] appeared first on Complete Developer Podcast [https://completedeveloperpodcast.com]. Hosted on Acast. See acast.com/privacy [https://acast.com/privacy] for more information.

Database sharding is a process of storing a large database across multiple machines. Because a single machine can only hold and process so much data, eventually some systems will scale beyond the ability of a single machine to handle data. Further, as systems scale, they may also need to split data between machines due to security and location considerations. Database sharding overcomes these problems by splitting the system into smaller chunks, allowing work to either be done in parallel, or only in the locations with the relevant data. Obviously, it matters a lot how you split up your data. For instance, it's unlikely that splitting a customer table based on the customer last name will be as helpful in a large distributed system as it would be to split up customers by location. You probably also want to have shards that are roughly the same size. The idea behind sharding is to improve performance, specifically via parallelization, but it's also helpful if it also provides some resilience to outages. So that will also need to be a consideration when you start thinking about sharding. Database sharding can be a very useful tool for making your application more resilient to load. However, it's complex and you really need to think through it carefully if you are considering using it in your environment. There are several different ways to do it, with different advantages and disadvantages, and these will need to be thoroughly considered before starting. Plus, sharding is actually a fairly drastic operation, requiring support and extra work for the remaining lifetime of your application. This means that you shouldn't really consider it until most other options have been exhausted. LINKS JOIN US ON PATREON [HTTPS://COMPLETEDEVELOPERPODCAST.COM/?FEED-STATS-URL=AHR0CHM6LY93D3CUCGF0CMVVBI5JB20VQ29TCGXLDGVEZXZLBG9WZXJQB2RJYXN0&FEED-STATS-URL-POST-ID=4205] LEVEL UP FINANCIAL PLANNING [HTTPS://COMPLETEDEVELOPERPODCAST.COM/?FEED-STATS-URL=AHR0CHM6LY93D3CUBGV2ZWX1CGZPBMFUY2LHBHBSYW5UAW5NLMNVBS8%2FY2RW&FEED-STATS-URL-POST-ID=4205] [https://completedeveloperpodcast.com/?feed-stats-post-id=4205]The post Database Sharding [https://completedeveloperpodcast.com/database-sharding/] appeared first on Complete Developer Podcast [https://completedeveloperpodcast.com]. Hosted on Acast. See acast.com/privacy [https://acast.com/privacy] for more information.

Effective communication is a vital aspect of any organization or team's success, and one tool that has been proven to be very useful is the Four Square Report. This report is a simple and effective way to communicate information about a project or task to a team or stakeholders. It was originally developed by the U.S. military to help soldiers communicate critical information in a clear and concise manner, and has since been adopted by many organizations and industries. 4 square reports were refined by the construction industry and have since been adapted to fit the needs of software development teams. The reports are based on the idea of breaking down progress and issues into four categories: achievements, roadblocks, plans, and risks. By providing updates on these four areas, the entire team can quickly understand what has been accomplished, what challenges are being faced, what the plans are moving forward, and what potential risks may arise. The effectiveness of 4 square reports lies in their simplicity and clarity. They are quick to create and easy to read, making them ideal for agile development teams that need to keep pace with fast-moving projects. Additionally, by regularly updating the reports, everyone on the team can stay up-to-date on progress and potential issues, allowing for early identification and resolution of problems. The 4 Square Report is a versatile tool that can be used in a variety of situations to help with decision-making and project planning. By considering four key aspects of a project or decision and filling out a simple, visual report, you can gain valuable insights and make informed choices. Remember to identify the most important aspects, be thorough and objective, use the report for collaboration, and revisit it regularly. By using the 4 Square Report effectively, you can increase the chances of success for your projects and decisions, and learn valuable lessons for the future. LINKS JOIN US ON PATREON [HTTPS://COMPLETEDEVELOPERPODCAST.COM/?FEED-STATS-URL=AHR0CHM6LY93D3CUCGF0CMVVBI5JB20VQ29TCGXLDGVEZXZLBG9WZXJQB2RJYXN0&FEED-STATS-URL-POST-ID=4199] LEVEL UP FINANCIAL PLANNING [HTTPS://COMPLETEDEVELOPERPODCAST.COM/?FEED-STATS-URL=AHR0CHM6LY93D3CUBGV2ZWX1CGZPBMFUY2LHBHBSYW5UAW5NLMNVBS8%2FY2RW&FEED-STATS-URL-POST-ID=4199] [https://completedeveloperpodcast.com/?feed-stats-post-id=4199]The post Four Square Reports [https://completedeveloperpodcast.com/four-square-reports/] appeared first on Complete Developer Podcast [https://completedeveloperpodcast.com]. Hosted on Acast. See acast.com/privacy [https://acast.com/privacy] for more information.