In 2012, I was working for an audiobook publisher on ePub conversion that added audio. For whatever reason, that project got shelved, so I was moved into audio auditing.

The job: For each set of tracks (bible versions included well over 1,000 each), listen to the first and last three seconds of audio for pops/clicks, overprocessing, usw. Flag hot files, combine good ones.

The workflow: Open tracks in VLC, manually advance from start to end for each one.

It was immediately clear this was not going to fly for how I spend eight hours a day. It’s possible to create a less efficient workflow, but it would take significant effort.

Visual Studio was installed on my machine, so I looked at media-control OCXs in VB.NET (this is very much a situation where the user controls were front and center, so the time needed to be spent on form design, not coding). In under a week of “spare time,” it was ready to go.

Track positioning and advancement were by default handled to job spex, but I added other options for edge cases.

New workflow: Select folder in app, note bad audio, concatenate good chapters.

A couple of weeks later, half the department was laid off. My boss invented a fictional scenario in which I’d failed to do what I was told, screaming at me on the floor.

I walked out the door.

In 2015, I was working at a Gannett hub and was tasked with creating the workflow and overseeing the nascent department being created to bring in external clients. (Clearly an $18/hour role.)

IT had handled CMS ingestion to a point, but malformed XML sends were an ongoing problem I had to manually tackle. Everything else was up to me to design and build out, including managing client expectations as we got our shit together.

When I accidentally discovered that the client’s CMS had your garden-variety security hole of only requiring a sign in to see the landing page by pasting a URL from one browser to another, I was able to automate budget ingestion by creating URLs via concatenation in Excel, extracting the table data and presenting it in a format my team could actually use.

The weekly sheets I created also had event triggers where updating status internally sent email notifications to the client when that step required their attention.

Then came the new centerwide page-volume expectations and heightened reporting requirements — which were so onerous that they were taking fully one-quarter of my team’s production time while the floor for satisfactory output went from 1.5 pages per hour to 2 (as counted over the entire shift). Combined, it meant that in one fell swoop, my designers were expected to go from 12 pages in eight hours to 16 in six. Work quality suffered tremendously, which is not ideal when we’re literally the department corporate is shopping around to bring in new clients.

I tried to find extant solutions, with the obvious one being that we should have API access to our own CMS. All the new data that designers were required to manually provide was already being generated; we just didn’t have access. This was a brick wall at the director level because they thought it entirely reasonable that a vendor would charge extra for us to access our own data, and there was no budget for that.

But losing 25% productivity was apparently a nonissue with over 200 full-time designers. Budget’s there for an extra 50 people, I guess.

So this is where I went off the reservation and added page tracking to the sheet. As designers marked things ready to proof, that timestamp was saved and attached to the user account performing the action, so there was simply no more reporting to do. Each designer ran a menu command at the end of the week to populate their reporting sheet.

My team went back to having 8 hours a day for design, and we were generally a happy bunch, cracking inappropriate jokes just like in newsrooms of old.

In an open floor plan.

This caused two issues. One, the other teams were starting to get pissed that we had this automation and they didn’t. I pressed for a wider rollout several times, revealing the second issue: The directors needed inaccurate reporting for a things like disciplining employees, and without that, they were going to have a hard time justifying what they were being paid to do.

I got a 0% raise for my efforts and was shunted to another department where I couldn’t cause as much trouble. Problem was, that “it could be more inefficient, but I’m not sure how” was even more applicable in this situation.

The job was manual ad placement, and we were a team of three. I spent the first couple of weeks learning the InDesign DOM since I’d just taught myself JS to automate Google Sheets. A month later, total workload was maybe 30 hours a week.

And this is when IT got wind of my repeated automation projects and put the kibosh on anything further. You can’t code at Gannett unless your title indicates that’s your role.

After being strung along for the final 18 months about transitioning into a role in IT, I finally gave six weeks’ notice and left. I’ve never actually heard an HR representative express surprise and dismay about management decisions, but that came out in my exit interview, and she said that given what actually happened in terms of communication vs. what I’d been promised and she’d been led to believe, she’d have quit as well.

Bringing us to today. Owner and his wife are my direct superiors at a small trucking firm. I make worse money than in journalism in absolute 2017 dollars, to say nothing of inflation-adjusted figures.

Owner told me he’d been wanting to figure out a way to automate trade-show receiving (spending 15 minutes to make $8 isn’t the greatest) for nearly a decade, but everything anyone had come up with met with client rejection on account of the amount of data that would need to be shared and our inability to replicate their receiver forms.

So I got in touch with our point person and asked which portions of the (triplicate … in 2023) receiver forms were actually necessary, created a slimmed-down template I was afraid might deviate too much … and it got immediate approval.

So, I populated that sheet with formulae to pull most needed data from a master sheet that’s, unfortunately, still a manual process involving opening Microsoft Forms results and pasting, but from there, a 10-line script creates all the new receiver forms since it was last run.

The form also has image uploads, so I can pull the remaining information from those, and we have art on hand to send to the customer when there are questions instead of having to pull apart a wrapped pallet or address onsite during show setup.

And instead of the warehouse manually generating truck manifests, as well as scanning the day’s pink copies after close of business, I added the manifest to the show sheet and populated it. I send receivers daily three hours before the old system putting it firmly within client operating hours, and the warehouse prints the manifest at trailer load.

Just had my annual review. $0 raise for that work.

Seriously, I learn new software and skills; I apply experience from several industry fields to create bespoke workflows; those workflows save from 25% to 90% labor. What the fuck else do I have to do to get off the treadmill of losing purchasing power every year?

