Live data from Hacker News

Learning to code vs. learning to automate

daedtech.com

31–40 of 190 posts

Re: Learning to code vs. learning to automate

#31

What's the modern-day equivalent of DeBabelizer? https://en.wikipedia.org/wiki/DeBabelizer https://creativepro.com/debabelizer-pro-5-the-ultimate-image...

ImageMagick [1]. You can do all kinds of really cool tasks with it and a little shell script. It’s a free software hidden gem, for sure.

[1] https://imagemagick.org/script/index.php

Re: Learning to code vs. learning to automate

#32

Earlier quoted context omitted.

What would you prefer? Manual is hardly an option.

Forest, trees... There are problems one should automate but there are many problems where automating is not worth the effort. https://xkcd.com/1319/ https://xkcd.com/1205/

Both of those comics assume you are automating your own manual task. It gets even more tenuous when you are fielding stakeholder requests to automate _their_ manual tasks, when developers cost substantially more than the entry level folks that end up being assigned these manual tasks, and you don't know how long the business process that requires this manual task will even persist in its current form.

That's where the opportunity may lie with no-code type platforms, to empower other departments to automate and maintain their own idiosyncratic workflows.

Re: Learning to code vs. learning to automate

#33

I totally agree that learning "just coding" per se should not be a goal. It should also help to solve some of your real problems and automation is one of the topic that is very likely you need to solve. When you do something that you like and at the same time need it pays off twice. In fact I got most of my programming skills by implementing simple automation task that I needed. I highly recommend AutoHotkey ( https:…

I just changed jobs from developing on Windows to developing on a Linux virtual machine in Windows. I miss AutoHotkey so much. There are so many things that the command line can't do -- GUI commands, window switchers, and so on.

It's a great example of how "learn to automate" can beat "learn to code". When you know how to do something by hand, learning enough about a program's API to do the same thing is a separate learning curve and may not be possible. Telling AutoHotkey "Do it like I do by hand, just faster" always works.

Re: Learning to code vs. learning to automate

#34
post #7

Earlier quoted context omitted.

what's wrong with automator exactly? i've been wanting to get into it on my new mac but i'm not entirely sure what i will use it for yet.

Personally I find it very weird to work with. I don’t see the point of learning a different and less powerful coding paradigm. It would be fine if it had it a current UI but you also should be able to write plain text code.

You _can_ write plain text code, add an Applescript or Javascript block. Or just use Script Editor directly instead of going through Automator.

Apple Events are quite powerful and let you add a lot of functionality.

Re: Learning to code vs. learning to automate

#35

Earlier quoted context omitted.

What would you prefer? Manual is hardly an option.

Forest, trees... There are problems one should automate but there are many problems where automating is not worth the effort. https://xkcd.com/1319/ https://xkcd.com/1205/

What is often overlooked in these sort of discussions, is the fact that there is more to take into consideration than "efficiency".

Certain tasks are in theory executable without specialised tools, if one is willing to pay for "the inefficient ways", but in practice they are just not feasible because the lengthy / convoluted workflow that results means that you are always having to focus on the minutae, which prevents treating all but the simplest issues.

For example, I could in theory write the space shuttle code in pure assembler, using a pen and paper, and huge teams. "It would just take very long". In practice you would never get it working.

Re: Learning to code vs. learning to automate

#36
> Throughout human history, there’s been a sort of “pain is gain” approach to the repetitive. There was value in putting your head down, getting into a rhythm, and working hard at menial tasks.

I was surprised when my sister told me, "I don't think everyone has that instinct to make things better all the time". That's like my fundamental drive! But she doesn't, and I guess I see why. Things didn't get better for hundreds of generations at a time while we were evolving, so inventing is not an instinct.

Re: Learning to code vs. learning to automate

#37

> Throughout human history, there’s been a sort of “pain is gain” approach to the repetitive. There was value in putting your head down, getting into a rhythm, and working hard at menial tasks. I was surprised when my sister told me, "I don't think everyone has that instinct to make things better all the time". That's like my fundamental drive! But she doesn't, and I guess I see why. Things didn't get better for hund…

That’s why even for creative work, getting into a repetitive work rhythm is important. Most high production authors like Stephen King have a strong writing routine like, wake up at this time and write for four hours using this pen at this desk next to this window.

Re: Learning to code vs. learning to automate

#38
Automation is the how, but not the why. We automate things that have become trivial, so that we can do something more meaningful.

It’s important to understand the functional value of programming (ie. automation), but what really inspires learning is the underlying purpose. What are we achieving through automation? What have we unlocked? That process of discovery is what’s most exciting, to me at least, about coding. It’s what I seek to learn.

Re: Learning to code vs. learning to automate

#39

When I was younger I dreamed up an idea of a shock suit, basically it would have been a set of long underwear top and bottom with electrodes that would act like a TENS machine to gently(or not so gently) nudge the wearers into performing a repetitive task with machine accuracy. I figured this would be great for an assembly line and could provide a cheaper alternative to a very costly robot while still providing emplo…

I wonder why is it immoral. I understand that mind control would be, but voluntary external muscle control?

Re: Learning to code vs. learning to automate

#40
I haven’t seen anyone else mention it, so FYI: Keynote on macOS defaults to exactly your preferred behavior: pasting images exactly in the middle of your slide.

I have to use both Keynote and PowerPoint for work and this is one of those small things I've come to appreciate.

Post reply on HN