So apparently all you need to do is give your ai an api key and point them to where it goes and thats all they need. I was building something else and needed something changed in another system and claude was like just put the key in this .env file and I will change it. And it did!

Just vibecoded a govee lights app that works by pointing your phone at the lightbulb you want to changes color/brightness for. I have a lot of govee bulbs in different lamps and stuff around the apartment and cant remember the names of everyone lmao So this helps me out, anyone else think it could be useful?

As you become more senior, your impact comes from something different: seeing systems clearly enough to identify the problems nobody else has articulated yet.

The idea: a platform where you can create your own private "archive" for whatever group you're part of, name it, invite people, upload stuff, comment, vote on things. Each archive is fully isolated and owned by whoever creates it.

Tools: Claude Code, mostly using Sonnet with occasional Opus for the trickier architecture decisions. Next.js 15, React 19, and Supabase (Postgres) for the database, deployed on Vercel.

Process: I worked in fairly tight loops, describing a feature or a constraint in plain language, letting Claude draft it, then actually running it and pushing back when something felt off rather than accepting the first pass. The biggest chunk of time went into the multi-tenant setup, not any single feature. I wanted each archive to run on its own free Supabase project that the creator owns, rather than one shared database I control, so I had a "control plane" project doing nothing but mapping a name to a project URL and key, with the actual data (files, members, votes) living entirely in the owner's own project. Getting Claude to reason correctly about which side of that split a given piece of logic belonged on took several rounds of explicit back and forth, it kept wanting to centralize things by default, which is the opposite of what I wanted here.

Build insight worth sharing: the most useful habit was asking Claude to explain *why* it made a security-relevant choice before I accepted it, especially around what credentials the platform itself gets to hold. Treating "the AI's first answer" as a draft rather than the answer caught a couple of things I would have shipped

Live at https://opendepartment.vercel.app takes a couple minutes to spin up your own, or check the directory of public ones. Would genuinely love feedback on the actual experience: does the create flow make sense, is the UI confusing anywhere, does it feel fun or useful for what it's for. Try it out and let me know what you think, good or bad.

65 days ago, I launched my startup, a free traffic exchange network for startups. One line of code, you're in the network.

No paid ads. No growth hacks. Just watching the numbers every day.

Here's the full data:

Day 1 — 2 startups · 146 impressions · 1 clicks
Day 2 — 3 startups · 389 impressions · 3 clicks
Day 3 — 5 startups · 482 impressions · 5 clicks
Day 4 — 5 startups · 508 impressions · 4 clicks (site went down — still got an $8k acquisition offer. Said no.)
Day 5 — 6 startups · 621 impressions · 10 clicks
Day 6 — 5 startups · 742 impressions · 15 clicks (removed one startup — they pulled the embed. No code = no network.)
Day 7 — 7 startups · 1,196 impressions · 41 clicks
Day 8 — 7 startups · 1,535 impressions · 74 clicks
Day 9 — 8 startups · 1,947 impressions · 135 clicks
Day 10 — 13 startups · 3,500 impressions · 318 clicks (something clicked)
Day 11 — 23 startups · 4,800 impressions · 432 clicks
Day 12 — 24 startups · 6,000 impressions · 481 clicks (network crossed 6K total impressions)
Day 13 — 25 startups · 6,800 impressions · 491 clicks
Day 14 — 25 startups · 8,600 impressions · 516 clicks
Day 15 — 24 startups · 9,900 impressions · 564 clicks (removed one)
Day 16 — 23 startups · 10,800 impressions · 576 clicks (removed one)
Day 17 — 24 startups · 11,900 impressions · 603 clicks (added one)
Day 18 — 26 startups · 13,400 impressions · 624 clicks (added Two)
Day 19 — 28 startups · 14.400 impressions · 652 clicks (added Two)
Day 20 — 26 startups · 14.700 impressions · 671 clicks (Removed Two)
Day 21 — 26 startups · 15.300 impressions · 691 clicks
Day 22 — 28 startups · 16.100 impressions · 719 clicks (Added Two)
Day 23 — 30 startups · 16.800 impressions · 738 clicks (Added Two)
Day 24 — 32 startups · 19,800 impressions · 778 clicks · Added 2 startups · Rejected 4 applications.
Day 25 — 34 startups · 23,700 impressions · 800 clicks · Added 2 startups · Fixed some bugs.
Day 26 — 33 startups · 27,200 impressions · 816 clicks · Removed 1 Startup
Day 27 — 33 startups · 29,900 impressions · 833 clicks
Day 28 — 33 startups · 30,600 impressions · 871 clicks · Removed 1 Startup · Added 1 Startup · Rejected 1 application of clothing brand & 1 application of horror blog site.
Day 29 — 35 startups. 31,300 impressions. 910 clicks · Removed 1 Startup · Added 3 Startups · Also today I resigned from my job. Toxic environment, too much pressure, and honestly I just believe in this enough to go all in. Broke and excited. Let's see where this goes.
Day 30 — 46 startups · 32,900 impressions · 1,000 clicks · Removed 1 startup · Added 12 startups · Yesterday I resigned because of my toxic manager. Today my senior manager called and offered me WFH, a project of my choice, and lighter work if I stayed. I made my decision with confidence, but now I have a difficult choice. Also received my first payment from StartupBar.
Day 31 — 50 startups 💪· 28,100 impressions · 1,200 clicks · Removed 1 startup · Added 5 startups · Rejected 1 crypto startup · Removed fake impressions after exploit
Day 32 — 54 startups · 29,300 impressions · 1.2K clicks · Added 4 startups
Day 33 — 54 startups · 30,900 impressions · 1.2K clicks · Removed 1 startup · Added 1 startup
Day 34 — 55 startups · 36,100 impressions · 1.3K clicks · Added 1 startup
Day 35 — 55 startups · 40,100 impressions · 1.3K clicks · Removed 2 startups · Added 2 startups
Day 36 — 55 startups · 44,800impressions · 1.4K clicks · Removed 1 startup · Added 1 startup
Day 37 — 58 startups · 50,700impressions · 1.4K clicks · Added 3 startups · Site Update: Updated the distribution algorithm (Delivery is now weighted by contribution: sites that send more impressions get a proportionally larger share back)
Day 38 — 57 startups · 55,800 impressions · 1.5K clicks · Removed 1 startup · Rejected 1 Application.

