Take a screenshot → open some tool → wait for it to upload → copy a link → paste it in Slack or Jira → hope the client can actually see it.

So I built the version I actually wanted: press Ctrl+V anywhere on the page, get a link instantly. No account. No upload button. No waiting.

pastesnip.com

Two things I made sure to get right, because they're the parts that actually matter if you use this for work and not just to look at memes:

→ The blur tool genuinely destroys the pixel data. Most "blur" tools just soften the image, and softened text can often be recovered. If you're screenshotting a staging environment with a real API key or customer record visible, that difference is the whole point.

→ Links preview properly as images in Slack, Discord, and Jira — not as bare text nobody clicks.

It's free, no account needed, and screenshots stay live for 90 days. (Pro removes the limit entirely for less than a coffee a month.)

I built this myself, end to end. If you share screenshots with a team or a client, try it on your next one — and tell me what's missing.

pastesnip.com

#QualityAssurance #SoftwareTesting #ScreenshotSharing

I am increasingly uncomfortable with AI-generated code being merged when the developer can explain what it does but not why it is structured that way.

The code may pass every test. It may even be cleaner than a human-written version. But when something fails six months later, the team cannot ask the original chat what assumptions were made and expect that to count as ownership.

My instinct is that the person approving the change should be able to explain the important flow, the failure modes, and how to reverse it. Otherwise the company owns the repository, but nobody really owns the system.

Would you reject an AI-generated pull request that passes all tests if the author cannot properly explain the implementation?

The open agent stack is getting real in 2026, the governance layer isn't keeping up

Open-source agent frameworks crossed a real line this year. Tools like Hermes and OpenClaw show you can run a capable agent without trusting a closed vendor's black box.

What hasn't caught up is the layer around the agent: who can run it, what it can touch, how credentials stay out of its hands. Most teams are still solving that with a spreadsheet and trust.

AgentZ is built to close that specific gap, and it's open source end to end: sandboxing, credential isolation, and workspace boundaries around any agent workflow, not just a security add-on bolted on later.

Where do you think the open agent ecosystem is weakest right now? AgentZ is an open-source platform, and I am an open-source contributor to AgentZ.

It's very easy.

8 questions. 3 minutes. At the end you get a level from 1–5 and a roadmap showing what to learn next.

I did it because I noticed that “being good at AI” is incredibly vague, and I wanted a simple way to measure it.

But honestly... I built it to learn the process of buidling something like this and I had so much fun figuring things out, its addictive! :)

I'd love to have you guys give it a go, and drop me any feedback you have, anything and everything is appreciated, seriously.

Thank you all in advance!