another checkout failed and I'm opening a flattened event in the old trace view (yes I opened another). our agent runs across 4 services and emits 7.4 million spans a week. among those spans 518000 flatten nested tool arguments into strings. the old workflow handles service timing fine and loses structure around state changes. the span hierarchy ends at a string field containing the nested metadata. across 2860 failed checkout traces I can see the final checkout record and all 5 tool names but I can't tell which tool was earliest to mutate state. tool call attribution now means comparing fragments across sibling events by hand. still opaque.

so we’re weighing a migration from Datadog and Braintrust is one of the options. its nested span inspection is what I’m testing against that boundary. also checking SQL filtering against trace metadata and whether trace search can isolate checkout writes without another export. failed traces would also go into evaluation rows for the regression dataset. the migration estimate is 2 weeks (ambitious) and I haven’t picked a path. which setup kept mutation order intact through migration without a custom parser for every tool?

For years, we designed software to be maintained, extended, and reused because building it was expensive.

But if AI makes creating a replacement almost trivial, does that change how we should architect applications? Do we still spend weeks building the perfect abstraction, or do we accept disposable software and rebuild when necessary?

Where would you draw the line between maintainable software and software that's simply cheap enough to replace?

Have you ever written a useful piece of code, only to spend ages trying to find it again weeks later?

We kept running into this problem. Code snippets scattered across old projects, random files, notes, and even ChatGPT conversations.

So we started building something to solve it.

It's called CodShot, a workspace where developers can save, organize, search, and reuse their code snippets. We also added some AI-powered features along the way.

But here's what we're genuinely curious about:

Would you actually use a dedicated tool like this, or are GitHub Gists, VS Code, and your current workflow already enough?

And if you would use something like this, what features would make it genuinely useful to you?

We're still improving the project, so honest feedback, even criticism, would mean a lot! 🙌

For anyone curious, here's what we've built: https://codshot.com

Here's a fictional website inquiry:

“We need a five-page site. Can you migrate our old blog, and who will update the site after launch?”

A friendly reply about the design process could still leave both questions unanswered.

A Reddit comment on my Briefthread demo pushed me to focus on the pause before replying: make the client's actual requests visible before asking someone to review a draft.

A checklist you can use without any tool:

- Pull out the client's actual questions, keeping their wording.

- For each one, decide whether your reply answers it, asks a follow-up or explains why you're deferring it.

- Keep unknown scope, budget and timing marked as unknown.

- If you edit the reply, check it again.

I've now built that into Briefthread, a demo for freelance web designers and small web studios. The original inquiry stays available beside the draft. You review each request before copying, and you can correct the request list if the local rules miss something.

If you handle website inquiries, try a fictional sample and switch to Reply draft: https://briefthread.pages.dev/

Does checking requests one by one help you catch an omission, or does it add friction you'd skip? I'd especially like to know which check you'd remove or change.

This is a browser-local demo using keyword rules and editable templates, not live AI. Use fictional inquiries only. It doesn't connect to your inbox or send email, and a reviewed draft doesn't mean the scope is agreed or the project is ready to quote.

Hey everyone!

I’m a full-stack engineer specializing in Laravel, React, and modular business web systems. Recently, I built and launched Diya CRM (role-based auth, quotation pipelines, automated PDF generation) and a few platforms for educational academies.

I’m actively looking to expand my professional network on LinkedIn with fellow developers, agency owners, and SaaS founders to exchange ideas, share feedback, and support each other's launches.

Drop your LinkedIn profile in the comments or connect with me here:
www.linkedin.com/in/muthulaskhmi-vivek-108314445

Excited to connect!

I've been working with Claude models to create my SAAS, but an issue is that it looks sloppy. Some times it does well, but the majority of times it looks the same as other SAAS.

Id like to know what do you use to make your frontend look professional and clean?

Connect with clinicians and developers interested in building healthcare technology. Free to join: https://medicalcofounder.com

I'm organizing Spareware, an international open project building free software that platform co-ops can run on: rides, food delivery, short stays, selling and renting homes, trades and freelance work, and buying and selling, plus free design and office tools.

The model:

- The software is free for everyone, anywhere.

- On each marketplace, workers keep all of the profit except the running costs (servers and payment fees). Nobody takes a cut on top.

- Every cost is published monthly on an open ledger.

- Workers vote on their app's fees and rules.

- Any local group can run its own copy, because the code is open.

It's built by volunteers who donate the AI tokens they don't use each week, with a person reviewing every piece. We're at the planning stage: the architecture is mapped, and no app is running yet.

Before we build, I'd really value this group's experience:

