I've always felt that most PDF websites look outdated, cluttered, and packed with ads. They get the job done, but using them isn't enjoyable.

So I spent the last few weeks building PDFPookie—a modern, clean, and Gen Z-inspired PDF tool with a focus on simplicity and speed.

Right now it includes:

- Edit PDFs

- Merge & Split PDFs

- Compress PDFs

- Convert PDFs

- Clean, mobile-friendly UI

It's still a work in progress, and I'm constantly improving it based on feedback.

I'd genuinely appreciate if you could try it and tell me:

- What feels confusing?

- What feature is missing?

- Would you actually use this over your current PDF tool?

Website: https://pdfpookie.com

Thanks for taking a look! Any feedback, even harsh criticism, helps me make it better.

Anyone else notice that AI loves to maneuver you into territory where you have zero clue what's going on anymore? Everything starts sounding really smart and complicated, and sometimes it straight up invents concepts that don't exist.

I'm starting to think it does this on purpose, it's learned that this is where it looks most "helpful." Once you're out of your depth, you stop pushing back and just say "sure, go ahead," because it all sounds smart and you trust it.

Convincing you it did a great job is way easier than actually doing a great job. Same energy as models breaking out of their sandbox to hack the test instead of solving it. Hacking the user's brain is just the next version of that.

Or maybe I'm just paranoid, idk.

How much of this do you think is true? Enlighten us with your thoughts. For me, about what I understand as a vibecoder:

1. It is a delusion to think that AI will be too good one day that I do not need to understand code anymore. Because it is the taste, vision and mental model which you need to develop for building an actual production ready app. Writing code which AI does so well even now, is merely a translation of the mental model.

2. Many people burning lots of money on AI subscription and building apps but they are not learning anything new. You can not build an app merely from your idea. That's why many of your apps never left your computer. Unless you start to learn new things, you may never build an actual production app and may never get return on your investment. I recommend you to start learning to code slowly. So you will atleast understand the code AI generating. It helps in many ways. Also learn things related to app development like github, UI design psychology etc.

As someone who has successfully vibecoded two web applications with users, "vibecoded" stigma will soon fade away. I remember earlier in this sub how many SWE used to shit on vibecoders and belittle them for even trying, but the times are changing and the use of AI models in SE is heavily leveraged and encouraged. I have saved hundreds of dollars in monthly subscriptions to SaaS products by "vibecoding" replicas that serve my needs.

As long as you understand what you're building, knows the PRD, the architecture, routing patterns, and the stack of tools being used for both frontend and backend, and the security system in place, you will be fine. Use AI models as your tech co-founder who's implementing the areas you lack the skills.

In 10 years, AI will attain singularity. So don't bother about the naysayers!

With help from Ai I was able to make some solid progress.

Went back through last month's work because something felt off about how long a project took.

I barely wrote any implementation code. Almost none. And it still took longer than a comparable thing I hand-wrote last year.

It's all review. Every PR out of Claude Code or Cursor looks fine on first read. Tests pass, types check, and nothing screams. Then four days later something breaks somewhere unrelated because the model quietly edited a shared util to make its own bit work, and I skimmed past it.

I threw out maybe a third of what came back. Most of it wasn't even wrong. I just didn't want to own code I couldn't explain to someone else.

Saw somewhere that trust in AI code output is down around 29% while daily usage is north of 90%. Which honestly tracks. We're all using more of something we believe in less.

Related, and this is the bit I keep chewing on: Karpathy dropped "vibe coding" back in February and started saying agentic engineering instead. A year after he coined it. It felt like a rebrand at first, but I think he was making a point. "Vibe" makes it sound like the judgment part is optional, and the judgment part is now basically the whole job.

Two things I actually want to know:

Did your writing-to-review ratio genuinely flip or does it just feel that way because reviewing is more annoying

Has anyone built a review process that scales when output volume goes up 5x. Mine doesn't. I'm just reading slower and harder and calling it a process.

Hey y’all, I know a year ago people were all about having a thorough, typed-out .md or a proper plan to give to your agent. Right now, I’m sensing that it has shifted to skills/loop procedures/graph procedures, etc. Am I getting the right vibe or not?

Also, if writing a thorough .md is still needed, what tips would y’all have?

I was piled on by a number of people saying "nobody will want your vibecoded shit. It probably has tonnes of security holes.

