PrimeFaces CookBook

This is the first book as I know about PrimeFaces Framework. As I saw on the web site of PrimeFaces; two new books were added to the PrimeFaces Family. :-)

I bought this book from the following link:
http://www.packtpub.com/primefaces-leading-jsf-component-suite-cookbook/book

The book starts with a very general information about Ajax and an important links for Primefaces. The authors also give their recommendations about forgetting things when preparing xhtml file content and CSS to the reader.

However this book gives you many useful samples for some of the framework's components, all of the components of this framework can be seen on the web site of the PrimeFaces.


I want to list an important web sites for developing web apps with using PrimeFaces.

http://docs.oracle.com/javaee/6/api/javax/faces/component/UIComponent.html

https://github.com/ova2/primefaces-cookbook
http://code.google.com/p/primefaces/wiki/PrimeFacesLocales

I feel that;
If this framework combined and merged with the Ibatis or similiar data mapping framework; ColdFusion developers seem to be familiar with this framework very quickly:-).

My Suggestion to universe :
It is nice to have that Netbeans or Eclipse IDE support(s) component visualization such as Drag-Drop Components to the xhtml file.

101 Design Ingredients to Solve Big Tech Problems

Until the section 5, you read 101 good ingredients and their illustrations. Each of them starts with a quote and I think, after reading each item, check it's drawing.  But I think you couldn't because  Drawings are at the  left side of the page. Unconsciously, I started with checking cartoons for each ingredient.

Mentioned design ingredients not only valid for tech problems. From the education to social sciences, in every area, many recommendations and Author's comments could be very helpful. 

Author(Eewei Chen) has complied with the own rules and keeps this book simple and very helpful. 

My last note not completely related with this book, I want to share:

  I don't understand why  CTRL and FN  keys are interchanged  for some new laptops. 

  There is a confliction with Ingredients 2: Understand customer needs. 

  I think this rule is omitted for the Lxxxxx's laptops. 

The Well-Grounded Java Developer: Vital techniques of Java 7 and polyglot programming

Up-to-date Development and Java 7 enhancements are mentioned  in friendly style by Ben Evans and Martijn Verburg.

Book starts with the Project Coin and it's scope.  The summary sections're (at the end of the each chapter) added very good value to all chapters.  

You could read exhaustive explanations of NIO.2 and DoI.

Topic, as  always, must come to Modern Concurrency: The Synchronized keyword is explained truly and  deeply :). After Java 5, the concurrency in Java was started to be more useful and easy for managing threads. Authors give suggestions for migration from the earlier versions of Java 5.

If you have not any idea about JVM langs, you could start to read about general concepts of Groovy, Scala and Clojure  at the second half of this book.

Summary

When you read this book, you  see and discover most of the stars in the Java and Java- Oriented-Development Galaxy. 

Author's comments in this blog are licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

Java™ Coding Guidelines: 75 Recommendations for Reliable and Secure Programs

If you read  the book (and prepared TODO list) which is in the following link: http://threadsandlocks.blogspot.com/2011/09/cert-oracle-secure-coding-standard-for.html,
you should read this new one.

General Purpose is same, More/Very Secure coding in Java.
CERT Oracle Secure Coding Standard for Java is like a Captain's Logbook.
"Java™ Coding Guidelines: 75 Recommendations for Reliable and Secure Programs" is the second for this category.

It contains very detailed examples about "Secure coding in Java".
75 different and necessary recommendations're detailed with their reasons.

This recommendations are grouped into 5 categories.
1.Security
2.Defensive Programming
3.Program Understandability
4.Reliability
5.Programmer Misconception

References in this book  are very helpfull and every reference like a wind moves you to the new resources for reading/searching them :).

[Book] The Elements of Java™ Style

This book'd been written in 2001.

Some important principles of Java for the Java Application Developers are still same  and items for usage list are, of course,  valid for the given samples in this book.

I see many new beginners on the net and the forums that i followed.

For the accustoming to the java programming language syntax, this book is very very good guide.
I believe in that your code should be understandable for every code reviewer.
Ok, source code is very good documentation but code comments and variable names are important as much as the code bugs and  source code style shows the respect of your program that you write. This my personal opinion :-).

May be this book needs for update to the including new Java features. Maybe it exists.

Java 7 Pocket Guide

If you write any api/plugin like FindBugs;
     This book is very good reference for the checklist.

If you trying to establish coding standards for your team; 

     This book is helpful to preparing considerations such as the naming of variables etc.

