This is a super valuable reference! Wish I’d seen something like this last year. 😆 All the issues you called out are painfully familiar, and I’ll add one more: AI building code that cannot run in production, because it triggers server timeouts. Now I always consider the need for background processing when building my specifications docs.
Jenny, we have arrived on Substack and would love to talk to you about reposting this story in the Code Like A Girl Substack Publication. If you shoot us an email to info@codelikeagirl.io, we can share how it would work.
Such a needed post, Jenny. With the current love–hate relationship people have with vibe coding, I really appreciate how you embrace it as a developer while also taking things at face value and showing others how to do it right & what to watch out for.
Thanks so much, Daria! I’m amazed by how many great ideas and prototypes non-technical folks like you are generating, and these voices deserve to be heard.
Developers may feel conflicted about vibe coding, but they can’t gate it for long. Better to embrace the change and join in.
Impressive breakdown. This is the kind of experience you don’t get just by trying it a couple of times. It feels like an entire different role and set of skills. It’s beyond traditional software development.
This right here shows me what software development roles might look like in the future.
Not yet….still coding the traditional way but using ChatGPT heavily in the process. I really need to start using a coding tool and giving it a try though
Interesting! I’ve been using AI to write standalone functions when I suspect it would take me longer to figure out the algorithm. For example, “write me a function that takes the current date and a previous date and tells me if the current date has passed Friday 11:59 PM.” I also ask it to help me figure out a coding pattern. Like “how do I validate an input matches certain values in JavaScript similar to Typescript enum.” Your article inspired me to ask it to look for security flaws in code I’ve written. Thanks!
I haven't vibe coded yet but I'm going to try soon☺️😎 let's see what happens.
Haha yes, let's see!
I'll share what happens with you.
This is a super valuable reference! Wish I’d seen something like this last year. 😆 All the issues you called out are painfully familiar, and I’ll add one more: AI building code that cannot run in production, because it triggers server timeouts. Now I always consider the need for background processing when building my specifications docs.
Thank you, Karen!
I’ve definitely run into those timeouts myself lol, I ended up adopting a simple queuing system to handle the load without too much tech overhead.
Feel free to check out the free list, would love to chat more about building soon!
Sounds great! 🤗
I have an ex-apple dev friend who snubs on Vibe Coding, also won't even sign up to test my platform because of "security"
It is what it is :)
Ahh no surprises if you experience that :)
I see this as the curse of knowledge, it’s fair judgement but will cost a lot more down the road.
absolutely.
people are always scared of what they don't know.
Excellent piece, Jenny! You packed a lot of value in that article. Saving it for reference.
Thank you, Veronica! I’m so glad it resonated with you. Keep me posted on how your product building goes, would love to hear more!
Of course, I will. Kind of you to ask.
That’s a guide for vibecoding
Thanks Farida :)
Great write-up Jenny, will be sharing this for sure!
Thank you Jonas!
Thanks for breaking this down in a simplified way.
Thank you Sharyph!
Jenny, we have arrived on Substack and would love to talk to you about reposting this story in the Code Like A Girl Substack Publication. If you shoot us an email to info@codelikeagirl.io, we can share how it would work.
I would do it right away!
Amazing. I have replied to your email!
Such a needed post, Jenny. With the current love–hate relationship people have with vibe coding, I really appreciate how you embrace it as a developer while also taking things at face value and showing others how to do it right & what to watch out for.
Thanks so much, Daria! I’m amazed by how many great ideas and prototypes non-technical folks like you are generating, and these voices deserve to be heard.
Developers may feel conflicted about vibe coding, but they can’t gate it for long. Better to embrace the change and join in.
Impressive breakdown. This is the kind of experience you don’t get just by trying it a couple of times. It feels like an entire different role and set of skills. It’s beyond traditional software development.
This right here shows me what software development roles might look like in the future.
Thank you Diego! Appreciate the comment. Do you vibe code?
Not yet….still coding the traditional way but using ChatGPT heavily in the process. I really need to start using a coding tool and giving it a try though
Haha let me know how it goes!
Interesting! I’ve been using AI to write standalone functions when I suspect it would take me longer to figure out the algorithm. For example, “write me a function that takes the current date and a previous date and tells me if the current date has passed Friday 11:59 PM.” I also ask it to help me figure out a coding pattern. Like “how do I validate an input matches certain values in JavaScript similar to Typescript enum.” Your article inspired me to ask it to look for security flaws in code I’ve written. Thanks!
You are welcome Miguel! Yes absolutely try it.
I’d be curious to see how you find it with the depth of your expertise!