A question for guys who into unusual programming stuff. i been programming for +12 years now .. first few years it was fun trying all sort of things from assembly x86 to neural networks and computer vision but after finishing college few years ago and getting into corporates and the job market .. i been coding only for work as a backend engineer and programming stoped being a hobby anymore .. especially with ai propaganda that is going on right now. now i want to try a completely different part of programming as a hobby again away from web/app/game development or CV and ML something that is useful and somehow low level. i thought about learning CUDA and exploring other aspects now but its hard to find super geeks now to ask after the AI boom. what other fields you guys are into that are fun, complex and unusual? submitted by /u/zeXas_99 [link] [留言]

Hey r/webdev 👋 I recently launched UtilCraft , a collection of free browser-based tools for devs and creators. The whole idea is that everything runs locally, nothing gets uploaded anywhere. Right now it has 16 tools across 6 categories: 🛠️ Developer tools (UUID generator, JSON formatter, Regex tester, Cron generator…) 🖼️ Image tools (compressor, converter, resizer) 📄 PDF tools (merge, split) 🔒 Security (password generator, hash generator) 📝 Text tools 🔄 Converters (color, unit) I'd love to know two things from people who actually write code for a living: 1. What tool do you find yourself Googling way too often that you wish was just… there? 2. Any of the existing tools that feel half-baked or could be way more useful? No account needed, no sign-up, just open and use. Roast it, suggest stuff, I'm all ears. 🙏 submitted by /u/Yolmack [link] [留言]

submitted by /u/InvadersMustLive [link] [留言]

Brighten your video calls with different toned ring lights Discussion | Link

Hey everyone, We’re building Antitech , a security layer for AI agents and LLM-powered workflows. We’re opening a small number of free early-access assessments for teams/builders working on AI agents. If you give us access to an endpoint of a Dockerized / sandboxed environment of your agent, we’ll test it against common and emerging AI-agent attack vectors, including: Prompt injection Indirect prompt injection Tool abuse Data leakage / exfiltration Fake authority / malicious context Unsafe agent behavior Weak guardrails and policy bypasses In return, you get a free vulnerability report showing what we found, how serious it is, and practical recommendations to harden your agent. This is completely free. No catch. We’re doing this because we want to work closely with real AI-agent builders while shaping the product. Early participants will also get: A big discount once the final product is ready Insider updates while we build Early access to new features The option to become a design partner Priority access to future assessments What we need from you: An endpoint of a sandboxed/Docker environment Permission to test within agreed boundaries A short feedback call after the report We won’t publicly disclose anything without your permission. If you’re building AI agents and want to know how they can be attacked before someone else finds out the hard way, DM me or comment below. submitted by /u/TheAchraf99 [link] [留言]

Turn your Google Drive into a stunning client gallery Discussion | Link

I’ve been working on Keylight, a licensing layer for macOS apps, and one of the more interesting technical problems has been designing license checks that work both online and offline. The basic problem sounds simple: “Is this app allowed to run?” But in practice, there are a lot of edge cases: What happens if the user bought the app, but is currently offline? How long should an offline lease stay valid? How do you prevent a license from being copied forever? How do you handle device limits without making the app annoying? What happens when a subscription expires while the app is offline? How do you rotate SDK/API keys without breaking old app versions? How much should be checked locally vs on the server? The approach I’m using is roughly: The app validates against the server when online The server returns a signed local license lease The app can continue working offline for a limited period Device activations are tracked server-side Renewals, upgrades, and revocations update the next lease Old SDK keys can be retired gradually instead of breaking existing builds It’s a small part of the product, but it has been one of the most interesting engineering decisions so far. Curious how others would design this. Would you keep most licensing logic server-side, or allow more local verification with signed license files? And for desktop apps, what do you think is a fair offline grace period? submitted by /u/nicolas1410 [link] [留言]

Hi everyone, I need some career advice. I'm from a non-IT background and have been working in a small company for the last 2.5 years, mainly doing HTML and WordPress work. I don't have much exposure to modern development, and with AI changing the industry so fast, I'm worried about my future career growth. I'm thinking of joining an offline Full Stack Development course in Chennai because online learning hasn't worked well for me. I'm confused between **Java Full Stack** and **Python Full Stack**. For those who have experience in this field: * Which stack would you recommend? * Which institute is better: Besant Technologies, Greens Technology, or FITA Academy? * Are there any better alternatives in Chennai? I want to learn real-world projects and build skills that can help me get better opportunities. I'm 2.5 years into my career and don't want to make the wrong decision at this stage. Any guidance, personal experiences really help full for me. Any advice would be greatly appreciated. Thanks! submitted by /u/Best-Quantity-4749 [link] [留言]

I've been paying attention to my own workflow lately and noticed a lot of my time goes into moving stuff between AI sessions, not the actual thinking. Like I'll get an output in one session and then manually bring the relevant pieces into another so it has what it needs. What I can't tell is how much of that is necessary vs. me just being sloppy. So I'm curious how others handle it: When you move from one session to another, what do you actually carry over? Just the output, or also the reasoning, the decisions, the constraints, what to avoid? Have you ever handed off too little and the second session went sideways? Or too much and it got lost in the noise? Does anyone have a mental rule for what's "enough context" to pass along? Trying to figure out if there's a clean pattern here or if it's just inherently messy. Curious what people have landed on. submitted by /u/riley_kim [link] [留言]

I build a security platform. Last night I stopped adding features and did something less fun and more honest: I sat down to make every capability prove it actually works — end to end, with real data, demanding a real pass or fail. "It ran" is not a pass. A page that renders is not a feature. A green checkmark is a claim, not evidence. So I went capability by capability and tried to break each one. I found four real bugs and one of them was a gut-punch: a whole detection engine that was wired into the UI, unit-tested, and never actually ran in production. Here's how the night went. The rule: drive it, don't admire it My method was boring on purpose. For each capability: Feed it real input through the real entry point (CLI or API), not a test fixture. Check the data actually landed (query the DB, don't trust the success message). Feed it a malicious input and a benign input — it has to fire on one and stay quiet on the other. The detection engine passed cleanly. I threw a PsExec process event at it and it lit up: $ zds-core detection eval --event '{"event_type":"process_create","process_name":"psexec.exe"}' 1 alert ( s ) : [ high] PsExec Execution — ( matched: map[process_name:psexec.exe] ) A wevtutil cl Security event tripped a critical "Log Clearing" rule. A plain notepad.exe matched nothing. Good — it detects, and it doesn't cry wolf. (Small UX papercut I fixed while I was there: if you forgot the event_type field, the engine silently matched nothing and printed "no rules matched" — which reads exactly like "you're safe." Now it warns you that the event can't match any rule. Silence that looks like safety is the most dangerous output a security tool can produce.) The one that hurt: ITDR Identity Threat Detection and Response. The engine has detectors for impossible travel, credential spraying, brute force, privilege escalation. All unit-tested. All green. I ran the real flow: POST two login events for one user — New York, then London thirty minutes later. That's ~5