1. What went wrong for platform co-ops you know, apart from the software?
2. How should votes on fees and rules work when the workers are in many countries?
3. What would make a local co-op trust shared software enough to run on it?

See all the demos: https://spareware-co-op.github.io/spareware/demos.html

Want to help build it? Ask to join here: https://github.com/spareware-co-op/spareware/issues/new?template=join-request.yml

When you ask to join, please include your LinkedIn or another public profile. We check everyone's background to keep the project safe.

Questions or ideas? Ask in our Discussions: https://github.com/spareware-co-op/spareware/discussions

i am in revops and comparing digital sales rooms for a team managing 20+ active deals. Every feature page looks the same now, rooms, content, analytics, MAPs, AI, all of it. The part i care about is what happens day to day once the deal gets messy.

Can the team see which stakeholders are missing, what is stuck, who needs a follow up, and whether the buyer is actually moving things forward? A nice room is easy to demo. Keeping execution visible across a buying group is the harder part.

For people who have used both Trumpet and Aligned, what feels different in actual usage? Not looking for a feature checklist, more interested in deal intelligence and stakeholder visibility. Appreciate any thoughts!

I started building ClientPDF in Jan 2026 because I wanted PDF tools that didn't require uploading files to a server.

But honestly, there are already tons of PDF websites, so I wanted to solve something more than just adding more tools.

Someone pointed out a fair problem with my project: why download and re-upload the PDF between every operation?

So I built a Unified Document Pipeline 😅

Now you can merge a PDF, organize pages, watermark, redact, sign or optimize it in one continuous workflow. Just click “Continue in Pipeline” to move to the next tool. There's also a floating toolbar to track your steps and undo changes before saving the final PDF.

Everything still runs locally in your browser. No uploading your documents to a server.

Started this back in Jan, and after multiple reviews and user feedback, it's improved a lot.

I'd really appreciate some honest feedback 🙏 What tools would you like to chain together? Anything confusing or missing?

And if you find it useful, sharing it with someone who works with PDFs would mean a lot!

https://clientpdf.tech

Solo dev in Melbourne. Last 12 months I've been building and selling ops software to small businesses on a monthly sub, about a dozen on it now. One of them also runs a small finance company and has asked me to build their back office from scratch.

Rough shape: a portfolio of active customer accounts, each with separate budgets (rego, insurance, fuel, servicing), money coming in monthly from employers, expenses paid out and recorded, monthly statements to each customer, and the whole thing has to reconcile to one bank account every month. All client money, none of it theirs, so a stuff up is serious. 2 or 3 users to start.

Where I've landed:
- Three phases, fixed price each, half up front half on sign off. Around $48k AUD total. A quoting tool as an optional fourth phase later.
- Software records and calculates, never moves money. Humans pay from the bank, system reconciles.
- I keep the IP so I can sell it to other businesses in that industry, they pay less because of that.
- Small yearly fee for hosting and updating the tax tables.

Never priced a custom build before, only ever done subs, so no reference point. Questions:

1. Fixed price per phase with a written sign off each, is that the right shape or do people regret it?
2. Does $48k sound low for ledger grade work where a mistake costs real money?
3. Anyone done the "I keep the IP, you pay less" thing, what did you wish you'd put in writing?

Cheers

Web and App: nova.valerois.com

Guys so i have done couple of things in the paste few days, i have crossed my 1k+ followers on Insta and facebook and got 10 users into waitlist and my app is also at the final stage.

But now i am thinking should i launch it in this week or should i hold on for some days until to get some more uses into the waitlist?

What do you suggest me guys ? What should i do now?

No idea how Wall Street values stocks?

I built IntrinsicInsightQ, a stock valuation engine that lets you challenge every assumption behind a valuation — from revenue growth and margins to WACC and terminal growth.

Instead of just giving you an intrinsic value, the platform lets you see how the valuation changes when you change the assumptions.

It includes DCF, DDM, multiples-based valuation, sensitivity analysis, Bull/Base/Bear scenarios, Monte Carlo analysis and peer comparisons.

I built it because I wanted a faster and more transparent way to understand why a stock is valued the way it is, rather than simply relying on someone else's price target.

It's now live and I'm looking for honest feedback.

What do you think? What would you change?

Try it here: https://intrinsicinsightq.com/

Hi everyone, I'm a student working on a project around SaaS retention, and I'm trying to learn from people who actually deal with this, not just read articles about it.

If you run a small SaaS, I'd love to hear:

1. What do you do when a customer cancels? (exit survey, email, nothing, something else?)

2. Do you feel you actually understand why people leave, or is it mostly guessing?

3. What's the most frustrating part of the whole process?

I'm not selling anything and don't have a link to share, I just want to understand the real situation. Any answer helps, even a short one. Thanks!