Pratica di Shadowing: BONUS: Should we do PCB or enclosure design first? (Feat Andrew Amirnovin) - Impara a parlare inglese con i video

Scegli una modalità di pratica

Ogni modalità apre una sala di pratica a schermo intero.

178 frasi
Se le frasi sono troppo corte o troppo lunghe, clicca su Edit per modificarle.
1
Hi everyone, it's Adrian here from Sophist.
2
I've just got another quick bonus podcast episode for you
3
because I was having a chat with our head of new product development,
4
Andrew, recently about whether you should do PCB or enclosure design first and I wanted to find out what his opinion was.
5
Let's get into that.
6
Andrew, welcome back.
7
Hi.
8
Hey, Adrian.
9
Good to be here again.
10
Glad to have you on.
11
And the reason for getting you on this time is because we saw a conversation on the Hardware Academy forum,
12
and I'll leave the link to that, listeners, so you can go check it out.
13
It's a forum and a website that helps SMEs
14
and entrepreneurs to get information and support to bring their new product ideas to life and to market.
15
And this conversation was about whether you should do PCB design first or enclosure design first.
16
And actually, there was quite a lively conversation about it.
17
And some people thought the latter and some people thought the former.
18
So I was just hoping to get your feedback on this.
19
Where do you stand?
20
and also hopefully you can give us some guidance on how to make the decision on
21
which way to go I'm assuming of course that this is going to be most relevant to people making
22
electromechanical products as well yes absolutely I think this was a very good conversation between a lot of engineers in
23
that forum and I think that really nobody got to in any kind of a conclusion
24
which way is the right way well to be honest i mean enclosure
25
or pcb which one should it be first kind of like chicken neck situation chicken
26
and egg situation you know it is really really difficult to decide without knowing much about the product you know if you
27
are a design engineer that you just kind of settled in your own ways
28
and you always do the pcb design first well you may run into some problems
29
when you try to put that pcb in a tighter enclosure that
30
that the id team has already you know kind of thought of
31
and then you'll have to kind of go backwards
32
and split the pcb
33
or whatever else you have to do in order to fit it there uh
34
and the backwards just the reverse could be possible you know
35
if you're a closure designer and you design the enclosure that is small and nothing is going to fit in there,
36
then there's going to be a war in the office.
37
People are not going to agree with each other.
38
And so I think the best way, honestly, is to come up with a process
39
that makes it easy for everyone to understand what is the right way to do this?
40
What's the, you know, in my opinion, honestly, in some cases, you know,
41
designing the PCB first makes a lot of sense, depending on the product.
42
And in some cases, building the, you know, enclosure makes a lot of sense because of the fact
43
that size and dimensions and the ID is more important than what's inside, for example, or what the user expects, you know,
44
imagine if iphone was the size of a tv uh
45
if the iphone was the size of a tv gosh i
46
mean i don't think anybody would buy an iphone it would be just too big
47
and you know if if the enclosure was decided to be
48
that big uh so i'm exaggerating of course but um you know everything needs to be
49
down to what makes sense for that product, not only in the design office, you know, with the team,
50
but also with the customers that we're going to sell this product for.
51
If the customers demand a smaller package, then the enclosure is the one that the way that has to go, right?
52
You have to design it for enclosure.
53
But if enclosure is not so important functionality is important and you need to build a product that really functions well
54
then basically you you do the pcb first and and try
55
and fit them in a format format or fun or a package
56
that uh that fits just about right
57
so i i came up with an idea
58
that i think might be helpful and not necessarily written on stone steps or process.
59
I think it's just an idea to help at least help our young engineers to kind of find their way
60
which way should be.
61
I call it the five steps of basically,
62
you know, the basic design of a brand new product that that doesn't exist
63
as much in the industry
64
or in the market maybe there is one competitor is just newly uh you know uh is producing one
65
or you know in that kind of a scenario is what we're talking about
66
well the first step is creating a product requirements document what is called prd
67
and typically this comes from I believe product engineering team
68
and they kind of design the form fit
69
and function of the early product
70
and the concept product they they come up it would be
71
nice actually they would come up with a user manual as well and preliminary product specification
72
maybe a reliability requirement for example
73
if it needs to meet a certain for example drop height
74
so this PRD would have so much information there
75
that would help at least the design team have an idea
76
of what the product should be like in terms of specification this could be very useful for PCB designers.
77
However, step two would be an ID, industrial design for the product.
78
I know that a lot of us have seen on TV, you know, a guy who is designing a car from a wax.
79
Have you seen that?
80
He's like scraping a little bit more from the front,
81
a little bit from the back and reshaping corners and so forth.
82
That's basically ID.
83
And ID, industrial design of the product, is critical to the success of the product.
84
It's kind of like the fashion designer.
85
You know, he's trying to make the look and feel of the product be appealing at the same time, functional.
86
And it's really a very, very sophisticated area in the engineering.
87
And through this idea, it gives the engineering team,
88
especially young design team, a good picture in their mind
89
and the image of what the product is going to look like at the end
90
or what it should be looking like once how it should be designed
91
and once you have that this id document should also have a detailed
92
or at least rough estimate of dimensions you know length widths height
93
and so on and this would help the designer understand okay well
94
if it's going to be that big then my pcb needs to be this big roughly,
95
you know, so they kind of have an idea what's going on and then where the buttons should be, where the LCD should be and so on.
96
So all of that will be an ID design, a look and feel of the final product.
97
But the next, also as important, next step is product functionality.
98
And that would give a really important point on what's the max operating temperature,
99
max operating voltage and current, and how should it operate, for example, you know, if it's a telephone,
100
what kind of LCD we want, what kind of features we want on this mobile phone, for example.
101
So basically, the functionality would have all the features,
102
functionality parameters and perhaps some of the electrical specifications
103
or maybe most of the detail electrical specifications in terms of how they should be designed
104
and again you know i'm just giving you these ideas they're not written on stone
105
and every company dependent on the product they're going to do their side of how they categorize these will be different.
106
Maybe electrical specification is under functionality in one company,
107
but maybe it's under PRD or user manual in another company.
108
So there's no one cookie cut type of categorizing or writing these information.
109
But as long as you have these sections identified and discussed within Teams, I think it's going to help a lot.
110
Number four, I think, is bill of material is very important.
111
Bill of material gives the picture of what kind of components
112
and materials need to be used and how they need to be sourced, how many of those are in the, for example, in the product,
113
and whether or not the total cost estimate is within the ballpark of the funding
114
or estimate of what the project cost should be, initial cost at least.
115
So I think that bill of material is important to know something about it.
116
And then lastly, step number five is when you're designing a brand new product that perhaps maybe only one,
117
you know, competitor has it, it would be good to have a sample of the competitor for competitive analysis
118
and or maybe even re-engineering so
119
that you can design your product even 10 times better in terms of functionality or design or features.
120
Yeah.
121
And then also need to get back to your own customer if you're designing for a particular customer,
122
understand what the customer requirements are.
123
Perhaps customer wants same product in the, you know, in the field,
124
but wanted like smaller version or cheaper version or bigger version, you know, you never know.
125
So it's very important to understand what really the customer wants.
126
Maybe the customer wants an industrial version, which is more robust and reliable, right?
127
So no matter what it is, this step is important, because imagine you don't tell your team that this needs to be industrial version,
128
and they start developing your product that doesn't even meet industrial version.
129
So you, you can ship that product, right?
130
So it is an important step in terms of trying to determine, you know, what to do.
131
So in my opinion, Adrian, I think if you take these five steps to a meeting
132
and have a comprehensive meeting from heads of departments and design and development,
133
reliability, you know, purchasing, manufacturing.
134
If you have all these heads of the departments there and you're going through these, you're saying, okay, we have a brand new product that we need to design.
135
Where should we start?
136
Well, knowing these steps and knowing these information,
137
not necessarily following these steps in the manner I mentioned, it can be mixed up or it doesn't matter which one is first,
138
just having these information for each area and knowing what the product is going to look like.
139
And in engineering, sometimes we call it form and fit
140
and function of the product if you know
141
that you'll have a big idea or big picture of the product
142
and then you can easily decide and brainstorm should we start with pcb first
143
or the enclosures i think at
144
that time it will be clear do you agree yeah i do
145
and i think the point that you made about validating it as well for your potential customer is important because
146
this is all about reducing risks right you're reducing the risks of bringing out product
147
that people aren't going to want to buy you're reducing the risks of overruns in terms of time because
148
if something has to be changed that's going to be that's
149
going to take time you're reducing the risks of cost overruns as well
150
because changes certainly the closer you get to production it's It's going to be more costly.
151
So being organized and having that basis of information and those five points that you've mentioned are really, really helpful for that will help you to choose the right thing at the right time.
152
So you don't want to end up making an enclosure, going through all of the time and expense to design it, start producing it, and then it's too small, for example.
153
Right, right.
154
Exactly.
155
I mean, if you imagine if you start with enclosure and too small, well, for sure, those PCBs are not fitting there.
156
And then on the other hand, if the enclosure is supposed to be small, then there should be a good communication with the PCB team
157
that the typical way of designing the PCB is not going to work.
158
It's just we need to come up with a ways of really small, maybe flex cables instead of, you know, if the product is small, like a digital watch, for example.
159
so so there are other ways that other technologies
160
that they're more miniature you're the many layers to each one of these pcbs
161
so there are ways of doing these things
162
but you just have to i think the rule number one
163
is communication among teams between cross-functional teams you definitely have to have very good communication
164
and i think that project managers
165
and the product engineers who are trying to launch this brand new product they need to be a good communicator
166
but also really need to manage the teams in a way that they understand that you know if the prod
167
enclosure needs to be go uh designed first then let's go with that let's not stick to
168
what you learned in another company uh necessarily uh maybe brainstorm and come up with
169
an innovative new process yeah great that's uh that's very very helpful
170
and hopefully that puts people's minds at rest if if they're wondering well pcb first or enclosure first but i suppose
171
in a nutshell it depends it does excellent guidance there andrew thanks for popping by
172
and yeah hopefully we'll get you on again soon thanks adrian
173
talk to you later thanks again for listening to this podcast
174
brought to you by the sophie's group we're on a mission
175
to provide you with everything you need to manufacture effectively in asia including inspections auditing new product development support,
176
contract manufacturing, 3PL warehousing and fulfilment, and much, much more across Asia's key manufacturing areas.
177
Visit us at sophist.com, that's S-O-F-E-A-S-T.com to learn more and get help.
178
If you've enjoyed the podcast today, please do rate, review and share because it will really help others discover us too.

