Components Books

This is a great book to learn how to build Flex Rich Internet Application. It is easy to read and follow, and it also includes SEO omptimization techniques for higher ranking in SEO results. Highly recommended!

This is a very basic introduction to Flex, and doesn't provide much into how it fits into web design as a whole!

The only problem with this book is that it's not AdvancED as they claim in the title. It's aimed for beginners who never worked on a bigger projects before. The way the authors approached building of RMX application is pretty cool, and newbies will learn something from them. There isn't any depth in the book though, everything they touch upon, and they touch many many things, is pretty shallow. Be it Project Management, Action Script, Flex, MXML, Skinning, SEO, it's all pretty basic. But as I said, I recommend it to anyone who wants to start doing Flex apps professionally.

I have mixed feelings about this book which I got because it was one of the first to cover Flex 3.

I think it is a bit weak on the pure Flex bit - I just can't see someone actually learning Flex out of it, though they will get a pretty good feel for what Flex does. It presents just enough information to explain their application, the RMX, no more. The coding examples are also somewhat hard to follow, with code being all over the place. Yes, it might be real-life production/business code but that doesn't mean that it is automatically great for teaching. Simpler, more illustrative, tighter code would have been better.

On the other hand, the book does a much better job at presenting the big picture of a Flex website and how all the parts fit together, almost at a business/planning level. The wireframe chapters and how to integrate ads are great. Also, though I don't use PHP+Drupal, which they use as a backend, I definitely came away with a confirmation that Flex wasn't tied to particular backend server technologies. If you do use PHP and Drupal, you will get more value out of it for sure.

All in all, a 3.5/5 book.

This book is not all about FLEX it spends time covering the creation of RMX which is not what i wanted at all. The authors are idiots and don't focus mainly on flex. If you want to learn flex puchase something else. If you are interested in their (the authors) project and what they use in their project spend 42.00. WHAT A WAISTE!!

I really liked the book since I had read a copy from my school library hence I decided to purchase one. Unfortunately since Amazon doesn't set any standards that all sellers should meet, my purchase was a rip off.

I order the book assuming it was a North American Copy Unfortunately The one that I received was printed in CHINA & FULL OF GRAMMATICAL MISTAKES please watch out for the seller "Express_Textbook" do not purchase unless u want a Chinese Version.

The seller does not specify this information so once you have made a transaction you'd have to go through the hassle of returning it.

A NOTE TO AMAZON ADMIN: PLEASE INSIST SELLERS WHEN SELLING NEW PRODUCTS TO SPECIFY DETAILS SO THAT CUSTOMERS CAN MAKE THE RIGHT CHOICE.

This book should be used only by the experienced users that can filter out problematic sections.
Major problems:
- first chapter, "recommended" by authors for university courses, is extremely chaotic (begin..end blocks are called loops, exercises ask you to use loops before introducing them, etc.)
- cover of the latest edition claims coverage of the latest Verilog standard - unfortunately it is very poor coverage: new interesting features such as libraries and configurations are not mentioned at all!
- I had to work hard during many trainings to correct bad coding styles showing in students reading this book as their first Verilog publication
- the book is grossly overpriced...

Main advantage:
- good set of examples

The claim that this book has become the standard for learning Verilog is true.
I use Verilog a lot but I still wish I had read this book before writing Verilog codes.

'The Verilog Hardware Description Language' is a very good tutorial and reference for intermediate designers.
I used this book in an upper level hardware design course. The course had a beginning Verilog course as a prerequisite. I hadn't taken that course but I had experience in digital design and VHDL. This book got me up to speed quickly with it's many examples and tight explanations of the Verilog Language.
Some pluses:
-Example designs are short, complete, and simulatable. Most are even synthesizable. This is good because an example can be quickly understood in its entirety. You don't need to flip through and stare and multiple pages to get an idea of what's going on. If you insist on having them, there are two long, practical examples towards the end of the book.
-The text is very well written. Similar in style to 'The C Programming Language by Kernighan and Ritchie.'
-Verilog 2001: Focuses on 2001, which is a little clearer than previous standards. I think all tools support 2001 by default now so that should be used.

Some minuses:
-Too expensive.
-Not enough discussion on how Verilog constructs are compiled and netlisted. This is critically important in FPGA/ASIC design. However, this book is not any worse than other HDL books in this respect. It's just so important, I really haven't seen anything that gives the topic the treatment it deserves.

