One of the cool things about being a software developer is there’s always something new to learn. New programming languages, new frameworks, new development methodologies, new techniques.
One of the cool things about being a software developer is there’s always something new to learn. New programming languages, new frameworks, new development methodologies, new techniques.
“Build or buy?”
It’s a common question in business:
How do software development teams make sure the products they release are of high quality?
Not so long ago, a cynical answer to this question would have been something like, “Since when did software development teams care about quality?” It’s unfair, but it’s rooted in perceived quality issues from all types of development teams, from “lone wolf” contract developers to giant software conglomerates.
What’s a computer?
Ask anyone that question, and you’ll probably get variations of, “A machine with a screen and a keyboard and pointing device, used for running various software programs.” This has been the general “high-level” definition since the personal computer became popular in homes and businesses in the early 1980s.
Once upon a time, computer programming was done in “machine language;” the low-level instructions that told the computer’s processor exactly what to do. At a somewhat higher level was assembly language, which hid much of the processor-level instructions but was still painstaking, easy to mess up, and hard to debug. Both levels were also specific to a type of processor; programming a computer with a different manufacturer’s processor meant learning a whole new language.
We’ve been hearing for years now that the future of computing is all about the cloud. Cloud computing, we’re told, will have numerous advantages for enterprises large and small:
