[fouric]

The difference is that a single $150k/year programmer can make software that replaces an unlimited amount of $40k/year secretaries.

Software scales - that's why programmers have such high salaries (which are usually only a fraction of the value that they're delivering anyway).

[seem_2211]

I’m saying those programmers should have secretaries to help them with all of the admin etc. They shouldn’t be booking their own flights, or making dinner reservations, or running expenses (or a lot of other manual work)

[Jtsummers]

My previous office went through that cycle.

Circa 2000 (and continuing through the 00s) there was a massive cutback in administrative personnel. By the time I got there (circa 2010) there were essentially no administrative support personnel except for those at the very top. During the 10s they realized that they were spending around $10k/year/person on travel related stuffs not because it was necessary, but because of the time lost to deal with the software that was supposed to remove the need for the full-time administrative staff.

By the end of the 10s, they'd restored the administrative teams and were spending much less per year on "overhead" (non-billable hour) even if you counted the admin teams as only overhead. Down from around $10 million to less than $1 million by just having a dedicated team that dealt with travel and finance stuffs.

The problem was that most people only traveled once a year, at best, and so they had no real experience with the unintuitive software. The average traveler was spending a week extra per trip, which was not billed to customers, dealing with reservations (1-2 days total pre-trip) and finances (2-3 days total post-trip).

[closeparen]

Mythical Man Month describes secretaries in a software context. What spoke to me about it was none of things, but instead: scheduling meetings, taking and distributing agendas and notes for those meetings, being the curator and librarian of project documentation. Just because these things are digital now, doesn’t mean any of the engineers on the team will step up to do them consistently or well. Many projects could run more smoothly with someone in that role.

[ketzo]

Many of those responsibilities have moved into the domain of the Product Owner / Scrum Master roles, which can work pretty well in my experience.

[grumple]

Every minute an engineer spends doing those things is a minute they aren't coding, debugging, or architecting. So what happens? We have to hire another engineer to pick up the slack. When we could hire an administrator for much less to handle those things.

[closeparen]

I continue to be amused that the many of the activities and artifacts promotion committees want to see when they consider engineers for the highest levels, are exactly this kind of "admin" work.

[Jtsummers]

Software can only replace some roles that administrative staff filled. Most often, like in the case of email and word processors, it distributes the work and eats up everyone's time by moving it from specialists to non-specialists.

[TeMPOraL]

Isn't it ironic.

The optimum should be, of course, software empowering the specialists, so they can do more with less, providing better service to more people. But hey, a specialist costs $X in salary; a specialist + software that empowers them cost $X + $Y for the expensive license. Meanwhile, a SaaS that allows everyone to do the task lets us save $X on the specialist, and costs peanuts... plus a good fraction of everyone's salary, but nobody notices that.

[bluGill]

The secretaries were specialists: in language. How much better would my posts be if someone who was good at writing and so would correct my grammar (grammar checkers are horrible - or were last time I tried, mostly I don't even look anymore). Often what I saw should be worded a little differently. Spell check doesn't notice when I spelled a different word than what I wanted.

I'm a faster typist than I am at talking, so I don't need a typist. I could really use someone to proofread for me. We have lost both.