“If you can’t explain it simply enough, you don’t understand it well enough”.
Challenge accepted. Here’s my attempt to explain native components of Kubernetes in five minutes with the objective of covering concepts and resource types that will enable you to t̶a̶l̶k̶ ̶a̶b̶o̶u̶t̶ ̶K̶u̶b̶e̶r̶n̶e̶t̶e̶s̶ ̶l̶i̶k̶e̶ ̶y̶o̶u̶ ̶u̶n̶d̶e̶r̶s̶t̶a̶n̶d̶ ̶i̶t̶ understand Kubernetes and deploy applications at a basic level.
As a pretext, I’ve found it useful to think of Kubernetes-related work not as a collection of verbose YAML files defining strange
kinds of resources, but as a set of abstractions representing common design patterns in application deployment.
To me, the areas that Kubernetes natively accounts for in logical — imo — order…
I’ve been conducting interviews for software engineers together with a couple of like-minded colleagues for some time now; and I thought it’d be nice to share my learnings and experiences from this journey of trying to be both a nice human, as well as a reliable gatekeeper for the team.
This piece that follows will try to provide some insights to an ever-improving attempt to answer the question “what does it take to conduct an awesome technical interview?” …
Views expressed here are strictly my own and do not constitute an official statement of any sort
With the private hire vehicle app still displaying five more minutes till my ride, a car that just pulled in gave a short honk that somehow sounded a lot like “don’t need check lah, it’s me”. I checked the number plate anyway and found my honk intuition to be healthy. And just like that I began my journey home — apparently still five minutes away from where I was.
As the roads became increasingly familiar, I began to count the minutes till I could hit the bed for my usual weekend sleep-in. …
Early on in the product development journey of MyCareersFuture, we decided to involve product owners as part of our end-of-sprint retrospective.
Since it was our first collaboration with Workforce Singapore (WSG), there were teething issues transitioning from the way things were traditionally done on their end (waterfall) to Agile; Including our product owners in retrospectives helped us to better communicate with them on our principles and workflows in Agile. …
Another year older, another year wiser. Supposedly, at least. So here’s a reflection on how 2018 went, and some setting in stone (or in some SSD belonging to Medium) on where 2019 will probably be going.
I set 3 things I’d like to do back at the end of 2017. They were 1. Pick up a martial art 2. Engage in a hardware project 3. Record a song.
As life has it, one doesn’t simply have one’s way.
Pretty much the only “thing” that went well, and I’m glad to say I’m still studying it till this day. …
Starting out, my biggest issues I had with Golang was the lack of tooling and the by-now infamous
GOPATH requirement. …
It was May 2018. I’ve always had an appetite for change, and had been in the Apple ecosystem for most of my modern mobile phone life. You know that stuff just works (disclaimer: this was the Jobs era). I cheated for one re-contract period with a Windows phone (still the best OS to me, but it’s sadly gone for good), but I used iOS for everything else.
During my deep relationship with iOS, Android had advanced to a point I thought I might give it a try. Since I was being nudged to switch from OS X to Ubuntu by forces that be, I decided to go for an all-out change out of the Apple ecosystem and got my Ubuntu laptop together with my — as my programmer type friends would have it — “first real phone”: a Google Pixel 2XL with stock Android. …
So we launched our latest offering about two months ago, a product targeted at helping local Professionals, Managers, Executives and Technicians (PMETs) find employment in the later stages of their careers.
Like how all good stories begin, we start with why.
Way before development starts – around 4 months prior – all products destined for the keyboards of engineers at Government Digital Services (GDS) undergo a phase called product conceptualisation.
During this stage where we’ve been tasked by the various ministries/agencies to solve a problem with technology, we take the time to talk to users about the ‘problem’ and find out whether it is a problem technology can solve. …
How many times have you ran some
./script.sh, it runs, some output appears, but you have no idea what it just did? That’s bad scripting UX at play and is what I will be covering in this short piece — how to write shell scripts with a more pleasant developer UX.
There’s a certain irony when writing scripts. Unlike code destined for products where your end-user is usually non-technical (sweep it under the bed! they won’t know!), code in scripts are a different monster, they’re for developers, by developers.
This results in some problems:
Fine, I lied, there actually is a server. If that’s a deal-breaker, you can leave now.
Still here? Awesome.
In a nutshell, a serverless architecture simply means the designing of an application without considering the server. There are a few sub-architectures, the most popular of which is Functions-as-a-Service (FaaS), which major cloud service providers like Google, Amazon and Microsoft already have offerings for.
Another sub-architecture is Backends-as-a-Service (BaaS), which is basically writing your application for use with cloud provided services that provide functionality normally provided for with a bespoke server application. …