Author Topic: When you follow the schematic but it doesn't work  (Read 11275 times)

0 Members and 1 Guest are viewing this topic.

Offline b_force

  • Super Contributor
  • ***
  • Posts: 1381
  • Country: 00
    • One World Concepts
Re: When you follow the schematic but it doesn't work
« Reply #50 on: July 27, 2018, 11:41:38 pm »
Thats what everyone said until their job turned into three lines of python.  :-DD

I agree but the focus is on automation. The whole point is that if a task is to be done regularly then automation has a cost benefit. Even our analysts automate with specflow and our project management team automate their workflow with python. Our graphic designers automate their pipelines with various tools (I don’t go there myself). Our management team run automated reporting they built themselves. Our customer support team drive our public API to resolve issues with their own scripts. Our entire front to back end process stack is automated. All our marketing is data and code driven.

Everyone is a programmer if they like it or not. We destroyed all of our competitors because of automation.

We’re “a loose interpretation of agile” but continuous delivery focused. Everything from code to production is automated.
To get a little bit back on topic, this is exactly why most schematics don't work.
PCB and analog design (I call analog everything else that's more than just 1s and 0s = non-lineair behaviour) doesn't seem to be relevant anymore these days.

The majority of vacancies I see is all about programming. In fact best is finding someone who is able to be a top notch programming, FPGA programmer and also has plenty of experience in PCB design.
Mostly all asked and noticed in just one sentence.
I really don't like to put people into boxes, but many of these things are an expertise on its own.
Just simply by the fact that it takes so much time and effort to master one of these skills that you don't have much capacity to master another one.
On the other hand, it looks like that people aren't respected anymore if they don't know 100% of the ins and outs.

This is also what's immediately wrong with most schematics online.
For someone having some kind of experience in board design and putting it all together, you can already see that a lot of times it's just simply asking for trouble.
People seem to forget that we don;t live in an ideal world an we will never be, hooray physics.

Offline tooki

  • Super Contributor
  • ***
  • Posts: 15804
  • Country: ch
Re: When you follow the schematic but it doesn't work
« Reply #51 on: July 29, 2018, 01:00:54 am »
Why would they need to know?

Innovation and research without knowing the underlying physics is like building structures without a solid base.
I can't see why the "bubble economy" risk doesn't apply to engineering as well.
I disagree, it depends entirely on the field. A software engineer doesn't benefit in any way, shape, or form from understanding the physics of the electronics that run their code.


What’s your native language, blueskull?

The vast difference between Chinese and English is not an excuse for me not to polish my English skill.
No, certainly not! Nor did I mean to suggest that your English is subpar (it's excellent, as far as I can tell from your writing.) I was just curious because it would give me a better image of your language background. (See next Q.)

I mean, I assume you know that in English, the L in salmon is silent.

Still, it's far from "see-men".
Yes, but the reason I asked about your native language is that one's native language not only informs how we speak other languages, but also how we hear them. (Like how many English speakers mishear the German "ch" as the "sh" sound.)

(I studied linguistics as my minor at university, aside from being a polyglot myself.)

What did she mean by blowing?  :o

A (likely electrical) load.
I hope the parentheses are true. Cuz blowing a non-electrical load is also… a thing. ;)


And why should they need to??

We are a research university, not a tech school. We are supposed to train people with a general, good and comprehensive understanding in the field(s) and expand body of human knowledge.

I don't expect details, but I would expect at least, for an ECE professor, to be able to explain roughly what a "hello world" does under the hood, down to transistor level.
I think even ECE is so broad that expecting that from everyone is absolutely unreasonable.


It’s a necessity. The amount of total human knowledge is growing at an exponential rate. It’d be literally impossible to try and learn all the stuff outside your niche.

No need to be "all". But a general understanding of everything related to the circle one travels is not too much to ask for.
Yes, but I doth declare that I suspect your meaning of a "general understanding" is far, far deeper than is realistic.
« Last Edit: July 29, 2018, 01:03:30 am by tooki »
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf