| ▲ | DiscourseFan 3 hours ago |
| I don’t know if that’s true, I made a little web app for displaying the schedule for my team based on our billable hours, and I didn’t do any of the scripting myself but I did have to think a lot about what the app would do and what it would look like and what kind of functionality I wanted, tradeoffs between functionality and specific use cases, etc. It just made the scripting part go faster, that’s all. |
|
| ▲ | Peritract 3 hours ago | parent [-] |
| That's still less thinking overall that someone who thought about all of that and thought about the scripting would have done. |
| |
| ▲ | IanCal 2 hours ago | parent [-] | | And even less than someone who wrote an interpreter for the script, less than someone who also chanted times tables while doing it. More thinking isn’t a simple good thing. Given a limit to how much thought I can give any specific task, adding extra work may mean less where it’s most useful. | | |
| ▲ | Peritract an hour ago | parent [-] | | That's not a good-faith argument; obviously we're talking about relevant thought, rather than distraction (which, in context, would be less thought). | | |
| ▲ | IanCal 41 minutes ago | parent [-] | | It is a good faith argument, my point is exactly that the actual scripting was not part of the relevant thought any more than the interpreter would have been. |
|
|
|