Member-only story
Closing Down The Discussion
A subversive way to take on disguised RTO mandates, if you’re feeling a little Machiavellian.
Although the tagline of this article sounds more like the clue to a cryptic crossword, this is one of the most important ploys that a modern day software engineer, as always intent on preserving both their sanity and their pay, can employ when subtle back to the office whispers come creeping uninvited into your inbox. So, pay close attention, and take this brother, may it serve you well in the Grand Game of Software Engineering.
Sometimes, people really do think that you ought to take the moral high ground in pretty much every situation. Unfortunately, this can often have a number of side-effects, that are often downright drawbacks — especially when your own needs aren’t served as fully as the needs of those who caused you to take up residence on that high ground in the first place.
I, like many other slightly questionable and damaged, sorry, “ambivalently minded” engineers in the Grand Game of Software Engineering, take the view that while, say, types are rigid, static, and completely necessary to the development process, morals, on the other hand, are nebulous things¹ that can be viewed from a number of directions, attract perspective, and are very much more subjective than objective.
