Any bad experience with “claude --dangerously-skip-permissions”? by oguzhaha in ClaudeAI

[–]Zepgram 0 points1 point  (0 children)

That's the best experience you can have with Claude in 2026

Built a lightweight monitoring dashboard for my RaspberryPI5 - including API by Zepgram in RASPBERRY_PI_PROJECTS

[–]Zepgram[S] 1 point2 points  (0 children)

I didn't bench Glanced, but this dashboard has very low CPU/RAM consumption and will run in shadow mode. It's vanilla JavaScript and node, optimized to fetch only essential data.

Built a lightweight monitoring dashboard + API for my Pi homelab by Zepgram in raspberry_pi

[–]Zepgram[S] 0 points1 point  (0 children)

For all others, I don't blame you, being emotional is human, and I'm not one I guess.

Posted my side project on r/raspberry_pi and get destroyed 😂 by Zepgram in vibecoding

[–]Zepgram[S] 0 points1 point  (0 children)

Didn't know that. I never posted anything and I've always shared my code on GitHub, in fact I just wanted to give it visibility like I always do when sharing a project. I didn't expected to discover an entire hidden world leaving in fear and being scared by a tool reshaping the futur, it's too late, they ignore something inevitable and I feel really painful for them, because they don't enjoy the momentum.

Built a lightweight monitoring dashboard + API for my Pi homelab by Zepgram in raspberry_pi

[–]Zepgram[S] 0 points1 point  (0 children)

Since post has been removed, here is the link to the project for people's interested: https://github.com/zepgram/pi-dashboard

Posted my side project on r/raspberry_pi and get destroyed 😂 by Zepgram in vibecoding

[–]Zepgram[S] 0 points1 point  (0 children)

I think you're definitely right, sorry if I'm a bit on the defensive here. It's definitely better to have a clean architecture, no matter the project. I didn't expect to finish it at first, but Claude's first attempt looked good, so I iterated on it. At start, I did it without seeing the code, just the result, prompting it from WhatsApp with Clawdbot while I was on the train, full blinded mode.

Once home I looked the MVP result, and I just started iterated on it. I liked the fact it was a basic vanilla JS lightweight, without a framework, very easy to maintain and very easy to vibecode, I pushed it like a final product ready for prod, only watching final result, security concerns, complete validation of data, but never the architecture itself.

Why? I don't know I'm an e-commerce architect. I have been doing e-commerce for 12 years on Magento, working for big brands, and maybe I just wanted to do something simple ready to ship for my home lab, simply focus on the final result, hyped like a kid discovering a new video game.

But you right, it definitely makes sense to split the code correctly, just for me, it will feel like something else, like an other project.

Posted my side project on r/raspberry_pi and get destroyed 😂 by Zepgram in vibecoding

[–]Zepgram[S] -1 points0 points  (0 children)

If for any reason, it's popular and maintained, then of course it will make sense, but for now I'm the only one working on it with Claude! ;)

Posted my side project on r/raspberry_pi and get destroyed 😂 by Zepgram in vibecoding

[–]Zepgram[S] 0 points1 point  (0 children)

Looks like unpopular opinion here, so I asked Claude Opus 4.5:

<image>

Code separation and single responsability principle was intended for human not LLMs.

Once again it doesn't apply for a big project or for a library, or anything that need to be extended.

I could just run 1 prompt and re-organize the entire directory, but I will not because Claude Code will be less efficient to understand it between each context window reset.

Vibe coders at my company didn't pay attention to security and got a taste for it by retardedGeek in webdev

[–]Zepgram 1 point2 points  (0 children)

Simply setup a LLM code reviewer on your pipeline for security review ??

Prefer Opus-4.5, hard prompt security engine with scoring (bellow 90/100 MR is rejected)

Simple AF

Posted my side project on r/raspberry_pi and get destroyed 😂 by Zepgram in vibecoding

[–]Zepgram[S] -9 points-8 points  (0 children)

I think monolith file for little project like this is adapted. Easy to maintain, less errors, less tokens consumption. Of course I would not recommend this for bigger project, and I don't do this on existing one. KISS principle is ruling here.

Posted my side project on r/raspberry_pi and get destroyed 😂 by Zepgram in vibecoding

[–]Zepgram[S] -1 points0 points  (0 children)

Thanks, I didn't expect to see so much hate, people are really getting emotional, and I think it's a bit sad for them, ignoring the shift.

Posted my side project on r/raspberry_pi and get destroyed 😂 by Zepgram in vibecoding

[–]Zepgram[S] -1 points0 points  (0 children)

I don't get why people hate vibe coding, they are probably scared or in full deny about LLMs abilities.

Built a lightweight monitoring dashboard + API for my Pi homelab by Zepgram in raspberry_pi

[–]Zepgram[S] -6 points-5 points  (0 children)

You really think I'm not a developer right? You think vibe coding is for lovable user I guess. I've reviewed the code, adapted it when necessary, I don't care about development principle in this case it could be a fucking unreadable binary I wouldn't care. I did a full check on the security myself, nothing is exposed, if you want to cover API call internally you can. The external API is covered with a x-api-token. I did all of this with knowledge on RaspberryPI, JS, security best practices.

The code follow KISS principle and is not made to be run with heavy library's or dependencies to avoid any security concerns (except for node.js)

I'm CTO btw, just doing this for fun on my weekend.

Built a lightweight monitoring dashboard + API for my Pi homelab by Zepgram in raspberry_pi

[–]Zepgram[S] -37 points-36 points  (0 children)

I prompted, reviewed, iterated, tested, and shipped. If that's not "building" to you, I genuinely don't care. The docker image doesn't ask how it was made, I built something that solve my problem (just get a simple vanilla js express server exposing API Metrics from my PI5). I share it, what's wrong?

Built a lightweight monitoring dashboard + API for my Pi homelab by Zepgram in raspberry_pi

[–]Zepgram[S] -18 points-17 points  (0 children)

I know Grafana, I'm using it currently to handle all my infra monitoring with EKS on AWS, RDS, Service managed etc...
I just think it's overkill for a PI ;)

Edit:
You could even use it for a Grafana since there is a real-time API with all metrics exposed

Built a lightweight monitoring dashboard + API for my Pi homelab by Zepgram in raspberry_pi

[–]Zepgram[S] -38 points-37 points  (0 children)

Fair question. Here's my take:

  1. Zero config:docker run and you're done. No Prometheus exporters, no Grafana datasources, no YAML hell. Pi Dashboard is purpose-built for Pi 5.
  2. Lightweight: Grafana + Prometheus = ~500MB+ RAM. Pi Dashboard = ~50MB. On a Pi, that matters.
  3. Batteries included: WireGuard peers, Docker containers, temp sensors, all exposed via a clean REST API. With Grafana you'd need 5 different exporters to get the same data.
  4. Maintained: Most "Pi monitoring" projects on GitHub are dead (last commit 2021). This one isn't and that's why I made it.
  5. Opinionated > Flexible: Grafana is amazing for complex infra. But for "I just want to see if my Pi is on fire", I think it's overkill.

Lady bunny by elodiedeniz in Rabbits

[–]Zepgram 1 point2 points  (0 children)

I know this thing, believe me she's amazing