As teams and organisations fail to deliver desired results, instigating a change in process, structure, and/or behaviour becomes critical. However, change can only be successful if teams are motivated to adapt to it. I have found the Regulatory fit theory (E. Tory Higgins) and Expectancy value theory (John William Atkinson) useful at this point to motivate teams to adapt to change (you can find out more in “The Lean Mindset, Ask The Right Questions” by Mary Poppendieck and Tom Poppendieck).
I’m amazed at how people’s workplaces are so utterly different to mine.
During the 1940s, at a top-secret location, somewhere in the middle of the New Mexico desert, a group of scientists were working on a project.
Their goal was to take a dangerous idea, like an Atomic Bomb, and birth it into the world.
One of the physicists at work, was the late Richard Feynman. He had famously won a Nobel Prize for doing something particularly clever with quantum electro-thingies…
But what people don’t know about him, is that he was also an accomplished safe-cracker.
It was only natural that when things got boring at work, he’d use his spare time to hone his craft. And so, he began leaving notes in place of his colleagues research papers…
“…I borrowed document no. LAXXXX — Feynman the safecracker…”
I’m also amazed at how similar our workplaces can be—
At Armakuni, we strive to be data-driven in our approach. We’re scientists, just as much as we are engineers and consultants. We work as colleagues, capturing your dangerous ideas (and ours) with a flurry of post-it notes.
We are passionate. We continuously experiment. We continuously learn. Especially from mistakes. The atmosphere is electric.
And that’s when I realised what Feynman and I have in common, is a love of being surrounded by people who are insanely focused; a love of being surrounded by people that are motivated by deep curiosity— not just about technology, but about everything.
But my favourite lesson from Feynman is just this:
It’s important to bring your self to your work.
Safe-crackers. Musicians. Poets. Bootleggers. Optimists. Calligraphers. Trainspotters. Painters. Comedians. Table-Tennis Champions. Passionate educators. Whoever you are. Bring it. With tempo.
If I’ve learned one thing during my first three-months at Armakuni, (and the truth is. I’ve learned so much from this team beyond Cloud-native, transformation and DevOps) it’s that your attitude is everything. Your outlook. Your willingness to push yourself. Putting your heart into your hustle, is what makes us successful. Together.
Every day is a new opportunity to make something great happen.
We may not have a secret lab in the desert, and we may not have a safe-cracker on the team, but I love working for a company that celebrates diversity, celebrates technology, and celebrates unique, talented, generous and deeply technical people. Because the truth is, Armakuni really gets these simple facts about business:
Change is constant. And,
the orienting impulse of all transformation isn’t about process—
It’s about people.
As Serverless is on the rise, the art of debugging and tracing is changing, too, as well as the day to day work life of Developers and Admins. At the Serverless Architecture Conference 2019 in The Hague, Billie Thompson, one of Armakuni’s Cloud Native Consultants, took time to discuss how Serverless is affecting the IT industry and how tracing is done in the times of Serverless.
Google Cloud Run is Google’s new Serverless Container as a Service (CaaS) product. Serverless is a term with many meanings; in this case, it means your containers will scale to 0 running instances when no requests come into your service for a while.
Having 0 instances of quiet services means a service provider can afford to be a bit smarter with their pricing, only charging you when requests are hitting your application, and not charging you at all for the servers that do the scaling.
Internally it’s built on top of Knative (pronounced “Kay-native”). Knative is an open source platform for building Functions as a Service (FaaS) services on Kubernetes, so perhaps we will see extensions in that direction in the future from Google. You could build a version of this on a private cloud by deploying Knative and using the “kn” client, what makes this different is that you’re not paying for the idle capacity on the Kubernetes cluster….. Continue
In this article, I question whether there is a transformation missing from the Transformation Priority Premise (TPP). In my last article, I implemented a simple function which checked whether the input number was odd or even. The goal of the exercise was to strictly adhere to the TDD cycle while also making sure I had all the tests I wanted at the end. This exercise lead to an impasse problem, where I couldn’t write the next failing test without changing the behaviour.
To get beyond this impasse, I changed the behaviour in the refactor stage and claimed that it was OK to do so because it enabled the next step in the unfinished process…. Continue
In one of my previous blogs I talked about migrating an app to Lambda. One challenges I had with my migration was finding good example and guides for Lambdas written in GoLang. The “Getting Started” type guides were great but it didn’t take long to exceed their limits of usefulness.
In this article, I want to consider a situation where considering the next test we want to write, influences the way we refactor.
For this article, I want to consider implementing a simple function to check if a number is odd or even. The function will simply return true if it’s given an even number, and false if it’s given an odd number.
As with my previous TDD articles, we are working very rigidly with the TDD cycle — we must write a failing test, we must implement it in the simplest way possible, we may then refactor… Continue
At Armakuni, we like to keep our skills up-to-date. In this instance, we wanted to spin up a copy of Pivotal Cloud Foundry on AWS. Things change pretty quickly with PCF, so we thought we’d share how we did it, and our thoughts on the whole procedure.
Since we last used PCF, the peeps at Pivotal have done quite a bit of work to help you out… Continue
At Cloud Foundry Summit Europe 2018 our COO Zenon participated in a second panel discussion, this time focussing on how Armakuni’s use of Cloud Native technologies, in particular Cloud Foundry and Kubernetes, underpinned the crucial Comic Relief donation platform used for Sport Relief 2018
Last week I had the opportunity to attend the JAX London conference and I am so grateful to Armakuni for making this possible. It was a great way to learn more about the hot-topics now in our industry, to concrete some of the knowledge I gained over the last months and to get to meet new people!
The conference spanned across 4 days, where the first and last days were workshops and the two days in the middle where full-on presentation days from amazing speakers…. Continue