Breaking News
Comments
Newest First | Oldest First | Threaded View
Kevin Neilson
User Rank
Manager
re: Code: The good and the ugly
Kevin Neilson   6/20/2013 3:47:15 AM
NO RATINGS
That is bad, but to be fair, it was hard to write good code in Applesoft: there was not enough RAM to put in many comments; variables were limited to two letters; there were no labels, just line numbers; there was no stack for GOSUBs; and we all used lots of GOTOs. The worst was when you needed to insert a line but you'd run out of line numbers, so you had to GOTO to new code at the end and then GOTO back.

BrainiacV
User Rank
Rookie
re: Code: The good and the ugly
BrainiacV   6/18/2013 4:48:21 PM
NO RATINGS
I used to clean up code that looked like this http://www.rostenbach.com/Programming_horror.gif This sample was from a best selling (at the time) database program for the Apple II.

chanj0
User Rank
CEO
re: Code: The good and the ugly
chanj0   6/17/2013 9:54:48 PM
NO RATINGS
Most developers prepared for interview with sophisticated algorithm such as linked list and binary search tree. They then ill prepared to write simple code such as macro. It is a surprise to me that any developer has difficult time writing simple condition, for loop and while loop although it isn't unheard of. Over the years, I have interviewed and hired developers ill prepared for simple code and fluency in algorithm and developers performed poorly in algorithm but excellent in simple code. Who comes out to perform better in the job? The one who is more cautious of any changes.

EREBUS0
User Rank
Rookie
re: Code: The good and the ugly
EREBUS0   6/17/2013 7:32:03 PM
NO RATINGS
I agree, good code is essential, but too often people forget that coding, is just a small part of the software development process. If you understand your requirements, design your code solution and properly test the software, then you can more easily avoid the simple coding mistakes that cause the problems. Knowing how to code does NOT make you a software engineer. It just means you know a small part of the process. Just my opinion.



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

Innovative Technique for Depicting PCBs Using Tiny Figurines
Max Maxfield
12 comments
Following my earlier column on Enhancing Electronic Enterprises With Edison Emanations, I discovered that my chum Alan Winstanley in the UK has a hidden side to him.

EDN Staff

11 Summer Vacation Spots for Engineers
EDN Staff
20 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
15 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
46 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)