The moths of programming are ideas in the software engineering industry that have become pervasive due to virality rather than reality. Although they may have some truth to them, they are often inaccurate, misleading, distracting or even damaging. I call them moths because they flutter around in a programmer's mind, getting in the way of truly good practice.

This chapter covers the topic of strict typing. Is the almost religious adherence to the ideas of strict typing actually justified? What is the origin of this? And is it really as strict as we think it is?

Support the show

• https://tinyurl.com/yc4pP968 (SIGNAL)
• https://www.dinodini.com (WEB)
• https://twitter.com/dndn1011 (DEACTIVATED, please use SIGNAL)
• https://www.youtube.com/dndn1011

The moths of programming are ideas in the software engineering industry that have become pervasive due to virality rather than reality. Although they may have some truth to them, they are often inaccurate, misleading, distracting or even damaging. I call them moths because they flutter around in a programmer's mind, getting in the way of truly good practice.

This chapter covers the topic of integrated development environments. What is the real reason for them? Do they actually help? Are they just a distraction? Asked Clippy for comment, but it declined to respond. I suspect we now know where it retired to.

Support the show

• https://tinyurl.com/yc4pP968 (SIGNAL)
• https://www.dinodini.com (WEB)
• https://twitter.com/dndn1011 (DEACTIVATED, please use SIGNAL)
• https://www.youtube.com/dndn1011

The Moths of Programming With Dino Dini
Chapter 8 - Scripting Languages

The moths of programming are ideas in the software engineering industry that have become pervasive due to virality rather than reality. Although they may have some truth to them, they are often inaccurate, misleading, distracting or even damaging. I call them moths because they flutter around in a programmer's mind, getting in the way of truly good practice.

This chapter covers the topic of scripting languages. What is the real reason for them? Do they reduce reliance on software engineers? Do they actually help? And just now many times do we need to nest a virtual machine inside a virtual machine anyway?

Support the show

• https://tinyurl.com/yc4pP968 (SIGNAL)
• https://www.dinodini.com (WEB)
• https://twitter.com/dndn1011 (DEACTIVATED, please use SIGNAL)
• https://www.youtube.com/dndn1011

In this double length episode, Dino objectively explores Object Orientated Programming, which he views as one of the biggest, if not the biggest, mistakes of software engineering.

OOP considered harmful?

Support the show

• https://tinyurl.com/yc4pP968 (SIGNAL)
• https://www.dinodini.com (WEB)
• https://twitter.com/dndn1011 (DEACTIVATED, please use SIGNAL)
• https://www.youtube.com/dndn1011

Macros have a bad reputation and often derided. As a result, their value and importance in solving real world programming problems is often overlooked, especially by the creators of new languages. Yet it turns out that despite the desperate (and often over complicated) efforts to consign them to history, they still have their place in C and C++ programming, and can be sorely missed in languages such as C# or Java.

Support the Show.

• https://tinyurl.com/yc4pP968 (SIGNAL)
• https://www.dinodini.com (WEB)
• https://twitter.com/dndn1011 (DEACTIVATED, please use SIGNAL)
• https://www.youtube.com/dndn1011

In any social media facilitated discussion about programming the topic of code optimisation with often arise. Anyone who has expertise in low level optimisation are likely to face a choice: being silent or enduring endless accusations of irrelevance and hubris. Most choose the former approach as a more efficient and effective path to take, even if they earn a living developing and maintaining optimising code generators.

The idea that Compilers Optimise Code Better Than Humans is, I argue, another Moth of Programming: an idea that has become popular in software engineering due to virality instead of reality.

Support the show

• https://tinyurl.com/yc4pP968 (SIGNAL)
• https://www.dinodini.com (WEB)
• https://twitter.com/dndn1011 (DEACTIVATED, please use SIGNAL)
• https://www.youtube.com/dndn1011

We often hear the phrase "Don't Reinvent The Wheel" all the time in software engineering, but what does this actually mean, and is it a useful mantra, or just another Moth of Programming?

Support the show

• https://tinyurl.com/yc4pP968 (SIGNAL)
• https://www.dinodini.com (WEB)
• https://twitter.com/dndn1011 (DEACTIVATED, please use SIGNAL)
• https://www.youtube.com/dndn1011

The moths of programming are ideas in the software engineering industry that have become pervasive due to virality rather than reality. Although they may have some truth to them, they are often inaccurate, misleading, distracting or even damaging. I call them moths because they flutter around in a programmer's mind, getting in the way of truly good practice.

Chapter 3 considers the classic moth "Always Comment Your Code".

It is commonly believed, commonly by less experienced programmers, that we should always comment our code. However, it is far better to create code that does not need commenting.

( You can also follow Dino on YouTube https://www.youtube.com/channel/UCd359G69NIqKeS-rP5v04lw )

Support the show

• https://tinyurl.com/yc4pP968 (SIGNAL)
• https://www.dinodini.com (WEB)
• https://twitter.com/dndn1011 (DEACTIVATED, please use SIGNAL)
• https://www.youtube.com/dndn1011