Breaking News
Comments
Newest First | Oldest First | Threaded View
Page 1 / 4   >   >>
I_B_GREEN
User Rank
Rookie
re: Most engineers are lazy…and that's often a good thing
I_B_GREEN   6/7/2012 5:05:55 PM
NO RATINGS
proactive, feedforward thinking, intuiative...

TFCSD
User Rank
CEO
re: Most engineers are lazy…and that's often a good thing
TFCSD   6/7/2012 12:44:14 AM
NO RATINGS
Cut and paste preivous comments and insert "Yep".

ChipBuilder
User Rank
Rookie
re: Most engineers are lazy…and that's often a good thing
ChipBuilder   6/5/2012 3:41:47 AM
NO RATINGS
assign lzy = 1'b1; (if you got the subtleness that its Verilog and not VHDL, I'm proud)

Frank Mlinar
User Rank
Rookie
re: Most engineers are lazy…and that's often a good thing
Frank Mlinar   6/4/2012 6:40:18 PM
NO RATINGS
I look at results, not what a person "looks like" while working. If I don't see good results when I expect them, I would then term that person as lazy or incompetent or needing additional direction/mentoring (or possibly having a bad hair day). Having said that, extensive experience of a person is very important in making an accurate judgement.

ghfarmer
User Rank
Rookie
re: Most engineers are lazy…and that's often a good thing
ghfarmer   6/4/2012 2:05:41 PM
NO RATINGS
When asked what my personal strengths were I once told an interviewer, "I'm lazy." It definitely got his attention. Then I got to explain what that meant. I refuse to do any repetitive data work. If I can get the computer to do it, I will. In my previous job I cut data entry time by 95% and increased throughput 16-fold while eliminating data entry errors. In a still earlier job as a cost estimator I automated the cost estimating system and increased throughput 10-fold, eliminating my position which got me a promotion into engineering. Telling the interviewer I was lazy was a gamble but it made me stand out from the other applicants and I got the job.

resistion
User Rank
CEO
re: Most engineers are lazy…and that's often a good thing
resistion   6/3/2012 6:51:26 PM
NO RATINGS
It could get tricky sometimes. If you have two team members, one who gets things done conventionally "the hard way" and one who got it done in an unconventional but quicker and more effective way, who should get more points? The unconventional way is often not recognized or even accepted by colleagues, more often than you'd think.

willc2010
User Rank
Rookie
re: Most engineers are lazy…and that's often a good thing
willc2010   6/3/2012 10:37:52 AM
NO RATINGS
The behaviour that this article describes and recommends is not laziness, but diligence. Diligent people are careful, persistent and industrious. Lazy people are idle and negligent. To say that engineers should be lazy is either to say that they should be idle and negligent, or to redefine 'laziness' as a kind of diligence, which just a pointless muddle. So it is probably better to do away with the 'laziness as a virtue' theme.

Chuck.Hill
User Rank
Rookie
re: Most engineers are lazy…and that's often a good thing
Chuck.Hill   6/3/2012 3:09:22 AM
NO RATINGS
I've always said: Necessity is the mother of all invention. Laziness is the father.

WKetel
User Rank
Rookie
re: Most engineers are lazy…and that's often a good thing
WKetel   6/2/2012 12:40:49 AM
NO RATINGS
I caution people that I am easy to get along with, except that I am sort of intolerant of two things, laziness and stupidity. I define laziness quite a bit differently, rather as an aversion to putting forth any effort to do an assigned task. That is a lot different than wanting to do it efficiently, and not need to redo it. Stupidity is refusing to expend the effort to understand something, which grows out of my definition of laziness. So you can see that we define them a bit differently. So my thinking is that good engineers want to do the job very efficiently, and only do it once, doing it right the first time.

zeeglen
User Rank
Blogger
re: Most engineers are lazy…and that's often a good thing
zeeglen   6/2/2012 12:17:15 AM
NO RATINGS
Back before simulations were readily available and logic design was still done with discrete gates there were two types of designers - those who rushed the schematic and worried about things like timing later; and those who carefully considered prop delays, setup and hold times, fanouts, and choice of the correct family for each function based on speed requirement during the schematic drawing phase. They were much slower completing the schematic, but their designs usually worked first time. The first type invariably spent a long time debugging obvious timing problems, and their designs were always flaky in the field.

Page 1 / 4   >   >>


EE Life
Frankenstein's Fix, Teardowns, Sideshows, Design Contests, Reader Content & More
Max Maxfield

Aging Brass: Cow Poop vs. Horse Doo-Doo
Max Maxfield
41 comments
As you may recall, one of the things I want to do with the brass panels I'm using in my Inamorata Prognostication Engine is to make them look really old. Since everything is being mounted ...

EDN Staff

11 Summer Vacation Spots for Engineers
EDN Staff
18 comments
This collection of places from technology history, museums, and modern marvels is a roadmap for an engineering adventure that will take you around the world. Here are just a few spots ...

Glen Chenier

Engineers Solve Analog/Digital Problem, Invent Creative Expletives
Glen Chenier
11 comments
- An analog engineer and a digital engineer join forces, use their respective skills, and pull a few bunnies out of a hat to troubleshoot a system with which they are completely ...

Larry Desjardin

Engineers Should Study Finance: 5 Reasons Why
Larry Desjardin
45 comments
I'm a big proponent of engineers learning financial basics. Why? Because engineers are making decisions all the time, in multiple ways. Having a good financial understanding guides these ...

Flash Poll
Top Comments of the Week
Like Us on Facebook
EE Times on Twitter
EE Times Twitter Feed

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)