Complete Developer Podcast – Détails, épisodes et analyse

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.

The post A Farewell To Our Fans appeared first on Complete Developer Podcast.

Hosted on Acast. See 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.

The post Preempting System Issues appeared first on Complete Developer Podcast.

Hosted on Acast. See acast.com/privacy for more information.

File transfer protocols can begin to look like alphabet soup when you first start learning about them, or even after you've been a developer for a while.

The post File Transfer Protocols appeared first on Complete Developer Podcast.

Hosted on Acast. See acast.com/privacy for more information.

How to approach other developers when you have found something horribly wrong with their code in a way that doesn't create conflict in your team.

The post Your Code Sucks appeared first on Complete Developer Podcast.

Hosted on Acast. See acast.com/privacy for more information.

Unexpected outages happen all the time. We've had them happen while recording the podcast several times. Having a plan of action when an unexpected power outage or internet outage occurs allows you to remain focused and productive.

The post Staying Productive During Outages appeared first on Complete Developer Podcast.

Hosted on Acast. See acast.com/privacy for more information.

Great friends, exceptional leaders, and champions of those who can't fight for themselves, the Enneagram Type 8 or The Challenger stands alone. They want to be independent, not indebted to anyone and do not let the opinions of others sway them.

The post Enneagram Type 8: The Challenger appeared first on Complete Developer Podcast.

Hosted on Acast. See acast.com/privacy for more information.

While there is a lot of misplaced hype about tools that will replace programmers, there are a lot of tools that can handle a lot of the mundane, boring code that many developers have to write. Low code and no code tools can often make it easy to stand up small applications that meet a business need, but aren't worth the expense of hiring a professional developer.

The post Low Code No Code appeared first on Complete Developer Podcast.

Hosted on Acast. See acast.com/privacy for more information.

A fixed mind is rigid and inflexible, unable to accept change or anything that challenges currently held views. A growth mindset looks to learn and improve through challenges and even failures to better themselves.

The post Fixed Vs Growth Mindset appeared first on Complete Developer Podcast.

Hosted on Acast. See acast.com/privacy for more information.

Relationships end, some break-ups are mutual with both people seeing the relationship as over. Other times one person is done and the other is not. This leads to grief over the loss of the relationship.

The post Surviving A Breakup appeared first on Complete Developer Podcast.

Hosted on Acast. See acast.com/privacy for more information.

In the early days of development configuring an application for deployment was a huge amount of work and was often encapsulated in installation programs that were complicated, error-prone, and could often destabilize other applications on the machine. In more modern software development, we've started to use container technology to fix these old problems, as well as to deal with some new ones.

The post The Benefits of Containers appeared first on Complete Developer Podcast.

Hosted on Acast. See acast.com/privacy for more information.