I'm sure most of us have had to deal with issues reported by end users that we ourselves aren't able to reproduce

This video is an extended case study going through my thought process as I tried to track down and fix a mysterious performance regression which impacted a small subset of end users

I look at the impact of acquiring mutex locks across different threads, identifying hot paths by attaching to running processes, using state snapshot comparisons to avoid triggering hot paths unnecessarily, the memory implications of bounded vs unbounded channels, and much more

Hi friends, I develop and maintain the komorebi tiling window manager and have been posting live coding videos documenting its development for just over a year now.

I'm starting a new mini series on building a visual debugging gui tool to aid development on komorebi and especially to help with understanding some of the more esoteric edge cases and the interactions between the twm, user-defined rules and WinEvents.

I'll be building this from scratch using egui/eframe, so if you're interested in what building a non-trivial real-world immediate-mode gui and integrating with other (Rust, in this case) processes via IPC looks like, you'll probably get something out of this series.

Sharing some numbers on what people can realistically expect with GitHub Sponsors on a moderately popular project without any external / VC / corporate backing.

In this video I discuss the trade-offs of building on top of unstable reverse-engineered private APIs, why I decided against it, and compare to similar software that chose to use them.

A couple of people who aren't particularly interested in the software itself told me that this was an interesting and engaging video on general programming approaches when building applications for closed-source systems, so I thought I'd share it a bit more widely here.

cross-posted from: https://lemmy.world/post/9143654

Apologies in advance for sharing two link posts here two days in a row. Unemployment may be driving me a little nuts... 😅

I've been working on Satounki since I got laid off last month. It's the culmination of a lot of experience building similar ad-hoc internal tooling at various places throughout my professional career.

Satounki already includes:

• AWS support
• GCP support
• Cloudflare support
• Auto-generated Terraform providers from the Rust API
• Auto-generated Typescript client wrapper from the Rust API
• Slack bot for request notifications, approvals and rejections
• CLI for requests, approvals and rejections
• Dashboard for exploring policies, requests and stats

The scope of this project is pretty big and I'm looking for contributors.

The majority of the project is written in Rust, including the generated Go and TS code. The stack is pretty simple; Actix, Diesel, SQLite, Tera etc., so if you have experience with writing web apps in Rust it should feel familiar!

Even if this is a totally new stack to you, this is a great project to develop some familiarity and experience with it, especially if you can help improve the quality of the generated Go and TS code at the same time!

Apologies in advance for sharing two link posts here two days in a row. Unemployment may be driving me a little nuts... 😅

I've been working on Satounki since I got laid off last month. It's the culmination of a lot of experience building similar ad-hoc internal tooling at various places throughout my professional career.

Satounki already includes:

• AWS support
• GCP support
• Cloudflare support
• Auto-generated Terraform providers from the Rust API
• Auto-generated Typescript client wrapper from the Rust API
• Slack bot for request notifications, approvals and rejections
• CLI for requests, approvals and rejections
• Dashboard for exploring policies, requests and stats

The scope of this project is pretty big and I'm looking for contributors.

The majority of the project is written in Rust, including the generated Go and TS code. The stack is pretty simple; Actix, Diesel, SQLite, Tera etc., so if you have experience with writing web apps in Rust it should feel familiar!

Even if this is a totally new stack to you, this is a great project to develop some familiarity and experience with it, especially if you can help improve the quality of the generated Go and TS code at the same time!

This (Windows employing different methods to prevent users from writing programs that programmatically change application focus) has been an ongoing struggle for me for the better part of 3 years.

I finally made what feels like some significant progress this past week.

If you've ever obsessively gone deep down into a hole trying to understand and wrangle weird OS-level behaviors before, you might enjoy this video and feel a vicarious sense of victory :)

I got laid off this month and have a lot of time on my hands while I'm looking for new jobs 😅

I tried making a LinkTree but the website UI for editing is so janky and frustrating, and on top of that you have to go Premium for advanced theming, again in the janky UI...

I found this great Hugo theme called Lynx and built out my own links webpage like we did back in 90s on Geocities with Dreamweaver

Some folks on Mastodon and Twitter messaged me asking for a walkthrough because there are a few rough edges that are mostly related to changes between Hugo versions and the docs on the theme, so I made this end-to-end video going from project init to deployment on Cloudflare pages with analytics enabled

It's a pretty fun project and I think it can also be useful as a "portfolio links" page for people that are looking for jobs right now

cross-posted from: https://lemmy.world/post/8269080

Someone on another website asked me whether it makes sense to use agenix or sops-nix to encrypt secrets for NixOS configurations.

I realized that I hadn't seen a good overview article of the different approaches to secret handling in NixOS and when each one is appropriate to use, so I put down all of my knowledge and opinions in this post 🤞

Found some time this past weekend to work on a little "passion feature" that I've been wanting to implement for a while now; sharing the technical write-up for anyone else who is interested in automating headless screenshots with these tools or with others (the knowledge is pretty transferable!)

These days I reach for chumsky pretty much any time I need to write a DSL parser.

I thought it would be an interesting exercise to take a DSL parser that I've written using chumsky and reimplement it the "old fashioned" way.

For a while I've wanted to work through this book in Rust, and while I could find some finished (and often further refined) implementations of lox in Rust, I was not able to find an equivalent step-by-step snapshot of code at the end of each exercise of the book in Rust.

I decided to try doing the first exercise myself and record the progress to hopefully help others in the future.

The code in the video is not (intended to be) the most idiomatic Rust, as I was trying to stick as closely to the source material in Java as possible, but I think that in a way this has its own advantages for people who are interested in learning more about Rust.