If you are very new for java 7, 

       This book helps  to upgrade quickly :-)

[Book] Java Quick Syntax Reference

Beginning to  learn a new programming language and getting accustomed to the language basics take time.

More practice could be good method but if you have less time to do; reading this book could be nice start-up.

For the fundamental java instructors, this book can be helpful to show language basics for syntax explanation if the presentation document is not ready:-).

Link is here:
http://www.apress.com/9781430262862

New books

http://www.amazon.com/Industrial-Deployment-System-Engineering-Methods/dp/3642331696/ref=sr_1_52?s=books&ie=UTF8&qid=1377971550&sr=1-52

http://www.amazon.com/Sencha-Touch-Action-Jesus-Garcia/dp/1617290378/ref=sr_1_31?s=books&ie=UTF8&qid=1377971656&sr=1-31

http://www.amazon.com/Getting-Started-Google-Guava-Bejeck/dp/1783280158/ref=sr_1_52?s=books&ie=UTF8&qid=1377971695&sr=1-52

http://www.amazon.com/TestNG-Beginners-Guide-Varun-Menon/dp/1782166009/ref=sr_1_68?s=books&ie=UTF8&qid=1377971720&sr=1-68

http://www.amazon.com/Extenics-Innovation-Methods-Wen-Cai/dp/1138000493/ref=sr_1_48?s=books&ie=UTF8&qid=1377971536&sr=1-48

http://www.amazon.com/Redis-Action-Josiah-L-Carlson/dp/1617290858/ref=sr_1_8?s=books&ie=UTF8&qid=1377971480&sr=1-8

Book of the month: Dark Side of Software Engineering

I started to read this book.
National Holiday will be  in the next week. So I hope reading this book :).



http://www.amazon.com/Dark-Side-Software-Engineering-Computing/dp/0470597178#_

Alan Turing

Thanks to Princeton University Press two new books are published.

I didnt read yet but in this month i hope so that i will :)

I think that, if you've been learned  and solve problems on the exams about Turing Machine or related with, this book deserves to be read by all of us :-)

http://press.princeton.edu/titles/9780.html

http://press.princeton.edu/titles/9779.html


For Amazon.com's customers :

http://www.amazon.com/s/ref=nb_sb_noss/181-1625451-3000115?url=search-alias%3Ddigital-text&field-keywords=alan+turing+princeton+press

How Google Tests Software

As you dont know, i never suggest a book before reading it  :-)

As i read in this book, Patrick Copeland is a senior director at Google's Engineering Productivity.
Jason Arbon ia a test engineer and Jeff Carollo ia a software engineer at Google.
This book prepared by this crew.

http://www.amazon.com/Google-Tests-Software-James-Whittaker/dp/0321803027/ref=sr_1_6?s=books&ie=UTF8&qid=1335000331&sr=1-6

When you start to read, you couldnt stop reading this book until the last page.
Sometimes you feel reading a periodical paper, sometimes a book :).
Chapters have many different styles from each other.

Test approach, test automation methods of Google are detailed.

They shared  interviews with  Google Colleagues  about their  test methodologies, methods, tools in the software engineering(Q&A style).


You can find the answer the "What  Noogler means?" question :).

According to book:

Quality is not equal to Test and explains the differences and relations between Q&T.
How many different test layers are used by engineers are detailed in this book.

You can learn how "Crawl-->Walk-->Run" is summarized the from canary to release lines.

Some of the clauses that underlined by me as follows:

"All engineers must reuse existing libraries unless they have very good reason not to based on a Project specific need."

"Dependencies must be seriously and especially with common code...."
and importance of readibility is explained in this section.

"Keeping it simple and uniform is a specific goal of the Google Platform."

"Life of Bug" section is interesting. Which Bugs are the heartbeat and workflow for software quality that you learn in the another section.

And what's next?--> i recommend  you reading this book.

Before & After this book:

Visit this Good blog: Sometimes you feel reading a book again when you surf on this blog.

 http://googletesting.blogspot.com/

If it is possible join this conference:

