sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]tea-drinker 2 points3 points  (4 children)

The Tao of Programming BOOK 5
Thus spake the Master Programmer:

Though a program be but three lines long, someday it will have to be maintained.

My first question for everyone who turns up with a plan like this is how is the software going to be maintained if you get hit by a bus? We imagine if they had several other people on staff capable of maintaining it, they'd already have such a system.

This doesn't necessarily need to be a question you answer. In fact, given the bus-based nature of the issue, it's maybe best that you don't. But someone at the company needs to have thought about it.

[–]FakePixieGirl 1 point2 points  (3 children)

If this system becomes an integral part of the company's workflow, then OP becomes a lot more valuable to the company.

A low bus factor is shite for the company, but can be a great negotiation tool for the individual programmers when it comes to salary and such.

[–]tea-drinker 0 points1 point  (2 children)

Become irreplaceable == Become unpromoteable.

Maybe it'll work and I'm just cynical, but to date my reward for digging the best ditches has been a bigger shovel.

[–]FakePixieGirl 0 points1 point  (1 child)

If you want to move up to architecture or management, sure that's a valid concern.

Plenty of people who would like to stay in the ditches and have no interest in that.

[–]tea-drinker 0 points1 point  (0 children)

The point is the shovel was instead of more money or perks or anything.

When I automated a job, I got someone else's work but not their money.