**Stop switching tabs just to see what’s playing🎵** I’ve always found it distracting to break my workflow just to check a song title or pause a track. YouTube Music's mini-player is okay, but I wanted something truly minimal—a piece of "digital glass" that sits on my desktop without borders, buttons, or clutter. So, I built GlassMusic. 🖥️✨ The Problem: Standard Windows widgets often feel heavy, come with unwanted borders, or lack intuitive controls. I wanted a 150x150 floating album cover that felt like a native part of my OS, but getting there wasn't easy. The Engineering Challenges & Solutions: The "Invisible" Data: Fetching real-time media thumbnails from Windows isn't as simple as reading a file. I had to implement an asynchronous winsdk worker to bridge the Windows Media Control API with a Python/PyQt6 interface. The "Punchhole" Handle: I wanted to move the widget without adding a bulky title bar. My solution? A "Punchhole" handle—a 100% transparent circle created using DestinationOut composition modes. It’s a functional void that lets you drag the widget while looking through it to your wallpaper. Smart Interaction: To prevent accidental music pauses while dragging, I built a movement-detection buffer that distinguishes between a "repositioning drag" and a "control click." Pixel Clarity: To avoid "burst" pixels on high-res monitors, I implemented SmoothPixmapTransform and subpixel antialiasing to keep album art crisp at every size. Features: ✅ Real-time sync with Spotify, YouTube, and Windows Media. ✅ Single click to Play/Pause | Double-click to Skip. ✅ Right-click "Shatter" animation to close. ✅ Zero-border, ultra-minimalist aesthetic. This project was a deep dive into PyQt6 GUI threading, Windows API integration, and UX design. 👇 I’ve dropped the GitHub link (Source + EXE) in the first comment below! #Python #PyQt6 #OpenSource #SoftwareEngineering #WindowsAPI #Productivity #UXDesign #Coding

Stop wasting time "stepping through" your code. 🛑 If you’re still debugging by adding 𝗰𝗼𝗻𝘀𝗼𝗹𝗲.𝗹𝗼𝗴 everywhere and hoping for the best, you’re playing on hard mode. The 𝗖𝗵𝗿𝗼𝗺𝗲 𝗗𝗲𝘃𝗧𝗼𝗼𝗹𝘀 are packed with "hidden" features that can save you hours of frustration. Here are 5 pro-tips to level up your debugging game: 🧠 𝟭. 𝗖𝗼𝗻𝗱𝗶𝘁𝗶𝗼𝗻𝗮𝗹 𝗕𝗿𝗲𝗮𝗸𝗽𝗼𝗶𝗻𝘁𝘀 Stop pausing every single time a loop runs. Right-click the line number and select Add conditional breakpoint. Example: response.status === 500 The Win: The debugger only kicks in when things actually go wrong. 🎯 𝟮. 𝗘𝘃𝗲𝗻𝘁 𝗟𝗶𝘀𝘁𝗲𝗻𝗲𝗿 𝗕𝗿𝗲𝗮𝗸𝗽𝗼𝗶𝗻𝘁𝘀 Ever inherit a codebase and have no idea which function triggers a button click? Where: Sources Panel → Event Listener Breakpoints. The Win: Check "click" or "input," and the browser will automatically pause the moment that event fires. 🕵️ 𝟯. 𝗧𝗵𝗲 “𝗜𝗻𝗶𝘁𝗶𝗮𝘁𝗼𝗿” 𝗖𝗼𝗹𝘂𝗺𝗻 Stop guessing which script triggered that random API call. Enable the Initiator column in your Network tab. The Win: Hover over the value to see the exact call stack that started the request. Tracing API logic becomes instant. 📦 𝟰. 𝗟𝗼𝗰𝗮𝗹 𝗢𝘃𝗲𝗿𝗿𝗶𝗱𝗲𝘀 (𝗧𝗵𝗲 𝗥𝗲𝗮𝗹 𝗠𝗩𝗣 🚀) Want to test a UI fix or a different API response without waiting for a backend deploy? Where: Sources → Overrides. The Win: Edit JS, CSS, or mock an API response directly in the browser. It persists even after a refresh. 🐢 𝟱. 𝗧𝗵𝗿𝗼𝘁𝘁𝗹𝗶𝗻𝗴 (𝗡𝗲𝘁𝘄𝗼𝗿𝗸 & 𝗖𝗣𝗨) Your M3 Macbook Pro isn't how your users experience your site. The Win: Simulate "Slow 3G" and "6x CPU slowdown" to see how your app behaves on low-end devices. Catch performance bottlenecks before your users do. Which one of these is a permanent part of your workflow? Or did I miss your favorite? Let’s swap tips in the comments! 👇 #WebDevelopment #JavaScript #ProgrammingTips #Frontend #Debugging #SoftwareEngineering

I always enjoy playing with #Angular Signals and making fun little wrappers around them to add functionality🔥 Today I made a broadcast Signal 📻 Open two tabs of your Angular app. Click a button in one. Watch the other window update instantly. No library. No store. No server. 15 lines of code. Meet sharedSignal, a writable signal that auto-syncs across every browser tab on the same origin. The trick? We override .set and broadcast inside it. That single tweak turns a local signal into a shared one without changing the public API. Because it returns a real WritableSignal<T>, you keep all Signal feature and it keeps working as expected with: computed, effect, linkedSignal, toObservable, resource 🙌 Zero extra work. Drop it into any component ✅ Perfect for: 🔸 Theme & locale 🔸 Feature flags 🔸 Auth session state 🔸 Cross-tab notifications 🔸 Optimistic undo across windows One caveat: structuredClone means no class instances or functions in the payload. Honestly? That's a feature. It's a forcing function toward plain, serializable data, which is exactly what should be crossing tab boundaries anyway. Here is a StackBlitz to play with: https://lnkd.in/eiufFfs9

