3 ms·
Protip: While we care intensely about "high quality" software, we define it as "well-designed" or "well-abstracted" or "loosely couple" and all kinds of things
by caseysoftware 9y ago
Protip:
While we care intensely about "high quality" software, we define it as "well-designed" or "well-abstracted" or "loosely couple" and all kinds of things that matter when you look at source code, customers care about:
1) does it solve my problem?
2) is it reliable enough? ("enough" depends on use case)
3) can I afford it? (not just cash but maybe TCO)
Edit: And this applies to most of the "hot startups" too. Ask anyone who has been at a major company through the growth years and ask how "good" their software was. Every single one will share horror stories about late nights, tight deadlines, horrible hacks, and "omg let's rewrite this whole thing!" arguments.
As things grow and stability becomes a priority (often customer-driven), things change for the better for the software.
- vdnkh 9y agoCustomers also care about: 4) How quickly can you fix it? 5) How quickly can you deliver this feature?
- rmk 9y agoIn my experience these two asks usually come from the early adopters and savvy customers, who are generally outnumbered by the (newer) customers who just want something that works and fits within a pre-allocated budget category. One notable exception of late has been security fixes. A lot more enterprises have become more aware of the need to patch their systems quickly in response to CVEs etc.