Showing posts with label Book Review/Key Points. Show all posts
Showing posts with label Book Review/Key Points. Show all posts

May 10, 2010

Book review: The Digital Photography Book: The Step-By-Step Secrets for How to Make Your Photos Look Like the Pros’!

The Digital Photography Book: The Step-By-Step Secrets for How to Make Your Photos Look Like the Pros’!

By: Scott Kelby
Publisher: Peachpit Press
Pub. Date: August 23, 2006
Print ISBN-10: 0-321-47404-X
Print ISBN-13: 978-0-321-47404-9
Pages in Print Edition: 240


This is very good book to learn various secretes to take stunning pictures using DSLR. Author has explained various tricks & terminolgies which explains how to use DSLR to shoot photos in various modes & conditions.

Here is some key learning...

Aperture


When possible, shoot at your lens’ sharpest aperture. For most lenses, that is about two full stops smaller than wide open (so the f-stop number you use will go higher by two stops). For example, if you had an f/2.8 lens, the sharpest apertures for that lens would be f/5.6 and f/8 (two full stops down from 2.8). Of course, you can’t always choose these apertures, but if you’re in a situation where you can, then shooting two stops down from wide open will usually give you the sharpest image your lens can deliver. Now, that being said, this isn’t true for all lenses, and if that’s not the case with your lens, you’ll find your lens’ sweet spot (its sharpest aperture) in short order if you keep an eye out for which aperture your sharpest images seem to come from. You can do that by looking at your photos’ EXIF data (the background information on your shots embedded by your digital camera into the photos themselves) in Photoshop by going under Photoshop’s File menu and choosing File Info. Then click on Camera Data 1. It will show the aperture your shot was taken at. If you find most of your sharpest shots are taken with a particular aperture, then you’ve found your sweet spot. However, don’t let this override the most important reason you choose a particular aperture and that is to give you the depth of field you need for a particular shot. But it’s just nice to know which f-stop to choose when your main concern is sharpness, not controlling depth of field.

Reducing Noise

If you’re shooting in very high ISOs, you’ll want to know about a popular Photoshop plug-in for wedding photographers called Noise Ninja (from PictureCode.com). Besides reducing noise, a happy side effect is that it also smoothens skin.

Shooting Panoramas

(1) Shoot your Panoramas on a tripod. If you don’t, you’ll pay.

(2) Shoot vertically (in portrait orientation) rather than horizontally (in landscape orientation). It’ll take more shots to cover the same area, but you’ll have less edge distortion and a better looking panoramas for your extra effort.

(3) Switch your camera’s white balance to Cloudy. If you leave it set to Auto, your white balance may (will) change between segments, which is bad.

(5) Press your shutter button halfway down to set your exposure, then look in your viewfinder and make note of the f-stop and shutter speed. Now switch your camera to manual mode and dial in that f-stop and shutter speed. If you don’t, and you shoot in an auto exposure mode of any kind, your exposure may (will) change for one or more of the segments, and this will drive you insane when working in Photoshop.

(6) Once you focus on the first segment, turn of auto focus for your lens. That way, your camera doesn’t refocus as you shoot the different segments, which would be (will be) very bad.

(7) Before you shoot your first segment, shoot one shot with your finger in front of the lens—that way you’ll know where your pano starts. Do it again after the last shot.

(8) Overlap each segment by 20–25%. That’s right, make sure that about 1/4 of your first shot appears in the second shot. Each segment needs to overlap by at least 20% so Photoshop’s stitching software can match things up. This is very important.

(9) Shoot fairly quickly—especially if clouds are moving behind your landscape. Don’t be lollygagging for two minutes between each shot. Glitter done, or something could change (lighting, clouds, etc.) in your pano, which will really mess things up.

(10) Use a shutter release, or at the very least a self timer, so you don’t have any camera movement as you’re shooting each segment. Nothing’s worse than one segment that is blurry.

Photoshop stitching for panoramas

1. Open Photoshop and then open all the photo segments (so all the photo segments are open at the same time).

2. Go under Photoshop’s File menu, under Automate, and choose Photo merge.

3. In the resulting dialog, from the Use pop-up menu, choose Open Files. Make sure the Attempt to Automatically Arrange Source Images checkbox is turned on, and then click OK.

