Saturday, March 24, 2012
Programming Collective Intelligence by Toby Segaran
Data Warehousing became a buzzword a decade ago.
I picked up some material and started to read.
I was pleasantly surprised .
Everything that was mentioned in the book , I have practiced before.
I were not aware of that it was data warehousing.
Collective Intelligence is not new something new.
Google and Netflix were not pioneers in this area in my opinion.
My Grocery Store, Electronics Store and Barber shop have been doing it for years.
Grocery Store does it by giving a card and providing discount and thus tracking your purchases.
Electronics store and Barber Shop does it by recording my phone number.
Still I am enjoying reading this book and highly recommended brain exercise book for programmers.
Chapter1
Machine Learning is a sub field of AI concerned with algorithms that allow computer to learn
Chapter 2
Making Recommendations.
This chapter shows how to build a system for finding people with same taste and for making automatic recommendations based on things that other people like.
Two systems for calculating similarity scores: Euclidean distance and Pearson corelation.
Euclidean Distance Score
Pearson Correlation Score
Sunday, March 18, 2012
What is new in Visual Studio 11 Beta
1. Build Windows Metro style Apps
2. Visual Studio IDE
-Backward Compatibility
-Better code browsing options
Windows Management
-Access frequently use files more easily
-Preview files in the Code Editor
Search/Search/Search....
JavaScript Code Editor
-IntelliSense
-parameter help
-Signature in statement completion
-Breakpoints
-Script Loader Delay-loaded scripts are now loaded in the development environment, which allows IntelliSense to
- Provide information about the script objects.
- Brace Matching
- Go to Definition
- Drag-and-drop reference
HTML 5 Offline Capablities
HTML 5 Offline
For Web Application to work offline, authors can provide a manifest which lists the files that are needed for the Web application to work offline and which causes the user's browser to keep a copy of the files for use offline.
http://www.w3.org/TR/html5/offline.html
How to create offline HTML5 Web
http://www.catswhocode.com/blog/how-to-create-offline-html5-web-apps-in-5-easy-steps
Windows 8
Rocky makes very interesting point.
Why touch being the important driver to either sell new PCS or a new operating system.
Right now PC users are struck with Second Class Web Applications.
Apps are resurgency of the smart client and distributing computing.
http://www.lhotka.net/weblog/CommentView,guid,bd6898d1-cbc2-4f02-a0f3-3a97486d3168.aspx#commentstart
http://www.lhotka.net/weblog/CareersAtMagenic.aspx
Our industry is in the middle of an exciting and trubulent time. The rise of numerous incompatible client devices and technologies, coupled with major changes in back-end server capabilities around public/private cloud computing , no SQL and big data make for a very unpredictable future.Such trubulence provides great opportunity for future growth.
Saturday, February 18, 2012
Making Your Application Tablet (IPad) friendly
We are working to make our application Tablet friendly.
We found the following issue
1. List Boxes look very ugly on IPAD. We may have redesign certain portions of our application.
2. Download to Excel format is not working for lot of applications.
3. Browser Print functionality is not working.
Stay tuned for more information.
Saturday, January 07, 2012
The myth of Infinite Scalability
Udi Dahan has written a nice post about Scalability.
I agree with him that Infinite Scalability is a myth.
Scalability costs and actives users count is different and dynamic as compared to Total Users Count.
My thoughts are
1. Know You System
Know the bottlenecks and have solutions ready. If you system is not scaling well with increase of active users or requests/per user, you should be able to give solutions to management. I have seen how people’s career has suffered because they could not provide answers to management.
2. Measure, Measure and Measure
Know you system's vital statistics
3. Follow Good practices
Good Practices never hurt. If x number of industry experts are saying that Y is a good practice. Follow Y practice if one don’t time to evaluate it. Hardware Scalability generally costs money where System Refactoring /Re-writing requires more cost and money.
Sunday, December 18, 2011
How do Manager and Programmer run ?
Programmer
runs for x minutes/hours
Manager
Sets a goal(Calories or Distance)
Calculates how to achieve goal in shortest time.
Thursday, November 24, 2011
How does BMW produce Ultimate Driving Machine?
According to Csaba Csere, a former editor of Car and Driver magazine
BMW’s goal is to make the Ultimate Driving Machine. If you work at BMW in any capacity and you’ve got a decision to make, you can sit there and say “ We’re the ultimate driving machine. Which one of these decisions is going to advance that objective”
Referenece:
http://www.msnbc.msn.com/id/43730198/ns/business-cnbc_tv/t/bmw-drives-engineering-perfection/
BMW’s goal is to make the Ultimate Driving Machine. If you work at BMW in any capacity and you’ve got a decision to make, you can sit there and say “ We’re the ultimate driving machine. Which one of these decisions is going to advance that objective”
Referenece:
http://www.msnbc.msn.com/id/43730198/ns/business-cnbc_tv/t/bmw-drives-engineering-perfection/
Friday, November 18, 2011
Difference between Factory Pattern and Abstract Factory Pattern
Factory Pattern : Produces IProduct Implementation
Abstract Factory Pattern: A factory-factory produces IFactories, which in turn produces IProducts.
http://stackoverflow.com/questions/1001767/design-patterns-factory-vs-abstract-factory
Sunday, November 06, 2011
TOGAF: Archtiecture Principles
My Architecture Principles
1. Domain Layer should be independent and lightly coupled to UI and Data Layer
2. Application should be automated tests friendly.
3. Requirement based change
4. Easy Maintenance
5. Configurable
6. Control Diversity
http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap29.html
Architecture principles are a subset of IT principles that relate to architecture work. They relflect a consensus across the enterprise, and embody the spirit and thinking of the enterprise architecture.
Architecture principles can be further divided into :
1. Principles that govern the architecture processes, affecting the development, maintenance and use of enterprise architecture.
2. Principles that govern the implementation of the architecture , establishing the first tenets and related guidance for designing and developing information systems.
Architecture principles are used to capture the fundamental truths about how the enterprise will use and deploy IT resources and assets.
Too many principles can reduce the flexibility of the architecture. Many organizations prefer define only high-level principles , and to limit the number to between 10 and 20.
Business Principles
- Primacy of Principles
- Maximize benefit to the Enterprise
- Information Management is Everybody's Business
- Business Continuity
- Common Use Applications
- Compliance with law
- IT Responsibility
- Protection of Intellectual Property
Data Principles
- Data is an Asset
- Data is shared
- Data is Accessible
- Data Trustee
- Common Vocabulary and Data Definitions
- Data Security
Application Principles
1. Technology Independence
2. Ease of Use
3. Requirement based change
4. Responsive Change Management
5. Control Technical Diversity
6. Interoperability
TOGAF
TOGAF is an architecture framework.
TOGAF 9 can be used for developing a broad range of different enterprise architectures.
The key to TOGAF is the method the TOGAF Architecture Development Method(ADM) - for developing an enterprise archtiecture that addresses business needs.
Architecture in the context of TOGAF
"The fundamental organization of a sytem, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution."
TOGAF embraces and extends this definition .In TOGAF , "architecture" has two meanings depending upon the context
1. A formal description of a system, or a detailed plan of the system at a component level to guide its implementation.
2. The structure of components , their inter-relationships , and the principles and guidelines governing their design and evolution over time.
TOGAF 9 can be used for developing a broad range of different enterprise architectures.
The key to TOGAF is the method the TOGAF Architecture Development Method(ADM) - for developing an enterprise archtiecture that addresses business needs.
Architecture in the context of TOGAF
"The fundamental organization of a sytem, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution."
TOGAF embraces and extends this definition .In TOGAF , "architecture" has two meanings depending upon the context
1. A formal description of a system, or a detailed plan of the system at a component level to guide its implementation.
2. The structure of components , their inter-relationships , and the principles and guidelines governing their design and evolution over time.
Saturday, September 10, 2011
IOC and DI Containers Comparison
The following link gives very good comparison of different IOC and DI Containers overview
http://elegantcode.com/2009/01/07/ioc-libraries-compared/
http://elegantcode.com/2009/01/07/ioc-libraries-compared/
Subscribe to:
Posts (Atom)