Scarica l'app

Tutto ciò che serve per parlare fluentemente

Pronuncia con IAVoto per ogni frase
Pratica IPAPadroneggia ogni suono
VocabolarioCostruisci il tuo lessico
Gioco di vocabolarioImpara giocando

Stesso Canale

FOR YOU

Video consigliato

Vocabolario e note di pronuncia per questa lezione

Questo video contiene 178 frasi e 2396 parole da ripetere con lo shadowing. Il parlato dura 16:42. Chi parla mantiene un ritmo costante di circa 144 parole al minuto, comodo per lo shadowing. Il 87% delle parole rientra nelle 3.000 più comuni dell’inglese, quindi il lessico è facile da seguire.

Vocaboli chiave di questo video

15 parole meno comuni del video, con pronuncia e significato:

  • enclosure /ɛnˈkloʊʒəɹ/ (sostantivo) — allegato. Something that is enclosed, i.e. inserted into a letter or similar package.
  • functionality (sostantivo) — funzionalità. The ability to do a task, performance, or execution; a set of functions that something is able or equipped to perform.
  • specification (sostantivo) — specificazione, specifica. An explicit set of requirements to be satisfied by a material, product, or service.
  • designer /dɪˈzaɪnɚ/ (sostantivo) — designer, progettista. A person who designs something, or who designs things as a profession.
  • necessarily /ˌnɛs.əˈsɛɹ.ə.li/ (avverbio) — necessariamente, a tutti i costi. Inevitably; of necessity.
  • helpful /ˈhɛlp.fl̩/ (aggettivo) — disponibile, utile. Furnishing help; giving aid; useful.
  • forum /ˈfɔːɹəm/ (sostantivo) — foro. A place for discussion.
  • estimate /ˈɛs.tɪ.mət/ (sostantivo) — stima. A rough calculation or assessment of the value, size, or cost of something.
  • requirement /ɹɪˈkwaɪɹmənt/ (sostantivo) — requisito. A necessity or prerequisite; something required or obligatory. Its adpositions are generally of in relation to who or what has given it, on in relation to whom…
  • podcast /ˈpɑdˌkæst/ (sostantivo) — podcast, audioprogramma. A program, especially an audio program, produced on a regular basis, delivered over the Internet in a compressed digital format and designed for playback on…
  • competitor /kəmˈpɛt.ɪ.tɚ/ (sostantivo) — avversario, rivale. A person or organization against whom one is competing.
  • format /ˈfɔːɹ.mæt/ (sostantivo) — formato. The layout of a publication or document.
  • package /ˈpæk.ɪd͡ʒ/ (sostantivo) — pacco. Something which is packed, a parcel, a box, an envelope.
  • guidance /ˈɡaɪdəns/ (sostantivo) — guida, direzione. The act or process of guiding.
  • manual /ˈmæn.j(u)əl/ (sostantivo) — manuale, guida. Synonym of handbook.