4. When the main Photo merge dialog appears, it will stitch the photos together into one seamless panorama (well, as long as you followed the rules laid out earlier). If you see a small seam at the top, between two segments, go ahead and click OK any-way—chances are it will be gone when the final image is created. If for some reason it’s not, use the Clone Stamp tool (S) to cover it by pressing-and-holding the Option key (PC: Alt key) and clicking nearby in an area of sky that looks similar to sample that area. Then, choose a soft-edged brush from the Brush Picker and clone (paint) over the little seam to hide it.

Sport

With sports photography, most of the time you’re going to want to stop the action, and to do that you’ll have to switch to shutter priority mode (or manual mode if you’re comfortable with it), and then shoot at a speed of at least 1/640 of a second (or faster) to stop the motion and keep your image sharp. The slowest you can generally get away with is 1/500 of a second, but that’s if y. Go with 1/640 or higher for better results (there are times when you’re going to intentionally want to shoot at slower speeds so you can blur parts of the photo to exaggerate the movement and speed, but for most situations, you’ll want to freeze the motion with a faster shutter speed like we’re using here).

Two lenses:

(1) A wide-angle lens (like a 12–24mm zoom). You’ll need these wide angles to capture full stadium shots, full court shots, close-up group shots, etc.

(2) A 300mm or 400mm telephoto lens (or a 200–400mm zoom). You’ll be better of if you can spring for a VR (Vibration Reduction for Nikon cameras) or an IS (Image Stabilization for Canon cameras) lens, because you’ll be able to hand-hold more shots in the lower lights of indoor events or nighttime events.

Sports – Panning

There are three keys to this technique:

(1) Use a slow shutter speed—ideally, either 1/30 of a second or 1/60 of a second. So, switch to shutter priority mode (using the mode dial on the top of your digital camera) and set the shutter speed accordingly.

(2) Pan right along with your subject—following them with your camera. Believe it or not, it’s the camera’s motion that creates the blurring background, because you’re trying to move (pan) right along with the athlete so they remain sharp while everything around them appears blurred.

(3) Use continuous shooting (burst) mode for your best chance to capture a sharp shot—capturing multiple shots per second really pays of here.

One important thing to remember: Don’t stop panning when the athlete leaves your frame—continue panning for a couple of seconds afterwards to get a smooth release.

Sports – shoot wide open

By shooting wide open, I mean shoot as close to your wide open aperture as possible (so if you have an f/2.8 lens, shoot at f/2.8 or one stop up). This will pay off in two ways:

(1) This will blur the background, creating a more dramatic, dynamic, and uncluttered photo of your subject. Busy backgrounds are a problem when shooting sports, and shooting with a telephoto lens at such a wide open aperture gives you a very shallow depth of field (meaning your subject in the foreground is in focus, while the back-ground is out of focus).

(2) You’ll be able to shoot at faster shutter speeds, which will greatly help when shooting indoors under artificial low-light situations.

Portraits

Lenses –

28–105mm zooms that are ideal for portraits

While Balance Issue-

White balance problems often happen when you shoot indoors under fluorescent, incandescent, or just “them regular ol’ light bulbs.” Of course, you don’t generally find out about them until you open the photos later on your computer and all the shots have either a yellowish, or greenish, or bluish color cast. By default, your camera is set to Auto White Balance, which works pretty well outdoors, but generally doesn’t work worth a darn indoors. The pros use three methods to avoid white balance problems when they shoot:

(1) they go into the camera and choose a preset white balance setting that matches the lighting they’re shooting in (it’s easier than you think—just go to your camera’s white balance section, and choose either Incandescent [for regular indoor lighting] or Fluorescent [for typical of ce lighting]). You can choose preset white balance settings for outdoor shots as well, and you’ll get more realistic colors there too.

(2) They create a custom white balance. Luckily, your camera will do most of the work for you if you just put a neutral gray card (you can find these at any camera store or B&H Photo) about 8 to 10 inches in front of your lens, and zoom in/out so the card fills your frame. Then go to your camera’s custom white balance menu and set it up to measure what it sees to create a custom white balance (it’s easier than it sounds—just take a peek in your camera’s manual). And,

