[kelnos]

> coding isn’t about the finished product. its a lot like writing. its about the process.

Well... sorta. If you're working on a personal project or open source project, then sure, yes, absolutely. If you're doing coursework or have explicitly set out to learn something new, then sure, yes, absolutely.

But when you're working at a job, they want you to use whatever tools will get the work done the fastest, and they usually don't care all that much about quality[0]. They don't care about your journey or process. They just care about the final product, and whether or not you met their arbitrary deadline.

[0] In my experience, the vast majority of "quality initiatives" at software companies are about fixing existing stuff that's broken, not about putting processes in place to ensure quality for new stuff. Even when the latter does happen, inevitably those processes will be short-circuited when there's a tight deadline.