Some(Scripting) journal

Writing from the workbench.

Field notes on frontend architecture, Rust, developer tooling, AI, and the decisions that make software easier to evolve.

Showing 6 of 53

  1. 01Using the shad/cn accordion with state in the URLToday we are going to be thinking about ways to deep link using an accordion from shad/cn. There are a few tasks that I will be looking to accomplish.
  2. 02Creating (rfv) the rg, fzf, nvim and bat collaborationThis is a post that I do not really want to take the credit for. Someone named Junegunn Choi write a blog post called Ripgrep integration, a walkthrough
  3. 03Hijacking the right command key (Macbook)When creating the perfect work environment. You sometimes want to customize a few tools. That you cannot always easily customize without a third party. This was an attempt to circumvent that. While going right to the source.
  4. 04Converting Next Pages to App DirectoryUpdating a project that uses the next pages setup to the newer app setup. To slowly learn what is changing and better understand the process.
  5. 05Jumping back into Rust 🦀 after a breakRust is one of the most complicated languages for me to learn. It is not extremely hard to really understand what is going on. It just requires a bit more time and effort. For this post we will start on day one of Comprehensive Rust by Google
  6. 06Beginner Testing & Error Handling in NextJSWhen building for production you want the ability to test everything that you do. Why would you want to do this? To allow your team to continue developing, but maintaining that your application is still working as expected. It is a standard of almost every software company. Even if there are no integration tests. There is usually some sort of static testing involving typescript and eslinting.