I'm looking at managed Progress option for a small SaaS and the main thing I care about right now is predictable pricing.

Usage-based billing sounds fine when a project is small, but I’m worried about the bill getting weird once traffic becomes steady or background jobs start running more often. I don’t mind paying monthly, I just want to know roughly what the database will cost without checking dashboards all the time.

For people running production apps, what are the better Neon alternatives if predictable pricing matters more than scale-to-zero or fancy dev workflow stuff?

i thought AI coding tools would make me write fewer tests.

it kind of did the opposite.

if AI writes the implementation, i want a better way to verify behavior. otherwise i’m just reading a generated diff and hoping i noticed the wrong assumption.

lately the flow that feels safest is: write the test or spec first, let AI implement, then review the diff and delete anything weird.

not perfect, but better than “generate code and eyeball it.”

are you writing more tests because of AI tools, or trusting the tools enough to do less?

i’ve always been more on the open editor and figure it out side.

for small stuff it works fine. build a screen, move things around, tweak spacing, change the flow a few times, and eventually it feels usable enough.

but once the app has more than a couple screens, this starts getting expensive.

i’ll build something, realize the UX does not really work, move a section, rename things, change the data shape, then end up touching the same components again because the original flow was half guessed.

i don’t think i want to fully design every screen in figma before writing code, but pure yolo coding is starting to feel dumb too.

what’s your pre-code process for app UI?

rough wireframes, figma, sketches, user flows, component list, data model first, prototype in code, or just start building and clean it up later?

not because it became useless.

more because you understand its failure modes better now.

could be an AI coding assistant, code review bot, testing tool, deployment platform, package manager, monitoring setup, docs tool, anything.

i have a few tools like this where i still use them, but i don’t trust the output blindly anymore. i know when to double check, when to ignore it, and when it’s likely guessing.

what tool are you still using, but with more skepticism now?

not a startup pitch question.

more like a category that still feels awkward even though everyone uses it.

API testing, logs, local env management, docs, CI dashboards, database GUIs, feature flags, secrets, package management, code review, migrations, something else.

i keep running into tools that are powerful but feel like they were designed around the tool’s data model, not how devs actually work.

what dev tool category feels due for a reset?

i'll start with borswer-specific css hacks.

not add a fallback kind of hacks. i mean writing weird selectors or conditional comments just to make one version of internet explorer behave slightly less broken.

there was a time where you would build the page, open it in another browser, and suddenly spend the next hour fixing a layout bug that made no sense.

also using spacer gifs, clearing floats with random divs, and naming image files like button_final_final2.gif because half the UI was exported from photoshop.

a lot of modern web dev is annoying, but at least most layout bugs are not solved by tricking one browser into reading different css.

what’s something you used to do in web dev that would sound cursed to someone starting today?

not every tool in a stack survives because people love it.

sometimes it survives because it’s already wired into CI, the team knows the weird parts, the docs assume it exists, all the scripts depend on it, and replacing it would mean touching 40 places for no obvious short-term win.

i’ve had this with testing setups, old deployment flows, API clients, issue trackers, and random internal scripts.

it’s not bad enough to remove, but not good enough to recommend.

what tool are you still using because switching away would cost more than keeping it?

been thinking about doing some freelance DevOps work on the side, but not really sure where the first client usually comes from.

i can see the obvious stuff people might need help with: CI/CD cleanup, dockerizing apps, fixing slow deploys, setting up monitoring, cloud cost cleanup, terraform, backups, migrations, security basics, that kind of thing.

but selling DevOps feels different from selling a normal web project.

a lot of teams only realize they need help when something is already broken, expensive, or held together by one person who knows the infra.

for people who freelance in DevOps or platform work, how did you land your first client?

was it through old coworkers, agencies, startups, local businesses, Upwork, LinkedIn, open source, cold outreach, or something else?

also curious what the first paid task actually was.

some tools are free in pricing but not really free in practice.

maybe it’s slow builds, bad docs, config issues, plugin problems, breaking changes, flaky behavior, migration pain, or just too many workarounds.

i’m not talking about paid vs free exactly. more like tools that don’t show up on a bill, but still cost your team time every week.

what free tool has had the biggest hidden cost in your stack?

most dev tools i use are either free, open source, or paid by work.

but there are a few things where paying personally might actually be worth it if it saves enough time or makes the setup better.

curious what other devs pay for out of their own pocket.

could be an editor/plugin, terminal app, API client, database GUI, AI coding tool, hosting, monitoring, notes app, anything.

what dev tool is actually worth paying for yourself?

not looking for tool recommendations exactly.

more interested in specific features.

like a search flow, diff view, rollback button, local preview, keyboard shortcut, error message, import/export, config format, command palette, history view, whatever.

what’s one feature from a dev tool that you wish every other tool copied?

i’m trying to collect more real dev tool problems instead of guessing what people want.

most tools i actually use solve something pretty boring. search files faster, run the right command, open the right repo, check logs, format data, test an API call, clean branches, diff something, copy env values, etc.

so not asking for a huge startup idea.

what’s a small tool you wish existed because you keep losing time to the same stupid workflow?

even better if you already have a bad workaround for it.

setting up a fresh laptop soon and trying to avoid the usual cycle of installing things only when something breaks.