(3) They shoot in RAW format, so they don’t worry about white balance, because they can choose the white balance after the fact, either in Adobe Photoshop’s Camera Raw dialog or in their RAW processing software (if they don’t use Photoshop’s RAW processor). This is just one advantage of shooting in RAW (see Chapter 10 for more on why RAW rocks).

City Night Life

To shoot running lights set the shutter speed at either 1/16, 1/8, or 1/4 of a second

August 20, 2009

Book Review: Web Site Measurement Hacks

cat[1]

Web Site Measurement Hacks
Tips & Tools to Help Optimize Your Online Business
By Eric T. Peterson Publisher: O'Reilly Media Released: August 2005 Pages: 432

This book focuses on various techniques to capture key performance indicators, potential customer actions, gathering crucial marketing & customer data and techniques to analyzing the captured data.

Note that this book doesn't covers anything on web site performance rather measurements in terms of hits, page views, visits etc.

This book is suited for anyone who want to get hold on mining & analyzing traffic to  web sites.

January 15, 2009

Book: 97 Things Every Software Architect Should Know

This book is not with 100 things because it is missing 3 things - details! details !! details !!!

The book title looks very attractive however contents are poor. You also don’t need to read all book, just read contents online & that’s all what you get.

lrg[1]

Contents



1 Don't Put Your Resume Ahead of the Requirements
2 Simplify Essential Complexity; Diminish Accidental Complexity
3 Chances Are, Your Biggest Problem Isn't Technical
4 Communication Is King; Clarity and Leadership, Its Humble Servants
5 Application Architecture Determines Application Performance
6 Seek the Value in Requested Capabilities
7 Stand Up!
8 Everything Will Ultimately Fail
9 You're Negotiating More Often Than You Think
10 Quantify
11 One Line of Working Code Is Worth 500 of Specification
12 There Is No One-Size-Fits-All Solution
13 It's Never Too Early to Think About Performance
14 Architecting Is About Balancing
15 Commit-and-Run Is a Crime
16 There Can Be More Than One
17 Business Drives
18 Simplicity Before Generality, Use Before Reuse
19 Architects Must Be Hands On
20 Continuously Integrate
21 Avoid Scheduling Failures
22 Architectural Tradeoffs
23 Database As a Fortress
24 Use Uncertainty As a Driver
25 Warning: Problems in Mirror May Be Larger Than They Appear
26 Reuse Is About People and Education, Not Just Architecture
27 There Is No 'I' in Architecture
28 Get the 1,000-Foot View
29 Try Before Choosing
30 Understand the Business Domain
31 Programming Is an Act of Design
32 Give Developers Autonomy
33 Time Changes Everything
34 "Software Architect" Has Only Lowercase a's; Deal with It
35 Scope Is the Enemy of Success
36 Value Stewardship Over Showmanship
37 Software Architecture Has Ethical Consequences
38 Skyscrapers Aren't Scalable
39 Heterogeneity Wins
40 It's All About Performance
41 Engineer in the White Spaces
42 Talk the Talk
43 Context Is King
44 Dwarves, Elves, Wizards, and Kings
45 Learn from Architects of Buildings
46 Fight Repetition
47 Welcome to the Real World
48 Don't Control, but Observe
49 Janus the Architect
50 Architects' Focus Is on the Boundaries and Interfaces
51 Empower Developers
52 Record Your Rationale
53 Challenge Assumptions—Especially Your Own
54 Share Your Knowledge and Experiences
55 Pattern Pathology
56 Don't Stretch the Architecture Metaphors
57 Focus on Application Support and Maintenance
58 Prepare to Pick Two
59 Prefer Principles, Axioms, and Analogies to Opinion and Taste
60 Start with a Walking Skeleton
61 It Is All About The Data
62 Make Sure the Simple Stuff Is Simple
63 Before Anything, an Architect Is a Developer
64 The ROI Variable
65 Your System Is Legacy; Design for It
66 If There Is Only One Solution, Get a Second Opinion
67 Understand the Impact of Change
68 You Have to Understand Hardware, Too
69 Shortcuts Now Are Paid Back with Interest Later
70 "Perfect" Is the Enemy of "Good Enough"
71 Avoid "Good Ideas"
72 Great Content Creates Great Systems
73 The Business Versus the Angry Architect
74 Stretch Key Dimensions to See What Breaks
75 If You Design It, You Should Be Able to Code It
76 A Rose by Any Other Name Will End Up As a Cabbage
77 Stable Problems Get High-Quality Solutions
78 It Takes Diligence
79 Take Responsibility for Your Decisions
80 Don't Be Clever
81 Choose Your Weapons Carefully, Relinquish Them Reluctantly
82 Your Customer Is Not Your Customer
83 It Will Never Look Like That
84 Choose Frameworks That Play Well with Others
85 Make a Strong Business Case
86 Control the Data, Not Just the Code
87 Pay Down Your Technical Debt
88 Don't Be a Problem Solver
89 Build Systems to Be Zuhanden
90 Find and Retain Passionate Problem Solvers
91 Software Doesn't Really Exist
92 Learn a New Language
93 You Can't Future-Proof Solutions
94 The User Acceptance Problem
95 The Importance of Consommé
96 For the End User, the Interface Is the System
97 Great Software Is Not Built, It Is Grown

