If you use the terminal on macOS, you’ve typed your password for sudo thousands of times. There’s a better way. Touch ID works for sudo, and Apple even ships a template config for it. Most people just don’t know it’s there. The Setup macOS includes a PAM (Pluggable Authentication Module) template at /etc/pam.d/sudo_local.template with the Touch ID line already written but commented out. All you need to do is copy it and uncomment: ...
I am a bit of a Xiaomi fan, so when I spotted the B3600 Pro I bought it without a strong reason. The UI was entirely in Chinese, and my Vodafone station was already good enough for daily use, so the router ended up sitting on a shelf collecting dust. Meanwhile, I have been running a fork of PicoClaw, a lightweight Go-based AI assistant, as my personal assistant for a while now. I have been genuinely impressed with how capable it is, so one day I looked at the idle router and thought: can I get PicoClaw running on that thing? Armed with my set of AI tools, I set out on an adventure. ...
The bottleneck in AI-assisted coding isn’t the models—it’s the interface. After months of experimenting with various AI-powered development tools, I’ve landed on a voice-first, multi-agent setup that removes the friction between thought and code. For context, my primary role is an Engineering Manager. I don’t write production code at work, but I build apps on the side and experiment with new AI tooling. The challenge: typing instructions slows down iteration, especially when exploring ideas or debugging complex problems. ...
After I switched to engineering management, I realized that I missed coding. With my new job, I spend more time on github, and innovation is very much encouraged at the company. As such, I’ve been fiddling around with LLM’s to see what works (and not). As I explore various models and learn more, I’ve developed a workflow that leverages multiple LLMs, each chosen for its specific strengths. Here’s how I use various AI models to boost my development productivity. ...
A quick recap on SRE Site reliability engineering (SRE) is a discipline that incorporates aspects of software engineering and applies them to infrastructure and operations problems.[1] The main goals are to create scalable and highly reliable software systems. According to Ben Treynor, founder of Google’s Site Reliability Team, SRE is “what happens when a software engineer is tasked with what used to be called operations.” ^ Source: Wikipedia How much time do you spend coding? I get this question quite often: “How much time do you spend writing code?” ...