Skip to main content

Posts

LLM System Instructions

Finding the Perfect "System Instructions" for Your LLM-Enhanced Codebase Workflow Hey developers! Today, let's dive into something that many of us face when using Large Language Models (LLMs) in our coding workflow — how to craft the perfect "system instructions" so your LLM can seamlessly assist you with your codebase. If you're like me, you've probably experimented with tools integrating AI capabilities in your workflow. Personally, I built a custom Neovim plugin called code-ai.nvim , designed especially to help me interact with LLMs efficiently. The plugin scans relevant files, bundles them with clear instructions, and sends everything neatly to the LLM. Cool, right? My Neovim Plugin: code-ai.nvim code-ai.nvim was built with a simple yet powerful objective: automate file scanning and sending clear context plus instructions straight to an LLM assistant. It helps me navigate large and complex codebases, quickly pinpoint bugs, refactor legac...
Read more
Recent posts

blackscreen mesa xf86-video-vmware

Solving the Blackscreen Issue Caused by Mesa and xf86-video-vmware Drivers on Arch Linux Arch Linux is loved for its bleeding-edge freshness, supplying you with the latest packages and newest features. But occasionally, this freshness can trigger unexpected issues. Recently, I stumbled into one such scenario—a typical system upgrade caused the dreaded black screen of despair upon booting! After some research, I traced it back to specific driver packages: Mesa and xf86-video-vmware . In this post, I'll guide you through what exactly happened, how the Arch community responded to it, and how I temporarily solved it by preventing these packages from updating. The Black Screen After "pacman -Syu" Like any typical Arch user, I ran the routine command to update my system: sudo pacman -Syu The command completed successfully, and I rebooted confidently. Unfortunately, confidence quickly turned into panic when I was welcomed by an entirely black screen. I initially tho...
Read more

Symfony API Documentation

How to Have Good API Documentation in Symfony How to Have Good API Documentation in Symfony API documentation is one of those things every developer understands is important , but it’s also quite easy to put off until “later”, which (let’s be honest) might never actually happen. Whether you’re building a project solo or as part of a team, good documentation is a lifesaver for both your current self and anyone who might (or will!) work with your API in the future. Why Good API Documentation Matters Let’s set the stage: you’re building an API backend with Symfony, and there’s a frontend team eagerly waiting to hook into your endpoints. Without clear, accessible documentation, every conversation becomes an ad-hoc Q&A session. Details get lost, mistakes creep in, and for every new teammate, the onboarding cost gets higher and higher. Good API docs are like a friendly guide—empowering your frontend team to work independently and confidently. But Do...
Read more

Symfony enable authentication

Enable authentication on Symfony There are many ways to enable authentication on Symfony. The most documented are listed in the documentation (no... really?) . The drawback of those methods is that they tend to push the user to use Doctrine. But I dont use Doctrine on my projects. I wrote the tutorial to show how to do without Doctrine: https://github.com/rakotomandimby/symfony-enable-database-authentication
Read more

Compose Compiler Kotlin

React Native: Compose Compiler and Kotlin version When building my React Native project on EAS build infrastructure, I encountered this error: This version (1.5.15) of the Compose Compiler requires Kotlin version 1.9.25 but you appear to be using Kotlin version 1.9.24 which is not known to be compatible. Solution: upgrade Expo and fix dependencies npx expo install expo@latest npx expo install --fix
Read more

Global AI under attack

Gemini a bit slower when Deepseek under attack (January 2025) In recent weeks, I've noticed a peculiar trend: the Gemini REST API, a widely-used service for developers, has shown signs of latency. Even more troubling are the frequent "503 Overloaded" error messages many have encountered. It seems this degradation in performance corresponds with an attack on Deepseek, another prominent player in the artificial intelligence ecosystem. This notion isn't baseless; after some digging, I stumbled upon a discussion thread where Logan Kilpatrick, a representative voice in the AI community, provided some insights. He mentioned, "Hey folks, we are not moving capacity away from 1.5 models right now. Looks like we might be getting hit by a DDoS attack. Will follow up as we mitigate this." There is a time correlation between Deepseek and Gemini capacity issues The temporal relationship between the issues facing Deepseek and Gemini is hard to ignore....
Read more