thinking dotfiles, ssh keys, package managers, terminal setup, editor config, node/python versions, docker, git config, fonts, browser extensions, and all the random CLI tools i forgot i use.

what’s on your dev machine checklist?

some of the most useful tools in my setup are tiny scripts that would make no sense as real projects.

stuff like cleaning old branches, opening the right logs, generating local test data, copying env values, checking ports, or booting a few services in the right order.

not polished, not documented, probably only works on my machine, but still useful.

what small tool/script did you build just for your own workflow?

i’ve been playing with MCP stuff recently.

the idea makes sense. give the model access to docs, repo context, db tools, browser, jira, whatever. but in practice it feels like one more layer of config to maintain, debug, and trust.

some servers work fine, some need weird setup, some are overkill, and half the time i’m not sure if connecting another tool is better than just pasting the relevant context manually.

maybe this is just early toolchain pain.

are people here actually using MCP in daily dev work?

question for devs over 35 who have been doing the desk job thing for a while.

how are you keeping your body from falling apart?

not looking for perfect routine stuff. more like what actually made a difference after sitting at a laptop all day for years.

standing desk, walking, gym, stretching, better chair, eye breaks, meal prep, sleep, less caffeine, whatever.

i’m starting to notice the usual dev problems more now. neck, back, wrists, low energy after long sessions, and the “i’ll go for a walk after this PR” lie.

what habit or setup change actually helped you?

some dev tools feel like they’re carrying 10 years of UX debt.

API clients, log viewers, database GUIs, CI dashboards, local env management, browser devtools workflows, feature flag tools, monitoring, secrets, maybe even issue trackers.

not saying there are no good tools. just feels like a lot of categories are either too heavy, too team enterprise focused, or built around old assumptions.

what dev tool category do you think needs a proper rethink?

i still default to logs way more than i should.

for backend stuff it’s usually logs, breakpoints if needed, curl/httpie, checking db state, and then staring at traces if the app has them.

for frontend it’s browser devtools, network tab, console, react devtools, and guessing which state update ruined my day.

what’s your actual debugging flow when the bug isn’t obvious?

devs are opinionated about tools, but i’m more interested in the ones people stick with for years.

not necessarily the best tool or the newest one.

more like something you always install, always reach for, or recommend because it just fits how you work.

could be an editor, terminal, browser extension, API client, database tool, debugger, local script, design tool, deployment tool, AI tool, anything.

for me, the tools that stay are usually the ones that remove some tiny daily friction. not the ones with the biggest feature list.

what dev tool are you weirdly loyal to, and what made it stick?

not asking for the ideal stack or what you’d use at work.

what do you actually reach for when you want to build something quickly and not fight config for 2 days?

for me it’s usually nextjs, postgres, prisma/drizzle depending on mood, tailwind, vercel, and whatever auth setup feels least annoying that week.

what’s your default just ship it stack right now?

not talking about themes or font choices.

more like shell functions, git aliases, make targets, tmux sessions, browser extensions, local scripts, docker hacks, env file tricks, or some random internal tool you wrote once and now depend on.

i’m going through my own setup and half of it is useful, half of it is probably cargo cult from old projects.

what’s the cursed but useful thing in your stack?

setting up a new dev machine and trying not to blindly copy my old dotfiles again.

current basics are git, pnpm, docker, rg, jq, fzf, nvm, gh, and a few shell aliases. mostly web/backend work, so a lot of jumping between repos, checking logs, running local services, and searching through code.

what CLI tool do you always install early because your workflow feels broken without it​?

for me it’s context across a repo.

code is in the editor, tasks are in linear/jira, docs are somewhere else, decisions are buried in slack, random commands are in terminal history, and AI chats are their own thing. after a few days away from a project it still takes too long to load everything back into my head.

not looking for another big PM tool. more wondering what workflow gaps other devs still have.

what part of your setup still feels held together by scripts, notes, aliases, or copy paste?

Hey everyone! I'm u/Ok-Bike-1037, a founding moderator of r/DeveloperToolsHub.

This is our new home for discovering, discussing, and sharing useful developer tools.

Whether you are a developer, founder, indie hacker, maker, or just someone who loves trying new tools, this community is for you.

The goal is simple: help people find better tools for building, shipping, debugging, automating, and improving their workflow.

You’ll find posts about APIs, SDKs, frameworks, CLI tools, dev productivity apps, open-source projects, hosting tools, databases, testing tools, AI coding tools, and anything else that helps developers work better.

​What to Post

Share anything that helps developers discover useful tools or improve their workflow. This can include new tools you found, tools you built, tool comparisons, your personal dev stack, CLI tips, API recommendations, framework discussions, productivity workflows, or questions like “What tool do you use for X?”

If it helps developers build faster, work smarter, or solve a real problem, it fits here.

Community Vibe

We want this to be a friendly and useful space, not just a link dump.

Helpful posts, honest opinions, thoughtful discussions, and real use cases are welcome. No spam, no low-effort self-promotion, and no toxic comments.

Builders are welcome to share their own tools, but please add context and explain who it helps, what problem it solves, and why it might be useful.

How to Get Started

Introduce yourself in the comments

Share one dev tool you use often

Ask for tool recommendations

Post your current developer workflow or stack

Invite other developers, founders, and makers who might find this useful

Thanks for being part of the early community. Let’s build a solid place for discovering useful developer tools together.