I'm a developer-turned-business owner who loves to explore the right tools for the job. I enjoy writing and documenting my journey. I use code as one of the tools to solve real problems.
It's really a combination of the two. As I'm the lead developer, I dictate what we'll use to solve a problem. So this could be a new technique or even a new language. It really all depends on what the problem is and what the best way to solve that issue is. I can push my own agenda a little though. With a recent issue, we needed to speed up a script by a lot and there are several ways to do this. I chose to use Golang. Because it solves the problem and because I wanted to learn it.
In my own projects I usually go with something I already know, because I want there to be as little friction as possible. I do my best not to give myself the opportunity to say: "This is too difficult, I quit". That's much easier to do for your own projects. I do however use all of my skills and build it "properly" from the start.
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.
It's really a combination of the two. As I'm the lead developer, I dictate what we'll use to solve a problem. So this could be a new technique or even a new language. It really all depends on what the problem is and what the best way to solve that issue is. I can push my own agenda a little though. With a recent issue, we needed to speed up a script by a lot and there are several ways to do this. I chose to use Golang. Because it solves the problem and because I wanted to learn it.
In my own projects I usually go with something I already know, because I want there to be as little friction as possible. I do my best not to give myself the opportunity to say: "This is too difficult, I quit". That's much easier to do for your own projects. I do however use all of my skills and build it "properly" from the start.