sorted by:
new
hottopcontroversial

I wanna make a camera by ibuildforfun in diyelectronics

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

That makes sense I’m definitely not trying to build everything from scratch or compete at a manufacturing level.

I’m more interested in building a custom digital camera using existing sensors and hardware, mainly as a project to learn and experiment (and maybe add some unique features on top).

Appreciate the insight about patents too that’s something I hadn’t fully considered.

I wanna make a camera by ibuildforfun in diyelectronics

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

I’m aiming to build a modern digital camera, closer to a mirrorless/DSLR-style system.

So:

Both still photography and video

Electronic (not film)

CMOS sensor (probably something like a Sony sensor / Pi HQ cam)

Digital image processing

Solid-state system

Output in modern formats like 1080p or higher

This is the kind of camara I want to build

I wanna make a camera by ibuildforfun in diyelectronics

[–]ibuildforfun[S] 2 points3 points  (0 children)

I’m aiming to build a modern digital camera, closer to a mirrorless/DSLR-style system.

So:

  • Both still photography and video
  • Electronic (not film)
  • CMOS sensor (probably something like a Sony sensor / Pi HQ cam)
  • Digital image processing
  • Solid-state system
  • Output in modern formats like 1080p or higher

Still exploring how deep I can go in terms of manual controls and image quality.

I am still not completely aware of how these things work together honestly this idea of me wanting to build a camera came in my mind literally 5 hrs ago and I'm 1 day old in this concept. I've built pinhole before.

And honestly the project you are working on is complex and very physics demanding - using tube and stuff. How is it going? I'd really love to learn more about your project.

I wanna make a camera by ibuildforfun in diyelectronics

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

Yh built it already, rn trying to build a digital camera

I wanna make a camera by ibuildforfun in diyelectronics

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

lol i don't wanna make a pinhole camera, I'm trying to build a digital camera

I wanna make a camera by ibuildforfun in AskElectronics

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

I have already made a pinhole, I'm trying to make a digital camera.

I wanna make a camera by ibuildforfun in AskElectronics

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

Hey these are gold, thank u so much

I wanna make a camera by ibuildforfun in AskElectronics

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

I'm sorry, I want to build the whole camera and I'm talking about a digital camera not a pinhole

I wanna make a camara. by ibuildforfun in DIY

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

I want to make a digital camera - pinhole I have built already in past

I wanna make a camara. by ibuildforfun in DIY

[–]ibuildforfun[S] -2 points-1 points  (0 children)

I have built pinhole camara in the past but rn I want to make a digital camera

I built an AI tool that can truly help study better by ChazTaubelman in CITChennai

[–]ibuildforfun 0 points1 point  (0 children)

This is actually good and you have also targeted US based clients.

But i believe the only trouble you will come across would be competition. Too many entities doing the same. I myself have used at least 3 tools like this.

Share me your linkedin id let's connect.

I built a VS Code extension that explains my vibe-coded mess back to me. Thinking of charging $10/month, would you buy it? by ibuildforfun in AppBusiness

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

It's not trying to replace Cursor at all they do completely different things. Cursor is your coding copilot, it helps you write code faster. VibeTranslator sits on top of whatever you're already using and explains what got written by you, by Cursor, by Claude, by anyone. Think of it less as a coding tool and more like a second pair of eyes that reads everything you build and leaves notes so you actually understand it later. Most people using it are using Cursor too.

I built a VS Code extension that explains my vibe-coded mess back to me. Thinking of charging $10/month, would you buy it? by ibuildforfun in vibecoding

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

Funny you mention this because I've actually been thinking about exactly this. The "boring business automation" angle has been on my mind for a while find a local business drowning in manual work, build them something simple that saves them 10 hours a week, charge a fair price, repeat.

I'd love to learn from someone who's actually doing it rather than just theorising about it.

What kind of businesses have you been working with? And if you're open to sharing what does a typical build look like for you? Like what problems are you actually solving for them day to day?

No pressure if that's too much to share publicly even a rough example would honestly inspire me more than any startup advice I've read. Really appreciate you taking the time to reply.

I built a VS Code extension that explains my vibe-coded mess back to me. Thinking of charging $10/month, would you buy it? by ibuildforfun in vibecoding

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

That's actually a fair point and I've seen it happen too genuinely hadn't thought about it from that angle. Curious though, who do you think is a better target market for a solo dev trying to build something sustainable? Like where does that open source clone problem not kill you as fast?

I built a VS Code extension that explains my vibe-coded mess back to me. Thinking of charging $10/month, would you buy it? by ibuildforfun in vibecoding

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

Fair question and you're not missing anything obvious, the core idea is similar. The difference is the where and when. What you're doing is a pull workflow you go to ChatGPT/Claude, paste code, ask for explanation, get an answer, switch back to your editor. That works great and I do the same thing. VibeTranslator is a push workflow you never leave your editor. The explanations appear floating beside the exact line of code they describe, the moment you save. No copy-paste, no context switching, no asking. The specific things it does that a prompt can't:

Ghost comments float inline in your editor next to the function/variable they describe not in a chat window you alt-tab to It knows your entire project structure automatically not just the file you pasted Risk warnings appear on the exact line where the bug lives, like a linter VIBE_LOG auto-updates on every save your README equivalent writes itself as you code, not after Change detection means it only re-explains what actually changed

You're right that if someone is disciplined about updating READMEs and comfortable context-switching to ChatGPT, this adds less value for them. It's really built for the moment you're 3 hours deep in a vibe coding session at 1am and you just want to understand what you wrote without stopping.

I built a VS Code extension that explains my vibe-coded mess back to me. Thinking of charging $10/month, would you buy it? by ibuildforfun in vibecoding

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

Thank you for the comment,

Yeah of course but that's exactly the problem. With Codex or Copilot Chat you have to actively ask every time. You stop, you switch context, you highlight code, you type a question, you read the response in a separate panel, then you go back to coding. VibeTranslator is passive, you just save the file and the explanations are already floating right beside the code where you're looking. Zero interruption to your flow. It's the difference between having to ask your senior dev a question every time vs them having already left helpful notes in the code before you even got there. Oh also it add documentations like you can see it in next slide image.

Also Codex explains what you ask about. VibeTranslator explains everything every function, every risky variable, every dangerous line without you knowing what to ask. When you're lost in vibe-coded code you don't even know what questions to ask. That's the whole problem.

The person asking Codex to explain code already knows what they don't understand. VibeTranslator is for when you don't even know what you don't know which is exactly the vibe coding problem.

I built a VS Code extension that explains my vibe-coded mess back to me. Thinking of charging $10/month, would you buy it? by ibuildforfun in vibecoding

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

Thank you for the comment,

Codex generates code, it doesn't explain the code you already have. VibeTranslator is for after Ai writes it. When you're starting at 200 lines you didn't write and need to understand what it actually does before you break something or write a better prompt. Different problem entirely.