Comment by mjr00
1 day ago
Going through this learning process is a critical growth point in every software development career:
1. Software developer is required to do some mundane configuration/setup/data manipulation task at the request of some other internal team
2. Software developer thinks "I'll write an internal tool so the internal team doesn't have to bug me! They can change the configuration/extract the data on their own!"
3. Software developer spends X amount of time building an internal tool (can be quite quickly with AI)
4. Internal tool is released; the internal team looks at it and says, "uh, I don't want to deal with this, I'm just going to keep forwarding requests to the software team."
5. Software developer does the task and realizes it's easier for them to do the mundane configuration/setup/data manipulation with existing tools rather than the internal tool. Internal tool is never used.
These configurations make so much sense when you're writing them. Like on a CLI tool when you pass in a flag, the syntax makes so much sense when you just wrote it.
But a few weeks later when you're trying to use it, you completely forget the syntax and all the little quirks that seemed so genius when you were writing the internal tool.
So you go back to existing tools.