I find this book relevant and very informative. If you want to master LINQ lingo, just read it.
For broader evaluation see my review on DZone.
P.S. DZone’s IT Book Zone is another great initiative. In short DZone gives you a free copy of a book and expects to receive its review in return. Fair agreement – one can stretch the envelope of IT domains for free, while DZone broadens thier public resources.
Some time ago, DZone has introduced an interesting feature – DZone Refcardz. This is a collection of cheat sheets (111 items by now) on different topics, e.g. programming languages, developer tools and IDEs, development approaches and trends.
Cheat sheets will never replace books, full time trainings or tutorials – they are meant to be short and brief; supply the reader with the basics and summary; simple enough. You won’t learn the subject in details but DZone refcardz are worth giving a try.
I can see several usage models: (i) get a general meaning on a subject new to me (if I like it, then I go for it in details), (ii) refresh something, (iii) get back to it when in need of checking something quickly.
DZone Refcardz homepage: http://refcardz.dzone.com
After several years of working with Java, C#, SQL and web technologies in general, there’s some time to use the other languages. Among others I’ll be writing some C++ code from time to time now.
I used C (and alittle bit of C++) when I was a student but that were all small projects and it was years ago. Now, it’s obvious I need to catch up with C/C++. I happened to get C++: The Complete Reference by Herbert Schildt. The word reference implies there’s probably no point in reading this book from title-page to colophon; there’s a lot of reference data like the standard function library. However, what I really liked about this book is it gives a quick introduction to most important aspects of C/C++ (e.g. pointers, classes, references, overloading, templates), of course with obvious and numerous code examples.
Recommended. It’s worth keeping this book nearby while working with C++.
After a while (busy days…) I’ve got a new book: Beginning SQL Server 2005 Programming by Robert Vieira.
I’m not considering myslef a SQL Server expert but to be honest I was afraid of this beginning word in the title. Yet I’ve been using SQL Server for a couple of years (apart from Java, C#, etc. – so not full time SQL developing). Also I attended a few SQL related courses when I was at the university. So I should have quite solid theoretical and pratctical background. However, as I was not working with SQL Server full time I decided to give that book a bash. You can always stop reading if you don’t like the book
Continue reading ‘Beginning SQL Server 2005 Programming’
For those who work with C# I’d like to recommend a book which is a kind of summary of knowledge on C# 3.0. The book is quite short (and small by the way – yet pocket reference) but it covers lots of details on C# and describes what’s new in C# 3.0. Everything in short and simple, with code snippets.
I read this book as a first step towards TS: Microsoft .NET Framework – Application Development Foundation. Basically, I’ve started wondering if passing this exam is not a good step in my .NET career and this is the entry point.
Anyway this book is not a C# bible, but it can really help as a knowledge reresher.
You may say I’ve been reading a lot recently. And you can be right saying that
I’ve just read Refactoring: Improving the Design of Existing Code by Martin Fowler. I was really looking forward to reading it and I must say it was worth.
Mr Fowler started the book with an example of how to refactor poor code that is hard to read. He showed the refactoring process step by step pointing out the benefits of the changes. Only then did he start with the theory: definitions, why, when, what to refactor, possible problems, etc. What I liked was he admitted the importance of unit testing the changes (short introduction to JUnit), which can confirm they didn’t break existing logic.
But the real core of the book were the chapters that described in details different aspects and areas of refactoring: composing methods, moving features between objects, organizing data, simplyfing conditional expressions, making method calls simpler, dealing with generalization, and big refactoring. Each item was a separate chapter and contained a number of refactoring techniques. All techniques delivered in an easy to read form – motivation, mechanics, examples in UML and code).
I learned a lot and brushed up a lot. Even although some aspects seemed to be obvious and clear I got the naming and fresh look on them.
Another book I recommend reading: Head First Design Patterns.
I need to say I only managed to read it when I tried for the second time. First time I gave up after three or four chapters. Although I believed the provided definitions, examples, code snippets were good, I was fed up with all this Zen talks, interviews with design patterns, and even their chit-chats.
However I decided to give it a try. I finished reading this book yesterday and I need to admit I’m very happy I did it! The book covered the most popular design patterns (e.g. decorator, abstract factory, proxy, observer) and presented them by showing how existing code can be improved by introducing them. It also reminded several object-oriented programming rules (e.g. polymorphism, Law of Demeter), meaning of Gang of Four, and good practises of using design patterns (when usem and when not). Now i need to say event design patterns chit-chats were crutial as they were supposed to repeat and consolidate given study.
Agile Project Management with Scrum by Ken Schwaber is a book I read a couple of months ago. I had never been involved in an agile project and I had been hearing “agile”, “scrum” for some time, and didn’t know what they all were about. Then one of my colleagues lent my that book.
I was really happy to read it because the author not only described mere facts (theory on how agile with scrum works) but also provided a number of life examples – real life problems and how introducing agile aprroach helped to fix them.
I recommend reading this book if you want to be quickly introduced to agile projects that employ scrum.
- Image by Bodum via Flickr
I’m finishing reading a very good book about designing web forms: Web Forms Design by Luke Wroblewski.
Personally I believe it’s a must-read-me book for anyone who is interested in web design, disregarding the fact if they are beginniers or highly experienced geeks. Both can find answers to questions they could ask, compare described examples, see flaws and advantages of existing forms in well known services, and finally choose the solution that fit best the end users.
The book is relatively short but full of suggestions supported with a lot of examples (screen shots). It is dived into several chapters describing individual aspects of web forms, i.e. labels, inputs, actions, help texts, error and success messages.
If you’re about to start playing with AJAX in ASP.NET it’s a good idea to read this book: ASP.NET AJAX In Action by Alessandro Gallo, David Barkol, Rama Krishna Vavilala (see on amazon).
It very well describes basics of AJAX and shows basic and more advanced techniques of applying it in ASP.NET. There are exaplanations of Microsoft Ajax Library, UpdatePanel, ASP.NET AJAX client components, bulding AJAX-enabled controls, and much, much more. All well written and supported with extensive examples.