I've been on break/fix and on the Sales Engineer side and know both - there's never a single side to these things.
I've been on break/fix and on the Sales Engineer side and know both - there's never a single side to these things. Sales Engineers in particular don't want to sell something dishonestly - it opens the company up to risk and it hurts their credibility, particularly if you sell multiple products. There are a few reasons I can think of: 1. The technical people that run the current implementation didn't put their requirements into the sales process. 2. Some of those features really don't matter to the business and were fodder. 3. The requirements were listed, but not accurately or with enough depth. 4. The Sales team didn't have enough knowledge (or training) to know the difference - or inaccurate documentation. 5. It was roadmapped close enough to implementation and including delays to go ahead anyway. 6. The competitor claims to have this feature but theirs is broken also, so it's a race to who can sell broken stuff faster - because nobody can truly do it. The people and the companies that support this exist certainly - just not for very long.
Posted by trout on May 28, 2015, 3:43 AM
Tags
Related issues
- This is my biggest problem with agents, they constantly defensively code for cases that have no chance of happening and in most cases a p...
- I wish there was something like LEAN for biology.
- The issue is really the extreme difficulty of programming them, especially for anything sequential (rather than combinatorial).
- I probably could have beared with it if it was only limited to programming, but it showing up in creative fields has made me feel all sor...
- I hate that I'm in deep enough to know what you mean.
- The biggest problem with “AI” is that big corps are shoving it down our throats.
Raise real-world problems, find people facing the same issue, and discuss solutions.6,500 issues0 comments
reliability (Other)
This is my biggest problem with agents, they constantly defensively code for cases that have no chance of happening and in most cases a p...
I wish there was something like LEAN for biology.
The issue is really the extreme difficulty of programming them, especially for anything sequential (rather than combinatorial).
I probably could have beared with it if it was only limited to programming, but it showing up in creative fields has made me feel all sor...
I hate that I'm in deep enough to know what you mean.
The biggest problem with “AI” is that big corps are shoving it down our throats.
in the middel of a coding session with 5.6 sol.
[Hero Run] 535B-A23B on 18T tokens
I've been on break/fix and on the Sales Engineer side and know both - there's never a single side to these things.
I've been on break/fix and on the Sales Engineer side and know both - there's never a single side to these things. Sales Engineers in particular don't want to sell something dishonestly - it opens the company up to risk and it hurts their credibility, particularly if you sell multiple products. There are a few reasons I can think of: 1. The technical people that run the current implementation didn't put their requirements into the sales process. 2. Some of those features really don't matter to the business and were fodder. 3. The requirements were listed, but not accurately or with enough depth. 4. The Sales team didn't have enough knowledge (or training) to know the difference - or inaccurate documentation. 5. It was roadmapped close enough to implementation and including delays to go ahead anyway. 6. The competitor claims to have this feature but theirs is broken also, so it's a race to who can sell broken stuff faster - because nobody can truly do it. The people and the companies that support this exist certainly - just not for very long.
Comments (0)
No comments yet. Start the discussion.