3 ms·

This isn't quite true. Enterprise knows what their problems are, and you should listen to them slavishly. The issue comes in when you listen to them for what s

by borski 12y ago

This isn't quite true. Enterprise knows what their problems are, and you should listen to them slavishly. The issue comes in when you listen to them for what solutions to build for their problems. They don't know what the right solution is, but they do know what the right problem is. If they knew what the right solution was, you wouldn't have a (good) business. In finding the solution, you will sometimes address a problem enterprise wasn't even thinking about, but is much larger and solves their initial problem as well. We (https://www.tinfoilsecurity.com https://www.tinfoilsecurity.com) started as a website security scanner - we're now a developer-focused website security scanner that focuses on DevOps integrations and automating the testing process earlier, rather than later. Nobody would have asked us to build that (nobody did), but that is what sets us apart and why we're beating our competitors.

fsloth 12y ago
"Enterprise knows what their problems are, and you should listen to them slavishly. The issue comes in when you listen to them for what solutions to build for their problems." So very much true. In the company I work for this principle applies to inhouse development as well. I.e the problems are obvious but the solutions not so much. We are an independent software vendor, but ownership of code is so scattered that essentially a huge portion of development is handled as if it would be done by external service providers - i.e. the driving force in development is business who know exactly what the pain points are but would want only quick hacks. Except, those pain points are so acute that if there are ready solutions available they will authorize purchases of ridiculous amounts of cash to have them solved. I imagine this is the situation in most businesses. Now, out of those problems some are really hard to crack, while others are just an artifact of lack of inhouse knowledge of the particular technical field. Those consultants that manage to offer viable solutions for these well known problem domains probably can earn their bread quite nicely.

by borski 12y ago

fsloth 12y ago

"Enterprise knows what their problems are, and you should listen to them slavishly. The issue comes in when you listen to them for what solutions to build for their problems." So very much true. In the company I work for this principle applies to inhouse development as well. I.e the problems are obvious but the solutions not so much. We are an independent software vendor, but ownership of code is so scattered that essentially a huge portion of development is handled as if it would be done by external service providers - i.e. the driving force in development is business who know exactly what the pain points are but would want only quick hacks. Except, those pain points are so acute that if there are ready solutions available they will authorize purchases of ridiculous amounts of cash to have them solved. I imagine this is the situation in most businesses. Now, out of those problems some are really hard to crack, while others are just an artifact of lack of inhouse knowledge of the particular technical field. Those consultants that manage to offer viable solutions for these well known problem domains probably can earn their bread quite nicely.