Hit a perfect 7-day streak this week, splitting my time between a massive aesthetic pivot in my Neovim config and a relentless testing marathon for openslate. With 22 commits and 10 PRs, I managed to delete over 2,000 lines of code while shipping a more stable integration layer.
TL;DR
There is something deeply satisfying about a week that ends with a net-positive refactor and a perfect 7-day streak. I spent the last seven days oscillating between the purely aesthetic—tearing down and rebuilding my Neovim environment—and the purely functional—writing enough integration tests for openslate to sleep soundly at night. Between 22 commits and 10 PRs, I touched everything from Lua config files to Svelte components and network retry logic.
What I Built
The Neovim Pivot (nvim)
If you’re like me, your editor is a living organism. This week, I decided it was time for a major evolution. I pushed 21 commits to my nvim repo, which resulted in about 3,200 additions and 2,000 deletions. That’s a lot of churn for a config, but the result was worth it: I’ve fully pivoted to a "Kanagawa modern-minimal" aesthetic.
I spent a significant chunk of time in lua/plugins and lua/config, cleaning up my <leader> notation and ensuring the UI felt snappy. I even updated the title logo and added a site HTML file to the repo. Most of the heavy lifting was actually maintenance—I have a CI job that updates all plugins to the latest versions, and I spent a few sessions manually resolving the fallout from those updates. There’s a specific kind of peace that comes from applying whitespace and lint fixes across 42 changed files. It’s the digital equivalent of vacuuming your office; you don’t realize how much the clutter was bothering you until it’s gone.
Hardening the Core (openslate)
While the Neovim work was about "feel," my work on openslate was all about "fact." I’m currently in the middle of a massive testing push. Even though the commit count looks low on the main branch, the PR activity tells the real story. I’m building out a robust integration suite to cover the entire application lifecycle.
I spent a lot of time in api/src, specifically focusing on authentication. I merged a critical PR that asserts the auth middleware returns a 401 when no cookie is present—it’s a small thing, but it’s the foundation of the whole security model. I also have several open PRs right now that cover the signup and signin flows, ensuring that the first user created actually gets the correct cookie back.
One of the trickier parts of the week was working on the build_fts_query logic. Full-text search (FTS) is always a bit of a nightmare when it comes to wildcard and quoting rules. I opened a PR specifically to test those edge cases because I noticed some weird behavior when users tried to search with special characters. Better to catch that in a test suite than in a bug report.
Pull Requests & Pipeline Fixes
This was a heavy PR week. I opened 10 in total, and they really represent the "breadth" of my current projects.
Over at opensre, I tackled a frustrating UI bug. I noticed that the interactive shell loading bar wasn't spinning while the LLM was doing its investigation. There’s nothing worse than staring at a static screen wondering if the backend has died or if it’s just thinking. I submitted a fix with about 150 lines of changes to ensure the progress state is correctly reflected in the terminal. Even though that PR is currently closed, the investigation into why the state wasn't bubbling up was a great deep dive into the shell's event loop.
I also spent some time on DevNotion (the very tool I'm using to track this!). I opened a PR to handle transient network errors during the "harvest" phase. When you're pulling data from multiple APIs, something is bound to flake out. Adding a retry strategy and a secure deployment plan (about 800 lines of new code) makes the whole system feel much more "production-ready" and less like a weekend hack.
The Tech Stack & The Streak
Looking at the language breakdown for the week, it’s a bit of a polyglot explosion. While Lua dominated my commit count because of the Neovim refactor, the actual logic was spread across TypeScript, Svelte, and a bit of Python.
The additions-to-deletions ratio (3226 vs 2063) is exactly where I like it to be during a refactor week. It shows that I’m not just piling on new features; I’m actively removing the old, brittle parts of the codebase to make room for the new stuff.
And then there’s the streak. Seven straight days of commits. It wasn't a forced grind; it was just one of those weeks where every time I sat down, there was something clear and actionable to do. Whether it was a 2am tweak to a Kanagawa color highlight or a mid-afternoon integration test for a media MIME filter, the momentum stayed high.
What's Next
Next week is all about closing the loop. I have a mountain of open PRs in openslate—everything from the command palette styling to the media DB filters. My goal is to get the integration test suite merged so I can start building out the next set of features on top of a "green" CI pipeline.
I’m also planning to dive deeper into the DevNotion harvest logic. Now that the retry strategy is in place, I want to see if I can optimize the data fetching to be a bit more parallel.
Until then, I’ll be enjoying the new, minimal look of my editor. It’s amazing how a fresh coat of paint can make you want to write another thousand lines of code. See you all next week!
Yash K Saini — Engineer, building in public — AI/ML, low-level (Rust/C/C++), and open source.
GitHub · X · LinkedIn · Portfolio
Generated by DevNotion
United States
NORTH AMERICA
Related News
Secret Claude Tracker Shocks Users After Anthropic's Anti-Surveillance Stance
12h ago
EV Batteries Defy Expectations, Last Hundreds of Thousands of Miles
1d ago
GBase 8a Performance Anomaly Case Study: How a Single Parameter Change Sparked a Chain Reaction
1d ago
Who Else Has Inherited a Codebase With Zero Comments and a Prayer?
1d ago
完美的平庸
3h ago