Breaking News
Engineering Pop Culture!

Can advanced tools actually slow us down?

NO RATINGS
View Comments: Newest First | Oldest First | Threaded View
<<   <   Page 2 / 2
Rod Dalitz
User Rank
Rookie
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
CEO
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
CEO
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
Blogger
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
Rookie
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
August Cartoon Caption Winner!
August Cartoon Caption Winner!
"All the King's horses and all the KIng's men gave up on Humpty, so they handed the problem off to Engineering."
5 comments
Top Comments of the Week
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
Flash Poll
Radio
LATEST ARCHIVED BROADCAST
David Patterson, known for his pioneering research that led to RAID, clusters and more, is part of a team at UC Berkeley that recently made its RISC-V processor architecture an open source hardware offering. We talk with Patterson and one of his colleagues behind the effort about the opportunities they see, what new kinds of designs they hope to enable and what it means for today’s commercial processor giants such as Intel, ARM and Imagination Technologies.