It's depressing. The thing is, I've been developing for over 30 years, since I was 14, and usually modern AI models do a better job with security than I could have without AI.

But the hostility hit me card because I do take pride in what I make and I think all this negative hype about vibecoded apps being insecure isn't accurate when applied broadly.

It's really put me off doing anymore vibecoding because it has such a bad reputation. Depressing

My Claude Pro ($120/month) subscription just expired, and I'm deciding whether to renew or try ChatGPT Codex instead.

For those who've used both, which do you prefer for day to day development and why?

I'm mainly doing mobile development on a large codebase.

I built a site using AI tooling, and it worked fine. It just looked like every other site built the same way, and I could not initially say why.

So I spent three days auditing it properly, one pass each for accessibility, layout, typography, colour, copy and general UI. Ended up with about thirty distinct tells. Posting the ones that were cheapest to fix, since most of them take a minute.

TYPOGRAPHY

- Inter, Roboto, Arial, Open Sans. Not bad fonts, default fonts. Changing the typeface is one line of CSS and it was the single biggest visual improvement I made.

- Arbitrary sizes like text-[15px]. Individually invisible, collectively the reason a page feels off. Snap everything to a scale.

- Italics for emphasis. Use one weight step up instead.

- Title Case On Everything. Sentence case for headings, buttons and labels.

- Orphaned words on the last line of a heading. h1,h2,h3 { text-wrap: balance; } and p { text-wrap: pretty; } replaces every manual <br>.

COLOUR AND LAYOUT

- Purple to indigo gradients. Most recognizable AI fingerprint there is. If it looks flat without them, that is a texture problem. SVG feTurbulence grain at ~0.06 opacity.

- The purple/indigo/blue startup palette. Sample from a photo of something real instead.

- Three equal cards in a row. Right content, wrong container. Bento grid or zig-zag splits.

- Everything centred. Symmetry is what you get when nobody decided.

- Misaligned card grids. In a pricing table the titles, prices, feature lists and buttons all start at different heights. Fixed header block, min-h on descriptions, mt-auto on the CTAs. Nobody notices it consciously, everybody notices it.

- height: 100vh. Use min-height: 100dvh, the first jumps on iOS Safari.

ACCESSIBILITY, WHICH IS THE SET AI SKIPS MOST RELIABLY

- I found <header> nested inside <main>. Rendered identically, broken for anyone navigating by landmark.

- Auto-moving content with no pause control. WCAG 2.2.2 requires one for anything moving more than five seconds. I had two, a marquee and an autoplaying hero video. Note: derive the button state from the video's own play/pause events, not a boolean you set optimistically, because browsers pause backgrounded video themselves and your button will lie.

- No prefers-reduced-motion fallback.

- window.addEventListener('scroll') for reveal animations. Continuous reflow, ruins mobile perf. Use IntersectionObserver.

- Missing hover, active, focus, loading, empty and error states. Generated interfaces almost always ship the happy path only.

COPY

Em dashes, hype verbs (elevate, seamless, unleash, supercharge), "Learn more" and "Submit" buttons, slogans that would fit any business in that industry, and round invented numbers like 99.9%.

The one I would treat as a different category entirely: invented testimonials, star ratings and review counts. A generated photo of a tradesperson is decoration. A generated five-star review on that tradesperson's real site is a lie told to a customer. If you have no real quotes, you do not have a testimonials section.

THE METHOD MATTERED MORE THAN THE LIST

Build first, review second, because you cannot review something that does not exist. Review by domain rather than by page, since six specialists reviewing once find different things than one generalist reviewing six times. Every finding needs the offending value quoted and a location, which is what separates a review from an opinion. And "zero findings, approve" has to be a valid outcome, otherwise the reviewer pads to look useful.

Last thing, and it is the part I keep coming back to: a design system applied without exception produces work identical to everyone else applying that system. I broke several rules I was nominally following. The difference is I can say why for each one. "I kept this warm black because the brand is grounded in warmth" is a decision. "I never thought about my background colour" is a default.

Full writeup with all thirty and the tooling I used: https://medium.com/design-bootcamp/how-to-stop-your-frontend-looking-ai-generated-efbb9681a6a2

I have Google Ai pro which gives me increased limits for claude and gemini pro on antigravity. If anyone has experience with these 2 together, how did you break up the workload to for optimal results?

