Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

My chatbot builder is over-engineered and I love it

fastmind.ai

Post reply on HN
Print view View original

1–10 of 14 posts

Re: My chatbot builder is over-engineered and I love it

#3

Post by toomuchtodo »

efilife wrote: post #2

What a great read. I love how much info about it is revealed and all of the advice. Makes me feel a bit better about my unreleased software that I think people would find useful

When in doubt, ship it. Some may get value, and ignore anyone who is providing criticism that is less than constructive. Please consider shipping that unreleased software.

Re: My chatbot builder is over-engineered and I love it

#6

Post by yding »

funfunfunction wrote: post #4

This is cool! I don’t see many people doing write ups on their tech stack as much any more. It’s nice to see the inside of a production-grade app like this. I’m curious, why command+r for the model? What benefits does it have over other SOTA models?

The short answer is he works at Cohere. But longer answer is that the model probably doesn’t matter that much.

Re: My chatbot builder is over-engineered and I love it

#8

Post by ffsm8 »

Oh man, reading this article gives me mixed feelings.

I think they're fundamentally misunderstanding where the over engineered critique generally comes from. I've done my fair share of over engineered software, because it's frickin fun to make them, especially if you're working alone or with 1-2 other people.

The issue from these projects pop up later, after we moved on to the next project or employer and other (usually junior) people need to support this. From the Greenfield developer POV, I love that as well. It's just bad for the business, not for the developer (it's called resume driven development for a reason)

Re: My chatbot builder is over-engineered and I love it

#9

Post by Knajjars »

ffsm8 wrote: post #8

Oh man, reading this article gives me mixed feelings. I think they're fundamentally misunderstanding where the over engineered critique generally comes from. I've done my fair share of over engineered software, because it's frickin fun to make them, especially if you're working alone or with 1-2 other people. The issue from these projects pop up later, after we moved on to the next project or employer and other (usua…

Hi there, I'm the author of the blog post. I realize I could have explained "over-engineering" more clearly. I don't mean it in a technical sense, but rather that I approached the project more like an engineer than a founder. The key takeaway is to learn when to take off your engineer hat and think like a founder instead.
Post reply on HN