The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I'm still waiting for my copy to arrive.
The preview looks promising. I especially like that chapter called 'acknowledgements'
I've already spotted some IL too, so I'll be sure to read that when my copy arrives!
Thank you and yes got some time so I can do bit extra stuff for my uni work
Good question and what I would like say,
1. You will find bit interesting when read page 2 (Compilation of a C# Program) in where I tried to explain the C# compilation process with the information regarding IL generation , JIT and so on. Compare to other book regard to this I use proper debugging to show how it works? And many more in Chapter 1.
2. I explain parameter passing with some simple example by showing the memory addresses and how it interact and also you would find what happens with the "this" parameter and many more. Compare to other book I think it is more intuitive.
3. I explain the C# Iterator in depth by explaining the underneath State machine which C# compiler generate for the the Iterator block. Compare to other book explanation about the Iterator block is really interesting in here.
.. and many more
14. lastly async and await (C# 5.0) has been explained extensively.
Congratulations on finishing and publishing your book. I only have had time to skimm it so far. Looks like a lot of good information that will enhance my knowledge. I am looking forward to getting into the details an examples.
I would suggest thought be put into an eBook version as well. The online version you have is great, but I prefer the eBook ultimately.
"Courtesy is the product of a mature, disciplined mind ... ridicule is lack of the same - DPM"
In addition to Pete, a blunder that many sites make:
When I put a design into the cart and pay, what do I get? Five Furious Finns redecorating my home? The non-exclusive, limited, non-transferable alienable right to use it as desktop background? A ferret?
Your "This site is running Team Viewer" announcement is kinda truncated/lost (I could only see that it's a team Viewer statement by looking at the page source -- but I don't care if sites run Team Viewer, anyway).
You've obviously spent a lot of time on the technical aspects of the site, but not enough on the content. It's easy to get lost like that, but you've really got to look at the site with the eyes of a user.
Questions the user will ask:
- What is this site for?
- What is is showing me on this page?
- What is on other pages, and why should I go there?
- What should I click?
- Why should I click it?
The first and last sentences of the answer to the first question in your FAQ should not be hidden away in an FAQ that is itself hidden away at the very bottom of the page; it should be at the top of every page.
The same goes for many of the FAQ answers. They should not be questions that people have to ask; you should provide the information to them.
And, a point of order, here, which really annoys me -- you can't have an FAQ if no-one has asked any questions!
The point of an FAQ is to answer questions that have been frequently asked by users; what you have is an unfriendly, hard to use dump for information that you can't be bothered to provide in a user-friendly way.
If a question has not actually been asked by a user, it should not be in an FAQ, because it has not been asked at all, let alone "Frequently".
An FAQ answer is a hotfix, which should be used temporarily, until the site can be amended to include the information properly.
I wanna be a eunuchs developer! Pass me a bread knife!