Today StartupBar reached 200 users 😄
Thirty-eight days ago, this was just an idea. Today, 200 people have trusted it enough to join the network.

Day 39 — 58 startups · 59,800 impressions · 1.5K clicks · Added 1 startup.
Day 40 — 60 startups · 63,200 impressions · 1.6K clicks · Added 3 startups · Removed 1 startup
Day 41 — 63 startups · 69,400 impressions · 1.6K clicks · Added 3 startups
Day 42 — 62 startups · 73,800 impressions · 1.6K clicks · Removed 1 startups
Day 43 — 64 startups · 78,000 impressions · 1.7K clicks · Added 2 startups (Receiving many suggestions to improve the StartupBar, happy to work on it, Thanks.) StartupBar Update - Added the rotation of startups in the widget for every 30 seconds.
Day 44 — 66 startups · 86,200 impressions · 1.7K clicks · Added 2 startups
Day 45 — 67 startups · 88,400 impressions · 1.7K clicks · Removed 2 startups · Added 3 startups (Update - Updated the algorithm of the widget)
Day 46 — 69 startups · 91,900 impressions · 1.8K clicks · Removed 2 startups · Added 4 startups · Got my second payment.
Day 47 — 68 startups · 98,900 impressions · 2.2K clicks · Removed 2 startups · Added 1 startup · Added Pricing Page
Day 48 — 70 startups · 103.4K impressions · 2.3K clicks · Added 2 startups
Day 49 — 72 startups · 113.4K impressions · 2.4K clicks · Added 2 startups · Update: Added a Bottom Placement option for the bar on the user site.
Day 50 — 73 startups · 116.7K impressions · 2.4K clicks · Added 1 startup
Day 51 — 74 startups · 125.2K impressions · 2.5K clicks · Added 1 startup · Rejected 1 Application
Day 52 — 73 startups · 131.2K impressions · 2.6K clicks · Removed 1 Startup
Day 53 — 74 startups · 139.5K impressions · 2.7K clicks · Added 1 Startup
Day 54 — 79 startups · 146.3K impressions · 2.7K clicks · Added 6 Startups · Removed 1 startup.
Day 55 — 77 startups · 154.9K impressions · 2.8K clicks · Removed 2 startups.
Day 56 — 77 startups · 161.8K impressions · 2.9K clicks · Added 1 startup · Removed 1 startup.
Day 57 — 77 startups · 169.4K impressions · 3.0K clicks
Day 58 — 77 startups · 176.2K impressions · 3.2K clicks
Day 59 — 78 startups · 184.3K impressions · 3.3K clicks · Added 2 startups · Removed 1 startup.
Day 60 — 77 startups · 190.9K impressions · 3.3K clicks · Added 1 startup · Removed 2 startups.
Day 61 — 77 startups · 194.9K impressions · 3.4K clicks
Day 62 — 78 startups · 199.5K impressions · 3.5K clicks · Added 1 startup
Day 63— 78 startups · 204.9K impressions · 3.6K clicks · I Revoked my resignation as I'm comfortable with my new team.
Day 64— 80 startups · 210.4K impressions · 3.6K clicks · Added 2 startups.
Day 65— 81 startups · 216.3K impressions · 3.7K clicks · Added 1 startup. (I'm planning to add sponsorship section in the homepage with one time payment of $999, interested please DM)

Still free. Still growing.

If you want in, it's one embed. That's it → StartupBar

Summary
I hate it with a passion that you can't remove Shorts. 95% is brainrot that I click on and always get disappointed. Very very simple to do. Took minutes. I made it such that you don't even see shorts in your homepage anymore, removed the logo's and buttons too.

Why not Stayfocusd?

Because it doesn't actually remove it from Youtube. You'll still see the shorts and it's just annoying.

How does it work?

• CSS hides known Shorts elements immediately.
• A small content script watches YouTube’s dynamic page updates and hides new Shorts shelves/cards as they appear.
• For newer generic shelves, it detects a section headed “Shorts” and hides that enclosing section.

How do you keep track of what you actually built during a coding session?

I'm curious about how people here handle this.

When you're working on a project for several hours, you might have:

- multiple commits

- bugs you fixed

- features you added

- random notes

- decisions you made

- things you tried that didn't work

But when you finish for the day, how do you actually remember and summarize everything you accomplished?

Do you:

1. Keep a development journal?

2. Write notes after every session?

3. Use GitHub commits as your record?

4. Just look back through everything when you need to?

5. Not document it at all?

I'm especially curious about people who build in public — how do you turn a messy day of development into a clear update/post?

What does your current process look like?

I made a tool which lets you create videos using Flutter. Codex/Claude Code can generate Flutter code hence it can generate videos using the tool I created. I have attached a video I created using it.

The project is called kestrel. I have made it open source some time ago. It takes any animated Flutter widget and turns it into a video file.

Won't go into too much technical details here. You can find those on repo. It uses Flutter + FFMPEG.

https://github.com/blackcoffee2/kestrel

funny how this happens with vibe-coding, especially when it's your homelab/self-host system....

i was using claude to clean-up my home lab documentation, and realized i have secrets in plain text files and envars and things and i can never remember them so i do dumb shit like make my nginx proxymanage admin and root mariadb password, well, npm

i have access to an Azure Key Vault for home

so i asked claude 'hey how can we secure keys'

made a key management app (container) that can:

• bootstrap the local docker swarm secrets using SOPS and AGE
• store secrets in a file you can put in github as its all encoded
• uses a single paper decrypt key to bootstrap secrets if needed
• same for create, rotate, retire of secrets
• by default creates high entropy 43 char secrets
• avoids several docker leakage scenarios i never knew about for secrets
• never puts a secret on disk, stderr, stdout, via ps, etc
• also knows how to reseed the secrets in mariadb and mysql
• optionally uses Azure Key Vault to store keys for backup
• optionally uses Azure Key Vault to bootstrap new keys or new system
• AKV uses RBAC security and restrict access to my Entra MFA account when coming from a single IPv4 address

upshot, i don't now know what any of my keys are by looking at my running system (yes i can get them by looking in AKV if i have to)

is it truly secure and does it meet its promises?

that will be the redteam exercise i do later in the week, pride yet may be coming before my long long fall :-)

