|
First, I'm not sure why the first option got so much votes ("... page explaining product ..."), in this context I don't think it makes much sense.
You see I wouldn't expect that some developer will just randomly stumble upon an overview page of some product and then have to read what the product is all about.
Instead I think it's more likely that he will be searching for a solution to some problem that he has and then find the product, perhaps it will lead him to a page that explain how to solve that exact problem.
Anyway, I think that beside the first option, this pool pretty much shows what I expected. The type of resource that some developer will want will depend on the product, but also on the person.
There are few types of resources and each could be preferred by different developers. It could be goal oriented (some quick sections like "how to" and "getting started"), learning oriented (like "basic and advance tutorials" and "lessons"), information oriented (like "complete reference" and "full documentation"), etc.
So, if you're not sure what kind of developers your product will most likely be targeting, then you'll basically need every type of documentation and each of them will require a distinct style of writing.
|
|
|
|
|
One product I support has a search function to help find stuff. Unfortunately the documentation contained is 4+ years out of date in many cases or completely absent in others. 
"What does this setting control? Hmmm, nope can't find it in the support documents."
"Oh! You offer an API that's great! Wait... why does the documentation you provided not list half of the operations? Plus in the half it does have the parameters described don't match what is the code is requiring I supply."
|
|
|
|
|
So let's say I really need to buy something to solve a specific problem I have.
I want to know how many people are using that product.
More people usually means the product is more mature, there is plenty of support (either official or community) and it has a future.
It sucks to buy a product that in two years no one uses anymore.
Having millions of users isn't a guarantee for a good product (Crystal Reports, Oracle, JavaScript...), but at least you'll find people who can help you with your problems and you have more certainties you don't have to replace it in a few years.
It's probably the #1 metric for a front-end framework and also why frameworks like Bootstrap, Angular, React and Vue are clear "winners" when it comes to adoption.
I'd rather have a bad framework that everybody uses than a beautiful framework that will be obsolete in two years because no one is using it anymore.
|
|
|
|
|
What I DON'T want an infinite scrolling web site with huge fancy graphics.
I DON'T want lifestyle BS ... just the facts Mam.
I DON'T want to rant on and on since it's time for lunch.
|
|
|
|
|
First I want to know wtf is the product and what problems does it solve (if any).
Then I want the whole freaking documentation, correct documentation at that - outdated manuals are worse than no manual at all.
If there are also quick "get started" and "common scenarios" that would be lovely. Knowing which side is the front of the product really helps.
Examples are part of the documentation: to be useful some snippet should be there, and that would be enough. Working examples are just peachy but I could work without.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
I don't know.. is is just me or are the weekly surveys changing from really techie-questions, like technology choice, languages and so on to more generic questions, that could as well be sent out from a marketing survey organization?
This weeks' question is a perfect example for this. If I were a company and I wanted to know what my future-customers like, I would ask a question like this.
|
|
|
|
|
Not everyone here at this site is developer all day long. We have project managers, CEOs, etc. People who run their own business have to do it all, not just head's down coding. Many members here own and run their own company.
If I had to guess, that would be the motivation behind some of these type of surveys.
|
|
|
|
|
Many of us cover different roles in different projects at the same time. Consultant life is a roller coaster like that, one moment you're a baboon coder, the next one system architect and the following one an integrator.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Why buy yours?
Why buy it at all?
Glittering generalities won't hack it - I need real reasons. Often enough, there are none, unless a shiny new package ("the latest") is somehow life-validating.
And I'm concerned with durability.
Amazingly like any other commodity. Or vis-versa.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
So, when answering the question "What's important when reading about a company's (dev related) product or service?"
A: It's recommended by people that I know and trust. That pretty much means people here at CP. I don't trust my coworkers, I know them too well! 
|
|
|
|
|
A fully functional set of Reference Implementations for different use cases.
Shameel,
http://thedeveloperspace.com
|
|
|
|
|
I find them useless if not damaging, as I do not engage in copy-paste developement unless all other roads fail, changing product is impossible and deadlines are looming.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
It all depends on the type of service/product you are offering after-all.
If a service has useful example projects with all the source files and documentation, I don't think tutorials are necessary, but if you have a product with a complex UI, tutorials (or even trainings) could be essential.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