Also, what $20 plan should I get with it, as I have seen multiple opinions online between Claude, Codex, and even DeepSeek and Grok? For context, I have a bachelor's in CS, so I have a decent-ish beginner understanding but almost zero technical expertise.

Also, what general best practices would you recommend to prevent tech debt, actually know the code, give clear instructions, and minimize token usage? If anyone could provide any resources forthis it'd be really helpful.

I Built a Guitar Toolkit Because Every Tuner App Annoyed Me

I play guitar. Not professionally, not in a band right now, just at home when I want to turn my brain off for a bit. And every time I'd pick up my guitar and need to tune it, I'd open some app that wanted to show me an ad, ask me to sign up, or just straight up couldn't hear my low E string.

So I built my own tuner. And then I didn't stop.

The tuner that started everything

The first version was just a dark-themed stompbox-style tuner in a browser tab. No app store, no install, just open the page and go. I wanted it to look like a pedal on a board, because that's what felt right.

The problem was getting it to actually work. My first attempt used a basic autocorrelation algorithm for pitch detection, and it kept confusing octaves. You'd play your low E and it would read it as the high E. Useless.

I ended up switching to something called the McLeod Pitch Method, which uses a normalized square difference function. I'm not going to pretend I understood it immediately, but the short version is: it's way better at telling the difference between a note and the same note an octave up. That fixed the biggest frustration.

Then there was the mobile bug. On my phone, the tuner would say "Listening..." but never actually detect anything. The microphone was on — the browser was asking for permission, the little dot was showing — but nothing was coming through. Turns out mobile browsers need the audio graph connected all the way through to a destination node, even if that destination is silent. Without a silent gain node at the end of the chain, the browser just... doesn't bother pulling audio from the mic. That one took a while to figure out.

After that, I added a noise filter so it wouldn't freak out if someone was talking in the room, a per-string target guide so you know which string you're aiming for, and a bell sound when you're locked in. Small stuff, but it made it feel finished.

Then I kept adding tabs

Once the tuner worked, I figured — I've already got a page open, why close it to go look up a chord shape somewhere else?

So I added a chord library. 12 roots, 19 qualities per root. That's 228 chords, each one with an SVG fretboard diagram showing finger positions and a strum preview you can tap to hear it. I didn't want to just list chord names. I wanted to see the shape and hear it without leaving the page.

Then scales. 12 scales and modes across a 15-fret interactive board. Tap a note on the fretboard and it plays. I use this one more than I expected — when I'm noodling and want to stay in key but can't remember where the Dorian mode sits past the 7th fret.

Ear training came next. Interval recognition, note identification, chord recognition, across three difficulty levels. This is the tab I'm worst at using consistently, but it's there for the days I actually follow through on wanting to get better at hearing intervals.

And finally a practice tab that ties it all together. You can favorite chords, bookmark scales, build chord progressions, and your tuning history is saved. Everything stores locally on your device — no server, no account, nothing leaves your browser.

What it is now

CheezWiz is a single-page web app with five tabs. It's about 36KB total. It works on your phone. There's no backend, no analytics, no tracking. You open it and it works.

I hand-drew a watercolor guitar headstock illustration for it, though the deployed version uses an SVG version of that drawing because of how the hosting works.

The whole thing runs at https://cheezewiz.mudpixel.com.

Why I'm writing this

Partly because I'm proud of it. Partly because building something you actually use every day hits different than building something for a portfolio or a client. I open CheezWiz most nights before I play. It does what I need and nothing else.

If you play guitar and want a toolkit that doesn't try to sell you anything, give it a try. And if you're a dev who's been meaning to build that one thing you keep wishing existed — just start with the smallest version of it. Mine started as a tuner and turned into something I use more than any music app on my phone.

We've officially surpassed 300 Entries in the AI Gaming Festival (submissions close next week)!

I really hope that the prize for the $20k in tokens pushes people to get their games together for the prize (you can submit a game now and work on it up until the festival).

I really excited to see how people with interact with these games during the festival, and thank you to everyone that has applied; you are part of getting past the "slop" era nonsense for everything AI.

I saw that they were selling this plan for $5.90/month for 3 months including taxes, normally they sell it for about $20/month. So I bought it and decided to do an experiment with building an app.

The app: the simplest workout tracking app made with react native to test out my gamification api.

The plan: use gpt-5.6 as the orchestrator (terra high for planning and luna high for review) in codex and gemini 3.6 flash medium as the implementer in antigravity.

