Have had many hats on in my life: Developer, Team Lead, Scrum Master, Architect and Product Owner. Now back to developer \o/ Interested in product discovery, quality assurance and language design.
Nah, it's more about distinguishing learning from creating. I've seen all too often devs putting horrendous effort into code, design and tests when they didn't know the underlying tech, dependencies and quirks yet, leading to constant refactoring along the way - which actually leads to bad quality if you are not willing to throw away all your design. And it's still more effort than necessary, you could do better when first experimenting with no regard to quality. And after learning, throw the experiment away.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nah, it's more about distinguishing learning from creating. I've seen all too often devs putting horrendous effort into code, design and tests when they didn't know the underlying tech, dependencies and quirks yet, leading to constant refactoring along the way - which actually leads to bad quality if you are not willing to throw away all your design. And it's still more effort than necessary, you could do better when first experimenting with no regard to quality. And after learning, throw the experiment away.