6 ms·
I don't think time to learn bash or programming intuition can reasonably be included in the timeframe to build a product. It's assumed that time starts after yo
by belkarx 4y ago
I don't think time to learn bash or programming intuition can reasonably be included in the timeframe to build a product. It's assumed that time starts after you come up with the idea to do something, and retroactively saying "this project took me a year" for something you created in a few hours is ... odd.
I agree that the time spent to find the libraries and their documentation should be factored in, so I'd like to note that that part of the process took ... 3 ddg searches (so +a few mins).
?where does parcellite store clipboard data -> https://www.mankier.com/1/parcellite https://www.mankier.com/1/parcellite -> `clipboard -c`
?regex for url -> https://gist.github.com/securibee/f15f8c7aaa0593cc32fc30f58540463f https://gist.github.com/securibee/f15f8c7aaa0593cc32fc30f585...
?get notified when something has been copied to clipboard linux -> https://askubuntu.com/questions/1167026/detect-clipboard-copy-paste-event-and-modify-clipboard-contents https://askubuntu.com/questions/1167026/detect-clipboard-cop... -> https://github.com/cdown/clipnotify https://github.com/cdown/clipnotify -> `while clipnotify;do`
:)
- ivanmontillam 4y agoI think we are caught in semantics for this discussion because you are talking about "direct costs" (X causes Y), but I'm defending the idea of "indirect costs" (X doesn't cause Y, but you had it lying around, so you used it). Using your previous knowledge inventory is not a direct cost of resource usage, but you'd not have been able to craft that script if you had not known about the tools.