Vibe Composing (Pt. 2) - The "boring" but exciting parts

After some back and forth with learning and reading all I needed for the project I finally dipped my hands into installing things and creating my project. This was a wild ride because I asked  A.I to create a python project for me. The wild ride begins!

Photo created with Google Imagen

The amazing triviality

So I asked the LLM to create a Python project and use the UV package manager. UV was not installed and I had to install it. Unlike Cursor which would have installed it for me CoPilot did not, just gave me the command and I applied it myself. And then the picture below happened.

Screenshot from my own machine

The project was created and it even "read my thoughts" and what I meant with RAG and added the relevant description. At this point my mind is blown. Obviously previous context was responsible for the description and yet it was pretty amazing.

The rest of the project was completed mostly with completions because I had to practice my Python skills. However even for that the AI in the IDE was very helpful.

The final act was to update the project.toml file


Screenshot from my own machine

Final Thoughts

Vibe coding and in fact composing is all the buzz, or is it? As someone pointed, we who try these new tools may be living in an echo chamber and see only vibe coding around us. Be that as it may, more and more tools leveraging A.I agents come out every day (cline, roo code and taskmaster  to name a few) and the future of coding will inevitably be governed by coding agents supervised (at least at first) by human developers.

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