June 02, 2008

High Performance Web Sites (Book Review/Key Points)

High Performance Web Sites: Essential Knowledge for Front-End Engineers by Steve Souders explains how you can optimize the performance of the Ajax, CSS, JavaScript, Flash, and images that you've already built into your site.

This books has total 17 chapters out of which 14 chapters are dedicated for each rule. Each chapter explains importance of rules & how it plays role in web site performance. To explain, author gave real world examples of top 10 websites including Amazon, AOL, MSN, Yahoo & YouTube.

  • Rule 1: Make Fewer HTTP Requests
    Role of images / CSS / inline images.
  • Rule 2: Use a Content Delivery Network
    Only 10–20% of the end user response time is spent downloading the HTML document. The other 80–90% is spent downloading all the components in the page.

    To measure the true impact of switching to a CDN, you need to measure the response times from multiple geographic locations. Services such as Keynote Systems and Gomez are helpful for conducting such tests.

  • Rule 3: Add an Expires Header
  • Rule 4: Gzip Components
  • Rule 5: Put Stylesheets at the Top
    The blank white screen phenomenon is due to browser behavior. Remember that our stylesheet wasn’t even used to render the page—only to affect the DHTML feature for sending email messages. Even when Internet Explorer had all the necessary components, it waited to render them until the unnecessary stylesheet was also downloaded. The location of the stylesheet in the page doesn’t affect download times, but it does affect rendering. David Hyatt has a great explanation of why the browser does this.
  • Rule 6: Put Scripts at the Bottom “How to configure Internet Explorer to have more than two download sessions,” http://support.microsoft.com/?kbid=282402
  • Rule 7: Avoid CSS Expressions
  • Rule 8: Make JavaScript and CSS External
  • Rule 9: Reduce DNS Lookups
  • Rule 10: Minify JavaScript
    Dojo Compressor (renamed ShrinkSafe and moved to http://dojotoolkit.org/docs/shrinksafe) is the one I’ve seen used the most. For the purposes of our comparison, I used these two tools.
  • Rule 11: Avoid Redirects
    Internet Explorer’s DNS cache is controlled by three registry settings: DnsCacheTimeout, KeepAliveTimeout, and ServerInfoTimeOut, which can be created in the following registry key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\InternetSettings\ There are two Microsoft Support articles describing how these settings affect the DNS cache.* These articles report the following default values for these settings:
        • DnsCacheTimeout: 30 minutes • KeepAliveTimeout: 1 minute • ServerInfoTimeOut: 2 minutes
    How Internet Explorer uses the cache for DNS host entries Tenni Theurer, “Performance Research, Part 2: Browser Cache Usage – Exposed!”,
  • Rule 12: Remove Duplicate Scripts
  • Rule 13: Configure ETags
  • Rule 14: Make Ajax Cacheable
  • The most popular tool for minifying JavaScript code is JSMin, developed by Douglas Crockford, a fellow Yahoo!. The JSMin source code is available in C, C#, Java, JavaScript, Perl, PHP, Python, and Ruby. The tool of choice is less clear in the area of JavaScript obfuscation. Dojo Compressor (renamed ShrinkSafe and moved to http://dojotoolkit.org/docs/shrinksafe) is the one I’ve seen used the most.

    YSlow crawls the page’s DOM to find all the components in the page. It uses XMLHttpRequest to find the response time and size of each component, as well as the HTTP response headers. YSlow provides other tools as well, including a summary of the page’s components and an analysis of all the JavaScript in the page using JSLint.

    Optimizing Wikipedia’s 12 PNG images brought the total size from 33K down to 28K, a 15% savings. There are several PNG optimizers available—I used PngOptimizer. Adding a PNG optimization step to their development process would improve Wikipedia’s performance.

    Examples - http://stevesouders.com/hpws/combo-none.php

    December 30, 2007

    Book Review: C# 3.0 Design Patterns, 1st Edition

    cat[1]

    C# 3.0 Design Patterns
    Use the Power of C# 3.0 to Solve Real-World Problems
    By Judith Bishop Publisher: O'Reilly Media Released: December 2007 Pages: 320

    C# 3.0 Design Patterns by Judith Bishop is a good book prefaces on various design patterns. This book may not be a reference book but can be a good text book for anyone who want to learn various patterns using C#.

    This book starts with introductory chapter on patterns, UML & some features in C#. Then the author takes ride to various patterns starting with structural, creational & behavioral. In each chapter author has explained each pattern using simple day-life example (illustration without code), basic coding example & then real-life coding example. This ‘pattern’ helps anyone to understand what is the design pattern & how to use it?

    Occasionally each chapter also highlights important features of C# & significance with pattern.

    In last chapter author discusses future of design pattern.

    Overall I’ll highly recommend this book for anyone who want to learn Design Patterns using C#.

    February 01, 2007

    Book Review: eXtreme .NET: Introducing eXtreme Programming Techniques to .NET Developers

    This book discusses implementing Agile XP practices in .NET world.  The book is useful if you are new XP & want to adopt any associated processes. However this book may not be interesting for you if you organization already adopted Agile processes.

    The book discusses about pair programming, test driven environment, refactoring,automated build processes, ways to solve complex problems & spiking (Spiking is the XP term given to research and experimentation. Spiking provides a way to discover more information about a specific part of the project)

    0321303636[1]

    March 28, 2005

    Inside Microsoft .Net Il Assembler

    This book is divided in following 6 sections mostly about IL language

    1. Quick Start – Discusses sample example
    2. Underlying Structures – structure of managed exe & metadata table
    3. Fundamental components – module/types/fields/methods etc
    4. Inside Execution engine – IL instructions
    5. Special components – events/custom attribs
    6. Interoperation – managed / unmanaged code interoperation

    Overall you cannot expect great from this book. However this book is good for beginners to get familiar with IL.

     


    By: Serge Lidin
    Publisher: Microsoft Press
    Pub. Date: February 6, 2002
    Pages in Print Edition: 496

    December 15, 2004

    Book: Code Complete

    This is good book for anyone who wants to become a professional in software. This book explains life cycle of programming, how to construct a good code & best practices while writing the code. (Update) Examples in this book are written considering C++/Java however common language specifications in C# automatically forces some of the practices mentioned in this book. If you are seasoned professional then it is worth to take a look at this book to crosscheck best practices for constructing the 'complete' code.

    Key points learned:

    • Software's Primary Technical Imperative is managing complexity. This is greatly aided by a design focus on simplicity.
    • Simplicity is achieved in two general ways: minimizing the amount of essential complexity that anyone's brain has to deal with at any one time, and keeping accidental complexity from proliferating needlessly.
    • Design is heuristic. Dogmatic adherence to any single methodology hurts creativity and hurts your programs.
    • Good design is iterative; the more design possibilities you try, the better your final design will be.
    • Information hiding is a particularly valuable concept. Asking "What should I hide?" settles many difficult design issues.
    • Lots of useful, interesting information on design is available outside this book. The perspectives presented here are just the tip of the iceberg.
    • Class interfaces should provide a consistent abstraction. Many problems arise from violating this single principle.
    • A class interface should hide something—a system interface, a design decision, or an implementation detail.
    • Containment is usually preferable to inheritance unless you're modeling an "is a" relationship.
    • Inheritance is a useful tool, but it adds complexity, which is counter to Software's Primary Technical Imperative of managing complexity.
    • Classes are your primary tool for managing complexity. Give their design as much attention as needed to accomplish that objective.