I don't get many chances to play tennis. Between work, everyday constraints, and lately some pretty uncooperative weather, court time is rare and valuable. So when I finally found a slot that worked β and the booking system refused to give it back β frustration set in fast.
Note: A π«π· French version of this post is available on Sciam's blog (my employer). Like many developers, my life is littered with unfinished side projects. But this time was different. This time, I had GitHub Copilot as my coding companion, and I actually finished. Let me tell you how AI-assisted development helped me build a gift card management application that I actually use every day β and I did it almost entirely without opening an IDE.
I've used Git Flow on quite a few projects over the years β and honestly, I've reached a point where I don't think it's the right choice for most modern teams anymore. It's not that Git Flow was bad. In fact, when Vincent Driessen came up with it back in 2010, it made a lot of sense. We didn't have solid CI/CD pipelines yet. Releases were manual. Teams were smaller and slower. Having a clean branching model for "features," "releases," and "hotfixes" was a huge step forward at the time. But now?...
I left Red Hat a few months ago and joined Sciam, but I had to return my corporate laptop. To maintain my workstation setup, I decided to reuse my old Dell XPS and migrate my data from one laptop to another. After installing a fresh Fedora system on the XPS, everything seemed fine initially, but some unexpected issues arose afterward.
Reading the article β4 Fallacious Reasons Why We Estimateβ, I felt it missed the most important part of why we estimate. The article seemed to suggest that estimation is only fraught with drawbacks and is ultimately useless. However, from my experience working with various teams at Red Hat, I believe that estimation holds significant value, albeit for reasons that might not be immediately apparent. In this blog post, I will delve into why we estimate, addressing misconceptions and highlighting...
Summer is heating up in the Eclipse Che ecosystem. More contributors, including Red Hat and SAP, are joining the Che adventure. Everyone is working hard on Che improvements, such as implementing the Language Server Protocol and multi-container workspaces. But they are not the only ones working this summer. Earlier this year, Florent and I submitted a few ideas to the Google Summer of Code (GSoC). The GSoC is a program organized by Google to encourage students to be more involved in open-source...
This blog post will soon be available in French on the Serli blog site. Once again, I spent a fantastic week at EclipseCon France in Toulouse. A huge thank you to the Eclipse Foundation for organizing this amazing event! This year, I learned a lot and had many interesting discussions about Eclipse technologies.
This year, I am participating in Google Summer of Code as a mentor for the Eclipse umbrella organization. I've submitted a few ideas about Eclipse Che and Eclipse Flux, and some of them have been selected. I am mentoring the project "Pair Programming with Eclipse Che," which involves improving an existing prototype I demonstrated at various developer conferences. You can check out the GitHub pair programming Che extension. A few days ago, my padawan Randika encountered issues setting up his...
Just got back from an amazing Jug Summercamp at La Rochelle. I was ready for the presentation of the Live Pair Programming with Eclipse Cloud Development and ... AGAIN! I faced display issues with the external VGA projector not being detected on my computer, the same issue I encountered a few months ago at Eclipse Con France. Hereβs how I managed to resolve it.
Hello everyone! I'm starting my new blog site. This blog site is hosted by Github Pages and uses Jekyll as the blog engine. For this first blog post, let's see how to create such a blog post: I'm going to detail all the steps to create a blog site with Jekyll, Github Pages, Docker, Eclipse Che cloud IDE, and Codenvy.