340 karma · joined June 1, 2011
AGI might not be taking off, but my usage of AI tools certainly is in 2026.
Blog: https://asadjb.com
This was the only KVM I found which connects to 2 Thunderbolt devices at once, everything else was relying on HDMI+USB3 for the host connection.
But I like using Amp Code more. So I built review-for-agent: a local web UI that shows your uncommitted changes as a diff, lets you leave inline comments, and exports a structured Markdown file you can paste straight back into your agent's chat.
It's a single Go binary that runs locally and works with any agent.
> [Agents write] units of changes that look good in isolation.
I have only been using agents for coding end-to-end for a few months now, but I think I've started to realise why the output doesn't feel that great to me.
Like you said; "it's my job" to create a well designed code base.
Without writing the code myself however, without feeling the rough edges of the abstractions I've written, without getting a sense of how things should change to make the code better architected, I just don't know how to make it better.
I've always worked in smaller increments, creating the small piece I know I need and then building on top of that. That process highlights the rough edges, the inconsistent abstractions, and that leads to a better codebase.
AI (it seems) decides on a direction and then writes 100s of LOC at one. It doesn't need to build abstractions because it can write the same piece of code a thousand times without caring.
I write one function at a time, and as soon I try to use it in a different context I realise a better abstraction. The AI just writes another function with 90% similar code.
Just now, after reading this article, I used Claude code and have removed the OMZ config within 5 minutes. Here's my prompt - maybe others could find it useful. I ran this from `~/.oh-my-zsh`.
``` Here's my zsh config - I'd like to remove oh-my-zsh and replace the provided functionality with just raw zsh. i use starship for my prompt so i don't need any help there.
can you explore the oh-my-zsh codebae and see what it would take to replicate the features it currently provides me in the shell?
my zsh config below:
export ZSH="$HOME/.oh-my-zsh"
ZSH_THEME=""
DISABLE_AUTO_TITLE="true"
plugins=(direnv fzf)
source $ZSH/oh-my-zsh.sh
Since you use starship and have DISABLE_AUTO_TITLE=true, you can skip prompt and title-related code. Here's what you'd need:
# Completions
autoload -Uz compinit
compinit
zstyle ':completion:*' menu select
zstyle ':completion:*' matcher-list 'm:{a-zA-Z}={A-Za-z}' # case insensitive
# History
HISTFILE=~/.zsh_history
HISTSIZE=50000
SAVEHIST=10000
setopt extended_history hist_expire_dups_first hist_ignore_dups
setopt hist_ignore_space hist_verify share_history
# Directory navigation
setopt auto_cd auto_pushd pushd_ignore_dups pushdminus
# Key bindings (emacs mode)
bindkey -e
bindkey '^[[H' beginning-of-line # Home
bindkey '^[[F' end-of-line # End
bindkey '^[[1;5C' forward-word # Ctrl-Right
bindkey '^[[1;5D' backward-word # Ctrl-Left
bindkey '^[[3~' delete-char # Delete
# Colors
autoload -Uz colors && colors
export CLICOLOR=1 # macOS ls colors
# Plugins replacement
eval "$(direnv hook zsh)"
eval "$(fzf --zsh)"Granted I've only done this like 5 minutes ago and might be missing functionality I'll realise later, but a quick few checks give me hope I have all the functionality I want.
However, I feel like maybe a different approach could be to store all the app state in the DB, and then export to this text only format when needed; like when interacting with LLMs or when someone wants an export of their data.
Breaking the file into smaller blocks would necessarily need a cache system I guess, and then maybe you're implementing your own DB engine in the cache because you still want all the same functions of being able to query older records.
There's no easy answer I guess, just different solutions with different tradeoffs.
But what you've built is very cool! If I was still doing text based accounting I would have loved this.
One thing which I disagree with in this article is the focus on file based data storage:
> That makes it 10 times harder because you need to parse the text file, update it accordingly, and write it back. But I am glad I did. That guarantees all my accounting books are in the same open format.
This quote captures my issues with it. It just makes things so much more difficult; and it makes the whole process slower as the file grows. I remember that when I used hledger for tracking my expenses over 3 years, I had to "close books" once a year and consolidate all the transactions for the past year into 1 entry in a new ledger file to keep entry/query operations fast.
I get the sentiment; you want open data formats that remain even after your app is shutdown. But you can get the same by using open formats; maybe a sqlite DB is good enough for that?
The only thing that would be more complicated with a DB is versioning & reviewing commits like this app does; which does seem like a very exciting feature.
I ended up creating a "SSH environment" manager 4 years ago to help with this: https://github.com/theonejb/sshenv
It's worked wonderfully for me since then, and it's something I use almost daily.
A big confusion for me initially was that my banks always talked about crediting my account whenever money was deposited/added to my account.
I finally understood it when I realized that from the banks perspective, an increase in my account is an increase in their liability towards me; they now owe me more money. Which is why they call it crediting my account.
So now I think of it like this: an increase in an asset is always a debit, an increase in liability is always a credit.
Until recently (most notably until the Bamboo Labs Carbon X1) you had to spend time setting up your printer to get a good first layer. This would involve changing the distance between the nozzle that lays out the melted plastic and the bed on which the model is printed. Because this distance varies not just between different units of the same printer, but also has to change based on what material (PLA, PETG, etc) you're printing with, it needed some knowledge to set correctly.
While that process did get much simpler (with most of it being automated), it still involved some tweaking on the part of the user. That's a problem for people who are new 3D printing. It meant that you couldn't start printing immediately after unboxing your printer. It also meant that you had to spend considerable time (a few hours at least in my case) figuring out what a "good first layer" means, and then tweaking your printer to print the first layer well.
With this update, you can now start printing immediately after unboxing your printer (after some minor assembly), which is a huge thing for people who are new to 3D printing.
When I got my first printer a few years ago, I remember having to spend a couple of hours initially learning how to do this calibration, and I didn't get great results until a few more weeks of learning and tweaking.
Note that this is from the perspective of a hobbyist. People using 3D printers on a commercial scale might find the other improvements to be a big thing for their use case.
A few months back, I was job hunting due to tech layoffs and ended up with two offers from different startups. One was a 2-year-old YC company with a larger team, while the other was a brand-new startup where I'd be the first engineer, building the tech stack from the ground up.
Deciding between the two was tough, so I tried a creative exercise. I wrote draft emails to both hiring managers, explaining why I chose not to join their startup. After about 90 minutes, my preferences became clear.
The only reasons I had for joining the more established startup were job security and better work-life balance. Meanwhile, my passion for the new startup was evident in the email I wrote. This exercise helped me uncover my true feelings.
---
It was a very useful exercise; might be able to help someone else faced with this issue.
I moved countries in 2013, and barely had 1 friend after I moved. I had a few office colleagues I was friends with, but very rarely met with them outside of the office.
My days were similar to what you describe. Working long hours and then sitting at home with Netflix or Youtube. COVID has made it worst in your case unfortunately.
Here's what I learned which might help you: - Watching movies or Youtube isn't necessarily a "waste" of time. It's just a way to spend time. You don't need to spend your time being productive or social. If the movies or videos let you pass the time in peace, enjoy that. I also enjoyed reading books back when I was living by myself, but the majority of my time was spent in "wasteful" activities like social media and movies. As long as it's a conscious decision to spend your time this way, I would suggest to not call it "wasted" time. You're spending time doing things that help you relax and unwind. It's not wasted. - It took me a long time (> 2 years) to find a group of friends that I was happy being around. College is really the last time in my life when I made friends quickly. I think it's purely because being together for hours everyday over the course of years naturally builds friendships. Making friends after college takes time. As someone who is introverted, it took me even longer. - The time I had to spend by myself was difficult at times, but that was just because of the way I had framed it then. Like you said, there's an expectation of how people your age have to act; go out and have fun. Ultimately it is someone else's expectations that you are enforcing on yourself. Find things that bring you some version of joy. Don't worry about what others expect you to do. - Find hobbies. If you have a well paying job and low expenses, you should try your hand at different things. I've tried and given up on so many things over the years. A few; like 3D printing and FPV drone flying have stuck around. Again, I used to think that I was failing because I didn't stick with hobbies for a long time. I now realize that it would have been worse trying to force myself to spend my free time on things I didn't enjoy. - Following up on the hobbies thing - find communities around your hobbies that you enjoy. It's a great way to make friends. Communities don't need to be in-person either. There are so many amazing people you can make friends with online through your interests.
Finally, working in-person with others in the office is a great way of accelerating friendships. Many in my current friends circle are people I met in the office, or people I met through my colleagues.
The last thing I'll end with is to not worry too much and give it time. That's essentially what helped me; giving it time.
Hope that helps.
I needed this because my UAE bank (Emirates NBD) exports transactions in a weird deprecated format; SpreadsheetML. YNAB can't import this. And converting this manually took time and (a lot of) patience.
Hoping to try out Elixir for this year.
I also sometimes build Conways Game of Life in a new language for fun.
The fact that DNS was also not resolving was a symptom of the DNS servers also being unavailable since they were part of the same IP address space that was unadvertised.
""Backdoor" may not be the right term, though it's difficult to be certain without knowing the details of the system's technical architecture. In the complaint, the term is used to describe a duplicate of the PSCA's DES running on servers based in a Huawei facility in Suzhou, China. Whether that copy arises from a covert remote access capability or an overt replication option under indifferent or permissive security policy isn't clear."
If I've built a small library that does something useful for my set of needs, it's not crap software. It works perfectly well for my needs.
If someone then goes ahead and uses my library, without understanding what needs it satisfies and what it does not, how is that on me?
I release it to the world with the understanding that someone else might have the same requirements that I had when I built it. Why shouldn't I have released it?
Only later did I realize that the bulk of the work is done by the C library, which is ~1500 LOC [2].
I guess parsing CSVs reliably is a reasonably difficult undertaking.
[1] https://github.com/python/cpython/blob/3.8/Lib/csv.py [2] https://github.com/python/cpython/blob/4a21e57fe55076c77b0ee...
From the conclusion:
>It is not hard to consider the chroot() system call a security feature. In theory, it sounds great, but if you really take the time to understand what is going on, it is not really a security feature, it is closer to what we would call a hardening feature. It might slow down an attacker, but in most situations it is not going to stop them. We are dealing with a situation where calling this a security feature is likely more damaging than not because it creates a false sense of security. It is human nature to let our guard down if we believe we are safe. Using chroot is no safer than not using a chroot. You would be far better off investing your resources into a custom SELinux policy and ensuring your system is properly hardened. Good security has no shortcuts.
I think the point is that you shouldn't consider chroot the only or best option for securing your system. It's just one tool in the toolbox and needs to be understood properly and not trusted blindly as the solution for all security vulnerabilities.
I'd much rather be tracked online and have my bank details safe than the other way around.
I got a boost in my Vim productivity after reading a similar StackOverflow answer a couple of years ago. It's a nice read for people familiar with Vim, and another good resource for new users.
"Your problem with Vim is that you don't grok vi." https://stackoverflow.com/a/1220118
But I got my rate of doing the "get-past-you shuffle" down quite a bit after learning a simple trick.
While I avoid eye contact, most people do not. Most people, when they see an on-coming person, judge which side (left/right) to pass them by looking at their gaze.
The trick is to look in the direction you want to pass the other person in. So if you're going to take the left side, look to your left.
Most people will then pass you on your right side.
Have you ever run into a similar situation?