📡 Abandoned Cold War Command Bunker, Scotland. Part 1 : Exploring the operations room
The military built this site as an Anti-Aircraft Operations Room (AAOR) in the early 1950s. The reinforced concrete structure was part of the Cold War strategic defence network in Scotland.
The building received radar data from the Sector Operations Centre, relaying it to gun sites that safeguarded the east coast of the Lowlands.
Advancements in radar and missile technology made the system redundant only a few years after it opened.
The structure consists of a square, two-storey reinforced concrete shell. It lacks external windows to increase protection against attack and improve security. Steel blast doors secure the ground floor entrances on the east and west sides. Concrete blast walls provide extra protection for these doorways.
The interior contains a double-height central plotting area with an upper-level balcony. Narrow concrete corridors surround this central room. They lead to smaller operations and service rooms.
rockSlayer
in reply to CaptainMan251 • • •agentTeiko
in reply to CaptainMan251 • • •Contramuffin
in reply to CaptainMan251 • • •TootSweet
in reply to CaptainMan251 • • •So, I'm not a manager, but I am in a leadership position. (I'm a "tech lead" on my team of developers, and I hold more "leadership"-ness than tech leads do on some teams.) And my experience comes more from software engineering than anywhere else.
The first rule is that to be a good leader, you have to be a good person. Don't "switch teams" if/when you become a manager. Your job is to advocate for your team. To cover and take blame for your team. To give them space to work. To give them the autonomy they need to improve their processes. To make sure they know they have the autonomy they need to improve their processes. To be vocal to your team in calling bullshit on upper management and agree with your team when your higher-ups do bullshit. To absorb bullshit from above as best you to prevent it from impacting the team any more than absolutely necessary. To talk your team up. To make sure their work is as "meaningful" as possible. To bolster their egos by trying to get them a bigger slice of the "jurisdictional pie". To ease up when they're struggling. To le
... Show more...So, I'm not a manager, but I am in a leadership position. (I'm a "tech lead" on my team of developers, and I hold more "leadership"-ness than tech leads do on some teams.) And my experience comes more from software engineering than anywhere else.
The first rule is that to be a good leader, you have to be a good person. Don't "switch teams" if/when you become a manager. Your job is to advocate for your team. To cover and take blame for your team. To give them space to work. To give them the autonomy they need to improve their processes. To make sure they know they have the autonomy they need to improve their processes. To be vocal to your team in calling bullshit on upper management and agree with your team when your higher-ups do bullshit. To absorb bullshit from above as best you to prevent it from impacting the team any more than absolutely necessary. To talk your team up. To make sure their work is as "meaningful" as possible. To bolster their egos by trying to get them a bigger slice of the "jurisdictional pie". To ease up when they're struggling. To learn from them and along with them. To ensure to the extent you can that they get insight into what's going on at higher levels of management (the high-level company goals and how what your team does fits into that as well as how decisions that might affect your team are made high up). To support your team's basic needs (sleep can be a big one when overnight on-call is involved, do everything in your power and everything not in your power make damned sure your team never has to do overtime, and of course money is tied to basic needs). To make sure the biggest personalities on your team don't silence or drown out others. To eschew needless busywork and take care of the necessary tedious bookwork behind the scenes so your team doesn't have to. To make time for your team, both on an individual basis and on a whole-team basis. To be a source of comfort. To foster relationships between your team and those outside their team that they need to work closely with to succeed as a team. To let them self organize. And to be honest, humble, and apologetic when you have made mistakes, and also open about the fact that you're learning how to be the best you you can be.
DO NOT UNDER ANY CIRCUMSTANCES fall into the trap of thinking you're "in charge". There are very few circumstances in which you should tell people what to do or assign things to people. (Help them to learn how to pull assignments rather than pushing assignments onto team members.) Also, don't try to "leave your mark" or push your agenda on the team. (No "I'm going to improve things". More "I'm going to help my team improve their own processes.") Push the team's agenda to those above you.
A few resources you need to read/watch/consume/whatever, whether you're in IT or not:
Turn the Ship Around!: A True Story of Turning Follower…
Goodreads