[sdiy] ot: is it true that Waldorf crashed?

Czech Martin Martin.Czech at micronas.com
Tue Feb 24 13:09:11 CET 2004


A bit too pessimistic.

Well, all , managers sooner or later loose
contact with reality, i.e. physics.
Some are not capable from the beginnning, others
will loose their skill, anyway, they will not
really know what you're doing.

As long as the people who know what they are doing
are not afraid and tell people who not not know
at all what's going on to simply shut up in technical
matters, it's ok.

"We do not talk about your roadmap/business plan
and you keep out of technical issues"

is a very good unwritten rule for company success.

If you're really good in your job, you'll win
all such fights against mid-level management,
because top management can afford to fire
the mid level guys (you do not notice when they are on vacation,
do you?), but they can not afford to fire
good programmers and certainly not designers of hardware.
Because that would stop development at once.

And if they fire you, the better it is because they
didn't estimate the value of your work anyway, which
means that this company will crash sooner or later.


It's like in football (well soccer for the american members),
you can not fire the team, so better fire the coach.


So there is no need to avoid technical education.
But you must excell.

The opposite is true: if the company is "baught" by a  larger
fish in the bowl, business people or generally mid level mgt.
people are in great danger.

Not so with good designers.

Been there, seen this.

I pick a fight with any managment person, and so far they never
did something to me, but accepted my technical point of view.


m.c.


> -----Original Message-----
> From: owner-synth-diy at dropmix.xs4all.nl
> [mailto:owner-synth-diy at dropmix.xs4all.nl]On Behalf Of TIm Daugard
> Sent: Freitag, 20. Februar 2004 21:07
> To: Synth DIY
> Subject: Re: [sdiy] ot: is it true that Waldorf crashed?
> Importance: Low
> 
> 
> > Thats because managers don't understand, good managers come 
> from people
> > who've been there and done it.
> > But that seldom happens as most programmers enjoy the work..
> 
> Another situation I've seen (and been in) is that the 
> managers come from
> elsewhere with little knowledge of the processes. The 
> programers (and hardware
> engineers and sharp technicians) are too valuable to the 
> company doing the work
> they do.
> 
> I told my son to get a business degree, because a technical 
> degree can result in
> you rapidily getting pigeon holed. I think the ultimate 
> degree to have in US
> gov. contracting would be a Dr of the pre-renassaince art of 
> the 10Km area
> surrounding Parma, Italy. You can fill the contract slots 
> requiring a doctorate
> without ever being expected to do anything in your area of 
> speciality. They
> would probably put you in charge of the contract.
> 
> I agree completely, that thinking long and hard about a 
> project is at least 50%
> of the work. The more thinking ahead of time the less rework.
> 
> Tim Daugard
> 
> BTW isn't anyone building anything any more?
> 
> 
> 



More information about the Synth-diy mailing list