I phrasal verb che sentirai

  • come up with (verbo) — ideare, escogitare. To manage to produce, deliver, or present (something) by inventing, creating, thinking of, or obtaining it.
  • go through (verbo) — attraversare. To travel from one end of something to the other.
  • step in (verbo) — rimpiazzare. To act as a replacement or substitute.
  • come up (verbo) — venire fuori, emergere. To emerge or become known, especially unexpectedly.
  • do in (verbo) — uccidere, finire. To kill or end; to defeat.
  • end up (verbo) — andare a finire, finire. To bring to a conclusion.
  • find out (verbo) — scoprire. To discover, as by asking or investigating.
  • go on /ˈɡoʊˌɒn/ (verbo) — continuare. To continue in extent.

Pronuncia a cui fare attenzione

Chi parla usa 33 contrazioni e forme ridotte, come you're, they're, doesn't. Pronunciale nella forma breve, così come le senti.

  • I suoni “sh” e “zh”: enclosure /ɛnˈkloʊʒəɹ/, dimension /daɪˈmɛn.ʃən/, conclusion /kənˈkluːʒən/, inspection /ɪnˈspɛkʃən/, closure /ˈkloʊ.ʒɚ/
  • Parole lunghe — attenzione all’accento: necessarily /ˌnɛs.əˈsɛɹ.ə.li/, electrical /ɪˈlɛktɹɪkəl/, competitor /kəmˈpɛt.ɪ.tɚ/, comprehensive /ˌkɑm.pɹəˈhɛn.sɪv/, preliminary /pɹɪˈlɪmɪnɛɹi/