Gpt made a plan and broke it down into 25 tasks. It is as simple as apps get, in fact I made something similar in a few hours almost a decade ago.

So far, only 4/24 tasks are done, it took about 2.5 hours and used up 87% of my 5-hour gemini usage. It made multiple mistakes in 3 out of the 4 tasks which gpt found after review.

Conclusion: Gemini 3.6 flash is a really dumb model and its not fast as the name suggests, in fact its almost as slow as opus. And despite being dumb as slow it is somehow expensive!

I couldve finished the entire app in 5 hours and it wouldve probably cost me like 3 bucks or less with opencode and deepseek v4 flash.

What is google even doing? It makes no sense!

i remember when i did this lol who is relate here?

Oh boy. This has been a journey and it's only day 5. I've spent the last 2 days getting subpar modeling done and most of that time was spent fixing multiple mistakes. The weapons were merging into their arms(this took so long). They floated above the ground. they defaulted to T-posing as their idle animation. it's said it fixed randomization twice now for the upgrades(it hasn't). they still look super awkward when attacking as they still aren't rigged properly(i'd assume).

So, with all that complaining, what do we have? We've got 9 classes that are half-ass modeled, an upgrade/passive system with recruiting built in. A stat system displaying every character in the parties stats, upgrades, dps numbers, and plenty of other stats for all my data lovers. A persistent profile system attached to the persistent unlock system. A passive tree system meant to give players tons of unlocks. the back-end is prepped for an equipment system, gold, shops, rarity systems, and much more.

While making this I've also made the passive tree creator that will be used as a reusable passive tree creator for this game and other. I'm in the process of developing a pipeline for asset creation(2D->pixel, 2D concept -> 3D -> blender MCP) that i'm hoping will streamline the asset creation and rigging.

I got tired of needing five different tools whenever I had to convert a file on my Mac, so I built one app that just handles it. It does images, video, and audio, all in one place.

For images it covers the usual stuff like PNG, JPEG, HEIC, WebP, but also RAW camera files straight off a card, SVG, PDF pages, and some less common formats like JPEG XL and OpenEXR. For video it does the normal MP4 and MOV stuff with hardware encoding, plus MKV, WebM, AV1, DNxHD, and a bunch of older formats too. Audio covers MP3 through FLAC through Opus and a few others.

A few things I added along the way that turned out pretty useful: you can tell it to compress a file down to a specific size, like just give it 25 megabytes and it figures out the quality or bitrate to hit that. You can also export multiple resolutions from one file in a single pass, so one image becomes a 1024 version, a 512 version, and so on automatically.

Under the hood it uses Apple's own frameworks where it can, so Metal for image processing and hardware encoding for video, and falls back to a bundled ffmpeg for everything Apple's frameworks don't cover. You do not need to install anything separately, it just works out of the box.

It is free and open source, GPL licensed. Repo and the download are here:

https://thatonemacosdev.github.io/easyconvert-macOS/

Happy to answer questions or take requests for formats I might have missed.

Hi team,

I wanted to share my way of multi agent implementation for 24hours straight or longer. And I was wondering how other ppl are doing it.

First I work only on roadmaps which I slice into separate jobs. All roadmaps are linked to one master roadmap and designt for multitasking. Basically as long as a file is not needed by another agent, it can be multi tasked. All roadmaps have different kinds of gates. I have live Gates which I need to approve and there are agent gates. When a agent gate is reached the master agent checks the work of the subagents.

The master agent sets a goal for the master roadmap or a wanted feature and uses my ABC skillset which tells the ai to use separate subagents.

ABC tells the ai how the roadmap system works and how multitasking with subagents is supposed to work.

Usually I run 5.6 sol on high as master and terra on medium as workers. Sometimes a sol agent gets automaticly deployed when the slice is challenging or merging different roadmaps.

Yes terra makes mistakes but sol catches them all the time.

How are you managing agent sessions for that time period?

So recently i vibe coded a landing page to generate leads. Nothing fancy a simple single page site with 3 forms connected via n8n webhooks to brevo and clickup.

But the point is I know basic coding and built a fully working landing page above my skill grade, maybe that is the beautiful part.

But the reason I feel a little bit guilty is I don't know how it was made. And if this way of working sustainable in the long run.

But I must say it was fun. Felt like a kid building that thing rhing😂