Possible minus:
-Not really for beginners. This is not a hardware design text.

I haven't used the CD that came with the book so I can't comment on that. My guess is anything on that CD is not as good as industry standard tools like Mentor's ModelSim.
Overall a very impressive book that will get you to productivity quickly in a Verilog project.

Was sharing this book with my workmate. Found it pretty useful. I think its a great reference book to have.
It has
+ A great Index.
+ Good examples.
+ Been written by the masters of Verilog.
- A lot of words (ie some people might find it very 'wordy')

Every ASIC/FPGA designer I know has this one in there shelf. So go for it.

I was a complete, absolute novice knowing nothing at all about PCs. This book is not just about instructions on how to make your own PC. It gives really important history and background information which is absolutely vital and fundamental to any novice trying to get a good grasp of the subject. By the time it came down to actually building my own PC, I had as good a grasp of the subject at this level as the author himself without having read any other book on the subject. It gives you all the information YOU need to be able to make your OWN judgement about what YOU WANT to build. Best of all, the author has written it in such a personal fashion that you will feel he is actually talking to you and you can imagine him working away in his garage - enabling you to see and appreciate things in a crystal clear way. It left me absolutely mesmerised. Every technical book is only valid for as long as the technology mentioned in it is also valid when you read it. Since computer technology moves really, really fast, the reader should consider some information that was current when the book was written to look at it from a historical point of view - this does not negate the validity of the information in any way. The author makes this fact clear by mentioning phrases like "By the time you read this...." followed by his comments about how things might have changed when you are reading the book at your time - and quite often he is spot on about his predictions, which I am sure needed a bit of digging. The flow of his language is wonderful and I feel sorry for those who criticise it because their first language isn't English - mine isn't either. The only matter you should be careful of is when you read about binary numbers but thats really to do with software at a core level - something that really did not concern me at this level. I have now made 2 PCs, connected to a third, made my own network, and studying MCSE to change my career. Congratulations on a book well conceived, thought out, planned, executed and written!!!!!

This book was a major disappointment, but I can only blame myself for this. I looked at the star ranking, but didn't read the reviews. I should have, because it would have helped me much better after reading the reviews. I am somewhat savy, but I was disappointed by this book because it didn't talk to me on a level of what type of product (or brands) would be best for me depending on my budget. For example, besides price, what makes the difference in components I pick? Is it speed? Will they work better? Some products that I buy might not work better if I buy the wrong companion component... this book didn't tell me that.

His writing leaves much to be desired. I should have never strayed from Upgrading and Repairing PC's by Scott Mueller. I just bought ISBN 0789723034 and it's great.

Who does the author think he is giving his 1-star book 5 stars?

As with most of the "build your own" books on the market, this one is pretty out of date. Also, the book supplies you with very little information which would help you select which components will best meet your needs and which components work best together (ie- which motherboards, video graphics boards ...). Basically this book just explains in very breif detail how the system all works together.

The most difficult thing in building your own system IMHO is deciding which components will best meet your needs and will work well together. I did not get any helpful info from this book along these lines. In fact the author does not even seem particularly knowledgeable about the subject matter in the book. I think I could have wrote a better book and I do not even consider myself a computer geek.

Bottom line, I waisted my money...

The book itself is so-so; it has some good information in it, nothing great, and you will certainly need to consult other sources, in print or on the Web, or get help from an expert, before you're able to build a fully functional computer.........

I have grown up with the author's books, on building a PC. Considering that from 386/486 there was not much around. I have still his 486, Pent II, when I get around to it get his Pent III.

I gave my son his earlier works to get started, and with a 2 week "intern" in a PC shop, he is now proudly showing me stuff. Granted his books are for the beginner/intermediate but there is just not many books out there who even attempt this. By the time they get printed, we see the next generation pent IV/giga herz which I hope the author deems to do that as well. Based on his start with some hands on and books like this and starting college he now can understand what is going on. In fact he was looking at Aubrey's Pent II book, so I will put the printout rating for Aubrey's Pent III book out, and hope there will be a similiar book on Pent IIII/AMD gigahertz forthcoming including the new memory, getting harddrives that are now 40-60 gigs.

His pent II book was discussing sub 10 gig drives. Anyway keep up the great work. Perhaps I will get a copy of the pent III and let my sone review it, since he is now overclocking his pent III putting cooling fans everywhere. Carey