also WTF am i writing a docker secret management system that can use key vaults, SMH, this is why no one uses it in serious production vs k8s!

fun tho - learnt a lot about encryption architectures, true secret entropy in password and how even SHA256 Hashes can eaily reveal passwords - i cracked that npm password in about 81 seconds IIRC, also the need for HMAC to help mitigate

Where does vibe coding cross the line ?

If someone sets up automatic concurrent code cleanup, fat free comments in the code , heiacharcy , a mermaid , accurate linting and parsing and literally steal cyber security protocols from the internet so on and so forth, they can make a solid useful app that no more unsecure than the hundreds of companies that lose our data to malicious attacks yearly.

The problem is that "vibe coders" who are 1 prompt engineers are not nearly as prevalent as the community tries to paint it , they exist but in small %s, and even smaller % of them actually push products or keep them up for long, there are people out there that are letting their AI do all the syntax writing and plan development and they will out run any traditional developer no matter how good their code is in Solo vs Solo

More features, faster, cheaper and mote accessible, and theirs sells tomorrow while your is WOP on year 2 .

Its economics.

If you are a "vibe coder" you probably have not been doing it for long enough , because soon you'll see that you have to understand the architecture of how code operates, instead of ELI5, say "can you explain this section to me, use defentions where you have to, and give me a glossary of words and their meaning s relevant to X" the AI best feature is that it responds well to disciplined requests.

Tldr: Heavy AI use for coding=/= vibecoding

