• Have converged onto a DE agnostic workflow.
• need only a few keybinds to help me move across windows and monitors.
• window estate management is done via emacs and tmux : don’t really need a tiling wm.
• opencode when I’m not learning anything and mostly know what needs to be done.
  • open a bunch of these in multiple tmux panes and you’re good.
• a vim-keybinds enabled browser

“For years, I’ve defended lisp in pragmatism oriented SWE back and forths with ’they’re all an AST underneath, anyway..”

Now that I’m writing lisp on the job, I’m in a “gotta catch’em all” kinda mood and thinking of elaborating upon the eccentricities in my upcoming blogs and videos.

There’s a lot of questions I have:
- when do you deploy which one?
- are there any bad ones?
- why does that one exist?
- ..

• I’d always wanted to write production lisp: was dreaming about it since sophomore year of uni (~7 years to that): finally.., we’re here
• going to start work on goose : along the way, chasing that lisp flow/enlightenment I once experienced long ago
• post discussions with some folks, clojure isn’t supposed the vanilla lisp and aspects orthogonal to that mindset await to be grasped
• going for a focused burst of immersion (practical coupled with a literature sweep (blogs, papers, books)) to really get a feel for what’s up
• have been going easy for the past couple of years when it comes to levelling up on my lisp speak because there was always some work I had to get done
• interesting that this is work now, long way..

Onboarding my next batch of hobbies you would sorta care about:

• software defined radio - was gifted (I asked for it explicitly) an RTL SDR kit
• hacking - hacking the art of exploitation is my bedtime read
• operating systems : writing an operating system - is what I promised my the (bit-mage)’s viewers lately : a promise, is a promise
• random wikipedia : I’m bored of the world and sorta intellectually hangry

stuff you wouldn’t care about:

This video explores a productivity workflow in Emacs that leverages window opacity, moving it beyond a purely aesthetic feature. The creator demonstrates how a translucent Emacs frame can be used as an overlay to view and control background applications, improving efficiency and saving screen real estate.

This video is the second part (0x1) of a series on writing an operating system. The creator, Raj, details the comprehensive studying and logging strategy he has designed to tackle this long-term project. The goal is to create a structured approach that fosters deep understanding, maintains motivation, and effectively manages the vast scope of the endeavor.

This video serves as an announcement and introduction to a new, long-term project: Operating System Development (OSDev). The creator, Raj, explains his motivations for taking on this formidable challenge, his plan for documenting the journey, and the tools he intends to use.

Why OSDev? The Motivation for a New Challenge

• [00:00:15] Raj explains he’s been feeling bored with typical software engineering projects, which often feel too easy, especially with the rise of powerful LLMs.
• [00:01:21] He was seeking a “formidable project” that would genuinely challenge him and couldn’t be easily solved by an AI tool.
• [00:03:00] A primary driver is a personal quest to feel competent. He believes that successfully building an operating system will cement his confidence as an engineer.
• [00:04:36] He wants to move beyond being a “hand-wavish” software engineer and gain a deep, fundamental understanding of the systems he uses daily, such as systemd.
• [00:05:43] The project also serves as an opportunity to get back into reading textbooks and explore “old-school” computing concepts, which he enjoys.

Project Plan and Documentation

• [00:02:40] The video series will be unstructured, presented as work logs and journals rather than polished tutorials. He compares the process to exploring an “open-world RPG.”
• [00:02:47] His entire journey, including notes and logs, will be version-controlled and publicly available in a GitHub repository.
• [00:10:48] He plans for a continuous, podcast-style format with at least one video per week (Saturdays), supplemented by shorter, micro-video updates for milestones to maintain a tight feedback loop with his audience.

Tooling and Workflow

• [00:06:21] Emacs will be the central hub for the project, used for coding, note-taking, journaling, and as an LLM client.
• [00:07:44] He will use Tmux for terminal management and work within an openSUSE Tumbleweed environment.
• [00:10:14] The project will involve programming in C and Assembly, which he sees as a return to the fundamentals of programming.

Channel Direction and Future Goals

• [00:09:44] Raj wants to shift his channel’s focus from showcasing tools in a “glass case” to demonstrating them in a real-world, complex application.
• [00:13:00] OSDev provides a natural, unforced use case to explore and evaluate different tools and programming philosophies.
• [00:11:15] He hopes the documented journey can serve as a guide for others who might want to start OSDev from scratch in the future.

Conclusion

Raj concludes by expressing his excitement for this new, challenging venture. He emphasizes that this project is as much for his personal growth and learning as it is for creating content. He plans to be much more regular with his uploads and invites viewers to follow along on this ambitious journey.

• alias vi
• doom gcc emacsclient (no window)
• cool retro term
• tmux
• conversation starter

I wrestle with boredom from time to time: probably because I maintain a healthy addiction for novelty.

Although my days are scheduled along with a mostly invariable undercurrent of overarching directives, a deliberate portion of “something new” keeps me engaged and aware in the longer run.

This idea of needing “something new” everyday has become the most recent constant in my life: to the point of me considering adopting a “new new” of “nothing new for a while and seeing how that feels”.