I reckon this book is fantastic. I have gotten up to speed with objects in no time. I am writing CF now that has objects doing inheritance and composition and it seems so straightforward. Before this book I was bamboozled. The power of the OO stuff is awesome. I can't imagine now not being able to do things this way.

It's only a small book but that is it's great strength. You don't have to wade through hundreds of pages so learning is quick.

I can't recommend this book highly enough.

The only issue I have had with this book is the super keyword. The book is written for verion 6.0 and shows a way to get around there being no super keyword available. As of version 6.1 there is a super keyowrd so that part of the text is obsolete. Anyway, it's only a few pages and it will still work anyway.

Hard to believe this book had only two authors. A real dissapointment from Hal Helms after reading this Fusebox books.
Save your money and wait for something more concise and focused to come out.

Description

"Discovering CFCs" is a slim book of some 160 pages. Curiously, the paragraphs are numbered. There are some 350 paragraphs in total, plus an appendix chapter. Quite a lot of space is given to diagrams, pictures, and code examples. There is an accompanying workbook in PDF that can be purchased from the publishers techspedition. The authors Hal Helms and Ben Edwards are known to the ColdFusion community as a writer in "ColdFusion Developer's Journal" and as one of the people behind Fusebox.
The book has ten chapters. The first is an introduction and the last a short story. The eight core chapters explain the object-oriented concepts, how to do object-oriented programming with CFCs, and the limitations of CFCs with some workarounds.
The code examples are often first in Java and then in CFC. In comparison to the Java code it becomes obvious how painful it is to program CFCs, because of the markup-language syntax and the limitations of the language. Helms and Edwards provide good discussion of some of those limitations, and provide workarounds for them. Among the limitations they work around are
* no private properties,
* no constructors,
* no super.
They also show how to use custom attributes and the meta-data to make self-documenting code. The book uses basic UML without making a big deal of it.
The last chapter is a fictitious conversation between three programmers about the pros and cons of object-oriented programming. It has a slight entertainment value, but doesn't really add much.
The book is aimed at CF developers who want to use CFCs. That is, they want to learn object orientation and how to do it with ColdFusion Components.

Critique

The book is trying to do three things at once:
1. Teach object-oriented programming.
2. Teach how to program CFCs.
3. Discuss limitations of CFCs and provide workarounds for them.
It would be better to do each of those things separately. A reader new to OO is likely to be confused by being taught an OO concept like super-class, then being shown an example in Java (a language that is besides the point of the book), then being shown the CFC code that takes half a page to do what Java does in three lines, and then the poor reader has to digest the limitations of CFCs and the suggested workarounds.

What will you get out of the book?

* Readers who don't know OO need better examples and less syntax problems of CFC. They should not read this book, but one of the good books about OO using Java as example language.
* Readers who know OO from Java or C++ or Smalltalk will find how to write CFCs. For them the OO stuff is superfluous. The book gives an introduction on how to write CFCs, but it does not cover the whole CFC syntax, so they will need the MX manual anyway. The book shows how to overcome some CFC weaknesses and that is useful.

As concerns style, I personally don't like so many footnotes, especially if they explain important things like the definition of "method signature". Some examples are unrealistic: a cat that knows it can sleep, eat, and play, is a taken as an example of an object with methods.

Do not buy this book, it is so out of date and teaches the wrong way of doing things..

This book is completely worthless. You are better off reading the documentation in ColdFusion about components. The examples are very simplistic and do not help to address why and how to use components in real-world applications.

There are also dozens of mistakes, including spelling, grammar and in the code examples which often make the examples difficult to follow. The numbered paragraphs are useless and seem to serve primarily as a way to increase the number of pages in the book. (If you do not include the code examples, this book probably contains only about 20 pages of writing.)

If you do buy this book, I implore you to skip the "Closing Thoughts" section which is an imaginary conversation between 3 developers that rambles on for 10 pages yet says nothing of value.

I will say the book is aptly titled: it helps you "discover" CFCs, but it does little to make them useful. I am considering sending this book back and asking for a refund. It's that bad.

as the previous reviewer notes.. there are some design pitfalls (like the equations in the front cover).... but these flaws do not effect study at all

very thorough treatment

as for floyd.. i have his Electronics Fundamentals: cccts, devices and appli. book.. and it isn't thorough.. i.e, for transistors biasing.. it only covers Voltage DIvider bias.. and only on the surface...

wat about TSEB, Basebias, the feeback biases.. etc.????

