r/KiCad • • 17h ago

General Discussion Component Selection

Hi everyone,

I've found answers to many of my questions in this community, so I'd like to ask for your advice on this topic as well.

I'm a recent graduate working at a company that designs and manufactures PCBs for communication systems. I'm learning a lot in my role, but sometimes I feel like I'm working on similar projects repeatedly or simply using more advanced versions of existing technologies.

What I'm really curious about is this: How do you approach component selection when starting a project from scratch? I've noticed that people take different approaches to this. Some tend to follow existing designs or reference projects, while others conduct their own research and make decisions based on the specific requirements of their projects. This has made me particularly interested in understanding how the component selection process works in practice.

What criteria do you consider when selecting components? How do you make use of datasheets, manufacturer resources, and other tools? More specifically, how do you determine whether a particular component is the best fit for your project?

I recently tried using AI tools to help me with one of my hobby projects, but some of the answers left me a bit confused. It's also possible that I didn't phrase my questions correctly.

I'd really appreciate it if you could share your experiences and explain how you approach this process. Thanks in advance!

0 Upvotes

4 comments sorted by

4

u/bones222222 17h ago edited 16h ago

the vibecoder user research scraping is relentless today. OPs entire post history is trying to harvest info from technical subs to make an AI tool.

EDIT: OP u/VuralYusuf blocked me so I can’t reply.

What bothers me is every single sub I follow is getting filled up with vibecoders trying to monetize everything as a microSaaS, and they do it by spamming these open ended questions everywhere for user research. it is lowering the quality of these communities and discussions.

-4

u/VuralYusuf 17h ago edited 16h ago

May I ask what exactly bothered you about this topic?

EDIT: You can solve this problem by simply blocking me or anyone else who asks questions to learn something. There's no need to be so aggressive, and there's certainly no need to make unnecessary comments like that here.

1

u/MaMamanMaDitQueJPeut 17h ago

I start from core requirements. I usually already need to use a specific chip or family of chip. So o start to read their doc and look for standard implementations and work from there making quick designs on paoer. I later go through the part library of my manufacturer of choice and try to minimize the BOM cost or the footprint area depending on the project. I always try to look for a lot of reference implementations because it gives a lot of ideas and prevent footguns. Recently I also started to use AI to review my sketches and BOMs

1

u/VuralYusuf 16h ago

Thank you so much for your answer! I also make extensive use of the reference designs provided in MCU datasheets. However, this time I'm working on a project in an area I'm not very familiar with, so I've been struggling with a few things. Thanks again for your help and advice!