r/developer • u/Ok_Veterinarian3535 • 1d ago
The Skill Stagnation Fear
When did you realize your tech stack was becoming obsolete, and what did you do about it?
r/developer • u/Ok_Veterinarian3535 • 1d ago
When did you realize your tech stack was becoming obsolete, and what did you do about it?
r/developer • u/Organic-Detail1330 • 3d ago
I'm part of the team behind ALGO Skills, an early-stage practice platform. Instead of isolated exercises, you implement simplified versions of real systems (a Unix shell, HTTP server, rate limiter, key-value store, up to a Raft consensus model) and handle edge cases and failure, like what a rate limiter does on request 1,001.
It's early and I'm not claiming it's finished or proven. I'm looking for a few people who want to try it and tell me honestly:
where you got stuck or confused
whether the challenges teach what they claim to
what you'd change or drop
Ideal testers: students, recent grads or early-career engineers who are comfortable coding and willing to attempt a few challenges, not just browse.
Early access is free and by request: ALGO
If you'd rather not sign up, comment with what you'd want from a platform like this, which helps too.
r/developer • u/KingOfChateau • 6d ago
I run Claude Code and Codex on my Mac pretty much all day. The annoying part was never the coding, it was me sitting there waiting to see if one of them had finished or was stuck on a permission prompt.
So I built Untether. It's a menu bar app with a local server, and you open it from any browser. I mostly use it from my phone.
The part I actually care about is tasks. You type ut task new "add rate limiting to the API" and it starts an agent in its own git worktree. When the agent says it's done, a second agent reviews the diff and your test command runs. If that's all green it merges by itself. If not, it goes back to the agent. You can also make it wait for you before merging.
A few things people asked me in other threads:
It's free and MIT, repo here: https://github.com/Nachx639/untether
You need an Apple Silicon Mac on macOS 14 or later. There's no installer yet so you have to build it, the steps are in the README. It's beta and I'm sure it breaks in ways I haven't seen.
It started as a fork of VibeTunnel, which is what gets the terminals into the browser. Most of the rest I wrote with Claude Code, about half the commits in the repo are co-authored by it, and for a while now new features get built by queueing them as Untether tasks.
If you try it, tell me where it falls over.
r/developer • u/I00I-SqAR • 6d ago
The monthly GNUstep audio/(video) call takes place every second Saturday of a month at 16:00 GMT to 19:00 GMT. That is 11:00 AM - 2:00 PM EST (US) or 17:00 to 20:00 CET (Berlin time).
It's a Jitsi Meeting at the hamburg.ccc.de server (ccc.de is the German Chaos Computer Club) - Channel: GNUstepOfficial (Sorry, reddit don't let me post jitsi links here)
We usually just talk (who wants it might share video too) and occasionally share screens. Everybody (GNUstep developers and users) is welcome!
Also see https://mediawiki.gnustep.org/index.php/Monthly_Meetings please
r/developer • u/Machine-Jonte • 7d ago
I have as so many others vibe-coded my own orchestrator app... and I love it! I think everyone should vibe code their own! It's like the new Vim configuration.
r/developer • u/Ok_Veterinarian3535 • 8d ago
It's 2030. What technology that is popular today has completely died, and what niche tech has inexplicably taken over the world?
r/developer • u/Wonderful-Writer146 • 12d ago
I'm excited to share what I've been building lately. Papr: a fast, lightweight Terminal User Interface (TUI) built entirely in Rust to streamline your academic research workflow. An Obsidian, Zotero, and Overleaf alternative, but a bit better.
Key features
Papr is 100% open source, works offline, is memory-safe, and is designed to be fast and lightweight (only 12 MB).
I'd love to hear your thoughts, suggestions, or feedback!
r/developer • u/PurpleDragon99 • 13d ago
AI broke cybersecurity: code is written faster than we can review, detection is blind, and patching is too slow. Visual language Pipe fixes all three—code becomes reviewable by construction, and every block stays observable and patchable at runtime by design.
AI shook the very foundation of cybersecurity. It upended established practices and assumptions. Anyone can now use AI to scan code and find vulnerabilities quickly. What’s even worse, bugs found during one pass of AI code scanning might not be reported after rescanning. This is because of the probabilistic nature of AI – it gives a different response to the same prompt. It means that someone can find a zero-day vulnerability that may not be rediscovered on a later scan, even using the same AI model and identical source code. This could let one person discover and exploit a zero-day that others never see.
Cybersecurity problems are quickly growing in many cybersecurity-related aspects simultaneously. Let’s focus on three of them. They are: (1) AI generates code faster than teams can review it; (2) runtime threat detection is unreliable; and (3) patching is too slow. I will divide the analysis into two stages: development (design-time), and production (runtime).
A problem AI brought to development impacts cybersecurity indirectly, but it is still a significant threat. AI generates code in huge amounts so fast that development teams cannot review it in a reasonable time. Add to this the pressure on development teams to deliver productivity gains due to AI implementation, and the situation becomes even more dire. Teams have no choice but to skip detailed review, approving PRs automatically. This results in bugs slipping into the codebase and eventually causing crashes and vulnerabilities in production.
The most popular proposed solution is using AI for code review. Essentially, we are going to use AI to review code produced by another AI. There are problems with such a solution due to certain properties of AI itself. The main issue is that AI is bad at handling big context: the longer the task or instructions you give it – the more it hallucinates and the more sharply it degrades on a very large context. I face this problem all the time when trying to ask AI to generate code for even a modest, clearly detailed specification - AI skips, misinterprets and deviates from the specification a lot. The workaround is to have AI generate only scaffolding and continue step-by-step in a tool like Cursor – which proves the point: the model can’t handle the whole codebase. A codebase is a very large context for AI. Are we confident enough to trust AI 100% that the quality of its code review will be comparable to a human’s, even after multiple rounds? Probably not, and this is why human eyes are still needed. It means we are back to square one - dealing with an enormous wall of text code.
Now we will look into the production post-deployment stage. There are two closely related problems there: one is about the reliability of threat detection, and the other – the speed of reaction to an attack.
Let’s start with detection. The single source of information about what’s happening inside the application is log data. Log statements are pre-placed by developers in source code locations where they think it is necessary. Very often, needed log statements are missing and therefore, any threat detection system (no matter if it is AI-driven or not) can be blind to certain types of attacks. We cannot blame developers for that, because they cannot predict the future. This is the failure of the observability process relying solely on logs to get runtime information about application behavior.
Another problem is a reaction to a known attack or vulnerability. The standard process is going back to source code, investigating the problem, changing the code, approving/merging a PR and deploying via CI/CD. The whole process might take days or weeks, even if a new deployment starts fast. The deployment itself might take several days, because often, deployment stages have heavy tests attached that need significant time to complete execution. I worked for companies running complete application tests on every deployment stage to ensure the highest quality of the deployment, but at the heavy cost of the speed. The question is what the production team is going to do while waiting for the fix deployment. They have two choices. One is just waiting, assuming that nobody will exploit the discovered vulnerabilities and data will not be stolen as a result of it. This might be true in the pre-AI era. However, the frequency of AI-driven cyberattacks is growing very fast, and we might not be able to afford to wait today – the risk of losing data is much higher. An alternative is shutting down the whole system or a large independent module while we wait for the fix. However, it will break the continuity of the business. As we can see, both options are bad.
So, we identified three problems – one during development (AI code is generated too fast), and two during production (detection is unreliable and patching is slow). There is a variety of tools and approaches trying to solve these problems. However, their reliability and simplicity are questionable. For example, we can try to disable a certain part of the application using feature flags and tools like LaunchDarkly. However, the whole process of feature flag management is complicated, and it gets exponentially complex as the number of feature flags increases. We need to test many combinations of feature flags during deployment so that we can be confident switching them live on production does not break the application. I worked in companies that used feature flags, and they had a policy to remove a feature flag as soon as it is no longer needed to avoid the complexity of deployment tests.
There is one approach that fixes all three problems at once: visual programming – and I am working on such a solution. This is an unusual combination, but such an approach was proposed before. What’s different this time is a more powerful visual language “Pipe” I designed. This visual language combines two properties not usually seen together in other VPLs: generality and power. Usually, relatively powerful visual languages are domain-specific, while general-purpose languages are pretty simple. I spent 7 years closing this gap and designing a VPL that has both properties together. The reason we need a VPL to be general-purpose and powerful at the same time is that all text-based languages have both properties, and that’s the reason they dominate. Just to have a real opportunity to absorb a part of text code (no visual language can fully replace text code, even Pipe), a VPL must have similar properties to text-based programming languages. Let’s see how Pipe solves the three problems outlined above.
The first problem is that it is humanly impossible to review huge amounts of AI-generated code in a reasonable time. This application of VPL is obvious – visual logic is much easier to grasp. VPL does not solve the problem completely, but it mitigates it. As I mentioned before, no VPL is able to fully replace text code, so it will be a mix of visual diagrams and text code. The bigger the proportion of logic moved to visual diagrams from text code, the bigger the benefit of reviewing logic visually is going to be. AI will be generating visual diagrams with some code inside, instead of 100% text code as it does now.
The other two problems (observability and patching) rely on the same property of Pipe – its powerful semantics allows it to keep the visual graph not only during development, but also on production. The reason semantics needs to be powerful enough for this is that otherwise a VPL needs to be translated to a text language to fill missing details in text code, because the VPL itself is not powerful enough to cover it with visual code. So, the deployment chain in this case goes via text, losing the visual graph.
Having a full visual graph on production allows direct access to visual blocks. This has profound consequences both for observability and patching. Observability can be dynamic by tapping monitoring directly into the inputs and outputs of any block at any time right on production, in real time, replacing or complementing log data. Patching also becomes faster because the block can be patched, disabled or rerouted directly, right on production.
A concrete example: a payment-validation block starts leaking customer data. Today a team files a ticket, changes the code, runs the full test-and-deploy cycle, and hopes no one exploits the hole in the meantime. With Pipe, an operator taps that block’s inputs and outputs, confirms the anomaly in real time, and reroutes traffic to a safe fallback block in seconds – while the permanent fix goes through normal CI/CD. The vulnerability is contained immediately; the business keeps running.
I anticipate a very reasonable objection that direct modification of application behavior on production is dangerous and it can cause cascading failures. This is an absolutely legitimate concern. There are two possible solutions.
One solution is separating eventual problem solving and immediate reaction. For example, we can disable a single block or a group of blocks related to just one application feature, not impacting the rest of the application. At the same time, we ask developers to start working on a fix that will go via a normal CI/CD cycle. This way, we do not have to choose between two bad options: shutting down the whole application or assuming nobody will hack the system while a fix is in the works. What Pipe offers is the third option – shutting down or rerouting a vulnerable or dangerous part of the application temporarily, while we wait for a fix. Having such abilities requires a prepared manual giving clear instructions on what to disable in specific situations – developers must prepare such manuals. The good news is that it should not be a burden as AI will be able to help here.
Another solution is building a more sophisticated delivery process with testing right on production, leveraging direct access to blocks to tap the test suite into inputs and outputs, sending testing data to inputs, and analyzing responses from outputs. This process does not necessarily have to fully replace a normal CI/CD deployment – it can complement it to ensure the quality of the direct fix until a new CI/CD deployment arrives.
The key idea of defense against AI-driven cybersecurity attacks is also using AI. However, AI for attack is different from AI for defense. AI for attacks must exploit just one vulnerability – a physical analogy is a sharp, pointy spear. AI for defense must be solid and without holes (a shield), because we do not know beforehand where precisely an attack (a spear) is going to hit. However, AI built on top of existing systems will have lots of holes in the shield, and patching these holes will be slow.
The hot trend today is self-healing engines – an intelligent AI layer on top of the application, detecting attacks and reacting to them automatically. There are two key requirements for such an engine: reliable detection and real-time reaction. However, it is very hard to satisfy these requirements in current systems due to the reasons outlined above: detection is unreliable as the engine can use only fragmented data from logs (shield holes), and reaction is slow as the fix needs to go via the full CI/CD deployment (slow patching of shield holes). What Pipe offers is a solid foundation for such self-healing engines providing reliable detection and fast reaction.
The most frequent argument I hear against Pipe is that it requires rewriting existing applications – it is true. However, Pipe only complements text code, mixing visual logic with text. It means that migration does not need to retire the existing codebase immediately. Instead, the migration can be gradual – starting by encompassing the whole application or module in one root Pipe block. Then, whenever ready, moving one step below and distributing text code inside the root block between visual blocks of a second-level workflow, etc. You can stop subdividing blocks at any point, so it's entirely your decision which parts of the system become visual and which remain as text. Pipe provides a complete API for integration with text languages as part of the specification. Also, AI can automate workflow generation, text code distribution between visual blocks, connectivity, and layout of all visual components.
Like everything else in engineering, Pipe has its upsides and downsides. The biggest downside is the need to rewrite existing applications. However, there is also a significant upside – solving three critical cybersecurity issues all together, by the design of the solution. Considering the explosion of AI-driven cybersecurity threats, the current security model might already be outdated and we need to change it. So, weighing upsides against downsides, the upsides definitely win.
Yes – and it has been tried many times. But every time, managing those components gets complicated: the more you have, the more complex the web of their interactions becomes. The winning combination isn’t just highly granular software in production – it’s also a visual representation that makes all the relationships between them visible. This matters for both observability and patching: the visual graph shows you exactly which components to tap into, and which blocks to patch, disable, or reroute.
Computers of the 1970s and earlier had only a text-based terminal interface requiring knowledge of specific commands, so the UI was very unfriendly. The GUI revolution brought windows, icons, buttons, and other graphical elements. This made computers much more accessible to users. However, programming did not make this transition, and we still program using text only. AI is the catalyst that finally forces the move to visual programming – not because it’s nice to have, but because we no longer have a choice.
Website: https://pipelang.com
Pipe IDE URL: https://www.pipelang.com/pipe/v1/
Tutorials:
r/developer • u/Significant-Sea-7238 • 13d ago
I usually have 2-3 Claude Code / Codex sessions going in different terminals, and the real slowdown was me not noticing one was waiting for permission.
My fix was building a small open source app that shows them in the notch (top of the screen on Windows). Working / waiting / done at a glance, and when one wants to edit a file I see the diff there and approve with ⌘Y.
https://github.com/MF-DEEV/Openbar
How do you handle it? Tmux panes, notifications, just checking every few minutes?
r/developer • u/Ok_Veterinarian3535 • 16d ago
What's a non-obvious sign you were heading for burnout, and what was the one change that actually helped you recover?
r/developer • u/ALonesomeDove • 16d ago
Hi,
I am a software engineer working full time as an independent contractor working 40 hours per week. I am interested into breaking into freelance work.
I have heard about sites such as Upwork and Fiver. I just need to make sure it doesn't have a conflict of interest with my current role and will not be more than a weekend or a couple of hours worth of work each weekday.
What is the best way to find these sorts of jobs? This is to all of you who have been able to work into this.
r/developer • u/Enough_Charge2845 • 17d ago
A keyword list from ChatGPT comes from general knowledge and says nothing about how many postings it rests on. A plausible suggestion is not the same as a common one.
A product manager could be told to add Productboard. None of 421 postings names it but roadmap appears in 85.5%. A software engineer could be told to add Angular, Vue or Swift. They appear in 2.9%, 3.2% and 2.3% of 1,360 postings while scalability is at 52.9% and Python at 44.8%. A marketer could be told to add LinkedIn Ads or Meta Ads. They appear in 0.3% and 0.6% of 347 postings, while go-to-market is at 53.0%.
ChatGPT is the better tool for rewriting a bullet. The counts for seven roles (3,518 postings) and the method are on https://resumefitting.com matching is by term, so a missed synonym counts as absent.
r/developer • u/UCREAS • 17d ago
If you're job hunting amid layoffs. I've mostly used resources I've found online and LeetCode.
Was looking around for more in depth list of interview questions. I think it's good. I've actually encountered an interview question on RAG that I prepped on. It's not like designing rate limited that's been covered a thousand times.
ymmv.
r/developer • u/blunt-vibz • 17d ago
Assuming Python and pip are available, I can install the required libraries in a virtual environment. I’ve already managed to install and run the Qwen2.5-Coder 1.5B model locally without requiring administrator privileges. With just five minutes of internet access during the lab exam, I can automate the remaining setup. Clipboard access is the only thing I still need to figure out.
r/developer • u/der_gopher • 18d ago
to learn go
r/developer • u/AccomplishedSugar490 • 19d ago
AI0Win has been abandoned, KBSI moved on to other pursuits, the entire IDEF series of methods have been deprecated as US federal standard, but one of those, IDEF0, despite getting conflated with ICOM diagrams, poor support in drawing tools, and a stagnated dedicated modelling tool, was different.
As one facility of a very ambitious project, I needed the model data and an effective way to author and maintain it collaboratively, so I created a web-based tool that does exactly that.
My own plans with what I created extend well beyond what AI0Win did, but to take it beyond, will almost certainly break the round-trip fidelity and compatibility I have maintained to date.
As it stands, I do not know of a single AI0Win user other than myself, and the even I don’t use it for more than testing since I have a functional modeller of my own to use.
If you used or still use AI0Win, please speak up or get in touch.
I have the new tool running on a small server that won’t hold up under the potential load of running as a free public service, but if you DM me an email address I can invite you to check it out as a demo.
If I’m the only remaining user, I’m going to pull the plug on compatibility I don’t need, so if you have any interest in such a tool, can use compatibility with AI0Win itself, or have a load of old AI0X or AI0 Neutral Text (.TXT) file you’ve lost access to and wish to convert, let me know how. I can probably help.
r/developer • u/Ok_Veterinarian3535 • 21d ago
Developers who have worked on a large, well-known, or legacy application: If you could go back in time and change ONE architectural decision from the start, what would it be and why?
r/developer • u/Forsaken_Desk412 • 21d ago
Hey everyone!
I've built a few simple apps before, but this is my first time building a visual novel game, so I'm trying to figure out the best way to approach it.
My budget is under $500, and I want to build something that I can expand over time without having to rebuild everything from scratch later.
I'd love some advice from people who've worked on visual novels or indie games!
A few things I'm trying to figure out:
• Game engine: Should I use Ren'Py, Unity, Godot, or something else? What would you recommend for a beginner who's comfortable with basic app development?
• Tech stack: If I want the game to be scalable and maintainable as I add more content and features, what would be the best approach?
• Best practices: What should I plan for from the beginning, especially when it comes to dialogue systems, branching storylines, character relationships, save files, and player choices?
• Budget: With less than $500 to spend, what should I prioritize? Are there any free tools or resources you'd recommend for art, music, sound effects, and other assets?
• Common mistakes: For those who've built a visual novel before, what do you wish you'd known before starting?
I'm also curious about how people approach monetization and publishing, although getting the game built properly is my first priority.
I'm not looking for the most complicated setup. I want something practical that I can build with, learn from, and expand as the game grows.
Would really appreciate any advice, resources, or lessons from your own experience. Thanks!
r/developer • u/Enough_Charge2845 • 24d ago
A recent analysis of 3,518 job postings from 81 companies across seven roles found some interesting patterns.
In several categories, generic terms appeared more often than the big-name tools. “Observability” showed up more than “Grafana,” while “SIEM” appeared more than “Splunk.”
That raises an interesting question: are resumes too focused on listing specific tools and not enough on the broader skills and terminology employers use?
The study breaks down the results by role, including software engineering, cybersecurity, DevOps, marketing, product, accounting and sales.
The full dataset, methodology and findings are here:
r/developer • u/Actual_South_2484 • 25d ago
my side project is a deterministic simulation in rust (same seed and same tick count give the same world), and most of my nasty bugs come from "harmless" refactors that quietly change outcomes. what i settled on:
curious how others handle this, especially golden-file style checks that don't turn into constant churn.
the project, for context, is a civilization sandbox that runs in the browser: https://thehumanbox.com
source (mit): https://github.com/1homsi/thehumanbox
r/developer • u/Efficient_Let216 • 25d ago
Same app. Multiple themes. The chart does not change when the colors do.
Meet 15 new people a day
A match stays open for 14 days
Host a night, or just show up
Check in, then talk to the room
Post the photo if the night earned it
A full birth chart, with the Sun, Moon, and rising on one wheel
Compatibility from both charts, not a list of signs
Discover, with a voice on the profile before the photos
Today’s transits on your own chart
One theme across the whole app, not a single button
Cosmic Pass when you want the paid stuff unlocked
Looking for testers to try it out and give feedback.
#TheLoveStar #dating #singles #astrology #events
r/developer • u/kunjontemon • 25d ago
Hey everyone! I’m exploring ways to extend an existing internal production health-check bot that monitors systems checks whether the important pages loads or not and sends status updates to Microsoft Teams.
I’m looking for ideas beyond basic health checks, such as proactive alerts, log analysis, incident detection, automated troubleshooting, or AI-powered features.
What useful automations have you built around monitoring bots? Which ones have made the biggest difference in real-world scenarios?
Would love to hear your suggestions and experiences!
r/developer • u/PurpleDragon99 • 28d ago
I'm happy to announce the release of the web-based Pipe IDE for my project - General-Purpose Visual Programming Language Pipe (https://pipelang.com)
Pipe IDE requires no account - all data is stored locally in your browser's database, keeping friction to a minimum.
This first version has limited functionality, but it already includes a core set of components that let you build realistic, working visual applications, with Python integrated as a text-based extension of visual programming.
Pipe IDE URL: https://www.pipelang.com/pipe/v1/
Tutorials:
The next milestone is converting Pipe IDE into a full-scale product with a backend database.
======
1. Why now?
The need for visual programming has become especially clear now that we're building with AI, which has introduced several serious problems that appear unrelated - yet visual programming addresses all of them at the root:
2. Why start with a book instead of building the software first?
Most new languages start with an implementation. For visual languages, that software-first path is exactly what traps them in a single domain and keeps them from ever becoming general-purpose. I did the opposite and specified the full language first; the software is what I'm actively building now.
It avoids both failure modes. Software-first visual languages get stuck in their first implementation's domain, while purely theoretical ones get buried in complexity - too intricate and incomplete to be practical. Pipe takes the middle ground: well-chosen, practical primitives within a complete, coherent architecture.
The book's subtitle says it best - "A Pragmatic Approach to Visual Programming." It rests on seven years of R&D but stays in the practical lane, and the result is a consistent, usable, end-to-end visual language.
3. Do we need to rewrite our existing system in Pipe?
To some extent, yes - but the transition is far less disruptive than it sounds:
4. We tried visual programming before, and it didn't work.
Every technology advances in a spiral - it fails several times before its lessons are learned and it finally succeeds. Pipe was built by studying exactly why earlier visual languages fell short. Two lessons in particular shaped it:
r/developer • u/Real_Grapefruit_5570 • 29d ago
I've been looking into ways to access YouTube data for projects involving video analytics, channel research, and content discovery. There are a few different APIs and tools available, depending on whether you need basic video details or more specific data like comments and transcripts.
Here are some options worth comparing:
Before choosing a solution, I'd look at a few things:
The official API may be sufficient for many projects, while other tools may be worth evaluating if you have different data requirements. I'd test the same few videos and channels across the options before settling on one.
What are you using to collect YouTube data? I'm particularly interested in solutions that work well for channel research and video analytics.
r/developer • u/vince_760 • 29d ago
Like most of you, I like to develop random shit all the time but I like to keep track of the analytics. Sometimes Cloudflare gives me boasted numbers due to bots, or getting hammered by one thing or another. My go to for so long has been Google Analytics, but for each project I needed to switch between the tabs and could never figure out how to see all the projects in 1 place.
So I built a dashboard that shows me all my live users from all projects from GA4 in 1 place. Gives me some basic analytics at the bottom and keeps me from going to multiple tabs if I need just a quick reference on how my sites are doing at any give point. I named it FlotillaHq.com give it a try if you want, its free. I dont get your data or anything just trying to help out other devs if it works for you.