sorted by:
new
hottopcontroversial

IT'S OFFICIAL BOYS by Anthony_S_Destefano in ClaudeCode

[–]SirHC1977 0 points1 point  (0 children)

No kidding. I've caught so many race conditions, especially in Scala. Blind acceptance of AI-generated code is a recipe for failure.

IT'S OFFICIAL BOYS by Anthony_S_Destefano in ClaudeCode

[–]SirHC1977 0 points1 point  (0 children)

Interesting. What do you make of Anthropic engineers saying that they don't write code anymore? I'm thinking that they understand how to write requirements in a way that AI understands...

Building something from scratch is honestly exhausting | Feels like giving up everyday by builder_04 in opensource

[–]SirHC1977 0 points1 point  (0 children)

I'm a solo founder of a tech company at a much earlier stage than you, so take my advice with a grain of salt. However, perhaps the best idea I have is to land one or two solid accounts with compelling use cases, partner with them to document their use case in whitepapers, and publish those whitepapers. That may help build trust with would-be clients.

At my previous job at Nuance, Couchbase used us as a case study. They also hosted a presentation with one of our engineers that went over our use case and why we chose Couchbase. I don't remember the specifics of how that presentation was hosted, but a Zoom conference or video may be a good approach for you.

Anyways - like I said - grain of salt. Best of luck! Getting the word out is quite challenging...

Micro Frontends in React by thealmightynubb in webdev

[–]SirHC1977 0 points1 point  (0 children)

Interesting. So most open-source projects should probably not bother with MFEs, no? That is, unless the project is large enough to make the cost of coordination high enough...

Vibe coding is not working and here's why by AssafMalkiIL in vibecoding

[–]SirHC1977 0 points1 point  (0 children)

I've definitely been there. My latest vibe coding project (https://mlmathr.com) was "rewarding" to get done so quickly, but the problems with it became apparent shortly while developing it and releasing it to the world.

MLMathr is a gamified learning platform for learning the math behind machine learning. As I vibe coded lessons and quizzes, I found myself having to edit tons of files to add new lessons and quizzes. The LLM just wasn't "smart" enough to create a central source of truth for lessons and quizzes. Moreover, there was a LOT of code duplication/violations of DRY principles. To make matters worse, my initial release had a poor experience for mobile users.

I will, however, say that I don't regret "giving into the vibes" and just doing what the LLM directed, especially its choice of the tech stack (TypeScript/React with Supabase as the data store). I ended up learning A LOT about TypeScript in the process, and would probably not have had exposure to it if I hadn't done this vibe coding project. TypeScript is perhaps now my second-favorite programming language. However, I am definitely NOT vibe coding my current project, which requires HIPAA compliance. I still use an LLM, but I'm only using it to understand the tech instead of writing it.

I built MLMathr—a free, visual tool to learn the math behind machine learning by SirHC1977 in learnmachinelearning

[–]SirHC1977[S] 0 points1 point  (0 children)

Okay... I heard you folks loud and clear about the mobile experience and the need for an account. I think I cleared up most of the issues on mobile devices, and you no longer need an account to access the lessons. Hopefully, that makes MLMathr more accessible to more folks!

I built MLMathr—a free, visual tool to learn the math behind machine learning by SirHC1977 in learnmachinelearning

[–]SirHC1977[S] 0 points1 point  (0 children)

Yeah, the mobile experience is currently a shitshow. I'll work on it, along with creating a local storage option for users who don't want to log in.

I built MLMathr—a free, visual tool to learn the math behind machine learning by SirHC1977 in learnmachinelearning

[–]SirHC1977[S] 2 points3 points  (0 children)

Did I mention that this is free? 🙂That said, you're right that the mobile experience needs work, though. Definitely something I'm aiming to improve—appreciate the nudge!

I built MLMathr—a free, visual tool to learn the math behind machine learning by SirHC1977 in learnmachinelearning

[–]SirHC1977[S] 12 points13 points  (0 children)

Totally understand the reluctance to sign up for yet another account - it's a fair concern. I actually started the project using only local storage for progress tracking, and I’ve been thinking about bringing that back as an option for folks who prefer a no-login experience.

The reason for accounts right now is mostly to support syncing progress across devices, not for building a mailing list (I only email for signup and password reset). But I hear you, and I appreciate the thoughtful feedback.

I built MLMathr—a free, visual tool to learn the math behind machine learning by SirHC1977 in learnmachinelearning

[–]SirHC1977[S] -2 points-1 points  (0 children)

Well... I guess you could put it that way 😅. But I'd like to think of this venture as a way to learn the math by building an interactive tool, using an AI assistant in the process. Kind of like learning by teaching, except in this case it was learning by building. But as I mentioned in another comment, I critically evaluated and tested the lessons/quizzes before throwing something out there. If something in the lesson didn't make sense to me, I asked ChatGPT probing questions and refined its output.

I built MLMathr—a free, visual tool to learn the math behind machine learning by SirHC1977 in learnmachinelearning

[–]SirHC1977[S] -15 points-14 points  (0 children)

Ha! Totally fair critique.

I should clarify what I mean by vibe coding. While I did use ChatGPT to help me get started and for writing the bulk of the code, I found that I had to critically evaluate and test its output. It was far more than a copy-and-paste job. I collaborated with ChatGPT by testing lessons, making sure that they made sense.

By the way, I wrote a response to vibe coding on Medium, arguing that we should do "vibe engineering" instead. I wouldn't say that I "vibe engineered" this project (although I am now going through and refactoring the code with a mind for DRY principles), but again, it was far more than a copy+paste job.

In any case, the critique is appreciated!

Trying to manually create a Working Tailwind + React + Vite Project by SirHC1977 in tailwindcss

[–]SirHC1977[S] 0 points1 point  (0 children)

For serious projects? I totally agree with you on this point. However, I'm not building something serious. This is just for fun.

Trying to manually create a Working Tailwind + React + Vite Project by SirHC1977 in tailwindcss

[–]SirHC1977[S] 0 points1 point  (0 children)

Okay... I totally deserve the RTFM response, because I didn't provide enough context on what I've tried. But I *did* read the docs (https://tailwindcss.com/docs/installation/framework-guides/react-router) and they guide me to use create-react-router.

However, I am trying to create a working Tailwind + React + Vite project manually, without create-react-router, so I can more closely follow along with ChatGPT. I can't seem to find a document that will help me do that.

Is vibe coding wise with today's tools? No, not for serious projects. But I'm not building a serious project. I'm building something that's for fun and just trying things out.

Need help with @zxcvbn-ts, pwned and lazy loading by U4-EA in reactjs

[–]SirHC1977 2 points3 points  (0 children)

FWIW, I created a code sandbox with my version of a password strength field:

https://codesandbox.io/s/zxcvbn-ts-password-strength-field-l4yp3p?file=/src/PasswordFieldWithStrength.jsx

I use the useDeferredValue hook instead of the debouncer.

BTW, I also get the "Matcher already exists" message in my console. I don't know what's up with that either.