Robert C. Seacord

The main reasons to use C are because of legacy applications, interface to different programming languages, or start working on an embedded project.
This book works great if you can already program in another language and already started with some C programming for one of the previously mentioned goals. Robert uses very dense language in this book to describe how C works into the very nitty gritty details. I almost felt like reading an IETF RFC standard. I also like that it uses very modern concepts and is up to date with C17. this book does not take you by the hand, it drags you along and you need to keep up with the language. If you can keep up you have a very deep understanding what coding in C entails and you can continue coding with your application, while preventing a lot of pitfalls.

If you just start out coding and want to do that in C for some reason, I would suggest a different book.… (mere)

I'm just over 10% in as of this writing, and I finally started getting to the part where it talks about secure coding techniques. Consequently, I'm not far enough into the book to comment on whether the actual core purpose of the book is well-presented and full of good advice. I can say that it's a little frustrating that the foregoing parts of the book have been the usual "this is why secure coding is important" and "these are examples of things that have blown up in the faces of the whole world" fluff expanded to take up ten percent of the book. I'm also slightly concerned that this author referred to [b:Secure Coding: Principles and Practices|1069723|Secure Coding Principles and Practices|Mark G. Graff|https://i.gr-assets.com/images/S/compressed.photo.goodreads.com/books/1521646329l/1069723._SX50_.jpg|1056398] in positive terms as if it is the best resource for secure software development process, given all the obsolete, broken, and generally ill-advised content in that book (see my review of Secure Coding: Principles And Practices for some details).

If the rest of the book presents good, practical advice for specific secure coding techniques, and stays away from bad advice about process-oriented ideas, it can still be worth four stars, though. I have high hopes, given the book's reputation and its author's pedigree. I'll try to remember to update this review later.… (mere)