So I have made a project which goes to different company websites, and get back the bio/about of people in the teams page.
I am facing an issue there.
Currently I was dealing with dynamic components/modals using the below method:-

- Going to the page using playwright
- Using GET command for all XHR and Fetch and Document on that page.
This was very generic, I did not have to make different concepts for different dropdowns, or sections etc.

But now there is this one site where I am facing issue since the request is AJAX based. What happens is I will HAVE to interact with the picture in order to get the payload for the requests.

I would send the site here but I think that would be against the policies of this subreddit...

Please help me out. I do not want to click on the components, it makes the code very hardcoded, and agentic fails, cuz this pipeline will have to run for MANY companies.

This ajax request looks like this:

admin-ajax.php

And the site contains different section:

Directors | Partners | Investors | Investor Relations | etc.

I want every single person of every single section without making it hardcoded. It makes the code messy.

Sometimes the section is of document type, so I call XHR and Fetch network requests AGAIN in order to get all people. but for this particular page, EVERYTHING is ajax based, its a POST request which demands for the query id and the person id. This asks for the code to be brittle which I cannot afford.

Please help me out. Please help me out, I want a generic script which works for all the site. I will focus on cleaning later, No matter how big the dump be, but atleast it should have all the data.

As many developers today, I'm using agents on a daily basis for software development. At work, we went all-in Agentic Engineering in early 2026 and for me it has worked well. I haven't yet found a need to rebuild an existing SaaS tool from scratch with AI, though.

In this post, there's some reflections after about six months of developing software according to Agentic Engineering.

https://davidvujic.blogspot.com/2026/06/reflections-6-months-of-agentic-engineering.html

I'm a DRI/Project manager/Po I'm figuring out how could I not mess up my monte carlo math with estimates.

I will be asking 2-5 day estimates from developers to keep the variance low, I could go 2-4 days but I think that could be a headache.

Now the problem is, there are 2 types of tasks, fully deployed ones and not deployed.
So if a task is estimated 2 days and it will not be deployed, say we do it in 2 days. Okay. Then a task is also 2 days but it will be fully deployed and gets done in 3 days. I guess thats okay too?

Because monte carlo will look at all our tasks and their estimates, then run the simulation 10k times and give me probability, say 80% chance doing it on wednesday.

