Friday, February 27, 2004
Communication:
Human Beings are social animals...
We have better ways of communicating between us. But it is always a problem with the software developers to communicate what they feel to their Managers. This article published in the famous Dr. Dobb's Journal was really helpful.
Have a look at this link.
Human Beings are social animals...
We have better ways of communicating between us. But it is always a problem with the software developers to communicate what they feel to their Managers. This article published in the famous Dr. Dobb's Journal was really helpful.
Have a look at this link.
Sunday, February 22, 2004
"The Seven Habits of Highly Effective People", Stephen Covey details out the seven characteristics that a person must have to be highly effective so that he can be successfull in both Personal as well as in his Professional Life.
These are the seven habbits from a view point of a IT person.
1. Be Proactive: Identify and mitigate risks. Involve all the stakeholders in all phases of the projects and get continuous feedback. Take responsibility and deliver on that.
2. Begin with the End in Mind: Be goal driven, Make a vision and try to achieve it.
3. Put First Things First: Do the important work first, the "must have" items, finishing with the least important. It is always better if you have 100% complete of 80% of your requirement rather than having completed only 80% of all the 100% requirements.
4. Think Win / Win: Solve the greatest number of requirements with the least amount of effort possible. Be creative. Try to reuse as much as possible, never reinvent the wheel.
5. Seek First to Understand, Then to be Understood: Do not start thinking about solutions too early on in projects. Understand the business requirements first and then look at solutions. If you want others to listen to you, first you must listen to others.
6. Synergise: Work as an effective team to achieve the maximum possible. The team as a whole is greater than the sum of its parts. In IT Projects you cannot say that you have done your part, you have to ensure that what you have to deliver is delivered properly on proper time which requires team effort.
7. Sharpen the Saw: You have to keep yourself updated with the latest happening in the industry. Try to learn and improve during every project.
These are the seven habbits from a view point of a IT person.
1. Be Proactive: Identify and mitigate risks. Involve all the stakeholders in all phases of the projects and get continuous feedback. Take responsibility and deliver on that.
2. Begin with the End in Mind: Be goal driven, Make a vision and try to achieve it.
3. Put First Things First: Do the important work first, the "must have" items, finishing with the least important. It is always better if you have 100% complete of 80% of your requirement rather than having completed only 80% of all the 100% requirements.
4. Think Win / Win: Solve the greatest number of requirements with the least amount of effort possible. Be creative. Try to reuse as much as possible, never reinvent the wheel.
5. Seek First to Understand, Then to be Understood: Do not start thinking about solutions too early on in projects. Understand the business requirements first and then look at solutions. If you want others to listen to you, first you must listen to others.
6. Synergise: Work as an effective team to achieve the maximum possible. The team as a whole is greater than the sum of its parts. In IT Projects you cannot say that you have done your part, you have to ensure that what you have to deliver is delivered properly on proper time which requires team effort.
7. Sharpen the Saw: You have to keep yourself updated with the latest happening in the industry. Try to learn and improve during every project.
Friday, February 20, 2004
The Four Pillars On Which OO Design Stands...
OCP – Open Closed Principle
Software entities such as classes, modules, functions etc., should be open for extension but closed for modification.
LSP – Liskov Substitution Principle
The base class should be able to substitute where a derived class is expected.
DIP – Dependency Inversion Principle
Abstractions should not depend upon Details but Details should depend upon Abstractions.
ISP – Interface Segregation Principle
Clients should not be forced to depend upon interfaces that they do not use.
OCP – Open Closed Principle
Software entities such as classes, modules, functions etc., should be open for extension but closed for modification.
LSP – Liskov Substitution Principle
The base class should be able to substitute where a derived class is expected.
DIP – Dependency Inversion Principle
Abstractions should not depend upon Details but Details should depend upon Abstractions.
ISP – Interface Segregation Principle
Clients should not be forced to depend upon interfaces that they do not use.
Thursday, February 19, 2004
Project Management - A New Approach...
There are various Software Development Models such as the famous Waterfall, Spiral, Iterative etc., - Lot of Frameworks such as RUP, MSF etc., - Still Failures. This has been a serious thought within me for quite some time and this series of articles that i am going to share with you will help you to manage projects in a better way leading to much more probalility of success.
Be ready for the feast...
There are various Software Development Models such as the famous Waterfall, Spiral, Iterative etc., - Lot of Frameworks such as RUP, MSF etc., - Still Failures. This has been a serious thought within me for quite some time and this series of articles that i am going to share with you will help you to manage projects in a better way leading to much more probalility of success.
Be ready for the feast...
A group of high-tech companies, including Microsoft and Intel, released on Tuesday a Web services specification for discovering devices attached to a local area network
Have a look at this.
Have a look at this.
Tuesday, February 10, 2004
Visio 2003 Software Development Kit (SDK) :
The Microsoft Office Visio 2003 SDK provides developers with tools, samples, and documentation to support custom solution development on the Visio 2003 platform using Microsoft Visual Studio 6.0 and Microsoft Visual Studio .NET 2003 development tools. The SDK is intended for beginning to advanced Visio programmers and Office developers in ISVs, SIs and corporate development environments. This SDK contains the first release of the ShapeStudio shape development environment and sample applications in Microsoft Visual Basic .NET and Microsoft Visual C#.
Download it from here.
The Microsoft Office Visio 2003 SDK provides developers with tools, samples, and documentation to support custom solution development on the Visio 2003 platform using Microsoft Visual Studio 6.0 and Microsoft Visual Studio .NET 2003 development tools. The SDK is intended for beginning to advanced Visio programmers and Office developers in ISVs, SIs and corporate development environments. This SDK contains the first release of the ShapeStudio shape development environment and sample applications in Microsoft Visual Basic .NET and Microsoft Visual C#.
Download it from here.
Sunday, February 08, 2004
Design Patterns : The latest addition to the logical chain in the evolution of OOPS. This presentation is an attempt to explore the GOF (Gang Of Four) Patterns. Please have a look at this for an introduction to the GOF design patterns. During the subsequent week we explore the sea of Design Patterns.
Friday, February 06, 2004
OPENXML is a new feature added to SQL Server 2000. This provides a rowset view over an XML document. Using this feature you can use XML document as a relational database format. It allows for the passing of an XML document to a T-SQL stored procedure for updating the underlying tables.
Have a look at this for more details.
Have a look at this for more details.
Subscribe to Posts [Atom]