Eric Sink has a great article on Tenets of Transparency for ISVs.

You can extend this to individuals in any job role. The more transparent you are, the faster you can get your work done.

Start with a simple exercise, before attending any meeting, send an email documenting your expectations for that meeting. You will be amazed how quickly the discussion moves forward.

Syndicated from Ashvil's Blog

Along with Comega, the MS research folks have come up with Spec#, which is oriented towards developing higher quality software by adding features like non-null types, checked exceptions, method contracts, model-based testing, etc.

The great things about these two research projects are that they extend and build on C#, which increases the chances that it will be usable by real world programmers, to provide actual feedback that can be used to enhance the C# language.

Hopefully, feedback from these projects will give C# 3.0 and 4.0 features that reduce programming time, reduce object-database-xml impedance, enable safer concurrent programming and help writing more secure and higher quality programs.

Syndicated from Ashvil's Blog

One of the reasons projects spin out of control is poor estimation and scheduling of work. There have been tons of material on estimation but scheduling has not got the same coverage.

One of the common pitfalls of scheduling is mapping a project plan estimated numbers to a team member at 40 hours a week. Let’s run though this with an example, John is working on a 6 month project that is assuming that he would be working for 40 hours a week for the next six months. Besides working on this project, John has to attend a regular staff meeting, take care of some production support issues, take part in a virtual team for planning, attend some training and mentor a new employee. Also, John is planning to take three days off around Thanksgiving to spend the week with his ...

One of the points raised by the NIH (Not Invented Here) folks is Reusing software artifacts does not encourage innovation.

The fallacy with the argument is that if there is already a reusable artifact, then by definition your artifact cannot be innovative. You are just reinventing the wheel and trying to claim that your wheel is better than all the others and thus innovative.

IMHO, Software Reuse allows you to focus on innovative ways to solve business problems by taking care of mundane building blocks.

Let’s take an example of Joe, an IT developer/analyst who is assigned to build reports. Joe decides to use ASP.NET and C# to write reports after understanding the requirements. Most of Joe’s time will be spent in writing queries, formatting reports and other low level activities. At some point of time, Management will start wondering why does it take so long to get a simple report and how come the report does not work in Excel. They will wonder where all the money they ar ...

If you have been reading Ashvil.Net or have subscribed to my RSS feed. Please take some time to help me understand why you read my blog by taking this survey, powered by nsurvey.org.

I plan to use this information to help me understand my audience better and fine-tune my articles, blog and presentations to my readers.

Thanks,
Ashvil

Syndicated from Ashvil's Blog

Looks like Som and his team finally heard Developers and .NET 3.0 will ship on XP with Avalon and Indigo support. Linux Desktops must be doing really well for MS seems to feel the pressure to ship Longhorn without WinFS.

This is a good decision for .NET developers as it gives them a wider market for Avalon and Indigo. Now that this decision is made, they can work on the next one.

Syndicated from Ashvil's Blog

Eric Sink has a good article on product pricing strategies on MSDN. It is a must read for anyone in the software business. If you are developer and don’t understand software pricing you will have no idea how commercially viable that widget you are developing is. Pricing is a complex issues and this article covers that all the main points that drive it.

One of the issues I have with the article is his example of setting a price point for a commercial version of Firebird. His argument of pricing it higher is not in line with his company’s pricing of Vault compared to VSS, Perforce, etc. Actually Perforce adopts his model but it’s pricing is out of reach for many developers.

One of the stupidest things to do is to price higher than lower. If you price lower you will lose money but gain customers and market share. You will find that customers want to spend money wi ...

Avik Sengupta has a good introductory article to IKVM, which can be best described as a Java Virtual Machine for the .NET CLR. So if you are creating a .NET application, but want to use that cool new Java library that doesn't yet have a .NET counterpart, here's a solution for you. Conversely, if you are a Java developer who wants to call a .NET library from Java, IKVM is what you need.

This should be very useful for interoperability between the two platforms but I doubt that anyone will use the Java language to write .NET programs or if it will bring the two communities together.

Syndicated from Ashvil's Blog

The Java world has portal standards called WSRP and portlets. Major Java portals seem to support it. It allows you to write a portlet using web services and defines standards for local portal component behavior. It's high time the .NET world adopts some standards in the portal market segment.

For example, if I want to write a component to a .NET portal, I need to choose if I am going to support Sharepoint, Dotnetnuke, Rainbow, etc. I cannot write a portlet that works in multiple .NET portals. This hurts the small ISVs that make money writing portal components as they have to choose which portal to support. It also hurts portal administrators as it limits their choices.

ASP.NET 2.0 supports web parts which could be used as a basis for .NET portlets but the portal vendors work together to build a standard that works. If you are a portal administrator or portal component vendor then you should start pushing your vendors to work together to build a common portlet standard for ASP.NET.

The biggest mistake a product manager can make is not understand the difference between the problem and a solution.

For example, Jill knows that Mark’s birthday is in a few days and she would like to send Birthday wishes. She can send a greeting card, email or call Mark. All these are different solutions to the same problem – Jill needs to convey her wishes to Mark. Understanding this difference is the key to building great solutions. In this example, AT&T competes with Hallmark to win Jill's business.

Before Intuit launched Quicken, the number one way home users did accounting was with a paper and pencil. Intuit realized that they need to compete with the paper and pencil method and not other home finance software vendors. If the home user thought the paper and pencil method was better, they would never adopt Quicken. Using this knowledge, Intuit designed the product with wizards and other UI techniques that made it more effective than the paper and pencil method.

Unf ...