Design Con 2015
Breaking News
Blog

Three months' design work in four weeks

Blog
12/10/2010 01:19 PM EST

 10 comments   post a comment
NO RATINGS
View Comments: Newest First | Oldest First | Threaded View
Dwight Bues
User Rank
Rookie
re: Three months' design work in four weeks
Dwight Bues   1/17/2011 6:32:47 PM
NO RATINGS
Um, OK. I think I can clear up a couple of points here. I DID get recognition from Management: did NOT get laid off in the next two RIFs, so I guess my "volunteerism" paid off. Incidentally, the enginners who subscribed to the theory of "A lack of planning on your part does not necessarily constitute a crisis on my part." actually DID get laid off!!! Sometimes it helps to "lean forward" a bit. Also, and this is a funny one, WE NEVER BUILT PROTOTYPES!!! Management, as a rule, didn't bid the Labor to kluge up the circuits beforehand. Makes me wonder how we did so well....

Salio
User Rank
Rookie
re: Three months' design work in four weeks
Salio   12/31/2010 9:13:55 PM
NO RATINGS
I probably would have done the same thing as you did by staying up late and working around the clock to get the job done. I am just curious wasn't testing done up front to see whether the design was as it was intended to be.

David Ashton
User Rank
Blogger
re: Three months' design work in four weeks
David Ashton   12/26/2010 8:24:06 AM
NO RATINGS
Point taken Glen. It's sometimes very difficult to know when to let management stew in their own crisis and when to step up and get them out of it. In this case they did recognise Dwight's efforts, apparently. And in the end, you have to live with yourself and your own criteria for a job well done. A supportive management style will always get more out of the workers than being hard-assed. Where I am at the moment, the "us and them" attitude is almost palpable and it has made a good company a very frustrating place to work. If you are part of a team it is a pleasure to contribute to getting the team out of a tight spot. If you don't feel part of a team, it's very difficult to give of your best.

zeeglen
User Rank
Blogger
re: Three months' design work in four weeks
zeeglen   12/26/2010 12:14:50 AM
NO RATINGS
I think EmbeddedNinja's comment refers to the old cliche "A lack of planning on your part does not necessarily constitute a crisis on my part." In other words, why should someone have to struggle to compensate for another's goof? Somebody goofed up, somebody else busted their butt to save the company's bottom line. Good engineering response to problem solving, jump in and resolve the problem with many hours of unpaid overtime. Unfortunately this engineering response gets no credit or acknowledgment (often upper management is not aware of the engineer's efforts) and is overlooked or forgotten during times of downsizing.

David Ashton
User Rank
Blogger
re: Three months' design work in four weeks
David Ashton   12/25/2010 10:36:22 PM
NO RATINGS
I think you're being a bit hard here. It's an engineering problem, does it matter where it came from?? So Dwight "did what every other young engineer would do – I "buckled down" and got to work." Good on him! He says also that "My boss was impressed...." so hopefully it got him ahead in the job. I think 90% of engineers would have taken this course of action, and rightly so.

EmbeddedNinja
User Rank
Rookie
re: Three months' design work in four weeks
EmbeddedNinja   12/14/2010 4:40:28 PM
NO RATINGS
I think it's ridiculous that you had to pay for someone else's mistake. Sorry, your lack of planning isn't my emergency.

Patk0317
User Rank
CEO
re: Three months' design work in four weeks
Patk0317   12/12/2010 6:13:34 AM
NO RATINGS
I love these old war stories! Too bad plds weren't fast enough at the time it would have made things much simpler. My very first design I used a dead bug socket instead of the normal one and my design of course didn't work until I put the part in upside down and soldered on some little yellow wires. My boss made me do this before he would let me spin another PCB! Anyone else got some good stories?

sharps_eng
User Rank
Rookie
re: Three months' design work in four weeks
sharps_eng   12/11/2010 11:03:58 PM
NO RATINGS
Were we more scared then? Recent designs of mine have used 900MHz datarates, and I have done lots of digital video without problems (certainly without board-level simulation timing tools). When I started, though, people were terrified of video rate signals (13.5MHz!) let alone ECL and beyond. I guess silicon was sooo slow then we had no margins left, and the bleeding edge of digital design was a black art. Now ts the other way about, Analog is the twilight zone.

agk
User Rank
Rookie
re: Three months' design work in four weeks
agk   12/11/2010 8:33:38 AM
NO RATINGS
A good experience with the video card designs and the propgation delays in the TTL circuits and the schematic capture ,simulations.In the 20 years time the scenerio completely changed.Going back and thinking of the past experiences some times gives us lot of pleasure.

More Blogs
Data protection and redundancy features implemented across entire SoC designs will help teams implement functional safety faster and at a higher quality level
Hackathon produces designs that could be assembled by villagers with limited resources.
2015 will likely be the year of widespread awareness and adoption of giga-scale SPICE. Willy Wonka may agree: "So much time and so little to do. Wait a minute. Strike that. Reverse it."
In January 2015, Lindsay Craig will be teaching technology workshops with his East African partners to farmers, educators, engineers, artists, students, and dreamers.
The open ESIstream protocol has less encoding overhead and higher data bandwidth than JESD204B. It's also significantly easier to implement ESIstream digital core.
Flash Poll
Like Us on Facebook

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)
EE Times on Twitter
EE Times Twitter Feed
Top Comments of the Week