|
|
|
|
|
by deviance
1913 days ago
|
|
(OP) I agree with the point you are making. Smaller tools that can be chained together to obtain new functionality is better (in my opinion also) than "bulky" feature-rich tools (which can never be truly feature complete). But! If you look at it from the perspective of someone who is a non-software developer (e.g. scientist, accountant, graphic designer, etc.) who just wants to do a specific task, it makes more sense to have dedicated tools for the job. Even if those tools, under the hood, are a combination of smaller tools, the end user should not be concerned with anything other than his/her field of expertise. With my question I was trying to get some insight into people's (who are not necessarily software devs) workflows and how we can improve those workflows (if we can). The question applies to software development as well: someone who is specialized, say in compilers (broadly speaking), for example, can help the workflow of many who don't have the time / resources to do it themselves. It comes to mind a feature that someone posted above: "List what packages have functions that can get called when I call function X". |
|