Coders Automating Their Own Job
61–70 of 499 posts
Re: Coders Automating Their Own Job
#62Re: Coders Automating Their Own Job
#63I've automated large chunks of my job away, but I've never felt that I ended up not having things left to do as a result. There are always more tasks to automate and more problems to solve. I get the impression from these stories that the dishonest part of what the self-automaters are doing is that they could do other tasks and use automation to increase their productivity, but instead chose to keep their productivit…
Re: Coders Automating Their Own Job
#64It should be noted that programmers are not automating themselves out of programming jobs . They're automating themselves out of data entry, or testing, or any number of other mindless tasks easily done by computers.
Re: Coders Automating Their Own Job
#65Earlier quoted context omitted.
Just curious, what's in your automation toolbox?
I usually write scripts in Python or Bash, depending on the task. I've had a fair amount of success using a cron for scheduling, but I've come to really enjoy using Jenkins for automated tasks. A lot of tasks make sense to trigger off of events other than the time and Jenkins is quite flexible in that regard.
Re: Coders Automating Their Own Job
#66It should be noted that programmers are not automating themselves out of programming jobs . They're automating themselves out of data entry, or testing, or any number of other mindless tasks easily done by computers.
Development jobs are shifting as more and more towards "plugging APIs together" and much less end to end development. Modern web dev is fantastically more productive and efficient than it was 10 or 15 years ago. Most/many SAAS apps are substitutes for aspects of what previously would have been part of a developers job to put into place.
Re: Coders Automating Their Own Job
#67> Wary self-automators, he speculates, “don’t trust our workplaces. The boss is going to say thank you, good work, now do it again.” Well, no shit. That is what the job of a programmer is - to keep automating things. There are an INFINITE number of useful things we need to do as a society, so we shouldn't be upset if we automate one of them away. Move on to the next. Of course, programmers should make sure they negot…
> Well, no shit. That is what the job of a programmer is - to keep automating things.
I think that many of these scenarios are occurring when NON-programmers realize that their jobs are automate-able and they set out to automate them. It means picking up new skills, practicing them and putting them to use without the consent nor permission of management.It is not necessarily an easy path, it takes time, and there's going to be trial and error involved and although the discussion is about automating 100% of a job away, there's many other possible outcomes such as effort-multiplication, getting rid of the grunt work and gaining more time to focus on deeper problems.
This is effectively "out-of-band" work that is a great experience for the individual but which _many_ organizations do not condone. A LOT of workplaces don't tolerate workers doing stuff that they're not being "told" to do.
Re: Coders Automating Their Own Job
#68How do I find a job I can automate away?
Re: Coders Automating Their Own Job
#69Re: Coders Automating Their Own Job
#70This was a pretty good article until the conclusion. It's like he's totally unaware that all the information is already shared. I guess it could be a weird plea for some sort of blockchain union or something. Homie should just google "task automation github".