I used this book during my junior in college and was so helpful in my analysis about transistors, how to bias them and the authors explanation about the Small Signal Analysis in AC Amplification. This book is one of the best books books I read about design analysis and design simplification

I had the 5th edition in college and bought the 7th edition for work and it helped me a lot in Transistors circuits design. It is easy to read and it doesn't give you too much theory that is sometimes confusing. Lots of example and even how to interpret Datasheets.

A must have in you library.

The authors' Preface clearly states that "over the years, we have learned that improved readability can be attained through general appearance of the text."

Well what if I tell these authors that their publisher, Prentice Hall, still hasn't achieved their stated and important goal even after 8 editions of this textbook.

They begin by poorly printing all the text's equations in the text jacket cover using horizontal format which is very difficult to read and locate a given equation. They should take a good look at a competing textbook by Floyd.

Floyd does indeed achieve what these two authors intended goal: of making the appearance help the reader want to read the text but have yet to actually achieve it. Floyd also has more technical topics which Boylestad et al clearly have left out in their textbook.

Boylestad is finally being dropped at my college after being criticized for some of the things I just mentioned above. Floyd is now being used.

Students like Floyd's easy format and other easy to follow features.

This book has to be the worst book on electronics ever. I had to use this book for my second course in electronics and it was just too simplistic and not in-depth enough. The examples are very simplistic and the worst part of the book is the problems. The problems are basically identical in difficulty to the examples with the "numbers" changed around. One can not even read the book and solve all the problems by simply flipping back to the examples and copying them. And I haven't even mentioned the ton of errors in the book. Every other formula is wrong and the notion is very poor and ambigous. If you are getting this book to help you in a course, good luck... You better hope your prof. gives excellent lectures and take good notes.

I found this book during my study maybe in library since 2000. This book is very good to introduced me to the filed of radio frequency circuit. I also bought the other 2 books, "Design of Analog CMOS integrated circuits" & " Design of Integrated for Optical communications" of Prof. Behzad from bookstore. But I think some parts are the same. I hope that the recent book " Fundamental of Microelectronics" have some differences from the others book because it has more than 900 pages. I am now prepared to do some research for RF power amplifier but from chapter9 of this book, it has not enough detail for me to do some research. Because recent book of Prof. Behzad is still expensive for me I will wait until the prices drop to less than 100USD

When I first bought this book, I was very hopeful. The book seemed to cover a lot of relevant material, in a concise fashion. When I tried to read it however, I found it a little bit too much on the concise side. I have read very complicated books with a lot of math before, and I could follow them easier than this "easy" writing style. Almost every subject is covered in other books in more detail and better. Sometimes it's nice to have a simpler book which is an introduction, and that is what I was hoping for, but this just didn't do it for me. I donated the book to the library, as I felt I would never really get too much out of it. This didn't stop me from buying Mr. Razavi's "Design of Analog CMOS ICs" and I liked his tutorial in the IEEE Phase Lock Loop book he edited. I know he can do a better job.

This is a repeat of a previous review I did. Since then I also read Mr. Razavi's book "Design of Integrated Circuits for Optical Communications" which was also concise but very nicely explained and I learned a lot from it.

The best thing about this book is its table of contents. In second place is the preface. And then it's all downhill. If you want to buy a list of topics in electronic communications, with brief summaries that explain absolutely nothing whatsover in any great (or even little) detail, and you really have no other use for your hard earned $100.00+ dollars, then please go ahead and buy this book.

If however, you value your cash, and would rather buy a book that rather than insulting your intelligence, at least attempts in good faith to teach you something, then please, don't fall for the marketing ploy of the title "RF Microelectronics". Because there's very little "RF" and even less "Microelctronics" in this text. Here's a taste of the marketing ploy from the very first line of the preface:

"The annual worldwide sales of cellular phones has exceeded $2.5B."

Do I see dollar signs in your eyes? I thought so. Don't fall for the trap. If you want to learn a thing or two about RF electronics theory as well as detailed explanations of what the job of each individual component (like a capacitor here or a resistor there) in a communication circuit is, then buy:

Modern Electronic Communication (9th Edition) by Gary M. Miller.

The Miller book's 9th edition is coming out soon. Even with 992 pages of text, it costs only $60.00.

I believe Razavi's book should never have been published because frankly, it's not a book at all. Why it's still in print (though stuck at first edition for nearly 10 years), is completely beyond any sane person's comprehension.