GTAC is the Google Test Automation Conference (http://www.gtac.biz/).

[Book] 97 Things Every Software Architect Should Know

If you are using any software or any program on the internet such as web page visiting like you are doing now, it means that you have any idea about software design and structure unconsciously or intentionally.

This book is firstly for Software Architects, secondly Programmers and lastly the people who are dealing with Software or have any interaction with software programs.

97 different articles, advices are placed in this book. My best one is 'Chapter 75. If You Design It, You Should Be Able to Code It'







The following list is the 97  headlines of this book:

 Don't Put Your Resume Ahead of the Requirements
 Simplify Essential Complexity; Diminish Accidental Complexity
 Chances Are, Your Biggest Problem Isn't Technical
 Communication Is King; Clarity and Leadership, Its Humble Servants
 Application Architecture Determines Application Performance
 Seek the Value in Requested Capabilities
 Stand Up!
 Everything Will Ultimately Fail
 You're Negotiating More Often Than You Think
 Quantify
 One Line of Working Code Is Worth 500 of Specification
 There Is No One-Size-Fits-All Solution
 It's Never Too Early to Think About Performance
 Architecting Is About Balancing
 Commit-and-Run Is a Crime
 There Can Be More Than One
 Business Drives
 Simplicity Before Generality, Use Before Reuse
 Architects Must Be Hands On
 Continuously Integrate
 Avoid Scheduling Failures
 Architectural Tradeoffs
 Database As a Fortress
 Use Uncertainty As a Driver
 Warning: Problems in Mirror May Be Larger Than They Appear
 Reuse Is About People and Education, Not Just Architecture
 There Is No 'I' in Architecture
 Get the 1,000-Foot View
 Try Before Choosing
 Understand the Business Domain
 Programming Is an Act of Design
 Give Developers Autonomy
 Time Changes Everything
 "Software Architect" Has Only Lowercase a's; Deal with It
 Scope Is the Enemy of Success
 Value Stewardship Over Showmanship
 Software Architecture Has Ethical Consequences
 Skyscrapers Aren't Scalable
 Heterogeneity Wins
 It's All About Performance
 Engineer in the White Spaces
 Talk the Talk
 Context Is King
 Dwarves, Elves, Wizards, and Kings
 Learn from Architects of Buildings
 Fight Repetition
 Welcome to the Real World
 Don't Control, but Observe
 Janus the Architect
 Architects' Focus Is on the Boundaries and Interfaces
 Empower Developers
 Record Your Rationale
 Challenge Assumptions—Especially Your Own
 Share Your Knowledge and Experiences
 Pattern Pathology
 Don't Stretch the Architecture Metaphors
 Focus on Application Support and Maintenance
 Prepare to Pick Two
 Prefer Principles, Axioms, and Analogies to Opinion and Taste
 Start with a Walking Skeleton
 It Is All About The Data
 Make Sure the Simple Stuff Is Simple
 Before Anything, an Architect Is a Developer
 The ROI Variable
 Your System Is Legacy; Design for It
 If There Is Only One Solution, Get a Second Opinion
 Understand the Impact of Change
 You Have to Understand Hardware, Too
 Shortcuts Now Are Paid Back with Interest Later
 "Perfect" Is the Enemy of "Good Enough"
 Avoid "Good Ideas"
 Great Content Creates Great Systems
 The Business Versus the Angry Architect
 Stretch Key Dimensions to See What Breaks
 If You Design It, You Should Be Able to Code It
 A Rose by Any Other Name Will End Up As a Cabbage
 Stable Problems Get High-Quality Solutions
 It Takes Diligence
 Take Responsibility for Your Decisions
 Don't Be Clever
 Choose Your Weapons Carefully, Relinquish Them Reluctantly
 Your Customer Is Not Your Customer
 It Will Never Look Like That
 Choose Frameworks That Play Well with Others
 Make a Strong Business Case
 Control the Data, Not Just the Code
 Pay Down Your Technical Debt
 Don't Be a Problem Solver
 Build Systems to Be Zuhanden
 Find and Retain Passionate Problem Solvers
 Software Doesn't Really Exist
 Learn a New Language
 You Can't Future-Proof Solutions
 The User Acceptance Problem
 The Importance of Consommé
 For the End User, the Interface Is the System
 Great Software Is Not Built, It Is Grown

[BOOK] The Sorcerers and Their Apprentices

Full Name of the book is "The Sorcerers and Their Apprentices: How the Digital Magicians of the MIT Media Lab Are Creating the Innovative Technologies That Will Transform Our Lives"
by Frank Moss.

I couldnt read yet.

But i want to share the following book reviews:

http://www.goodreads.com/review/show/242837755
 http://www.goodreads.com/book/show/9093391-the-sorcerers-and-their-apprentices

Java Performance

Very nice book review:

http://www.infoq.com/articles/book-java-performance


very nice book..

Lord of the Files: Essays on the Social Aspects of Software Engineering

I want to announce this book as the book of the month
http://www.amazon.com/Lord-Files-Aspects-Software-Engineering/dp/0986941808/

This is facebook page: http://www.facebook.com/LOTFiles



The contents of the book are following as:

1. I, Programmer
2. The Software Engineer Life Cycle
3. Your Favourite Methodology is eXtremely Gay
4. White Trash Software Engineer
5. What the Bleep Should We Know!?
6. Nobody Ever Got Laid For Buying IBM Equipment
7. All We Really Need To Know about Software Engineering Is in the Film Office Space
8. A Seven-Layer Hierarchy of Careers in Computer Science
9. What's Your Secret Sauce?
10. Pandemonium Reigned

I have to confess that I wanted to read this book because the headlines are very interesting at the very first time.  I ordered and one-and-half month later this book was delivered by Amazon.com, finally I had a chance to read it, thanksfully :).

