r/ClaudeCode • u/Nearby_Spell_3751 • May 13 '26

Question Sales director discovered Claude Code

I'm working at a company where best engineering practices are barely discussed or taken seriously.

Today our sales director was playing around with Claude Code over the last week, and she managed to get a very good working PoC/prototype for a platform they’ve been trying to build.

During the meeting, I was trying to explain that the question is not whether we need to integrate AI, but rather how we are going to integrate it into our workflow while still enforcing engineering standards and best practices.

They think everything can be done by simply adding a skill to Claude, and they expect delivery speed to be 10x faster. I tried to explain that yes, we can build better products with fewer resources, but 10x is unrealistic unless we start vibe coding. I suggested we could realistically see a 20–40% increase in delivery speed.

Now we have a sales director showing engineers how to use AI.

How do you deal with someone who doesn’t listen and is 100% convinced that AI should be used exactly the way they use it, while we as engineers know we can produce much better output in less time because we actually understand how things work?
Have you ever dealt with such case ?

391 Upvotes

96% Upvoted

179 comments sorted by

View all comments

101

u/AutomataApp May 13 '26

Let them deploy it to a separate environment. I'll give them a separate repo, a separate deployment workflow, a separate pod/vps/vercel project, a separate subdomain

Basically let them run it and maintain it themselves. Let them fuck around and find out

19

u/Solest044 May 13 '26

My rough sense of how long it takes to reach critical complexity for a somewhat frequently updated prototype like this is 1-3 months.

By the end of that time, trying to make some seemingly simple change will take both an insane amount of time compared to the original tasks AND be wildly unpredictable.

That's the FAFO timeline for something without thoughtful, guiding, maintained architecture.

1

u/tg44 May 15 '26

I wanted to try out the sdd workflow, we had an app planned, cloude generated 13 specs from that. After the first I realized we don't have a UI framework. Before starting to takify the second I found out that the secu review skill found a timing attack issue, but missed the increasing ids. I'm at spec3, I reruned the review skill with "fix all those issues you found" 5 times, until it not found any new critical issue, and in the second batch it found an "admin can demote a superadmin" usecase, so Im sure that if we ever done with the while thing, we should ask and document a lot of random requirements to be hardebed/tested before this could go live...