Although it is a little bit old and there are so many other books on the subject, I still think that it is one of the bests. This book gives you a good basic knowledge of wireless circuits and systems. It's a good reference to look at too. In general, all books by BR are good, he is an incredible writer. His books are always very good to start with when you don't really know anything about the subject. As you get to know the subject more and more, you will know the value of the book and will discover more practical stuff in it. I totally recommend this one and all his books.

This book covers a good deal of material in a very hot area. However, coverage is uneven with occasional mistakes. The book seems to be collected in a hurry some lecture notes. For example, the formula for the relationship between jitter and phase noise given at the beginning of the book is wrong (even units do not make sense) and is not the same for the expression given in the PLL chapter (it makes more sense).

I believe a good book on the field is yet to be written.

I'm dissapointed with the book as it does not give us enough information on holistic aspects of Tube Amp building as it contain too much of unnecessary basic information and pictures. I think it's good for an overview for valve amp building theory but not practical.

For your own good, don't take the advice of people saying that this book is "great for beginners" etc. A background in electronics will help you, but an understanding of general amplifier design, practices and layout is assumed by the author and this book may be over your head at parts otherwise. Also, the author is british, so he'll write something like HT and you may not know that that means high tension which is britspeak for high voltage.

Also, I was hoping to get a solid guide on circuit design as well as amplifier construction and layout, but the circuit design is almost completely absent. Perhaps this is too much to ask for... after all it's "Building Valve Amplifiers" not "Designing Valve Amplifiers." If you want to design and build an amp, this book is only the second half of the solution.

With that said, it is probably one of the best resources once you reach the build phase of your project. The author gives numerous valuable tips to avoid humming, distortion, shocks, and all other negativities that can occur with tube amps.

This book does give hints about proper consruction techniques but it is NOT about building a complete amplifier of any sort. It would be a good book to have on the shelf; it is not the first one to buy.

This guy builds beautiful one-off tube amps. Amazing. The section on suspending the first stages of a tube amp to reduce microphonics using the elastics from you knickers pays for the book, right down to the calculation of the required mass for the circuit. I think everyone who want to build tube circuits will find some wacky techniques of interest.

The book has nothing to do with tube amp theory. It's all about how to make a chassis with the required holes, wiring, grounding, etc.

Lovely.

It is a good book directed to beginners. You will find there many advices on how to plan an amp lay out and hints on metal working.
Don't expect to find there math based circuit analysis for the advanced experimenter.

I wish I had read this book earlier, When most of the books dealt with a lot of theory, this is one book which makes you feel like you handled a real-life project.The sample Programme is very generic and shouldinterest one and all, He delves systematically into the subject. If one were uncomfortable with MIDL, I suggest he/she go thro' this book and come out all the wiser. I have yet to see a book which deals with conversion problems and solutions while converting a client-server model to a web model. A few things I found lacking were examples on threaded apartments and surrogates. But I give it full marks still because the parts covered are given such a nice treatment.

The Component Object Model (COM) was introduced by Microsoft in 1993 to solve several problems. The leading problem was the inability to reuse code because class encapsulation was incomplete. Therefore certain implementation details of methods inside a class could inadvertently become exposed and exploited by some users and not by others. This made changing the implementation problematic. The underlying concept of COM is to make it possible to design and deploy software components much as electronic devices can be built from resistors, capacitors and inductors. You can safely replace a resistor of a certain number of ohms with a like resistor and be absolutely certain the replacement resistor will function identically to the replaced resistor. With components that act like black boxes and perform well defined functions in undocumented ways, you are well on your way to having replaceable software components. Next came the problem of versioning where a component would retain all of its previous functionality yet add some new ones. Users of the old version would not enjoy the benefits of the new version yet would function perfectly with the new version. Users of the new version would function with the old version after deciding the new version was unavailable and degrading their expectations. Versioning is carried out through unique 128-bit integer identifiers called Globally Unique IDs. Then COM goes a bit crazy with concepts like apartments and non-stack, non-heap special memory areas for passing across communications link and special types called variants that must be used in place of familar types. For example, a CString becomes a BSTR in COM. A COM object is instantiated through a special API call which returns a pointer to an interface through which other methods can be located and called. The housekeeping rules include careful reference counting so that unused objects can be removed from memory when the reference count goes to zero. On the whole, COM solves many problems yet is extremely cumbersome. No doubt, many careers have been made becoming expert with COM. Luckily, COM has been functionally replaced with the .NET framework which offers all of the advantages of COM with none of the muss or fuss. COM will be with us for a long time since major products are written using COM to include core business applications at some of the world's largest enterprises. I avoid COM as much as possible because I think it is ugly even though it serves a purpose. I am happy because there is an alternative. So, if you want to learn COM, by all means buy this book. But know that the technology is over a decade old and is slowly on its way out of favor.

