Breaking News
Oldest First | Newest First | Threaded View
User Rank
re: Code: The good and the ugly
EREBUS0   6/17/2013 7:32:03 PM
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.

User Rank
re: Code: The good and the ugly
chanj0   6/17/2013 9:54:48 PM
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.

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

Kevin Neilson
User Rank
re: Code: The good and the ugly
Kevin Neilson   6/20/2013 3:47:15 AM
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. Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)

What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.
Like Us on Facebook
Special Video Section
LED lighting is an important feature in today’s and future ...
The LT8602 has two high voltage buck regulators with an ...
The quality and reliability of Mill-Max's two-piece ...
Why the multicopter? It has every thing in it. 58 of ...
Security is important in all parts of the IoT chain, ...
Infineon explains their philosophy and why the multicopter ...
The LTC4282 Hot SwapTM controller allows a board to be ...
This video highlights the Zynq® UltraScale+™ MPSoC, and sho...
Homeowners may soon be able to store the energy generated ...
The LTC®6363 is a low power, low noise, fully differential ...
See the Virtex® UltraScale+™ FPGA with 32.75G backplane ...
Vincent Ching, applications engineer at Avago Technologies, ...
The LT®6375 is a unity-gain difference amplifier which ...
The LTC®4015 is a complete synchronous buck controller/ ...
The LTC®2983 measures a wide variety of temperature sensors ...
The LTC®3886 is a dual PolyPhase DC/DC synchronous ...
The LTC®2348-18 is an 18-bit, low noise 8-channel ...
The LT®3042 is a high performance low dropout linear ...