Your IDE doesn’t remind you to hydrate — Hydration Assistant does, and only when you’ve actually been coding. - Activity-aware (not a dumb 25-minute alarm) - Smart mode + status bar + optional chime - Silly/motivating messages so it’s not another boring notification - Local-only — built for devs who care about privacy Search Hydration Assistant on the VS Code Marketplace or install directly: https://lnkd.in/gVnWGxjc #VSCode #DeveloperTools #Productivity #Health #BuildInPublic #DrinkWater

I've been a Windows-native user for over 20 years. When I started running 4 Claude Code agents simultaneously — each with its own dev server — the experience was trash. 8-10-12+ terminal windows, constant alt-tabbing. Spending my brain's computation on something as wasteful as juggling terminals felt like a personal defeat. Inspired by slavery-memes around AI, I decided to build my open-source Basement project and literally put my agents into the basement/on chain. Four AI agents. Four terminals. Four dev servers. One browser window. Everything visible at once — sessions, git status, running servers, system stats, and more. A piece of drama: the left half is a pixel-art dungeon where your agents literally walk around. Working agents do some stuff you see. Idle agents wandering aimlessly. If you leave idle agent for too long, it'll just walk to pentagram and burn it alive, indicating that it's better to put the agent to sleep and save your CPU/RAM/Attention span. So basically your peripheral vision becomes the monitoring tool. Sounds ridiculous, but works perfectly. No build step. No bundler. Two dependencies. npm install, npm start, done. If you run multiple Claude Code sessions on Windows and feel the pain — this can help you a lot. https://lnkd.in/dsS8PRVp

Game: http://wordluc.it/ I built a real-time multiplayer sand simulator in Go, fully playable in the browser (and on mobile). Github: https://lnkd.in/dcg54VMe This project started with a few simple questions: - How does a netcode actually work? - What is WebAssembly, and how can I use it? And I kinda get it with a few headaches along the way, otherwise, where’s the fun? For the tech stack, I used Go for both the backend and frontend(along with HTML and CSS), leveraging WebAssembly to share the same logic across both sides and improve efficiency where needed. I also reused JavaScript where necessary for simplification and optimization, especially for handling WebSocket reads (to avoid cross-boundary bottlenecks that would otherwise hurt performance). I also implemented a custom binary communication protocol: - 64-bit messages (client → server) - 16-bit (per cell) updates (server → client) Performance was a key focus, so I built a chunk-based system: - Only active chunks are simulated - Neighboring chunks are included in the simulation to avoid “floating cells” (the Harry Potter effect). - Clients only receive updates for what they can actually see(and extra border chunks to prevent popup when moving around). For fun, I added a “god mode” that lets you view the entire map (1200×750), compared to the standard 240×120 player view. The whole project runs on a VPS using Docker, with Redis handling storage. #golang #webassembly #gamedev #systemsprogramming #opensource #redis #netcode #online #html #css #javascript #raylib #Websocket

Compose Guard is a project close to my heart ♥️.I love writing clean code, but developers often make mistakes in Jetpack Compose. Lint can overwhelm with hundreds of warnings at compile time, so I built an Android Studio plugin to catch issues in real time and make things easier. https://lnkd.in/gfvBPvWR

Day 17 of 30 Apps in 30 Days → Teleprompter 🎬 A desktop teleprompter that's completely invisible to Zoom, Google Meet, OBS, and Loom. Not a CSS trick. Actual OS-level APIs: → macOS: NSWindowSharingNone → Windows: SetWindowDisplayAffinity(WDA_EXCLUDEFROMCAPTURE) The window floats above everything. Nobody on your call sees it. You read your script. That's it. --- What I built in ~24 hours: ✅ Always-on-top floating window ✅ Screen share invisible (the whole point) ✅ Opacity slider that actually works cross-platform* ✅ Smooth auto-scroll with adjustable speed ✅ Pass-through mode (mouse clicks fall through to windows below) ✅ Mirror text for physical teleprompter setups ✅ AI script summarizer powered by Claude ✅ Full keyboard shortcuts ✅ Auto-release pipeline for macOS + Windows via GitHub Actions *The official Tauri API ignores alpha on Windows. Fixed with one line of CSS instead. --- The mistake that cost me an hour: I tried to make a "smart" click-through where one UI strip stayed interactive while the rest passed events through. CSS pointer-events: auto, etc. Doesn't work. set_ignore_cursor_events() is OS-level. The OS doesn't know about your HTML. The fix? Don't fight it — pass-through is keyboard-only mode. Show a shortcut reminder and move on. --- Stack: Tauri v2 · Rust · React · TypeScript · GitHub Actions Website: https://lnkd.in/gWfqwTbN Download (free, open source): https://lnkd.in/gbWEsuei 17 down. 13 to go. #30AppsIn30Days #BuildInPublic #IndieHacker #Tauri #Rust #React #OpenSource

I’ve recently completed a project I’ve been working on: ReportForge, a desktop application focused on pentest reporting. The idea came from a practical need. Most existing tools are either cloud-based, which is not ideal when handling sensitive data, or overly complex for individual use. I wanted something simpler, fully local, and easier to control. ReportForge allows you to structure pentest projects, document findings, manage evidence, and generate reports in a consistent way, while keeping all data stored locally. From a technical standpoint, it’s built with Python, using PySide6 for the interface, SQLAlchemy, and SQLite. The main focus was on building something usable and coherent, not just functional. Repository: https://lnkd.in/e-mFTrWg Feedback is welcome.