REGISTER | LOGIN
Breaking News
Comments
Newest First | Oldest First | Threaded View
<<   <   Page 2 / 2
Rod Dalitz
User Rank
Author
re: Can advanced tools actually slow us down?
Rod Dalitz   5/25/2012 8:46:22 PM
NO RATINGS
I have a motto over my desk: "Why is there never enough time to do a job right, but always enough to do it over?"

WireMan0
User Rank
Author
re: Can advanced tools actually slow us down?
WireMan0   5/25/2012 7:34:33 PM
NO RATINGS
New tools would probably be great if only the documentation kept pace. While trying a new software IDE for a microcontroller a few days ago, I inadvertently closed two windows on the display. I couldn't figure out how to get them back. The docs explained what those windows would show but had no information about how to open them. Sad.

Les_Slater
User Rank
Author
re: Can advanced tools actually slow us down?
Les_Slater   5/24/2012 9:21:16 PM
NO RATINGS
Remember back in those days drawing diagonal line on the edge of a deck of cards so if they were dropped all you had to do was carefully get that diagonal line back.

Duane Benson
User Rank
Author
re: Can advanced tools actually slow us down?
Duane Benson   5/24/2012 3:54:13 PM
NO RATINGS
It's not just the "do it fast/do it over" that causes me to sometimes question all of the "advances." The proliferation of options is also staggering. If you look at all of the library functions available in .NET and other tool chains, you can spend a lot of time just searching to the right library function to use. On the one hand, that frees up a lot of time from wrote tasks, but it also can cause delays. There are so many that you can't keep them in your head so you likely have to research each time you need to use one.

cdhmanning
User Rank
Author
re: Can advanced tools actually slow us down?
cdhmanning   5/24/2012 2:39:40 AM
NO RATINGS
I remember my first year of programming. FORTRAN on punch cards using a mainframe. We submitted our programs as batch jobs and got a print out back hours later. Due to the time involved, you would be very careful about what you submitted, painstakingly checking the code before cutting cards (cards == money) and then checking the cards again before submitting. It was more than once that a 200-line program ran - correctly - first time. Frugality was important too. I wrote a 56-line Fortran program to print out wall calendars. Worked great, but was pretty hard to understand. Now editing and compilation is cheap/free and I don't worry so much about getting it perfect first time. Forgot a variable name? So what just compile and see the errors the compiler throws up. Would I trade back for the Good Old Days? No thank you! I also remember dropping the 2000 punch-card source code for a compiler when I tripped down some stairs. It took quite a while to get them back in order and re-punch damaged cards.

<<   <   Page 2 / 2


Like Us on Facebook
EE Life
Frankenstein's Fix, Teardowns, Sideshows, Design Contests, Reader Content & More
Martin Rowe

Test Tool Finds Ethernet Wiring Errors
Martin Rowe
Post a comment
When my house was renovated several years ago, I had the electrician install network outlets in numerous places, then run the LAN cables to a wiring closet. But he didn't document the ends ...

Martin Rowe

Local Electronics Store Supplies Engineers and Hobbyists
Martin Rowe
5 comments
Rochester, N.Y. — Tucked away in this western New York city known for its optics is Goldcrest Electronics, a local store that's supplied businesses and individuals with electronic ...

Martin Rowe

How to Transform a Technology University (Book Review)
Martin Rowe
1 Comment
The Presiding Genius of the Place by Alison Chisolm. WPI, Worcester, Mass., 234 pp., 2016. Engineers love to discuss, and often criticize, engineering education. They often claim ...

Max Maxfield

Aloha from EEWeb
Max Maxfield
Post a comment
Just a few minutes ago as I pen these words, I posted this blog about this month's Cartoon Punchline Competition over on EEWeb.com.