Great Expectations from Next Generation Search Engines :)

Dear visitor,

When we want to search essays, web sites about image processing for bmp files,

We have to
1. go to any internet browser
2. write the web site which is known as search engine such as Google :)
3. type the keywords in many styles: * bitmap file * process *, etc.
4. read and visit the result links.

I dreamed to in 2020s the search engines will

1. Opened documents on computer recognized and automatically search page and offers will be listed by using any shortkey.
     Do you mean searching topics for Image Processing for Bitmap?
     Do you want to  search essays on image processing?
     ....

2. When you will enter a smart search engine web site,  all opened web sites will be analyzed  and search purpose will be asked to you?

3.  What is yours?



Enjoy :-)

Automation on software programming

Last decade was passed with maturation of programming languages. I think that, Last 5 years of 1990s, one of the biggest  innovation  award belongs to the middle programming language's and of course Java.

When i was learning  C programming language in 12 years ago, i really need automation of C programming language.

Beacuse only Language syntax never adequate for write a program in C. You should know libraries and OS standarts etc.

You have to read PC Intern :) carefully.

If you are a C developer, being a good C programmer, it  takes 2 years at least.

I think it is valid for many languages.

It comes to  common languages such as .Net and Java and maybe C++.

.Net is announced begining of the Y2K. When I meet this language in 2001,  I can say that the tool is wonderful(specially Interfces names)!

And a lot of programs exists and will be exist hopefully!

No  matter what language you choose, automation always be part of you.

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#_

BPEL: Tell me please, where is my garbage value?

Dear visitor,

When you write or update any Bpel flow, would you please check the variables in the flow (have any initial value at least one assignment before it is used).

Otherwise, Show will go on :).

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/).

Pithy Software Engineering Quotes

Thanks to  Larry Bernstein, i learned the following quotes:

“Documentation is a love letter that you write to your future

self.” – Damian Conway

“Programmers are the tools for converting caffeine into code.” –

Unknown

“Theoretically, software is the only component that can be

perfect, and this should always be our starting point.” – Jesse

Poore

“The sooner you start to code, the longer the program will take.”

– Roy Carls

“Give the laziest man the hardest job, he'll find the easiest way of

getting it done.” - Anton Martin Sorenson -

source: http://www.acm.org/ :-)

Secure Mail Please :)

Many of us got  mails as junk and you may open such mails.

I prepared a sample mail transaction for secure communications :).

Thin line between Architecture and design :-)

Grady Booch said
"All architecture is design but not all design is architecture. Architecture represents the significant design decisions that shape a system, where significant is measured by cost of change."

[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 :).

Virtual Developers Day

I really great appriciate to say that the virtual developers day is comingggggg.

For more information you can visit http://www.oracle.com/.


Happy with JAVA!

Eden Space

in other words Heap Memory.

According to forums: The pool from which memory is initially allocated for most objects, as i see a minor garbage collection


As programmer being, when you learn java programming, you start to find details in java.
Eden Space is one of the important spaces for Java. The others are two survivor spaces.
So when you are reading a book about Java Performance, it is the second thing that you learn :) of course it is Eden Space after you learn that what you dont know and what you want to know.

Create your sound with Java

Have you ever known that you can make music by using Java.

it is imposible for many years.

Please check the following links and enjoy !


Nice Api:
http://www.jfugue.org/examples.html



http://docs.oracle.com/javase/tutorial/sound/index.html

PrimeFaces

Most of java web developers are familiar with JSF and JSF based frameworks.

PrimeFaces is two years old.

This project is open source and has many different demos and and their components.

ShowCase and Showcase for Mobile that I looked up.


All of the components and  source codes are reachable(free).

The  important links follow as:

http://www.primefaces.org/

http://wiki.primefaces.org/dashboard.action

XML User Interface Language (XUL)

Yahoooo!

Maybe you know and use XUL...

XUL is one of the Mozilla Projects. It allows you write java script by using xml tags.

If you've a Gecko-based browser you can run the codes which is written by using XUL.

For more information:

https://developer.mozilla.org/En/XUL