Been really busy with things haven’t got around to posting a book in like a week or so..

But I’ll post one today..

This book...

This book, available for free online or you can buy it, written in 1994. But so under appreciated by people for some reason most people never have seen it or know about it. But this is the ONLY book I know of that actually covers this topic.. the only book in existence that specifically goes thru how OOP can be done with C.

NOW hold up before you say just use C++ stop and think for a second.. bear with me.

First off this book is purely for informational purposes and educational use to deepen your understanding of what OOP is actually doing behind the scenes in languages like C++ where keywords exist for these things and you just blindly use them without thinking about under the hood.

This book contains a lot of code and builds you up a complexly library from scratch to make OOP in C... now I don’t take this book literally and this but I have implemented some concepts from this book in projects in the past, and it helps a lot.

Also in my honest opinion If you finish this book, you will be a better C programmer AND c++ programmer, C programming because it teaches you a lot about complex things that you never thought about doing with the language. It proves you can do polymorphism can do inheritance and encapsulation. And it’s not really bloated either.

This books is an awesome book, if you don’t understand C pointers you definitely will after this book.. if you don’t understand OOP in C++ what’s really going on.. you will after this book. After all C++ began as just a preprocessor of C.

Great book for writing reusable, extendable large scale embedded c systems.

Anyway.. rare book of which should not be rare considering it’s free.

Probably the MOST complete software book on a very broad subject.

This is book to read for those of you are near college grad, first job in the industry. But to the level of detail and broad coverage this book has I think it’s actually a great book for everyone in the industry almost as a “baseline”

From requirements, project planning, workflow paradigms. Software Architecture design, variable naming, refactoring, testing, releasing the book covers everything, not only high level but also in reference to C.

Why C ...because in the consumer electronics, automotive industry, medical electronics and other industries creating physical products c is the language of choice, no changing that. BUT it’s not a C book... it contains C and goes into dept into C but it’s not a C book, C is more like a vehicle for the book, because there are long established, successful industry’s built around it. Plenty of examples.

When I say it’s the most complete on a broad subject seriously like example the chapter about the C language is not a brief over like many other books, for example 10 pages alone are dedicated to just pointer! Many C books have only a few paragraphs on the subject. This goes on depth.

Other topics, recursion, how to write documentation for your code.

Lots of detail and philosophy of the construction of software.

Even if you are a veteran software engineer you could probably learn a thing or two from the book.

It’s not book that you can finish in weekend, unless you can read and comprehend over 1000 pages.

Very few books cover such a broad topic ALL while still going into great detail on those subtopics. the second part is what lacks in most “broad topic books” ..

Code Complete.. is definitely “Complete”

So the image doesn’t match the rest of my book images because I tried to make an amage to cover of the book, inception style kinda haha 😂

Life Hack: don't use alcohol or chemicals, rub off glue residue easily with olive oil / baby oil

Works like a charm and also doesn't break cardboard videogame boxes/ book covers

What's your favourite animal on O'reilly book covers?

If there is 2 books you should read before trying to tackle TAOCP... this might be on it.. as well as the Concrete Mathematics book.

Anyway. This book covers not just the fundamentals of modern algorithms and data structures but it also makes the leap to understanding multithreading and algorithms using multithreading.

Some argue the certain concepts in this book are presented without explanation of how they work, but I guess that should be something the reader try’s to figure out from another book or constructive thinking critically. Keeps the reader on their toes for understanding.

This is also the reason many people suggest the sedgewick algorithm books, of which will be posted another day.

I’m slacking been so busy, forgot to post yet another book..

Soo here ya go..Engineering A Compiler.

For those who don’t like the Red Dragon compiler book for whatever reason, most don’t like it because they don’t believe the dragon book covers topics in a “Teachy way” and doesn’t explain certain things. As well as not cover one topic.

Then this may be the book for you. It’s significantly newer than the “Dragon book” and I believe it does do a better job laying out for “learning”.. I could see this book being used in universities.. I’m sure it is, but mine never had a compiler course so whatever. Good book

Fun fact.. it references the dragon book, as well as the other books the dragon book authors wrote as well as articles in the ACM..AND! It also references Knuths art of computer programming and other books of knuth AND references the Algorithms book. All books I have previously posted.

I have not read this book, only skimmed as I have recently received it this one. May do a follow up or even at it to the list to make a YouTube playlist going chapter by chapter thru the book.

Question - is this meaningful or is this retarded?

if

2*3 = 6
2*2 = 4
2*1 = 2
2*0 = 0
2*-1 = -2

then why doesnt this work?

6/3 = 2
6/2 = 3
6/1 = 6
6/0 = 0
6/-1 = -6

if n/0 is forbidden and 1/n returns the inverse of n, why shouldn't zero be its own inverse?

If we're talking "0" as in an infinitely precise definition of zero, then 1/n (where n is arbitrarily close to 0), then the result is an arbitrarily large answer, close to infinite, because any floating point number beneath zero (like an infinitely precise approximation of zero) when inverted, produces a number equal to or greater than 1.

