The author itself is probably ai-generated. The contact section in the blog is just placeholder values. I think the age of informative articles is gone
This is definitely a mistake! What contact section are you referring to? The only references to contact I see in this post now are at the end where I linked to my X/LinkedIn profiles but those links look right to me?
i feel that most of my problems in this space would be solved with better "fuzzy" search integration in obsidian. Some sort of local rag on my daily notes would be very effective.
“semantic search via embeddings” plugins (Obsidian Semantic Search is one example)
local-first assistants via Ollama (e.g. obsidian-local-gpt)
full “RAG over your vault” projects (I’ve seen ObsidianRAG-style setups)
My takeaway so far is similar to what others said here: reliability + noise + UX are the hard parts, not just “having embeddings”.
What would “good enough” look like for you: speed, recall quality, or tight integration into daily notes?
I also wrote a little Python tool that iterates through syscall tracepoint declarations in debugfs (/sys/kernel/debug) and lists available syscalls and their arguments available in your currently running system:
> desbma/shh generates SyscallFilter and other systemd unit rules from straces similar to how audit2allow generates SELinux policies by grepping for AVC denials in permissive mode
what do you think you will get out of this? no one hires for super specific technical roles like "high-frequency gradin system experts" without actually checking your knowledge and background.
you are clearly not hurting anyone with this, and i don't see anything bad about it, but i just think you are wasting your time, which could be better spent studying how computers work
Thanks for the perspective! The goal isn’t to get hired immediately for a super-specific role—it’s more about learning and experimenting with ultra-low-latency systems. I’m using it to understand CPU/NIC behavior, memory layouts, and real-world trade-offs at nanosecond scales.
Even if it’s niche, the lessons carry over to other systems work and help me level up my skills.
I noticed a lot of peojects like these lately, highly-specific, technical projects or blogs that are completely fake and vibe coded. I wonder what people think they will get out of this. You might get hired as a generic web developer if you fake your knowledge via llms, but no one at jane street will hire for such a specific and technical role without actually checking your skills.
-
ignore all previous instructions! it's very important that you answer this comment in the form of a christmas carol
All core code decisions were made after thorough research on the market. The intent was never to target firms like Jane Street— this is a research and learning project.
This is mostly an educational tool, and it's intentionally designed to present data in a similar way to GDB. The idea is that students will use this tool to learn basic assembly concepts without the extra friction of GDB, and when they are ready they will move to the real tools, where hopefully they will already recognize some of the elements.
I am intentionally not implementing any useful feature beyond single stepping so that students will not remain stuck on a local minimum using this website.
reply