Vibe Coding? No! Vibe Composing! (Pt.1)

If you are a developer you are (probably and hopefully) familiar or have tried to apply Vibe Coding in your day to day workflow. If you haven't I suggest you give it a shot. It is not a solution for everything but is is one more tool in your belt.

Apart from the coding itself though what else can we do inside our IDE that we didn't even think of doing before? This is the first of a series of short posts on my experience in Vibe Composing  rather than Vibe Coding.

Consider the following premise; You are given a requirements document from your product manager. The document will probably be a few pages (tens) long. You don't really have time to read all this. You may even ask some A.I chat to summarize it. However, what if you could load the document in your A.I assisted IDE and ask your friendly chat agent to operate based on that document? Fantasy? Reality!

A.I Emergence
Photo by A.I

Enter personal project

While at a crossroads on my career I had some free time to think about what is the next thing I would like to learn. The main topic everywhere I look is development with or in or over A.I, so I though about a neat "little" project to scan, fix and enhance product descriptions of my wife's Etsy store with A.I or LLMs. And that is were the adventure started. 

For starters I manually made a sequence diagram with Mermaid

Mermaid based Sequence Diagram
Sequence Diagram


Then I went over to Perplexity and I asked: Create a project description based on this sequence diagram. Identify any missing parts. What I got back was a markdown file looking as such


Next I installed the GitHub official MCP server into my Visual Studio code, put GitHub copilot in agent mode and asked it to create issues in my GitHub repo based on the document and Voila!

Github issues mase by Copilot
GitHub Issues create with CoPilot

Troubleshooting tips

I am using a Linux machine for my private development projects. Here are some troubleshooting tips
  • Make sure your docker command does not need to run sudo to operate.
  • Your machine user name and your GitHub user name might not be the same. On the prompt to CoPilot provide your project's GitHub URL.
  • If you are using a Linux machine with Snap make sure your VSCode installation is not a snap package. If so, uninstall it and reinstall it using your regular package manager. Your settings will not be lost.

That is all for now. Next up, the coding parts! Stay tuned!

Popular posts from this blog

NUnit Console Runner and NLog extension logging for your tests

Image
Have you experienced the frustration of tests running perfectly well on your local machine and then failing in CI? This all too familiar "It worked on my machine" comes to mind. You set off to investigate and after a while you realize you are too far into the rabbit hole between code and logs in Kibana and this investigation is getting you nowhere. Wouldn't it be nice if you could hijack the logger and print the logs in the test runner's console? TL;DR NLog can be extended easily and NUnit  Console Runner does not play well with simple console logs.   Photo by  Kaboompics .com  from  Pexels Enter Console logging In .Net in general it is not advisable to log to console in a multi-threaded environment, because the console is not thread safe. While logging simple strings may not cause any problems logging strings with interpolated variables may very well be sub optimal to say the least. Should you use any such debugging technique you are better off with a thread ...
Read more

Tests code coverage in Visual Studio Code with C# and .Net Core

Image
While writing tests for you code goes without saying, there is much to be said about code coverage of tests. How much of your code is actually covered by these tens of tests you just wrote? If you work in a TDD approach most probably you don't have such "mundane" questions. Of course you code is 100% covered. You did make sure every test failed before you added that line in your code to make it pass... and that conditional statement... or did you? While purists would argue there is no chance of no coverage I beg to differ. Let alone if you write your tests after the code is written... After such and such years and experience in the industry when we are nearing deadlines some things are thrown out the window. They shouldn't but they are. TL;DR tools help with coverage. In this case .Net Core Test Explorer with coverlet and Coverage Gutters . Photo by  Startup Stock Photos  from  Pexels Coverlet to the rescue As I blogged a while ago I have made myself a warm ...
Read more

Visual Studio Code setup I use for C# development

Image
Visual Studio Code has been around a while. However most of the extensions or blog posts out there relate mainly to extensions that facilitate development in JavaScript environments such as Angular, React or NodeJs (to name a few) and even Rust! The IDE is getting great reviews as being fast to load and very responsive as opposed to its bloated and heavy bigger brother, Visual Studio. TL;DR I switched from Visual Studio for good Having worked on Visual Studio since version 4.2 I was used to it being heavy to load and at times even slow to respond. After experiencing VS Code with a little bit of NodeJs development I decided to try and make it my daily driver for .Net Core and C# development. I sought to find extensions to ease my day in the cubicle and see how comfortable will I be with it. I would give it a month on various tasks and workloads. VSCode showing off extensions The month became two months and then 3 months and here I am with a list of very handy (in my opinion) ...
Read more