Buy Now, Pay Later
As low as
$7.90
/ mo
Learn more
- – 6-month term
- – No impact on credit
- – Instant approval decision
- – Secure and straightforward checkout
Ready to go? Add this product to your cart and select a plan during checkout.
Payment plans are offered through our trusted finance partners Klarna, PayTomorrow, Affirm, Afterpay, Apple Pay, and PayPal. No-credit-needed leasing options through Acima may also be available at checkout.
Learn more about financing & leasing here.
Selected Option
Free shipping on this product
30-day returns
Learn more
This item is eligible for return within 30 days of receipt
To qualify for a full refund, items must be returned in their original, unused condition. If an item is returned in a used, damaged, or materially different state, you may be granted a partial refund.
To initiate a return, please visit our Returns Center.
View our full returns policy here.
Availability:
Only 1 left in stock, order soon!
Arrives
Sunday, Aug 31
Recently Viewed
Format: Paperback
Publisher : Addison-Wesley Professional
Publication date : January 1, 1976
Edition : 1st
Language : English
Print length : 352 pages
ISBN-10 : 020103669X
ISBN-13 : 95
Item Weight : 1.05 pounds
Dimensions : 9.22 x 6.34 x 0.71 inches
Best Sellers Rank: #796,526 in Books (See Top 100 in Books) #812 in Software Development (Books) #2,790 in Business Technology #6,443 in Mathematics (Books)
Frequently asked questions
If you place your order now, the estimated arrival date for this product is:
Sunday, Aug 31
Yes, absolutely! You may return this product for a full refund within 30 days of receiving it.
To initiate a return, please visit our Returns Center.
View our full returns policy here.
To initiate a return, please visit our Returns Center.
View our full returns policy here.
- Klarna Financing
- Affirm Pay in 4
- Affirm Financing
- Afterpay Financing
- PayTomorrow Financing
- Financing through Apple Pay
Learn more about financing & leasing here.
Similar Products
Top Amazon Reviews
Format: Paperback
In a certain way, software engineering is an art. In the past few decades, we have found some best practices. Nowadays there are tons of buzzwords out there -- agile, BDD, TDD, KISS... It's easy to get lost in the jungle of "software engineering methodologies". There is no silver bullet though. Instead of chasing those buzzwords in the hope of finding the best way to write software, my personal experience tells me that we should go back to the root of software engineering: why we are writing software, and what is the relationship between software developer, software, and machine. I think Software Tools answered those fundamental questions elegantly. Or, at least it brought up those questions. This book covers almost every aspect of programming, in the context of writing practical command line tools for UNIX. At that time, FORTRAN was the de facto programming language. There was a big cognitive gap between the programming language at hand (unstructured, messy, low-level), and the programming model in our head (structured, clean, abstract, high-level). To address this problem, the authors proposed to build software "into" the programming language, instead of "in" the programming language. This insight is still valid today, because we still haven't found a programming language that can match the thought pattern of human brain directly. We still have to manually translate our high-level thoughts into low-level program statements. Software engineering about conquering not only the complexity of the outside world (e.g. the inherent complexity of the task that software want to handle), but also the complicity of the programming language itself (e.g. the language itself is not as neat as our thoughts). After all, there is little software engineering concern if the task at hand can be done with a domain-specific language (very high-level usually) in 100 lines. Complexity comes in when we cannot have a language that is high-level enough to match the task at hand, so we need to organize the code to better match the tasks. The idea of programming into language is so old, yet so new. It was first proposed by the generation of early LISP programmers. They would build their own LISP from ground-up, up till the level where they can use the new LISP to solve the problem. The problem is, your language is not LISP. In fact, your language sucks. I am sure that there are good features in every programming language, but you can hardly find all your favorite language features or high-level constructions/libraries in one language. The fact that there is no silver bullet language calls us to patch up, to enhance our language, until it matches the abstraction level of our mental model, or the tasks at hand. Software tools is the book that teaches you how to use your language to build clean and useful blocks and then get things done. It does so by building some of the most useful tools in the UNIX programming environment. Once you followed the idea of building into a language, language will not be your obstacle, and all the best practices are in fact ways to enhance the language (e.g. design patterns). I also enjoy the writing style of this book. There are hands-on examples across the book. There is no checklist/dogma, but examples and tips drawing from those examples. You can get a lot from it if you actually try to build those software tools in C. Anyway, do not miss this classic if you really wants to craft good software. For me, it is the missing manual for me to conquer my stupid programming language. Programming languages are and will always be stupid, and that's why I need to transform them to be MY language. Using this book to guide that transformation today, and you will be more productive when using your language.
...
show more
Reviewed in the United States on November 15, 2008 by Eric Turner
Format: Paperback
While the book is about software written in Fortran IV (technically Ratfor), the concepts are fundamental and predate object oriented programming. I lost my copy and bought a new one, just to remind myself of its great ideas.
Reviewed in the United States on December 6, 2018 by Gregg Marshall
Format: Paperback
Software Tools is an excellent book that shows a programmer (coder, software engineer) how to write good programs to implement useful tools.
Reviewed in the United States on August 9, 2017 by Tom Johnson
Format: Paperback
seems a bit dated to me. Not the most relevant book I've owned. It was a pleasure to read, though.
Reviewed in the United States on October 22, 2010 by AJ
Format: Paperback
This would be considered fairly standard well-known items these days, but in the context of the evolution of software development this book has been a significant mark along that path.
Reviewed in the United States on June 20, 2015 by Patrick S Malloy
Format: Paperback
Not just a programming book, a philosophical outlook on how work should be done. It will change how you think and work.
Reviewed in the United States on January 10, 2016 by MB
Format: Paperback
No matter how old the book is, It still a classic software design guide, notwithstanding
Reviewed in the United States on September 23, 2016 by LIUGANNING
Format: Paperback
fast shipment, good quality. Anyone who is interested in programming should read this.
Reviewed in the United States on May 7, 2015 by kwillia