Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
On an earlier job I was sharply criticized for just leaving my desk, at all. I was working in software docs and really had to talk to the developers. My typical process was to try the software on my own, develop a rough outline (the hard part was coming up a 'suggested use.' with so many options, what was the 'intended use'?), and then march the draft to the developer to see what I had missed. This took so much less time than the email flurry. I was at least a factor of four faster than the other writers. But I was accused of "annoying the developers" by trying to do things the right way.
Oh, cancer risk, too? Well I had it (in remission but getting scans and inspections every three months or so). Gotta run to the shop. No more time to write.
The only time I was cheated from was in grade school. The teacher assumed (or rather confused me with) my brother who was not quite so well behaved as I. When the classmate cheated from me, she did a poor job, but she still got a higher grade than I did.
Face it. Life is unfair.
This rigid formatting has worked for me. I have spent a lot of time with R&D and was never showed by the math. I have a lot of simulation experience with FEA as well as chip and circuit design, embedded system compilers, and some real-time testing of mechanical stuff ranging from tires (small) to 17 ton compressor rotors.
More importantly, I learned how to deal with change. I was the first student on campus with an electronic calculator. The acceptance of the technology was instantaneous, the profs just added more problems to the tests. The simple act of "doing more stuff" has followed me during my entire career.
The greatest irony has been my lack of "formal" computer training. I had a single programming class in high school. Yet, my entire career has been computer-based. My computer usage has not been limited to "engineering." I have done a lot writing (trade press) and learned layout work along the way. Doing documentation for a CAD vendor, you learn how to write in a different style and QA just becomes part of the process -- you do want make sure what you write about actually works. Working for FEA vendors, I again learned how to make the stuff work and created simple examples to show the process. (The heavy duty math helps you understand how FEA works). And my coding skills were used in crafting documents with an early flavor of XML.
Learning though a rigid structure has allowed me cope with whatever comes my way.
When a thinking manager was asked how to cure the backlog, he replied, "Triple my trained staff." While he was being truthful, his candor got him moved to job where he could do no harm.
Autosave still has not cured me. I will still CTRL-S every few lines. Even with autosave on CAD I will still do other saves. Still, my paranoia does save me.
Not so long ago, I discovered that several years of engineering files had been vanished. We had paper copies but still that loss was annoying.Turns out that I had made a backup of that file set and it was found in my home cache of "work" disks. I slept better.
So of course my entire career has been spent using computers. I did use BASIC on my first job (HP 9830, dual cassette drives and a whopping 16KB of RAM), doing real-time data acquisition on large centrifugal compressors. I also wrote a resume as a series of PRINT statements in 1976. This resume was handed back to me in 1983 when I went to work at Penton publishing -- separate story. I have done a lot of CAD, structural analysis, software docs (issued 12,000 page of embedded systems compiler docs one year) and webwork. For another doc project, I hand-coded the help as
Yes, BASIC started me on the road to ruination. 40 plus years later and I am still at it.
Rational behavior in software will not necessarily result in rational behavior in driving.