4 ms·
Customers, in my experience, want to have their cake and eat it too. Nobody wants complex, cumbersome tools, but they do want every iota of flexibility they ca
by Icathian 7y ago
Customers, in my experience, want to have their cake and eat it too.
Nobody wants complex, cumbersome tools, but they do want every iota of flexibility they can imagine delivered in unrealistic timeframes for vanishingly small budgets. Complex, kludgy software is usually the result of customers prioritizing fast and cheap over good, and being given exactly what they asked for.
- orblivion 7y agoIs this for a single client, or consumer software with lots of customers? When I use modern consumer software I feel like I'm dealing with a lot of what somebody else asked for.
- Icathian 7y agoI specialize in building internal analytics tools and apps, so my experiences are mostly with a single client or a small team running a business functional area.
- kevindong 7y ago> Nobody wants complex, cumbersome tools, but they do want every iota of flexibility they can imagine Wanting virtually unlimited flexibility inherently already dooms a project to be complex. That's before talking about timeframes and budgets.
- Icathian 7y agoI agree in general, but I do think there are occasional counter-examples that stand as proof that you can have real flexibility and power without building a mudball. fork/exec, map/reduce, etc. These are foundational for a reason. Mostly though, yeah, you pretty much nailed it.
- enitihas 7y agofork/exec create a huge amount of complexity, and it's possible the NTCreateProcess API is a better API, even with it's tens of arguments. You have to keep n things in your head while doing fork(), like what happens to signals or threads.