Come esercitarsi con questo video

  1. Ascolta tutto il video una volta senza parlare e annota le parole che non conosci.
  2. Fai shadowing frase per frase a velocità normale, ripetendo ognuna finché il tuo ritmo coincide con quello di chi parla.
  3. Registrati e confronta con l’originale, facendo attenzione a parole come enclosure, functionality, specification.

La grammatica di questo video

Le strutture che chi parla usa di più, con le parole esatte del video:

StrutturaNel video
Forma passiva be + participio passato — conta ciò che accade, non chi lo fawas decided · is called · should be designed
Present perfect have/has + participio passato — un’azione passata che conta ancora adessohave seen · Have you seen · you've mentioned
Frasi relative who / which + frase — un’informazione in più su una persona o una cosaguy who is · version, which is

Cos'è la tecnica dello Shadowing?

Shadowing è una tecnica di apprendimento delle lingue supportata da studi scientifici, originariamente sviluppata per la formazione dei traduttori professionisti e resa popolare dal poliglotta Dr. Alexander Arguelles. Il metodo è semplice ma potente: ascolti un audio in inglese di madrelingua e lo ripeti immediatamente ad alta voce — come un'ombra che segue il parlante con un ritardo di solo 1–2 secondi. A differenza dell'ascolto passivo o degli esercizi di grammatica, lo shadowing costringe il tuo cervello e i muscoli della bocca a elaborare e riprodurre simultaneamente i modelli di discorso reale. La ricerca dimostra che migliora significativamente la precisione della pronuncia, l'intonazione, il ritmo, il discorso connesso, la comprensione dell'ascolto e la fluidità del parlato — rendendolo uno dei metodi più efficaci per la preparazione alla prova di speaking dell'IELTS e per la comunicazione reale in inglese.

Tecnica dello shadowing: leggi la guida completa passo dopo passo →