Yigithan Guven

I Spent Hours Automating a 0.5 Second Task (And It Was Worth It)

2025-09-16T00:00:00+00:00

You know that bone-deep exhaustion from doing the same tiny task over and over? Yeah, I got tired of manually switching between my Speakers and 3.5mm headphones every time I boot up.

It’s not that I forgot. It’s that I’m lazy and got sick of clicking the same two buttons every single day.

So naturally, I did what any reasonable developer would do: spent an entire evening building an automation script to save myself 0.5 seconds of clicking.

The Problem</h2>

My setup is simple:

Daytime: Logitech 2.1 speakers connected through my display</li>

Nighttime: Headphones for those considerate late-night sessions</li> </ul>
But manually switching got old fast. Boot up at 10 PM and have to switch to headphones. Boot up at 8 AM and switch back to speakers. Every. Single. Time.
Nah, I’m done with that.
The Solution: Peak Developer Behavior</h2>
Built a bash script that runs at login and automatically switches based on time:

10:00 AM - 12:00 AM: Speakers for daytime productivity</li>
12:01 AM - 9:59 AM: Headphones for quiet night sessions</li> </ul>
# The core logic is beautifully simple current_hour=$(date +%H) if [ $current_hour -ge 10 ] || [ $current_hour -eq 0 ]; then target_device="$HDMI_DEVICE" # Speakers else target_device="$ANALOG_DEVICE" # Headphones fi </code></pre> The Technical Bits (Because I Went Overboard)</h2> Of course I couldn’t just write a simple script. It had to be bulletproof: Waits up to 45 seconds for PipeWire to initialize (because audio systems are moody)</li> Handles device detection and graceful failures</li> Moves existing audio streams to the new device</li> Logs everything to debug when things inevitably break</li> Uses lock files to prevent multiple instances</li> Shows desktop notifications because why not</li> </ul> The script is way smarter than it needs to be. Classic over-engineering. Was It Worth It?</h2> From a time perspective? Absolutely not. I’ll never recoup those hours. From a “my computer now reads my mind” perspective? Hell yes. Every boot, the right audio device is just there. No thinking, no clicking, no repetitive strain on my clicking finger. That’s the beauty of personal automation projects. They’re rarely about efficiency. They’re about that tiny dopamine hit when your environment just works the way you want. The Code</h2> Threw it on GitHub</a> for anyone else who’s tired of clicking buttons. It’s heavily commented because future me will forget how any of this works. Works on any Fedora system with PipeWire or PulseAudio. Just update the device names for your hardware. What’s the most ridiculous thing you’ve automated to avoid a simple manual task? Please tell me I’m not alone in this madness.

Omarchy: My Fastest and Most Beautiful Dev Setup Yet 2025-09-15T00:00:00+00:00 I recently tried Omarchy, the Arch-based distro made by DHH (creator of Ruby on Rails), and I’m honestly blown away. This isn’t just Arch preinstalled with a few packages — it’s a complete, curated system. Omarchy comes with Hyprland, LazyVim, and an entire development setup ready to go — but what impressed me most is how effortless everything feels. The configuration and setup experience is smooth, consistent, and genuinely enjoyable. And the best part? It’s a single ISO install that sets up a complete development environment, and a keyboard-driven workflow in minutes. You don’t spend hours configuring like you would with vanilla Arch — you reboot, log in, and you’re ready to work. For now, I installed Omarchy on my thinkpad, and I’m not ready to switch my Fedora desktop just yet. Fedora is still my main machine, and I keep Windows around for two things I can’t replace: NVIDIA GPU performance — my RTX 3080 runs at full speed and drivers are far more stable and performant in Windows than on Linux.</li> Microsoft Visual Studio — for some C++ projects, Visual Studio and its build tools are still the most reliable and convenient choice.</li> </ul> My Current Setup. Omarchy even comes with cool screen savers. (Just Ignore the cables i hade to replace one of them recently 😱) Even so, Omarchy might be the most exciting development setup I’ve tried. It feels like a hacker’s dream machine, right out of the box, and I love how easy it is to configure and make my own. By the way, this site you’re reading is built with Zola, the Rust-based static site generator, using the Tabi theme — fast, clean, and perfect for sharing posts like this. Why does the Quest 2 Unity Application open in window mode instead of VR mode? 2022-11-18T00:00:00+00:00 There are several reasons why the Unity application may open in window mode on Meta Quest 2. This issue can be particularly frustrating when updating apps on platforms like Oculus App Lab. If your application is functioning in window mode, consider the following troubleshooting steps: 1. XR Plug-in Settings</h2> Navigate to Edit > Project Settings > XR Plug-in Management in the Unity Editor. Ensure the following settings are configured: Enable “Initialize XR on Startup” for both Android and PC tabs.</li> Check the Oculus option under both Android and PC tabs.</li> </ul> 2. OpenXR Settings</h2> Within the XR Plug-in Management settings, access the OpenXR settings tab. Verify that Oculus Quest Support is enabled in the OpenXR Feature Groups. 3. Target Platform Configuration</h2> Ensure that the Unity target platform is set to Android for Oculus Quest 2 development. Navigate to File > Build Settings > Player Settings and confirm that Android is selected as the target platform. 4. Console Errors</h2> Check the Unity Editor console for any errors related to XR plugins. Addressing these errors can resolve issues with VR mode initialization. 5. Testing with Oculus Link</h2> Consider running your application in Play mode using Oculus Link to test its functionality in VR mode. By following these steps, you can ensure that your Unity application launches directly into VR mode on Meta Quest 2, providing a seamless experience for users.

Yigithan Guven

I Spent Hours Automating a 0.5 Second Task (And It Was Worth It)

Omarchy: My Fastest and Most Beautiful Dev Setup Yet

Why does the Quest 2 Unity Application open in window mode instead of VR mode?

2. OpenXR Settings</h2> Within the XR Plug-in Management</strong> settings, access the OpenXR</strong> settings tab.</p> Verify that Oculus Quest Support</strong> is enabled in the OpenXR Feature Groups.</p> </p>

2. OpenXR Settings</h2>
Within the XR Plug-in Management</strong> settings, access the OpenXR</strong> settings tab.</p>
Verify that Oculus Quest Support</strong> is enabled in the OpenXR Feature Groups.</p>
</p>