Skip to main content

On Marshall

Nobel peace price winner most known as state secretary and the Marshall plan, George C. Marshall, was one of the pillars on which the US military might founds on today

As army chief of staff, Marshall was responsible for who to fire and who to keep. When he stepped into the office on the day Germany attacked Poland, The US army was old dated, and their military tactics were as well.

The US was a third rate military power. Less than 200k men and a handful of tanks and bombers.

On his reign, it grew to be a force of 9 million and to be the world's most powerful army. His contributions to the war effort were so significant in his peers' eyes that President Franklin Roosevelt said that "I could not sleep at night with you out of Washington"

How did he do it?

Before the US got involved in the second world war, he was to retire hundreds of senior leadership. They did not fit the Marshall profile. In essence, it is a handful of character traits.

1. Good common sense
2. Professionally educated
3. Physically strong
4. Cheerful and optimistic
5. Energetic
6. Extreme loyalty
7. Determined

Marshall did not care if his subordinate was a bit eccentric; he just needed to fit the profile. The focus was on that the general was a team player, leaving their ego behind. He earned respect for his subordinates even though his hiring and firing methods were seemingly harsh.

Marshall gave you a chance if you fit the profile. Then you had a relatively short period to show if you are capable. Successful commanders were promoted, and the not so successful ones were relieved. Fortunately, getting fired was not the end of your career, but rather a temporary setback where you could step back into similar or even higher positions later on.


Sources
Labels:

Comments

Post a Comment

Popular posts from this blog

I'm not a passionate developer

A family friend of mine is an airlane pilot. A dream job for most, right? As a child, I certainly thought so. Now that I can have grown-up talks with him, I have discovered a more accurate description of his profession. He says that the truth about the job is that it is boring. To me, that is not that surprising. Airplanes are cool and all, but when you are in the middle of the Atlantic sitting next to the colleague you have been talking to past five years, how stimulating can that be? When he says the job is boring, it is not a bad kind of boring. It is a very specific boring. The "boring" you would want as a passenger. Uneventful.  Yet, he loves his job. According to him, an experienced pilot is most pleased when each and every tiny thing in the flight plan - goes according to plan. Passengers in the cabin of an expert pilot sit in the comfort of not even noticing who is flying. As someone employed in a field where being boring is not exactly in high demand, this sounds pro...
Post a Comment
Read more

PydanticAI + evals + LiteLLM pipeline

I gave a tech talk at a Python meetup titled "Overengineering an LLM pipeline". It's based on my experiences of building production-grade stuff with LLMs I'm not sure how overengineered it actually turned out. Experimental would be a better term as it is using PydanticAI graphs library, which is in its very early stages as of writing this, although arguably already better than some of the pipeline libraries. Anyway, here is a link to it. It is a CLI poker app where you play one hand against an LLM. The LLM (theoretically) gets better with a self-correcting mechanism based on the evaluation score from another LLM. It uses the annotated past games as an additional context to potentially improve its decision-making. https://github.com/juho-y/archipylago-poker
Post a Comment
Read more

Careful with externalTrafficPolicy

On a project I am working on is hosted in an EKS cluster with the NGINX ingress controller (the one maintained by Kubernetes). It is deployed using it's official official Helm chart, which I realized, after a lengthy debugging session, was a mistake. The initial setup I aimed to improve had several flaws. Firstly, we were using the AWS Classic Load Balancer in front of the nginx ingress in the cluster, which has been deprecated for some time (years?). Continuing to use it makes little sense to us. The second issue was that we were only running one(!) nginx pod, which is quite sketchy since the exposed web services had essentially no high availability.  I switched to the Network Load Balancer (NLB), which was straightforward - I just needed to change the ingress-nginx service annotation to specify the load balancer type as NLB: service.beta.kubernetes.io/aws-load-balancer-type: nlb However, increasing the replica count turned out to be tricky. When I bumped it up to two, I began to ...
Post a Comment
Read more