Andrew Yourtchenko
@ayourtch.bsky.social
Embedded programming, some Rust, 3D-printing and active mobility. Hacking on fd.io by day at cisco. Release manager for VPP. CiscoLive Europe NOC - automating stuff. Bits of code: GitHub.com/ayourtch ; all posts are entirely only mine.
Cool, glad you like it! :)
November 11, 2025 at 10:54 AM
Cool, glad you like it! :)
seen zellij.dev/screenshots/ ?
Screenshots
Default interface with a few panes and tabs Zellij with the Strider plugin Strider is a ranger clone and comes built-in with Zellij. To run, load its layout with:
zellij --layout strider
Basic multi...
zellij.dev
November 10, 2025 at 3:34 PM
seen zellij.dev/screenshots/ ?
“Intro to phrenology” article in 3… 2… 1… 🙈
November 7, 2025 at 5:42 PM
“Intro to phrenology” article in 3… 2… 1… 🙈
Every single consumer (smartphone, laptop) device is subject to software upgrades by its vendor, and the three of them control probably 99+% of the fleet. If the threat model assumes the cybersecurity industry being a factor, how does this angle compare ?
November 7, 2025 at 12:44 PM
Every single consumer (smartphone, laptop) device is subject to software upgrades by its vendor, and the three of them control probably 99+% of the fleet. If the threat model assumes the cybersecurity industry being a factor, how does this angle compare ?
Really cool! A little UX feedback: iPhone 13 Pro with Safari, on the first scroll the hyperlinked text in the blog seems to expand and then get back to its width. Not sure whether it’s an intentional effect, so thought to let you know !
November 7, 2025 at 9:59 AM
Really cool! A little UX feedback: iPhone 13 Pro with Safari, on the first scroll the hyperlinked text in the blog seems to expand and then get back to its width. Not sure whether it’s an intentional effect, so thought to let you know !
They didn’t specify which human…
November 6, 2025 at 9:34 PM
They didn’t specify which human…
agreed, also more well rounded *should* mean better real world coding experience as well. In any case - this is all great news
November 6, 2025 at 9:32 PM
agreed, also more well rounded *should* mean better real world coding experience as well. In any case - this is all great news
Stick the chicken into the pressure cooker and boil for a 3 hours. The result is edible in its entirety. (Yes, I am lazy ;-)
November 6, 2025 at 9:21 PM
Stick the chicken into the pressure cooker and boil for a 3 hours. The result is edible in its entirety. (Yes, I am lazy ;-)
The coding benchmark results seemed a bit weaker though ?
November 6, 2025 at 9:18 PM
The coding benchmark results seemed a bit weaker though ?
and it’s probably very obsolete by now! 😂 The potentially interesting thing is that it’s supposed to be included into the hash calculation forwarding devices load balancing, so you could in principle affect the network path your flow takes ! but then labs.ripe.net/author/joel_... confuses …
IPv6 Flow Label: Misuse in Hashing
When RFC1883 was published in 1995 it marked not the end of the process that produced the IPv6 protocol architecture, but rather was a milestone in the evolution of the IPv6 protocol.
labs.ripe.net
November 4, 2025 at 9:20 PM
and it’s probably very obsolete by now! 😂 The potentially interesting thing is that it’s supposed to be included into the hash calculation forwarding devices load balancing, so you could in principle affect the network path your flow takes ! but then labs.ripe.net/author/joel_... confuses …
A rare IETF meeting would go without someone inventing yet another use for the flow label! 😂
November 4, 2025 at 9:10 PM
A rare IETF meeting would go without someone inventing yet another use for the flow label! 😂
Agreed. Understanding the max amount of risk for each case, putting a cap on it and giving the ways to undo the wrong where possible. And being transparent to interfacing entities about all of this.
November 3, 2025 at 8:09 PM
Agreed. Understanding the max amount of risk for each case, putting a cap on it and giving the ways to undo the wrong where possible. And being transparent to interfacing entities about all of this.
i like the way you describe it; though to me it feels a good bit like judging whether a given email message is spam, purely by its contents. The first 80% are trivially easy, the last 0.1% are extremely hard.
November 3, 2025 at 6:50 PM
i like the way you describe it; though to me it feels a good bit like judging whether a given email message is spam, purely by its contents. The first 80% are trivially easy, the last 0.1% are extremely hard.
I have been using Claude on pyo3 bindings to a rust crate and boy did I remember your post… except in that case there’s no easy answer as I am already Rust :-).. the closest I could find is to start claude inside the activated venv, it seemed to make things a little better.
November 3, 2025 at 11:44 AM
I have been using Claude on pyo3 bindings to a rust crate and boy did I remember your post… except in that case there’s no easy answer as I am already Rust :-).. the closest I could find is to start claude inside the activated venv, it seemed to make things a little better.
If people are subscribing to a block list “ai bros”, maybe they just don’t want to be “bridged” ? I know the list, tried it and removed it from the block lists I use, because *i* found it too restrictive for *my* tastes. But someone who wants to eliminate AI topics entirely might find it just right.
November 2, 2025 at 12:59 AM
If people are subscribing to a block list “ai bros”, maybe they just don’t want to be “bridged” ? I know the list, tried it and removed it from the block lists I use, because *i* found it too restrictive for *my* tastes. But someone who wants to eliminate AI topics entirely might find it just right.
Some “design choices” (as per my comment here: github.com/ayourtch/nat...) aren’t pretty - but as that uses my own library, I treat it as an improvement being needed for “ease of use” of it.
November 2, 2025 at 12:44 AM
Some “design choices” (as per my comment here: github.com/ayourtch/nat...) aren’t pretty - but as that uses my own library, I treat it as an improvement being needed for “ease of use” of it.
Another example: github.com/ayourtch/osi..., which it then folded into the library itself; about three days from start to finish with fun debugging inbetween: stdio.be/blog/2025-05...
November 2, 2025 at 12:31 AM
Another example: github.com/ayourtch/osi..., which it then folded into the library itself; about three days from start to finish with fun debugging inbetween: stdio.be/blog/2025-05...
A bit hard to capture it well… less prone to LLM getting lost, perhaps. With a couple of JS projects, I ended up with a thoroughly tangled mess with multiple functions repeating, that had to eventually be shredded. Rust is much stricter with that - and great compiler error messages help LLM a lot.
November 2, 2025 at 12:27 AM
A bit hard to capture it well… less prone to LLM getting lost, perhaps. With a couple of JS projects, I ended up with a thoroughly tangled mess with multiple functions repeating, that had to eventually be shredded. Rust is much stricter with that - and great compiler error messages help LLM a lot.
I did quite a few side projects in the past year in Claude+Rust, in summary: happy. Eg: this game took 1.5 days with 0.5 days LLM-coding a buggy JS prototype and then a day of LLM-converting it into somewhat less buggy Rust: stdio.be/circuits/?ur... - Rust edit interactions felt much more “robust”.
November 2, 2025 at 12:20 AM
I did quite a few side projects in the past year in Claude+Rust, in summary: happy. Eg: this game took 1.5 days with 0.5 days LLM-coding a buggy JS prototype and then a day of LLM-converting it into somewhat less buggy Rust: stdio.be/circuits/?ur... - Rust edit interactions felt much more “robust”.
I only had one thought - “why?”
October 31, 2025 at 9:04 PM
I only had one thought - “why?”
With the URLs it is often iffy - often the origins do ban the agent retrieval, not sure if that were the case - it then attempts to retrieve the data in roundabout ways, but often gets distracted with the task itself :-)
October 31, 2025 at 4:50 PM
With the URLs it is often iffy - often the origins do ban the agent retrieval, not sure if that were the case - it then attempts to retrieve the data in roundabout ways, but often gets distracted with the task itself :-)