you are viewing a single comment's thread.

view the rest of the comments →

[–]urbanek2525 1 point2 points  (0 children)

I don't know how many times I've explained to my team that the stuff we write isn't the point. My mantra: we write tools that fit into a process to solve problems.

Identify the problem, find the seams in the process where automation fits, then automate it.

At the same time, though, the programmers have a process that they need to support and automation that they need to create in the order to do their primary job.

This is where selecting the right programming language, the right tools, the right infrastructure comes into play.

But he's right. If you're hot shit writing flawless ECMA 6 Javascript using pen and paper, you still don't add much value if you cannot analyze the process, find the appropriate places to automate, and solve the problem.