Home
Feed

Extend

Hashnode Pro
Hashnode for Agents

Resources

The foreword
Hashnode gql skill

Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Discussion on "Code Smell 47 - Diagrams" | Hashnode

Feed/

Discussion

Maxi Contieri

Software Engineer

Dec 9, 2020

Code Smell 47 - Diagrams

Diagrams are not code. They cannot be a code smell. They are just Diagram Smells. TL;DR: Don't use diagrams. They are obsolete and dead. Problems Maintainability Trash code Code Duplication Diagrams focus only on structure (accidental) and not ...

maximilianocontieri.com2 min read

#programming #code-smell #clean-code #2articles1week #software-design

Responses1

Markdown supported · ⌘↵ to post

Chris Bongers

Looking to get into development? As a full-stack developer I guide you on this journey and give you bite sized tips every single day 👊

Dec 9, 2020

I tend to disagree, we still use diagrams and functional designs to help understand the semi/non-technical client what we are building.

It's a decent way to validate if what we are going to build is what they envisioned.

We rather spend the hour making the diagram and functional designs than building something only to realize it's not what they wanted.

Maxi Contieri

Software Engineer

Dec 9, 2020

Sure !

But you use diagrams to talk to other humans. That's a very valid scenario.

I prefer to validate what user wants using TDD.

The main problem with diagrams is that you discuss DATA with users. And data is accidental. You need to discuss behavior with them. And, IMHO, functional tests and acceptance tests are better for it.

We can validate rapid prototyping and validations with diagrams or Acceptance tests. I prefer the latter.