4 ms·
it's very hard for a business process to do with "good enough" code. in many situation either the output is complete and correct or it's of marginal utility. i
by LoSboccacc 6y ago
it's very hard for a business process to do with "good enough" code. in many situation either the output is complete and correct or it's of marginal utility.
it is also geared heavily toward internal software, so it has a very narrow scope, it's not really for startup, it's not really for large enterprise with their it deps, it's not really for jim in accounting with his excel honed trough year of hard work...
it will find a niche for sure, but the harder part of the use case it covers is modeling workflow interdependencies and that complexity doesn't lie in the software
- fragmede 6y agoThe third option is a small army of temps to clean up the data - either incoming or outgoing, in order for the "good enough" code to work acceptably well. Judging from how many of these so-called second-class employees exist in the valley, I'm not convinced that it's actually possible for code to be better than "good enough" - but that doesn't stop me from trying!