4 ms·
I’ve had four jobs in my life and have always been stunned by what is still done by hand. Every company had a task which could be heavily automated but was inst
by MattGaiser 7y ago
I’ve had four jobs in my life and have always been stunned by what is still done by hand. Every company had a task which could be heavily automated but was instead consuming 4-30 people.
So if you think the software market is large, consider all the stuff software never reached.
- tootie 7y agoI've seen this even at technology companies. It's like our devs hours are valuable so we can't invest them in something everyone is comfortable doing with a spreadsheet already.
- MattGaiser 7y agoInternal access to developers is absurdly structured a lot of the time. One company a friend worked for billed internal developers at twice what IBM would charge for projects. At other companies, dev time is allocated without any kind of cost analysis whatsoever. It reminded our Romanian business analyst of the Soviet Union.
- qppo 7y agoThis happens to me a lot, but it's basically a kind of technical debt. Most of the time the upfront time investment to automate something properly versus doing it manually is hard to justify. Especially if it's a task that only I understand and now I need to document the problem and the automation instead of just the problem. Business logic doesn't make for elegant APIs that I can hide behind a script and throw on a server, even if it's repetitive or tedious.
- tootie 7y agoThere's also the risk of allocating a team of folks with spare cycles, having the get half way through the work, then getting pulled into billable work and leaving it unfinsihed.
- dillonmckay 7y agoWe are always looking for ideas! Can you give a few examples, please?
- ladberg 7y agoNot OP but I had a friend who has interned at a few record labels. He's not really a programmer, but knows enough about programming to know what kind of task should be automated. He described a portion of his job to me that he and a bunch of other entry-level workers spent a few hours a day doing (basically scraping and storing data off the internet to be sent to business people for analysis). I worked with him to develop a Python script do basically automate half his job in a few hours that could have saved the company tens of thousands of dollars. The company didn't want to dedicate/hire an actual programmer to maintain it, so they kept paying employees to manually scrape the web. The crazy part is the next summer he interned at a different company and literally the exact same thing happened. He re-made the original script, saved tons of work, and the new company still didn't end up using it after he left.
- dillonmckay 7y agoDoes he get paid at the internships?
- ladberg 7y agoYep, but not as well as tech internships. Still, the company was throwing money down the drain because they didn't know that even a semi-competent programmer could automate those jobs.
- MattGaiser 7y agoOh, many companies have only themselves to blame for being blown away by technology.
- goto11 7y agoAre these companies irrational? Perhaps, but there might also be an important point. A manual process is robust, fault tolerant, and easy to adjust to new circumstances or changing business requirements. A Python script is fixed, and they day it breaks down due to some slight change in scraped data, you have to pull in a developer to fix it. For a company without dedicated staff to support such automation, it is a high risk. Ad-hoc automation can turn workflows into Rube Goldberg machines. A Python script here, an Excel macro there - soon nobody knows whats going on and nobody dares change anything. Developers often think only one step ahead: It was manual, now it is automated with a script. Win! A business have to consider that larger picture - future support, maintainability, risk etc.
- ngngngng 7y agoWe have an "internal systems" team at my current company to solve this problem. The product manager for the team knows everyone and keeps tabs on what's being done that could be automated. It's not used to replace people (at least it hasn't been yet) rather it's used to allow the team to stay the same size and scale up their operations to meeting the growing business demands. I think many companies could benefit from a team like this.
- MattGaiser 7y agoOne of my four jobs was on such a team. Unfortunately, they canned it (after I left) as they couldn't figure out what it did. If my team of 8 devs had just one dedicated to improving infrastructure and processes, we could probably increase our overall output by 30% in a year.
- icelancer 7y agoHa, I'm happy this exists. I created this department at the company I founded at and directed it for some time. We call it the internal tools department. It still exists today and is run by a former employee of the department. It's very valuable for us.
- terryjsmith 7y agoThis is great. How do they deal with the on-going maintenance of the tools they build? Do they move to the main product team or does the internal systems team continue to maintain them?
- cosmodisk 7y agoI wrote a piece of code last year in probably no more than a few hours.Showed it to a few guys in my team.Instead of sharing my excitement,they were like "if you run this,what are we going to do then?". She was right,if I'd do it, the size of the team would be reduced by half.But then,what I'd get? Do I get a bonus the size of those employee's salary for 6 month? No.I'd get a grand or two and instead and a pat on a shoulder,while those guys won't find a job for momths.So what's the point?
- MattGaiser 7y agoWithin the company, there is often no point. You want to be the guy selling it outside the company. You can easily claim tens of thousands for the same work then.
- bob33212 7y agoManagement has to be ok with reducing headcount. You would think that all managers would be incentivized to made their groups more efficient but there is a high correlation between headcount and political power within an organization and people don't like to give that up for free.
- recursive 7y agoThe point is getting that thousand bucks before someone else does. Or to make the company efficient enough to survive in a market where the other company's already efficient.
- cvlasdkv 7y agohelping your company save costs (at scale) is almost always stupid compared to selling that knowledge to other companies.
- tcgv 7y agoYou're in a delicate situation, since you'd be to blame for your co-workers potentially loosing their jobs. Nevertheless, doing nothing is also risky, since someone else from another department could show up and automate away your jobs leaving you in a hard place, and you won't have any control over that. If you propose the automation yourself, and plan it's adoption within your team, you may have a chance of taking advantage of it, and even try to bring in more responsibilities within the company to your team to secure your teammates jobs.