Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations cowski on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Large Time-Wasters

Status
Not open for further replies.

rondodude2000

Student
Apr 21, 2021
1
Curious what some of your pain points are, that take time from your actual job. For example, documentation, paperwork, entering data, etc.
 
Replies continue below

Recommended for you

And?

It is a capital mistake to theorise before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts. (Sherlock Holmes - A Scandal in Bohemia.)
 
Wow, harsh responses.

I wouldn't say it is wasted time since I'm not going to spend time on something that doesn't need doing or doesn't have value to me. That being said, there are certainly tedious aspects to any position. Paperwork, entering data, documentation, etc. are part of the actual job. They might not be the flashy exciting parts, but there is a purpose and value to doing them. Some of them take more time than we'd like, but that's part of personal development figuring out how to do them as efficiently as possible.

For instance, the time taken to read and respond here. It isn't helping my job per se, but I find value in taking a few minutes every once in a while to step back from whatever I'm focusing on to look at unrelated things. It helps my thought process and prevents me from constantly thinking in circles if I don't take that step back.

Andrew H.
 
SOME meetings are time wasters; some people cannot efficiently run meetings, so they meander and digress into the weeds.

Everything else is part and parcel to your job; you cannot engineer without data, or documentation of what you are supposed to do and that documenting you completed your tasks and why decisions were made. Engineers are notoriously bad at documentation, resulting in much "wasted" time subsequently, when either that specific engineer or someone else tries to continue on with p!ss-poor documentation. The end result of that is many engineers would rather start from scratch rather than slog through poorly commented code, or designs that don't explain why certain design decisions were made. THAT is a SERIOUS time waster, and likely to result in a second, p!ss-poorly documented project. I've had a contract that completely failed because the engineer decided to start from scratch, dumping a decade of lessons-learned, and not understanding the requirements, resulting in a completely failed design that cost us a possibly lucrative follow-on contract.


TTFN (ta ta for now)
I can do absolutely anything. I'm an expert! faq731-376 forum1529 Entire Forum list
 
Point and click web based training. While I might score 90% or 99%, retention is just about zero.

As others have said, meetings. I've got it down to 2 15 minute planning meetings, and two, hour long, technical meetings a week.

Cheers

Greg Locock


New here? Try reading these, they might help FAQ731-376
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor