Show how your product solves problems that developers face when implementing their solutions. Describe how the product works in terms of how a developer sees it. At the same time, describe how it works in terms of the business benefit it provides since the developers will probably influence their manager to purchase the product. Perhaps issue an evaluation guide for developers, and one for their managers.
Integration
Show how your product integrates with programming languages, dev tools, and platforms. Focusing on productivity gains, for example, that result from using the product can help developers and their managers make more informed choices - it also gives your product a tangible result (cost savings) that just about anyone can appreciate.
Samples
Provide lots and lots of samples - Samples for really simple things and samples of complete, working systems. A lot of a developers' product's success lies in its samples since the samples can be easily modified and integrated into an application, or in some cases, used as the basis of a new application.
When you replace your 3.5" drive with CF, CD-R(w), or whatever, you give up control of your system. Think about it - you can start up your system today from a floppy with operating systems like DOS, QNX, and Windows. In fact, DOS and QNX can reside on one 3.5" floppy.
When you no longer have a floppy you become subject to whatever restrictions are in place for CF/CD/Whatever media have at the time - and we all know hardware based DRM is on the way. Don't be short-sighted: keep those 3.5" drives spinning!
Slashdot Mirror
Show how your product solves problems that developers face when implementing their solutions. Describe how the product works in terms of how a developer sees it. At the same time, describe how it works in terms of the business benefit it provides since the developers will probably influence their manager to purchase the product. Perhaps issue an evaluation guide for developers, and one for their managers.
IntegrationShow how your product integrates with programming languages, dev tools, and platforms. Focusing on productivity gains, for example, that result from using the product can help developers and their managers make more informed choices - it also gives your product a tangible result (cost savings) that just about anyone can appreciate.
SamplesProvide lots and lots of samples - Samples for really simple things and samples of complete, working systems. A lot of a developers' product's success lies in its samples since the samples can be easily modified and integrated into an application, or in some cases, used as the basis of a new application.
Typical. Maybe non-starving people should be GM to stop eating so much that there's nothing left over for people in rest of the world.
When you replace your 3.5" drive with CF, CD-R(w), or whatever, you give up control of your system. Think about it - you can start up your system today from a floppy with operating systems like DOS, QNX, and Windows. In fact, DOS and QNX can reside on one 3.5" floppy.
When you no longer have a floppy you become subject to whatever restrictions are in place for CF/CD/Whatever media have at the time - and we all know hardware based DRM is on the way. Don't be short-sighted: keep those 3.5" drives spinning!