I already hate the term ‘vibe coding’.

I already hate the term ‘vibe coding’.

Can't we come up with another term?

-Conversational engineer? (wanky)

-AI Product Architect? (kind or right, but boring)

-Code whisperer? (also wanky, please don't ever, ever call me this 🤣)

Seriously, though... The term 'vibe coding' works for smaller projects and apps... but it doesn't quite sum it up for large-scale development.

An honest timeline of building Ghostart to get to the point of launch next week on 21 November:

-An entire year of very long days and weekends, building and refining.

-2 failed attempts at building Ghostart the year before, both aborted in abject fury (good learning curve for coding with AI, though!)

-30+ years of business experience training people to communicate online, marketing, managing development teams, writing content, editing copy (and writing 3 bestselling novels).

-3 months in beta, learning what features users actually want, use and don't use

Does the term 'vibe coding' undersell the craft? But what *should* we call ourselves if not vibe coders?

++ I'm Nigel, creator of Ghostart. I help professionals develop an authentic presence on Linkedin for career growth, professional development and to raise awareness of their company or brand.