Has anyone found a efficient way to avoid repeating the initial codebase assessment when working with large projects?
There are several projects on GitHub that attempt to tackle context and memory limitations, but I haven’t found one that consistently works well in practice.
My current workaround is to maintain a set of Markdown files, each covering a specific subsystem or area of the application. Depending on the task, I provide only the relevant documents to Claude Code to limit the context scope. It works reasonably well, but it still feels like a manual and fragile solution.
I’m interested in more robust strategies for persistent project context or structured codebase understanding.
I moved back to Arch Linux after my 11 months old MBP died and took over a month to get it fixed. Not really looking at going back to macOS.
There are no aspect of the Apple OS that I miss and Linux desktop just works nowadays.
Some years ago I stumbled across pictures of Pazyryk mummies and I felt a stong emotional connection with the style of the drawings, especially the magical animals.
I decided to get the animals tattooed on my arms and I Will continue with the upper body and the legs.
But wasn't Iran already docile to America? Sure, it wasn't a crystal clear ally like Saudi or the Gulf states, but behind the anti-Zionist propaganda and "evil US" blabbering, there were decades of backchannel negotiations, regional pragmatism, and even moments of cooperation — especially when mutual interests aligned, like in post-Taliban Afghanistan or the fight against ISIS.
It didn't work for me. I spent ~2 years trying to learn German and all I managed to retain are a bunch of nouns, verbs and adjectives. I am still unable to speak properly, let alone read a newspaper article. I suspect that the Duolingo "teaching style" does not work for me. It also depends on the objectives, since I was more interested in some kind of fluency as opposed to being able to read or write in German.
I am the maintainer of beanborg (https://github.com/luciano-fiandesio/beanborg), a set of scripts for automated categorization of financial transactions on top of beancount. Using plaintext accounting in the last 5 years has dramatically improved my family's financial health.
Unfortunately, plaintext accounting is not for everyone.
I noticed that there is a big gap in this space, especially for European users. There are several personal finance applications, but they seem to integrate mostly with US banks and, in general, they seem to be very dollar-centric.
So, I'm working on a simple app to manage personal finance, based on the concept of double-entry accounting with features like budgeting, projections and data analysis.
There are a lot of privacy-related considerations, so for the time being I will eat my own dogfood and offer it to close friends. Let's see how it goes!
SEEKING WORK | Remote Work | Worldwide Availability (EU-based)
Strong fullstack software engineer with 20+ years of experience. Stack: Kafka, K8, AWS/Azure, Postgres, API design. Very experienced on JVM optimization and perf tuning.
SEEKING WORK | Remote Work | Worldwide Availability (EU-based)
Strong fullstack software engineer with 20+ years of experience. Stack: Kafka, K8, AWS/Azure, Postgres, API design. Very experienced on JVM optimization and perf tuning.
SEEKING WORK | Remote Work | Worldwide Availability (EU-based)
Strong fullstack software engineer with 20+ years of experience.
Stack: Kafka, K8, AWS/Azure, Postgres, API design. Very experienced on JVM optimization and perf tuning.
I wonder how does he actually work as a digital nomad. Internet on DB trains is massively unreliable, there are entire patches of country that are not covered by mobile signal.
There are several projects on GitHub that attempt to tackle context and memory limitations, but I haven’t found one that consistently works well in practice.
My current workaround is to maintain a set of Markdown files, each covering a specific subsystem or area of the application. Depending on the task, I provide only the relevant documents to Claude Code to limit the context scope. It works reasonably well, but it still feels like a manual and fragile solution. I’m interested in more robust strategies for persistent project context or structured codebase understanding.