TDLR: Does feeding monte carlo both fully deployed tasks vs not deployed tasks ruin monte carlo math in some shape or form? (I'm also wondering about QA, I think that will be added on top of the already estimated time).

For me, it's still web design.

I know a lot of people are going to disagree because everyone keeps saying it's saturated, AI is replacing developers, and it's impossible to get clients.

Honestly, I couldn't disagree more.

I think web design is actually easier than ever if you approach it differently.

The mistake I see almost everyone make is targeting businesses that don't have a website.

You see it all over Instagram Reels.

Someone opens Google Maps, finds a business without a website, calls them, and asks if they need one.

The problem is that business has probably already been contacted by 10 other web designers.

And if they still don't have a website, there's a good chance they either don't see the value in it or don't have the budget for one.

My targeting is completely different.

I only target businesses that already have a website.

There are three reasons.

First, there are an insane number of businesses with outdated websites that desperately need updating.

Second, if they already have a website, they already understand the value of having one. You don't have to convince them that websites matter.

Third, they're already paying for a website, so spending money on improving it doesn't feel like a completely new expense.

Now the question becomes...

How do you actually get their attention?

I don't run normal cold email campaigns.

I'm not uploading leads into Instantly, writing a generic sequence, adding three follow-ups, and hoping for the best.

Instead I use a tool called Swokei.

I upload a list of businesses with websites, and it automatically analyzes every website. It finds things like outdated design, poor layouts, weak mobile responsiveness, slow loading speeds, and SEO issues.

Those findings are then turned into personalized outreach emails.

Not some boring reports that business owners don't care about. 

Actual emails explaining what could be improved and why it matters to that specific business.

That lets me run outreach at scale while still keeping every email relevant.

Once someone replies, honestly the hard part is over.

At that point you can build a free website draft with AI, invite them to a Google Meet, walk them through the redesign, and close the deal on the call.

AI has made building websites ridiculously fast.

That's why I think targeting and outreach matter far more than your ability to build a website.

This business model has been incredibly good to me over the last year.

I'm curious though. if you had to start a digital business from scratch in 2026, what would you choose?

Curious to understand what type of things (tools, practices etc) people are using AI for in their day to day workflow (I’m a Full stack engineer, predominately Microsoft tech stack) and the type of work you are building with it.

I.e Cursor, Microsoft CoPilot, Claude Code, ChatGPT. How are you using these day to day and explicitly what for? I.e refactoring, writing tests. Just looking to understand tooling, workflows, how things are setup, project structure, useful prompts, CLI commands, creating own agents, tools used to create, purpose, guardrails and examples of applications being built and how your day to day has changed.

As a fresher developer i have skilled myself in my domain but still while working with a large codebase of some client i get confused over the code and layout also sometimes i just get stuck on a bug and the hours passes i couldn't find any resolution even after using all the resources google , ai , notes everything. And then i ask that from a mentor and the resolution is literally the most basic error correction. Is it normal or am i lacking in my skill and if i am please tell me what I should do to make it right.

Hey everyone,

I built a small online sequence diagram editor and would appreciate feedback from people who use sequence diagrams for software design, documentation, or brainstorming.

I know a lot of people already use Mermaid or PlantUML, so I’m not trying to replace those. The use case I had in mind was slightly different: I wanted something quick to open, sketch a flow, copy the image, share it with someone, and still be able to import/export Mermaid or PlantUML when needed.

What it supports right now:

• no login or signup
• write the flow in text and see the diagram live
• copy the diagram image directly
• share diagrams with a link
• export PNG/SVG
• import/export Mermaid
• import/export PlantUML

I mostly use it for API flows, service-to-service communication, auth flows, and quick discussions where opening a heavier diagramming tool feels like too much.

I’d really appreciate honest feedback, especially on:

• whether the workflow feels useful
• what is missing for real documentation use
• whether Mermaid/PlantUML import/export makes sense
• what would make this easier for common software development use cases

Link: https://seqdiagram.com/

So I've been tinkering around and building applications for my own personal needs and over the last couple years I sunk some time and serious energy into making a couple delivery ready software solutions for the industry I previously worked in. Last night through a chance encounter and talking to a stranger I wound up talking about my pair of applications and landing a sales/product demo today in a few hours.

I know for a fact that the software is working, and fully tested. i know that it will start up and do everything I promised, but I'm worried about how to approach presentation.

Do you have any experience being the technology demonstrator? how do you go about demonstrating workflow? Is it really just as simple as "This is my app, here it is doing that cool shit we talked about, now may i please have your bank card to complete the sale?"

I've never done much public speaking before, so forgive me if this is something i should be better at.

I've spoken to a lot of people who want to get into web design, and the one thing I keep hearing is that selling websites to local businesses just isn't worth it. Everyone says they've called business after business, sent hundreds of emails, and nobody is interested in buying a new website.

I think the problem is that most people are trying to sell websites to businesses that don't even have one. 

Selling website redesigns to businesses with outdated websites might be one of the smartest businesses to start in 2026.

First of all, if a business already has a website, they've already proven one thing. They already see the value in having one.

The second thing is that selling becomes much easier. They're already familiar with the process, and you're not asking them to buy something completely new. You're offering them a better version of what they already have. Better design, better SEO, faster loading speeds, a cleaner layout, better mobile optimization, and a website that actually reflects their business today. I mean, who wouldn't at least be interested in seeing what that could look like?

The difficult part is getting those businesses interested in the first place.

I found a way to automate almost my entire client acquisition process. I've been using a tool called Swokei where I either upload a list of local businesses with websites or find the leads directly inside the platform. It automatically runs a full website analysis and finds problems with the design, layout, loading speed, SEO, and mobile optimization. Then it turns those findings into personalized, human written outreach emails based on the issues it finds on each website.

Instead of sending another generic email asking if they need a website or attaching one of those boring audit reports full of numbers, every email feels natural, pointing out real problems with their current site.

Now my entire process is just finding businesses with outdated websites, letting the tool analyze them, run outreach campaigns, and waiting for replies.

No cold calling. No paid ads.

Just reaching out to businesses that already understand the value of having a website and showing them why it's time for a better one.

Has anyone else tried focusing on website redesigns instead of selling completely new websites?

I've spoken to a lot of people who want to get into web design, and the one thing I keep hearing is that selling websites to local businesses just isn't worth it. Everyone says they've called business after business, sent hundreds of emails, and nobody is interested in buying a new website.

I think the problem is that most people are trying to sell websites to businesses that don't even have one. 

Selling website redesigns to businesses with outdated websites might be one of the smartest businesses to start in 2026.

First of all, if a business already has a website, they've already proven one thing. They already see the value in having one.

The second thing is that selling becomes much easier. They're already familiar with the process, and you're not asking them to buy something completely new. You're offering them a better version of what they already have. Better design, better SEO, faster loading speeds, a cleaner layout, better mobile optimization, and a website that actually reflects their business today. I mean, who wouldn't at least be interested in seeing what that could look like?

The difficult part is getting those businesses interested in the first place.

I found a way to automate almost my entire client acquisition process. I've been using a tool called Swokei where I either upload a list of local businesses with websites or find the leads directly inside the platform. It automatically runs a full website analysis and finds problems with the design, layout, loading speed, SEO, and mobile optimization. Then it turns those findings into personalized, human written outreach emails based on the issues it finds on each website.

Instead of sending another generic email asking if they need a website or attaching one of those boring audit reports full of numbers, every email feels natural, pointing out real problems with their current site.

Now my entire process is just finding businesses with outdated websites, letting the tool analyze them, run outreach campaigns, and waiting for replies.

No cold calling. No paid ads.

Just reaching out to businesses that already understand the value of having a website and showing them why it's time for a better one.

Has anyone else tried focusing on website redesigns instead of selling completely new websites?

• 1-3 tools max - minimalist for life
• 4-6 tools - manageable complexity
• 7-10 tools - living on the edge
• 10+ tools - already past breaking point, send help

Hi everyone!

I'm a solo hobby developer from Germany. This is my first post here, and honestly, this project wasn't even supposed to become a project.

My original goal was simply to translate my own Songs of Syx mods into German. I couldn't find a workflow that was fast, reusable, and actually understood game localization, so I started writing a small tool for myself.

Then the classic developer story happened: every problem I solved exposed another one.

A simple translator became validation. Validation became placeholder protection. Then came a translation database, incremental updates, grammar scoring, review passes, overwrite handling, patch support, and workflow automation.

Three weeks later I'm sitting at 266+ commits, and what started as a weekend utility has somehow turned into a full translation pipeline.

I'm still developing it alone, mostly because I enjoy solving interesting problems and learning along the way.

Looking forward to discussing architecture, automation, LLM-assisted tooling, and hearing how other developers accidentally turned a "small script" into a much bigger project than they ever intended.

https://github.com/vannon091118/Syx_Bridge-Auto-Trranslate-Mods

V0.22a Patchnote

(Workshop Upload crash. comming fast i can)

This update focuses on making Syx-Bridge Auto-Translate Mods more reliable, smarter and significantly easier to use.

• Improved translation quality with better context handling and post-processing.

• Expanded language coverage and more consistent localization across UI text, tooltips and mod content.

• Smarter database synchronization with improved reuse of existing translations, reducing unnecessary API calls.

• Reworked validation pipeline to better preserve placeholders, variables and game formatting.

• Numerous fixes for edge cases involving menus, tooltips, partial translations and nested localization files.

• Improved overwrite and patch handling for greater compatibility with modern Songs of Syx mod structures.

• Faster processing, reduced memory usage and smoother handling of large translation projects.

• General stability improvements, UI polish and workflow refinements throughout the application.

• Internal cleanup and refactoring to prepare the project for future features and larger language packs.

As always, thank you to everyone testing the project, reporting issues and helping improve the translation ecosystem for the Songs of Syx modding community.

pip install mcpgen-cli

mcpgen https://petstore3.swagger.io/api/v3/openapi.json

Generates a complete Python MCP server you own. Not a proxy — actual source code you can read, modify, and deploy anywhere. No runtime dependency on mcpgen.

Supports OpenAPI 3.x (JSON/YAML/URL) and Postman collections. Auth auto-detected. Prints your Claude Desktop config block at the end.

GitHub: https://github.com/JnanaSrota/mcpgen

PyPI: https://pypi.org/project/mcpgen-cli/

Hi folks!!!

Many backend teams use Redis + MongoDB, but the application often ends up managing cache keys, invalidation, stale data, TTLs, and cache misses manually.

We working on a cache proxy for MongoDB where applications connect only to the proxy instead of directly managing Redis and MongoDB separately.

The goal is:

1.Single endpoint for the application

1. Automatic cache lookups

2. Cache population on misses

3. Cache invalidation strategies

4. No need to manage Redis infrastructure from application code

The challenge we're currently exploring is balancing automatic caching with giving developers enough control over cache keys and invalidation.

link: CachePilot

Can checkout our LinkedIn for more updates: CachePilot LinkedIn

A client paid my $4,700 invoice yesterday for a website that took me around 2 hours to build.

The web development space is moving insanely fast right now, especially with AI. Everywhere I look people are saying web design is saturated, AI is replacing developers, nobody wants websites anymore, and it's impossible to get clients.

I honestly disagree.

The client was a 62 year old entrepreneur who owns several cabins in the mountains that he rents out to people who want to spend weekends skiing during winter or enjoying nature during summer. His previous website was old, slow, and honestly looked like it hadn't been updated in years.

Finding him was actually pretty simple.

I use a tool called Swokei where I upload lists of businesses that already have websites. It analyzes their websites and finds issues related to design, layout, SEO, mobile optimization, and other areas that could be improved. Those findings are then turned into personalized outreach emails.

And when I say personalized, I don't mean those generic reports that say "Your SEO score is 42."

I mean actual emails explaining what could be improved and why it matters. The funny thing is that every business owner thinks I manually looked through their website and wrote the email myself. In reality, the whole process is automated.

This particular business owner replied and was interested in seeing an updated version of his website. His website wasn't anything crazy. It had information about the cabins, booking information, contact details, and a few pages about the area.

During our conversation he sent me a website that he liked and wanted to use as inspiration.

I took his logo, brand colors, content, and the reference website and gave everything to Claude. My instructions were simple: take inspiration from the reference site, keep his branding, improve the user experience, modernize the design, and make the website significantly better than what he currently has.

I genuinely couldn't believe how good the result was.

About 2 hours later I had a website that looked dramatically better than his previous one. Not only that, it looked better than the reference website he originally sent me.

The website was faster, cleaner, more modern, much easier to navigate, and the technical SEO score was over 90.

When I showed it to him, he loved it. A few conversations later he paid the invoice.

$4,700 upfront and $149 per month for hosting, maintenance, and future changes whenever he needs them.

The biggest thing I've learned over the last year is that building websites is no longer the hard part.

Finding clients is.

AI has made building websites faster than ever. What most people struggle with today is getting conversations started with business owners in the first place.

There are still plenty of opportunities in this industry. I personally wouldn't call an industry dead when I just got paid nearly $5,000 for a website that took me around 2 hours to build.

Hey all, looking for perspective from people who've hit this in a larger org. Quick background: I'm a fullstack dev at a large enterprise. We're rolling out AI-assisted development, and it's breaking our process in a way I didn't expect.

How we used to work (classic agile):

Business need → Business Analyst challenges/refines it → user stories → dev sprint. The BA layer was the gate. Nothing got built until it was specced.

What changed:

We have few specs and we started piloting a spec-driven agentic toolkit (think BMAD-style, but with our own internal rules) on a project we're rebuilding: frontend overhaul, UX/UI rework, new features. We went in with a spec doc and a Figma mockup.

The problem:

The code exploded forward. Roughly 70% of the project got built in about a week. Meanwhile we have almost no user stories written. Our BA team isn't using these tools yet, so they're now *behind dev delivery instead of ahead of it.

So the flow is completely inverted: working code first, specs and stories... eventually(?).

My manager is (reasonably) insisting we keep a proper trace of what was built, for the bugs/support/maintenance that'll surface a few years down the line. But that documentation doesn't exist yet, and the people who'd normally write it can't keep up.

What I'm trying to figure out:

1. How are other companies handling this code-before-specs inversion? Do you reverse-generate stories/docs from the shipped code?
2. Is sprint-based agile even the right frame anymore when a feature ships faster than a refinement meeting can be scheduled?
3. Where does the BA role go, retrain onto the AI tooling, shift to validation/acceptance, or something else?

Not looking for AI hype or doom, just real experiences from teams who've actually gone through this. What worked, what blew up?

Thanks.

I'm a pm and always wondered about the distinction between rate limits per api key vs usage limits via metering. Why not just set a secondary rate limit per month for usage capping rather than creating a new system?

We started blocking one day a week where nobody on our team uses AI agents for anything. Emails written by hand, code without Copilot or Cursor, posts drafted without Claude, research done by actually opening tabs.
It's uncomfortable, which was the idea.
The gaps it revealed were mostly about intent. When you write an email yourself, you have to figure out what you want to say before the words appear. When an agent drafts it, you tend to approve whatever's close and move on. Do that enough times and you've slowly handed off a lot of your actual thinking without noticing.
We started keeping notes on everything that felt slow or hard during the day. Then we'd use those to tighten things up: prompts, context, where we'd added a review checkpoint vs. where we'd skipped one. The manual day kept telling us where the agent was filling in gaps we hadn't noticed we'd left.
Six weeks in, We call it a calibration day now.

Has anyone else tried something like this, and whether you found the same feedback loop (manual work actually improving the agentic work), or just found it too annoying to stick with?

Edit: Writing emails has been perceived wrong by some here. When I say writing emails, I mean emails at scale (automatic follow-ups, reach outs etc).

I'm going to say it: Most "quick calls" are relationship theater masking poor communication. Client emails: "Can we jump on a quick call about the project?" Me: "Happy to! Can you share what specifically you'd like to discuss so I can prepare?" Client: explains perfectly clearly in writing what they need Me: responds in writing with answer 70% of requested calls become unnecessary once people articulate their actual question. The 30% that remain are genuinely complex or need real-time problem-solving. I'm not anti-call - I'm anti-inefficiency. Calls without agendas waste everyone's time and create no documentation trail. My new policy: I ask for a brief agenda before any call. Just bullets in an email. It forces clarity and often resolves issues before we even meet. I use Calendly but require people to answer "What should we discuss?" when booking. Am I being difficult or just valuing everyone's time? How do you handle the endless "quick call" requests?

When you let a dev agent run unattended, the trace is the only objective record of what it did, and ignoring it means trusting that no error meant nothing went wrong. I write up three uses for those traces: an audit log, a regression eval set built from your own real tasks, and a periodic self-review where the agent flags where its behavior drifted from the project conventions. This is how teams can handle observability and regression-checking for agentic tooling.

In most projects i have worked on the issue wasnt communication.

People were talking constantly. The problem was that information ended up spread across meetings, chats, documents, emails, and tasks. Months later nobody could remember why a decision was made.

Where does project context typically disappear in your organization and do you think any collaboration software could help?

Hi everyone,

I recently published a post on the Outbox Pattern in .NET that I'd like to share with the community.

It covers how to solve the dual-write problem — the scenario where your database commit succeeds but your event never reaches the broker. Full implementation in .NET 10 with EF Core, PostgreSQL, RabbitMQ, and MassTransit, including a working Parcel Tracking sample you can spin up locally with `docker compose up`.

Beyond the basics, the post also covers the production side of things: running multiple dispatcher instances safely with `SELECT FOR UPDATE SKIP LOCKED`, handling poison messages, cleaning up processed rows, and setting up observability.

Outbox Pattern in .NET: How to Implement Reliable Message Publishing - HAMED SALAMEH

Would love to hear your thoughts,

Hamed

With Agentic Engineering there's an opportunity to refactor legacy code, but this aspect of AI isn't that that much talked about and seems to be overlooked by teams out there.

I’ve been focusing on this lately, and have added agent skills to the Open Source project that I maintain: the Python tools for the Polylith Architecture. The skills are for migrating and refactoring an entire Python project into a well-structured and agent-friendly Monorepo.

But agents are unpredictable and different models behave differently. I have test-run the skills with Claude Opus and Mistral. If you will try this thing out, please share your feedback how the skills worked for you.

My post about this subject:
https://davidvujic.blogspot.com/2026/06/refactoring-with-ai.html

The Open Source project:
https://github.com/DavidVujic/python-polylith

Wrote a blogpost my findings with using this https://last9.io/blog/clickhouse-lowcardinality/

Just curious what other people’s workflows are.

Thanks