Every chapter was established on key points of Software Engineering. Author's personal opinions make you smile, sometimes force to think on issues.

In addtion, Author gives a lot of resource books' list at the end of each chapter of the book.

SDLC explanation and illustrations are very thoughtful.

You can see the Sense of humour on the social aspects of software engineering world!
Author has very interesting opinions about why women don't choose programming etc.

When it comes to conclusion, very smart clause waits for you :).

I selected  a page of  this book, for you:)

Page 1: Typical Software Engineer :).

The C Programming Language

This book is the sacred book of the programming for C beginners.

Many programmers translate this book own native languages.

Every main rule are explained with the good samples. Authors are fathers of C.

1978 is the first publishment year of this book.  Popularity of C Language played a big role on changes and inprovements of C.

From variables and expressions of C to the Unix System Interface and Standartd Library, this books gives an information for begginers, students and programmers.


Now everybody who are using unix operating system, it  thanks to Kernighan and Ritchie.


Regards,
Arzu

PC Intern - 2

If you want to programming on any operating system,  it is the correct book for you at the very first time after learning C or C++.

No matter what OS you are working on, this book is very detailed and contains main issues about system programming.

I have to confess that, not completely i read this book. Many chapters  of this book expand my opinion through the software architecture how to do.
May be you are not system programmer, but i insist that this book helps to learn design and main characteristics of flows, jobs on OS.

PC Intern changes what you see on the software program architecture.

Really! :)

[Book] The Clean Coder: A Code of Conduct for Professional Programmers

Have you ever read any  book about software professionalism?

If your response is "no", i want to meet you with book which contains advises to people who work  on software products such testing or programming.

Writer of this book is similiar to this blog :), isnt he?

The CERT Oracle Secure Coding Standard for Java

I really like September because many books will be published.

One of the books I mentioned is "The CERT Oracle Secure Coding Standard for Java"

James Gosling a part of comment for this book as follows:

“In the Java world, security is not viewed as an add-on a feature. It is a pervasive way of thinking. Those who forget to think in a secure mindset end up in trouble. But just because the facilities are there doesn’t mean that security is assured automatically. A set of standard practices has evolved over the years. The Secure® Coding® Standard for Java™ is a compendium of these practices. These are not theoretical research papers or product marketing blurbs. This is all serious, mission-critical, battle-tested, enterprise-scale stuff.”

When it comes to the book:

How could your applications  be more secure. Secure for this book, has the very deepest meaning (as i think).

When i read this book of the every sentence about vulnerability, i derived many todo's.

According to writers:  "Java is a relatively secure language" :).

This book must  be read by java developers  who cares about vulnerability!

Clean Code

Clean Code is by Robert C. Martin and his friends:).

This is the second book that i  smile when reading (this book) :) after Head First Series :).

As I understood, Mr. Martin's Series Style  is always like this. He explains software projects and general systems concept with examples from our life and his life(Chicago sightseeings).

This book helps you to understand difference between good and bad code.
Various code samples are illustrated for each chapter. Also, writers added referenced books for your search.

In my opinion, one of the indispensable factors that make of programming is test driven development(TDD). This book tells importance of TDD with good samples to the readers.

As this book said:

Clean Code is readable and must be robust. Good programs is produced by reworking. You must know your library.

The following remarkable question as i read:

TDD and Refactoring then Clean Code, so what about your system level? Is it complex or simple? (at the chapter 11 ).




Nice site:
http://www.garshol.priv.no/blog/105.html