Название: The Art And Science Of Software Development
Автор: Charles Tatum II
Издательство: Amazon.com Services LLC
Год: 2020
Страниц: 124
Язык: английский
Формат: pdf, rtf, epub
Размер: 10.1 MB

Maybe you've had a passing curiosity about computers, and about software, the apps that run on them. Have you ever wondered what it takes to write software, to "code"? This new book, written by an information technology industry veteran, explains in simple terms what's involved with writing a software application and, should you become more serious about it, certain things you can expect once you find a job.

So, what, then, is the point of this book? I wrote it as a sort of summation of what I’ve seen and experienced from a career spanning over 30 years. It is a sort of “brain dump” of various ideas, notions, concepts, and anecdotes that someone who’s just entering the field of software development might find valuable.

The book is divided in two halves. The first half, “Science”, covers most of the bits and pieces that make up the field of software development or “writing code”. I introduce you to them so that you can get a feel for the kind of moving parts you’ll be dealing with, should you decide to undertake software development for any purpose, professional or casual.

The second half, “Art”, is more of me “holding court” – passing on a sort of wisdom on things I’ve observed over a career of writing software. It is my own perspective, my own experience – I do not expect everyone reading my situations or opinions to nod uniformly in agreement. But, yet, I expect quite a few will.

And really, there is an art to doing software development. Unlike pure mathematics, in which many problems have a single solution (or, occasionally, no solution) with software development solutions are partly a matter of style and creativity. The difference between a good piece of code and a great one may be modularity (how self-contained and reusable some pieces are), efficiency (how a developer chose to code something), or flair (perhaps attacking a technical solution in a manner no one would have imagined). While there are indeed some principles on which the majority of software developers should agree, after that, each tends to make their own path. I know I have.








[related-news] [/related-news]