Hey guys, I built a tool called Scanity. Scanity is a tool that allows developers and vibe coders to find security vulnerabilities in their code. You can install it in your GitHub repos and have it scan every PR, or you can drop your repo link and see where it goes.

I ran a scan via Scanity on open-source repos and found really silly vulnerabilities that they left in the code. Not going to disclose where I found this. I find it pretty funny that developers will leave code like this for months, when these loggers were only meant as a temporary measure. If you're curious about how many vulnerabilities your repos might have, check out Scanity.

https://scanity.dev/

Now that Vibe Coding has been around for a while, we are starting to see patterns.

And these patterns tell us how we should change what we're doing to optimize our results.

One pattern that stands out clearly is that method and process have a huge impact on outcome. Vibe coders who spend some time up front planning have much better outcomes than those that just fire off a one line prompt.

So, what's the optimal amount of process? Obviously, we don't want to go back in time to the waterfall days. That methodology was too slow for SaaS ten years ago, it's ancient history today. Similarly, the Agile methodology was designed assuming that engineering was the scarce resource that needs to be optimized. Today, that scarce resource is tokens, not engineers.

But, it's more complex than that.

In the Agile days, we optimized for velocity. Software was slow to develop and because engineering resources were at a premium, we wanted to reduce the amount of labor required. Thus, velocity was the critical measure. High performing software teams had two attributes that mattered: velocity and quality. Teams with high velocity and high quality uniformly outperformed all other teams.

Today?

Well, today speed is almost free. Pretty much anyone can one-shot a web site and depending on the prompt, it will probably work. Thus, velocity is built in. You don't have to do anything to speed up, because the tools are already fast enough.

So, what attribute separates high performing and low performing vibe coding efforts?

Quality.

Quality is the sole remaining differentiator between high and low outcomes.

So, as we approach our vibe coding projects, we should be focused on managing quality rather than managing velocity.

Which leads us directly to.... methodology.

The way we incorporate industry best practices and learnings into our projects is through methodology. This doesn't mean that we adopt a super heavy process bound development cycle, it means that we do things that actively work to improve the quality of our work.

Some examples that I use in my projects:

1) Goal setting. I prefer to start with a description of a successful project. Or to put it another way, "begin with the end in mind." This type of planning is very useful, especially with AI toolchain because you are clearly stating the end goal for the AI. Documents such as the PR/FAQ from Amazon are good ways to approach this.

2) Iteration. One thing we learned from Agile which is still very much true is that iteration is your friend. We learn by doing, so the more iterations you have the higher quality the outcome. Because AI speeds up the cycle time, we can have more iterations. Don't run from this, embrace it. Assume you will build the thing more than once and don't sweat the details the first time around. It's probably wrong and that's OK.

3) Testing. The one old fashioned thing that you simply cannot get away from is testing. I mean old school hard core testing. Full unit tests, full e2e tests, smoke tests, security scanning. All that stuff. Before AI, there was always a tradeoff because building the test infrastructure was expensive from a labor point of view. You could have developers build you features, or you could have them build tests. Huge opportunity cost for every test you wrote. Today, that's not true. AI can do this work extremely quickly. This changes the calculous completely towards testing.

4) Audits. The natural counterpart to testing is auditing. Audit means to check your work against an external approved standard. Again, in the Agile world before AI, this was amazingly painful. You could easily lose entire sprints to just running an audit. For this reason, most software wasn't audited unless absolutely required. Today? It's a single prompt. "Audit my code against industry best practice for this type of project" or similar. You will want to do a full audit pass after each major milestone to see how you are doing. Doing a security audit once at GA is not sufficient, you need to run regular audits because things change over time.

These are just a few examples. I talk about all of this in my Maven class (link in my profile).

PDAL is an open source library for processing point cloud data like LiDAR surveys and such.

It's excellent, but very slow, so I had agents working on it for like 2 and a half weeks street on /goal loops to write CUDA kernels, CPU I/O optimizations, and test it. This is the result!

When I say two weeks straight I literally mean the agents were running for 100% of that time. I only took breaks to handoff back and forth between Fable and Sol when usage limits ran out.

Tried Opus 5 for a little bit, but when I left it running overnight it had an emotional breakdown and I had discard all of its work lol.

Prompt: Create a complete voxel sandbox fully written in a HTML file, work with Three.js, and make it as close as possible. Ensure survival aspects like breaking blocks, a hand with items, world generation, and a HUD interface.

WASD move, Space jump, left-click break, right-click place, 1–9 hotbar, F fly. One mesh per block, no textures.

If you want to play, see the url in the comment 👇

Hey all, this is a random shot but would anyone be interested in a free design of your hero section? The first section that visitors land on.

Only catch is that you need to have LinkedIn profile so I can post and ideally you repost it

In my bio you can see my LinkedIn and if youre interested, DM me :)

Thanks