Denis 'GeneralGDA' Gladkiy

Denis 'GeneralGDA' Gladkiy

Software Engineer at Aiclo

About

Creator of Seamcult, engineer on Aiclo. Computer graphics programmer.

Badges

Tastemaker
Tastemaker
Gone streaking 10
Gone streaking 10
Gone streaking
Gone streaking
Gone streaking 5
Gone streaking 5

Maker History

  • Seamcult
    SeamcultA pattern design tool for the LLM era ('paper' for patterns)
    Nov 2026
  • Aiclo
    AicloAI-powered platform for custom clothing design.
    Nov 2025
  • 🎉
    Joined Product HuntNovember 12th, 2025

Forums

Why is imperfect AI fine for code but not for pattern making?

I'm a software engineer in garment CAD, and I work with pattern makers every day. Their job takes a lot of engineering thinking honestly, it's much closer to programming than most people would guess.

AI almost never writes perfect code either. Who cares? It still removes a huge amount of routine work, and the programmer polishes the rest by hand. Sometimes the output is bad, but it's so fast and cheap that it hardly matters. A $100/month subscription is a small fraction of what a pattern maker or an engineer earns, so it pays off even if it saves just a little time.

So I'm puzzled by how many pattern makers dismiss AI with "It can't produce a perfect result from a single prompt!" Of course it can't. So what? Why is that limitation fine in programming but a dealbreaker in pattern making?

Pattern makers here what would AI have to do to earn a place in your workflow?

Is your product really ready to ship, or are you just trusting your QA report?

Shipping software isn't just about passing functional tests.

Localization issues, accessibility gaps, and bugs across different devices can easily slip through the cracks.

Most teams still rely on separate reports to make one big release decision.

Curious to hear from founders, QA engineers, and developers:

Unpopular opinion: "Build in public" is slowly becoming an echo chamber.

Don't get me wrong sharing progress is great for accountability.

But lately, it feels like 90% of "build in public" posts are just founders selling tools, templates, or courses to other founders, rather than talking to actual end-users.

If your target customer isn't an indie hacker, posting MRR screenshots on X won't move the needle.

View more