|
Message Closed
modified 27-Oct-20 14:18pm.
|
|
|
|
|
You may have replied to the wrong message because my post was neither about C nor Kernighan & Ritchie 
|
|
|
|
|
I was going to say Clean Code by Robert C. Martin but Sander beat me to it, so I'm gonna go with Specifying Systems by Leslie Lamport. Not only is it a really interesting book but it's also pretty good for brushing up on discrete mathematics.
|
|
|
|
|
I read Leslie Nielsen because I didn't expect to see any other Leslie on CP.
Had to read it twice 
|
|
|
|
|
Haha, I haven't read anything else by Dr. Lamport but this book was excellent. I feel like this topic (discrete representations of software systems including liveness, safety, and fairness properties) is one of those topics where in 10 years there will be some testing framework that will allow you to verify code against a specification which has itself been mathematically verified for correctness.
There are some companies that have already used this concept for products (CosmosDB) but as far as I'm aware it requires manual verification of code against a spec which is tedious and time-consuming.
|
|
|
|
|
|
I used to have that book. Steve McConnell is great!
Real programmers use butterflies
|
|
|
|
|
Algorithms, by Robert Sedgewick and Kevin Wayne
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries
by Krzysztof Cwalina, Jeremy Barton, Brad Abrams
|
|
|
|
|
Not a programming book, but I have a copy of A+ core hardware on my desk. It's underneath my monitor to raise it's height :P
|
|
|
|
|
Not that I reading it anymore, but have a special place for my copy of PC Intern - System Programming by Michael Tischer...
It is about DOS so mostly irrelevant, but I've learned a lot about how to see things from that book...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
For nostalgia, I still have IBM's Guide to Operations, and Technical Reference, for the PC; which included a source listing of the BIOS, printer codes, memory addresses, etc. Now you just go and buy a chip.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
Yes.
"Clean Code" by Robert C. Martin.
His central point is that most of the time you READ code, so you have to write it in a way that you can read it easily.
And he shows how to do this - and wrote the book in a way that you can read even the book easily.
|
|
|
|
|
C# and the .NET Platform by Andrew Troelsen
jhaga
|
|
|
|
|
'C' Programming, K & R, first edition.
|
|
|
|
|
This was one of the first programming books I ever bought.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
"The C Programming Language" 1st edition 1978 by Brian Kernighan and Dennis Ritchie.
it's absence of restrictions and it's generality.
notable mentions
"Foundations of Python Network Programming" 2004 by John Goerzen
"The Principles of Object-Oriented JavaScript" 2004 by Nicholas C. Zakas
|
|
|
|
|
I'd have to go with Charles Petzold's Windows (C) Programming book.
|
|
|
|
|
Back in the office I have a half dozenish of them. Several are stacked under the non-height adjustable monitor I left there back in march (I liked my spare monitor at home better), and the other half were used to put my laptop screen at a similar height to my monitors (at home I'm using a 6-pack of Coke  ).
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
The C Programming Language by Kernigan and Ritchie
I read this book in mid 80's and it was inspirational to me. At that time I had an Amiga, with Aztec C Compiler and used this book to travel through the mechanics of programming. Very well explained and not too much technical (… sure?). But for me, this book was a trap, because C is in itself a very hard matter to learn well and those guys put it as a if it was like a stroll on a farm and not like climbing the Everest.
The day you do not learn something new, is a wasted day!
|
|
|
|
|
Yes I do:
Méthodes de programmation (2nd ed. Eyrolles 1986)
by Bertrand Meyer (who created the Eiffel programming language and the idea of design by contract), and Claude Baudoin
|
|
|
|
|
I haven't touched it in a few decades but Starting Forth by Leo Brodie. And yes I am old!
|
|
|
|
|
Wow, Forth. There's a blast from the past! Unlike Cobol, I don't usually hear a lot about old software written in Forth. I can't remember the last time I've even heard it. 
Real programmers use butterflies
|
|
|
|
|
At one of the places I worked at I selected Forth (multitasking version I wrote) as an intermediate language. The PC would compile flow charts into Forth text files which would be downloaded to an industrial controller where the Forth interpreter/compile would compile it to machine code. Their system still uses it today.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
