I also strongly disagree with the notion of automation just because we can. However, this is a positive and constructive community. Your comment was neither. Please, don't make comments like this. If you have something to add to the conversation, feel free, but that doesn't including flinging insults. Here is Dev.to's code of conduct: dev.to/code-of-conduct. Please read it thoroughly. Cheers.
Chris, this is an interesting article. Nice! I worked with CMSs and automated templating systems for several years, e.g. WordPress. I too thought, "why aren't we automating the generation of these things?" The caveat that I found was, the automation software is always more complicated than actually just creating the product. It takes more time to create potential variables, rather than a polished and focused result. I actually wrote an article a long time ago called, Abstraction for the sake of Abstraction. In the article, I talked a bit about this, but focused on automation tools in the JavaScript ecosystem.
Hey Forest, I agree we shouldn’t do it all the time; the notion was to explain that you can if you need to. I’ve worked with some internal tools/generators that have been a godsend. There are definitely positives to the approach, and they were what I was trying to highlight.
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.
I also strongly disagree with the notion of automation just because we can. However, this is a positive and constructive community. Your comment was neither. Please, don't make comments like this. If you have something to add to the conversation, feel free, but that doesn't including flinging insults. Here is Dev.to's code of conduct: dev.to/code-of-conduct. Please read it thoroughly. Cheers.
Chris, this is an interesting article. Nice! I worked with CMSs and automated templating systems for several years, e.g. WordPress. I too thought, "why aren't we automating the generation of these things?" The caveat that I found was, the automation software is always more complicated than actually just creating the product. It takes more time to create potential variables, rather than a polished and focused result. I actually wrote an article a long time ago called, Abstraction for the sake of Abstraction. In the article, I talked a bit about this, but focused on automation tools in the JavaScript ecosystem.
Sorry, I definitely came on way too hostile.
Hey Forest, I agree we shouldn’t do it all the time; the notion was to explain that you can if you need to. I’ve worked with some internal tools/generators that have been a godsend. There are definitely positives to the approach, and they were what I was trying to highlight.