3 ms·
So there is no necessary relation between a task being trivial, and how long it takes. I wish more non-engineers could grasp this. It's so annoying when people
by tdavis 17y ago
So there is no necessary relation between a task being trivial, and how long it takes.
I wish more non-engineers could grasp this. It's so annoying when people say, "It's not done yet? But you said it would be a trivial feature to add!" I am then forced to explain all that means is I know how to add it and can visualize the general diagram in my head, but since I am not regurgitating the precise implementation from memory it isn't merely a matter of rote data entry.
This may be a problem caused partially by us, too; I don't care about implementation time because the implementation is the trivial part; it'll be done whenever it's done and I'm not really bothered by that since the problem itself is already solved. Hell, most of the time I don't even have an interest in fully implementing a solution to a problem I've already mentally solved.
I guess I should note this doesn't apply much for me at the moment seeing as how I co-own a company, but it's an annoyance when it comes to dealing with clients.
- jkkramer 17y agoIf you use a word in a way that most people don't, how can you be surprised when they misunderstand you? I use "straightforward" to describe trivial problems, when I can see the implementation path clearly. "Trivial" implies easy and quick to most people. It's not hard for them to grasp, you just have to communicate more clearly.