Hacker News new | ask | show | jobs
by AeroNotix 1610 days ago
When I worked at HP over a decade ago it was literally my job to walk into a department and find processes that were automatable, implement whatever program or automation was necessary and gtfo.

One of the highlights for me when working there was automating a process which took three people thirty days to perform. I made a point to unnecessarily optimize the program to the point where it ran in a handful of milliseconds.

These kinds of low-hanging fruits are all over certain industries and companies which aren't primarily software-development based.

I sort of miss it, in ways.

4 comments

2 jobs ago I had a management level position ("Head of Architecture") for a decent sized engineering multinational.

My fondest moments are actually when I helped people do mind numbingly awful tasks by automating stuff - this was not my day job but I had a lot of freedom.

One guy was so delighted that I had scripted in less than an hour some ghastly bit of spreadsheet work that he estimated was going to take him a few weeks that he immediately ran out and bought me a bottle of wine!

This is partly why I miss it, sometimes. The work itself is largely pretty easy to do and the impact can be huge. Not just in a time-saving way, but to the people involved and ultimately the company.

I often think about the sheer volume of tasks like this the world over where a tiny Python, or even say, AutoHotKey script could automate it. The amount of hours mankind must spend on utter drudgery astounds me.

By far, my favorite accomplishment from last year was (effectively) automating a barcode lookup. The historical process took 5-10 minutes and was performed 5+ times per day. My half day of scripting now saves ~1HR of daily labor. Nearly a year after I created it, and one woman still stops me every time she sees me to thank me for improving her job.
Yup. That reminds me of a time when a co-worker in another department (technical but not software) told me that the people she managed had to do a very tedious task extracting and cross-correlating data from files that my project produced. They were sometimes spending 4+ hours each day doing it.

It took me all of one lazy afternoon to build a utility to do the same work and present it in a nicely formatted report. Their workload on this task went down to about 5 minutes per day.

Had something similar at a larger company I worked at! There was this team that was tasked with automating stuff from the other teams. And then they got split up and individuals were sprinkled around the company. I guess it was sorta like embedded devops in a way because they were supposed to spread that "automate stuff" mindset.

Thinking about it now, it makes sense. It's a bit of a waste to have one team that automates stuff, and everyone else just thinks of automation as "that's not our job!"

A good way to make friends too.
Not the people whose jobs likely went away as a result, however.
You'd be surprised how often that isn't the outcome. It definitely does happen, but a lot of the time the company is left with a task that's now automated and an employee that's received a ton of training on the business systems. There are almost always other products that sales wants to push that there simply wasn't the bandwidth for before...

There is always more business - sometimes companies choose to put automated employees towards that (and get huge moral boosts to the employees that automated the thing - the employees that were automated - and everyone nearby who appreciates how useful automation is) and other times they decide to trim a marginal cost off the bottom line and end up discouraging further innovation and, probably, losing a lot of people they actually still need.

Companies that, essentially, get some of their labour replaced for a free (or marginal cost) should realize that there are a lot of more savings like that to be had - and that if they use that savings to invest in growth it will pay off in the future. Companies that choose stagnation die (and you should leave them to die without you as an employee).

The difference is whether you are automating a "profit center" or a "cost center". Automate a profit center, and you free up people to do more profitable stuff. Automate a cost center, and they can lay everybody off and cut costs.

The whole notion of "cost-" and "profit centers" is a terrible construction of modern management theory. But it is how almost all businesses work nowadays. Never work in a cost center department (unless you can use it for grift the way HR directors do).

The notion of cost centers is why most web sites are crap. For most businesses the web site is a cost center, and everybody working on it is piling on superfluous tech to pad their résumé with, and to make themselves more essential.

It is simply an internal implementation of rent seeking.

You can burn fossil fuels and cause damage through pollution and be applauded for being highly profitable.

Meanwhile people building sustainable energy or at least reducing the damage caused by pollution will be considered a drag and harshly criticized.

Ultimately the problem lies in the fact that we have built entire societies around the idea of exploiting externalities. You can't build a healthy society around such a thing and yet we keep doing and loving it.

This is spot on. The final conclusion is that we are in a cul-de-sac though, any kind of exit seems to be across capital expenditure barriers that are too high to surmount and if you succeed there will always be a competitor to your plan that does things the old way and that looks short term to be cheaper.

I think the big problem is that we do not show the full price at the outset, the 'sticker price' is usually only a fraction of the total cost and the payer of the sticker price has no idea of what the total cost eventually will be. If we could only make them aware of that it would already be a step in the right direction, and the remainder might be fixable by taxation.

It depends on the company. My day job can reduce required headcount for the work we handle. Some companies use that excuse to lower headcount, but in cases where valuable employees are involved they get moved to other jobs where their knowledge can add value while not doing the boring and repetitive tasks.