u/Foreign_Lead_3582

I’m an Industrial Engineering student with a big interest in the art of PCB design, and I decided to make it the focus of my thesis.

There’s a ton of material online about schematic capture and layout, but I’ve found surprisingly little about everything that happens before and after those stages which is exactly what I’m researching.

So I’d love to interview people who work professionally with PCBs, whether you’re a designer, engineer, librarian, manufacturer, reviewer, sourcing person, or involved anywhere else in the process.

It would just be an informal conversation about how things actually work in practice. And if you’re comfortable with it, I’d also be happy to cite your experience in the thesis.

If you’d be willing to help, please comment or DM me :)

P.S. Even if you’re not interested, please leave an upvote, it would genuinely help this reach the right people

I’m an Industrial Engineering student with a big interest in the art of PCB design, and I decided to make it the focus of my thesis.

There’s a ton of material online about schematic capture and layout, but I’ve found surprisingly little about everything that happens before and after those stages which is exactly what I’m researching.

So I’d love to interview people who work professionally with PCBs, whether you’re a designer, engineer, librarian, manufacturer, reviewer, sourcing person, or involved anywhere else in the process.

It would just be an informal conversation about how things actually work in practice. And if you’re comfortable with it, I’d also be happy to cite your experience in the thesis.

If you’d be willing to help, please comment or DM me :)

P.S. Even if you’re not interested, please leave an upvote, it would genuinely help this reach the right people

I want to run a faceless Instagram and TikTok page based entirely con Carousels.

The baseline seems pretty simple to me, I was thinking about Activepieces for the posting and automations, codex to create those automations, and a platform for both visibility and management of coordinate profiles, calendars etc...

I am worried by the quality of those carousels, do you have any advice about it? Tricks, skills, content or anything that helped you?

Also do you have any advice from your experience in general for doing this?

I have to launch a research on the cheapest functional way to segment pdf documents into sections and catalog each of them.

I'll do it for thousands of pages daily and I'd like to have it fully reliable and optimized in terms of costs.

I was thinking about running campaigns with Codex, now, how would you give the instruction to the agent? Would you use something like the /goal with expressed conditions? Or maybe giving it a loop or some graphs to operate within? Would you give it the task to search papers for it?

I'm asking it because I'd like to upskill my usage

Per gli studenti ed ex studenti di ingegneria elettronica, quanto nel vostro percorso avete imparato a disegnare e valutare PCB?

Da esterno mi sembra molto

I’m working on a fork with more component metadata and better filters to make searching my libraries easier. Once it’s more mature, I’d like to publish it for others to use and see what the KiCad maintainers think of the changes.

I’m also testing whether an AI agent can use the extra data to find components more reliably.

It’s going well so far, and I’d like to expand it to other parts of KiCad where we spend more time on repetitive tasks than on design. What comes to mind from your own workflow?

I’ve been designing schematics independently for a while, and I’ll soon be working with a company where I’ll also be involved in reviews.

Since I’ve mostly worked with a personal library so far, I’d like to come in a bit prepared for how schematic reviews are handled in a company setting.

For those of you who do this regularly, what do you actually spend most of your time checking? What are the things you tend to focus on that no course did explain to you?

I know every design is different, but I’m curious if there’s a sort of 80/20 here, a handful of things that make up most of a real schematic review.

For those with experience in multiple companies: how much overlap do you typically see between the component libraries of different companies?

Do most companies eventually converge on many of the same parts (like MPNs) or are their libraries largely company specific?

I’ve been designing schematics independently for a while and I’m now considering helping a company with schematic reviews.

They asked about my familiarity with component errata. I haven’t encountered them much having used my own library since always, so I’m curious:

How often do you actually run into relevant errata?

Do you routinely check them during reviews?

How often do they lead to schematic changes?

I couldn’t find much consensus online, so I’d be interested in hearing from people doing this professionally.

My neurodivergence put me in a deep rabbit hole with PCB schematics, I am understanding most of the things I read, but I am having an hard time with understanding what an EE do during reviews. How does it work, I saw there are ERC and DRC, is it all? Is there something else? Do you have any resource to understand it? I'd love to get to see deepest point, even though I know I won't understand much

Buonasera, sto conducendo una ricerca su violenze e abusi fisici (di ogni genere). Vorrei intervistare persone che ne hanno subito uno, sperando di trasformare l'esperienza in un beneficio per chi si troverà in futuro in procinto di ciò. Per chi si sente pronto/a a parlarne, può scriverlo qui o a me; per chi preferisce non farlo, nessun problema, in ogni caso mi spiace moltissimo per l'evento. Grazie

Is it possible to build a very little device with AML, for less than 30€?

What is the minimum you can spend to get a small device or a SoM with it?

Is it possible to build a very little device with ML, for less than 30€?

Sto considerando di passare da dipendente a libero professionista e vorrei capire un paio di cose, quanto capita che ci siano fatture che non vengono pagate?

Quanto tempo porta via? Capita che uno semplicemente si scordi di stare appresso al cliente considerando quanto passa dall'emissione al pagamento?

Sto considerando di passare da dipendente a libero professionista e vorrei capire un paio di cose, quanto capita che ci siano fatture che non vengono pagate?

Quanto tempo porta via? Capita che uno semplicemente si scordi di stare appresso al cliente considerando quanto passa dall'emissione al pagamento?

Sto valutando di lasciare il posto fisso per mettermi in proprio, ma la parte che mi spaventa di più è la gestione "legale" del rapporto con i clienti.

Per chi è già freelance/libero professionista:

Quanto spesso vi capita di dover scrivere, leggere o rivedere un contratto (o anche solo un preventivo con clausole) prima di iniziare un lavoro?

Vi è mai capitata una clausola che poi vi ha creato problemi (pagamenti, proprietà del lavoro, penali, exclusiva) che magari non avevate notato subito?

Quando avete un dubbio su un contratto, cosa fate di solito? Chiedete a un commercialista/avvocato, cercate online, chiedete a un collega, o semplicemente andate a intuito?

Mi piacerebbe capire quanto pesa davvero questa parte nel lavoro quotidiano prima di buttarmi e magari poi bruciarmi.

Piccolo sfogo, ma quanto mi frustra che sto cercando un auto su subito e autoscout e il mio schermo è colonizzato da Panda, 500 e Lancia Y, NON LE VOGLIO.
Per favore ditemi che esiste un modo per escludere i marchi

Da persona non competente in materia ho sentito ho sentito spesso parlare di avvocati divorzisti, del lavoro, d'affari...

E da qui il dubbio, quanti 'tipi di avvocato' esistono?

Vale la pena conoscere questa repository: https://github.com/ahmeabd/italia-corpus

Risolve un problema che chiunque abbia mai provato a lavorare con testi di legge italiani conosce bene: la normativa è pubblica, ma i formati fanno schifo e hanno bisogno di scraping e/o parsing, qui basta il git clone.

La cosa più figa secondo me è questa: ogni aggiornamento normativo è un commit. Un diff fa vedere cosa è cambiato.