A lack of certain skill sets should not be an inhibitor to making changes and tweaks to embedded systems, but there are risks in deploying code that you don’t fully understand, even if an AI model has helped you to generate it.
Many would argue that the term ‘vibe coding’ is unhelpful and overly casual, evoking an image of drinking whiskey and then writing stream-of-consciousness code, but there is a genuine sense in which the approach described in this particular case study has much in common with project management.
The aforementioned case study concerns an individual who used an AI platform to make changes to an existing Arduino sketch, gaining the necessary insights to a level of coding they would not otherwise have had, in order to make a series of adjustments they wanted to make to a project.
There are clear risks and variables here, but unpack the phrase ‘vibe coding’ and the truth is that many more experienced coders than myself have admonished coders to get their priorities right when it comes to writing often very complex code.
