because it’s all just temporary, so you throw every new request together in the fastest way you can
I have been finding many use cases for “throwaway” AI coded tools like parser based calculators… the old: “if it takes you a day to write it and it speeds up a week long task by even 20% then it’s a win” thing has had the cost of “writing it” come down by a big factor for simple things - a parser tool thingy that might have taken 4 hours can now be certified good enough for internal use in 40 minutes, and if it’s saving 3 hours of hand work that has turned a “meh, maybe we’ll do this again sometime - I’d rather write the tool than drudge through 3 hours of brain-dead error prone work” into an overall big win.
i will never understand that attitude. four hours of exploration, learning and puzzle-solving sounds like the best part of the job. an isolated, well-specified problem that can be completed in a day is like the most fun you can have programming. why swap that for an hour of code review?
I guess it’s not puzzle solving for me anymore. The puzzle is solved in my head, the four hours of exploration are mostly occupied with looking up annoying details about how to do what’s in my head within the syntax and limitations of the latest re-invention of whatever lanugage has been selected / is available in the environment. Both routes have to be tested, but glancing over provided source code and nodding “yeah, that looks right” then testing the successful implementation is a hell of a lot more satisfying for me than deciphering complier errors, untangling version incompatibilities, looking up function signatures, etc.
Our department is too small to really need an architect, plus there’s a lot of egos running around who want to be an architect, I’m fine with the title Software Engineer.
I have been finding many use cases for “throwaway” AI coded tools like parser based calculators… the old: “if it takes you a day to write it and it speeds up a week long task by even 20% then it’s a win” thing has had the cost of “writing it” come down by a big factor for simple things - a parser tool thingy that might have taken 4 hours can now be certified good enough for internal use in 40 minutes, and if it’s saving 3 hours of hand work that has turned a “meh, maybe we’ll do this again sometime - I’d rather write the tool than drudge through 3 hours of brain-dead error prone work” into an overall big win.
i will never understand that attitude. four hours of exploration, learning and puzzle-solving sounds like the best part of the job. an isolated, well-specified problem that can be completed in a day is like the most fun you can have programming. why swap that for an hour of code review?
I guess it’s not puzzle solving for me anymore. The puzzle is solved in my head, the four hours of exploration are mostly occupied with looking up annoying details about how to do what’s in my head within the syntax and limitations of the latest re-invention of whatever lanugage has been selected / is available in the environment. Both routes have to be tested, but glancing over provided source code and nodding “yeah, that looks right” then testing the successful implementation is a hell of a lot more satisfying for me than deciphering complier errors, untangling version incompatibilities, looking up function signatures, etc.
sounds like you should transition to being an architect
Our department is too small to really need an architect, plus there’s a lot of egos running around who want to be an architect, I’m fine with the title Software Engineer.