The book is out of date. I've found it very interesting

In general, I like the book with its informative sample code. If some one is trying to leran DCOM programming, this book is definitely a good tutorial. Aside from that, I have a few gripes:

(1) There are some errors in its compaion CD-ROM. For example, the MIDL compiler always generate a *.h file which is different from the ones on the CD-ROM.

(2) In Chapter 7, the OrderEntry object hierarchy example lacks a professional RDBMS schema design. The author should have used an ERD (Entity Relationship Diagram) or UML notations to illustrate the corresponding RDBMS schema design.

(3) Since the author works for Microsoft, it seems that the author was rather bias without mentioning any pitsfall of the COM/DCOM model, such as its binary-only proprietariness and the lack of Trader Service as found in the Corba spec, which I think is essential in developing and deploying a true enterprise distributed system.

The book doesn't compare to other DCOM books on the market

Hi,

What's the difference between this book and ISBN# 0130163945 ?
They appear to be the same.

This book is very helpful for anyone interested in troubleshooting electronic circuits. You don't have to go to college to learn electronics because this book has two years worth of college inside. I give this book five stars for it being such a useful book.

beware.. i have an older bersion of this exact same text... and it is all in electron flow... nowhere on the cover did it say it was so...

so most of your currents will be coming out of ground.. and going into the source.. (source as in like +12 line voltage driving a cascade of amplifiers.... and all the grounds at the bottom.. ur currents are coming from the ground.. up to the +12 line voltage... althought this is what electrons do.. in real life.. everyone works with conventional flow)

also.. since this book is a condensed version of two of his other books.. the topics are coverely slightly... i.e... the only BJT transistor biasing technique the author goes into is the VOLTAGE DIVIDER BIAS.. and even that.. he doesn't go into that much...

This book covers all the basics, but it doesn't go deep enough into the theory nor applications...

The problem is, this specific series of books covers 2 books, crunched up in the space of one... usually CIRCUITS is a separate textbook and Electronic Devices is a different textbook ..... but here Floyd squashed it into one book...

He even has separate series of textbooks.. where CIRCUITS and ELECTRONIC DEVICES are separate.... i suggest u buy the two separate ones... instead this condensed package.... those two are really good

I had engineering years ago, but no electronics. I bought the 4th edition of this book and used it for self-study. I think its a very good book. I thought the examples were good and I worked a lot of the problems. I dont't recall many mistakes in the text or the answers. I also thought the section on the oscilloscope was good. I did have to read some of the material over several times to understand it. Chapter 19 Amplifiers and Oscillators was the hardest material to me. There was some material in that chapter that I never could figure out. I learned a lot from this book!

poorly written and organized. the exercises are a terrible. such tedious math. the claim that this book 'teaches you to think like a designer' is a joke. obviously none of these authors have ever been designers.

I liked the math. I think people should learn to recheck things a little more frequently than they do. I think it was organized well enough to follow coursework. I believe it would be useful to others. I recommend the book.

NOTE: However, that I am a beginner, and I can't tell if this would be a good book or not for more advanced individuals.

This text book was a rquirement to a class I'm still taking. So I'm not completely through the text yet. The careful crafting of the chapter's stucture gently leads this student through the tortuous details of modeling the highly non-linear sub-micron mosfet. Particularly useful are the end of chapter summaries that highlight the most critical and useful topics and equations. I do wish there were some problems at the end of the chapter that included answers. When the math gets this convoluted, it's nice to know if you should recheck your work. It would also help to use some standard units. An equation with the mixed length units of 60 *10^-6cm, 42 angstroms and 0.3 nm seems like just a trap for a student.

This book covers the basics well, but does not cover any concept in depth. This book might be good for undergrad class for introduction class, but not a good one for grad level and one interested in advanced topics in VLSI.

The book serves as textbook for students as well as reference for digital circuit designer and EDA developers. Starting from the fundamentals of semiconductor physics and fabrication the reader will step through the key issues of digital IC design in deep submicron technology. The examples support the understanding of the material very well.