If the multiplicative identity, 1, covers the entire set of integers, then why shouldn't division by zero be the inverse of the multiplicative identity, excluding the entire set? It ONLY returns 0, while anything n*1 ONLY returns n.
This puts even the multiplicative identity in the set covered by its inverse.

Ergo, division by zero produces either 0 or infinity. When theres an infinity in an formula, it sometimes indicates theres been
some misunderstanding or the system isn't fully understood. The simpler approach here would be to say therefore the answer is
not infinity, but zero. Now 'simpler' doesn't always mean "correct", only more elegant.

But if we represent the result of a division as BOTH an integer and mantissa
component, e.x

1.234567 or 0.1234567,

i.e. a float, we can say the integer component is the quotient, and the mantissa
is the remainder.

Logically it makes sense then that division by zero is equivalent to taking the numerator, and leaving it "undistributed".
I.e. shunting it to the remainder, and leaving the quotient as zero.

If we treat this as equivalent of an inversion, we can effectively represent the quotient from denominators of n/0 as 1/n

Meaning even 1/0 has a representation, it just happens to be 0.000...

Therefore

(n * (n/0)) = 1

the multiplicative identity

because

(n* (n/0)) == (n * ( 1/n ))

People who math. Is this a yea or nay in your book?

Just bought a book that covers some techs that I use, but want to get better at. I get less than a chapter in, and realize something is horribly wrong. I check the publication date. 2015.

I am so fucking stupid.

Rant portion:

Fuck me, there's not a ton of great resources for Lua. I have the book, and it's actually fucking incredible, but as soon as I have a question which I would usually Google, either it's a SO question that almost hits the mark (but absolutely does not answer my initial question) or a mailing list that DOES answer my question but holy FUCK it's difficult to read!

I 100% recommend the Lua book, though. It's remarkably helpful and covers just about every little detail of the language and it's corresponding c API, and even some of how Lua works behind the scenes.

Non-rant portion:

Finished up the first version of my library and now I'm binding it to Lua and this time around I'm using all the best practices including setting and checking metatables so that Lua can't segfault. It's going great, I properly learned about the Lua stack, and I feel good. Cross-platform double-buffered command line via a scripting language... What a way to enter 2020. Everything went so smooth that I got to 3am before I realized what even happened.

NO FUCKING WONDER I SUCKED-ASS IN HIGH SCHOOL ALGEBRA!!!!!

Arghgghhghgh ughhh....

I want to beef up the hell out of my Maths Chops so I can maybe try going back to school for a A.S. in EE or hell even an B.S.

I'm using my company's Safari Learning account for getting free-ish access to college algebra books and I'm self studying.

I'm still in Chapter 0 where the book covers shit you're supposed to know from previous years of education. I'm just learning about some of this shit now!!!

While it's possible that I didn't pay attention in high school lectures, I took geometry in 9th grade and was an A/B+ student and felt confident in maths. I got to Algebra II in High School and suddenly nothing made sense anymore, reality fucking-fell-apart!

Suddenly, I'm failing tests left and right and struggling with the lecture concepts and I could never seem to grasp materials covered in class anymore to even be able to finish the homework assignments.

Fast forward to me being 15 years older and wanting to take a stab at this shit again, but with new found determination to get into EE so I can fuck around with small electronics for pet projects I want to do. I'm starting with College Algebra to try and learn when suddenly, low and behold I have a HUGE FUCK-MOTHERING GAP in my core understanding of the language/syntax/grammar of mathematics.

Been fucking knee-capped for the last decade+ because I either slacked off during those fundamental lectures (which again; is totally plausible) or I had a complete fucking imbecile for a math teacher that glossed over the topics and fucked not only me but the 40+ other kids in that class.

I'm not going to blame the teacher, although I really fucking want to, but I can't remember how the class scored on tests or homework to be able to fairly and objectively make that judgement against the educator.

FUCK!!! I hate my 15 y.o. self right now

Any recommendations for introductory books on electrical engineering? I'm looking for something that goes into detail on the basics: tension, current, resistance, inductance, capacitance, etc. I have very little knowledge on the subject (I know what the basic components do and that's it) and I found myself struggling a bit with the most basic concept: voltage.

I grabbed my multimeter, a few resistors and a battery and played around a bit. For some reason it doesn't really "click" why on a 5v circuit with 3 2.2k ohm resistors (I think) the voltage around each resistor was like ~1.3 volts or something, while on a circuit with 2 resistors the voltage accross each one was ~2.3 something volts (I don't remember exact values). Like, I know that voltage is a difference in potential, but I still don't get it and idk what I'm missing. Why is the difference in potential accross a resistor different if the circuit has 2 resistors in series instead of 3. It kinda makes sense in my head but at the same time it doesn't.

In short, I want to know the "why" stuff works the way it does, not just the "how".

Also, if the book covers common practices, components, and circuits that'd be very helpful. I want to learn how to build well-designed, reliable and safe circuits.