Thanks for letting me vent.

  • If you have these skills, have you considered applying to technical roles directly? You might have better luck if you start off in a technical role, either in IT or software development. You could use these projects as experience on your resume, and I’m sure at least one potential employer would see the efficiency gains you provided and be interested to talk with you.

    •  Pete Hahnloser   ( @Powderhorn@beehaw.org ) OP
      link
      fedilink
      English
      4
      edit-2
      1 year ago

      I was unemployed for 30 months after leaving Gannett, finally landing this position because I met the owner in detox.

      I got jobs through my cover letters, and those are no longer read at a point in the process that would work to my advantage. My actual work history is rather scattershot because journalism was not a good field to get into, and layoffs every six months were the rule for a couple of years.

      Of the 700-plus resumes I sent out (with fucking cover letters) for positions from juuuuuuust this side of my ethical boundaries in communications roles to pure-play coding, I got a single reply (and didn’t get the job). I then got a grant to do a full-stack course after getting frustrated with response levels, and that certificate didn’t move the needle, in addition to the company, which touted its placement services, dropping me like a rock as soon as I was done. A few hundred more resumes proved it did nothing for me.

      If there’s a way to get people to accept that someone who has roles in several industries brings a lot of intangibles to the table, I haven’t found it. Coding positions seemed to want me having been in a cube for the past three years and no experience before that because it would make me too expensive.

      I’ve gone to several networking events in Austin, tech, tech-adjacent and general purpose, and met three kinds of people at the tech ones:

      • We’re not hiring, but you can think in code, and that’s all you need. You won’t have issues finding a job.

      • We’re hiring, and it looks like you’ve only used X language for a few months. You need to go back to school.

      • What the fuck are you even doing here? Go back to journalism. Editors can’t code.

      So, again, outside of having taken coursework to shore things up and networking to the best of my ability, I’m at a loss for how to ever start making decent money. I feel I would be fairly compensated with my current skillset at $80K, and hope to grow from there. But I have to say, getting shown the door for projects that save up to seven figures and being told I’m being unreasonable about what my skills are worth from everyone is not confirmation that this work actually has value, even though others somehow get paid six figures for the same level of acumen and experience.

      I am the poster child for what happens when you automate hiring to the point that all boxes need to be checked for any consideration, people with more than a couple years out of college are round-filed, and there’s no opportunity to sell yourself with a story.

      Did I mention that all of this stuff is not where I’ve won national awards? Those are for writing … but only when I believe what I’m writing.

      • As a software engineer by profession, I can’t say I’ve run into many people who fall into that third category you brought up (“Edits can’t code”), although I’m sure there are people like that. Most people I’ve met are pretty open to encouraging people who are interested in learning to code.

        It’s possible this is an issue with your resume. Like you said, many companies have chosen to automate large parts of the review process, so it takes some work to structure the resume around that. If you’re applying for technical positions, you may want to focus on the technical work you’ve done and less on the writing. For example, you may want to list technical skills (programming languages, software development tools, etc.) right away, and for each of your positions, list the technical achievements you’ve made within that role (“Created X that improved efficiency by ~90%”). Call out the impact of your achievements! Keep in mind that while your writing accomplishments are important, if you’re applying for a technical role, there needs to be some way to relate those accomplishments to the job you’re applying for.

        Also, if you do want to make a career out of programming, I recommend taking some time to learn tools common in the trade. Familiarity with Git and Bash will help a lot, for example. Try pushing a bunch of code you’ve used for learning onto GitHub/GitLab and putting the URL to your profile on your resume!

        Of course, not having a degree in a programming-related job will make things a bit more difficult (I’m assuming you don’t?), but there have existed employers open to hiring people without a college degree, even if they’re less common. Just keep in mind that just like writing, there is a lot of different subdomains for programmers, and not all of those domains require deep software engineering experience. For example, many IT positions don’t require much coding at all and are more designed around troubleshooting/setting up network devices/creating tools to improve efficiency/etc.

        •  Pete Hahnloser   ( @Powderhorn@beehaw.org ) OP
          link
          fedilink
          English
          2
          edit-2
          1 year ago

          Appreciate your thoughts. I started off my job search in 2020 by spending some scratch on both automated and professional human resume reviews. Believe it or not (because most people choose not to, as the prevailing sentiment is there is nothing wrong with anything but me as far as the hiring process goes), my starting point was received well, as I’d already gotten my bullet points massaged into action effects with hard numbers, and my tech skills were front and center. I was told I’d have no issue finding a job, and that I was a shoo-in in several industries.

          So, here’s the thing with my learning style: Nothing sticks without a project. Having written a grade book program for my high school (VBA in Excel), I started off as a CS major but quickly abandoned that because I didn’t find anything I was learning to be actionable. More coursework is not a viable solution. And this is not frustration directed at you personally, but I’m really fucking sick of being told “you need to go do X” after losing time and going into debt for X repeatedly with zero to show for it.

          Overall, the people who frequent networking events here are pleasant and like to try to be helpful … until you get someone who could hire you and rakes you over the fucking coals for deigning to even speak with them without four more years of Rust than it’s existed.

          I’m frankly done with learning stuff because one person told me to. I’d have some 300 years of schooling ahead of me if I “just learned” every single thing I’ve been told is the one thing holding me back from landing a job, and at a certain point, there’s just no point. And then there’s the chorus of “oh, no, that’s a terrible idea to learn that … no one’s going to be using it in three years.” There’s a lot of gaslighting at play.

          And I don’t even really want to be in tech. Very few ethical (by my definition: “we sell a desirable product instead of manipulating our customers/users”) companies send hiring managers to events in my experience. Their whole goal seems to be getting off on telling me all the things I’m lacking with no intention of it being helpful.

          I like helping people (myself included) by automating tedium away and reducing error opportunities. Managers don’t want that sort of person and sure as fuck won’t ever create a role to make grunts’ lives easier, since it might threaten their control.