Alberto on code life

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...

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! 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...

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 ...

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) ...