#testability — Public Fediverse posts

I've been playing with #Github #Copilot as more than just fancy tab-completion in my editor. This will annoy many people. I agree with most of them on most things. I agree that people responsible for the production of code should think carefully about the code. They should value #readability, #maintainability, #testability etc. I agree that some ways of using #AI for coding are just terrible practice. I just don't think that all AI use is inherently evil.

https://dev.to/drhyde/god-is-my-copilot-copilot-is-my-new-god-5h6i

#GithubCopilot

Have you ever wondered how to measure #CognitiveLoad? There is no standardized scientific method for measuring it. However, for teams involved in software delivery and operations, we can ask about their understanding of the software, business domain, and user needs. By identifying factors that contribute to increased cognitive load, such as #testability, #operability, prioritization difficulties, and domain complexity, we can work towards alleviating these challenges.

I can't quite convince myself yet that all inheritance/coupling is intrinsically bad, but I'm more and more recognising abstract base classes (ABCs) and #mixin classes as anti-patterns because they hinder #testability, which to me is key to quality software; #ABCs and mixins are by construction impossible to test on their own, and both patterns only make sense if a language supports inheritance, so it seems that the simplest option to avoid them is to get rid of inheritance altogether.