It was a rainy Sunday and I had an itch. What would a super simple, barebones micro-frontend framework look like? No webpack magic, no complex tooling, just the browser's native module system and some common sense.
A day later, I had Trailhead - a proof of concept that's surprisingly close to production-ready. This isn't a replacement for Single-SPA or Module Federation. But it's not completely crazy either.
This post is about the git skill level I expect when someone puts “Git” on their CV – practical, professional usage rather than just knowing git commit.
Before you write GIT on your CV for your next job interview, make sure you know how to use GIT professionally; read on.
If you are here you know that GIT is likely the most popular version control system used in the known universe. If you are a developer looking to get paid GIT is one of your most important tools for doing a professional job.
Any developer can write code. Professional developers know how to organise code changes so that they can be easily reviewed, patched and reasoned about. GIT like other version control systems is the tool that helps us to work professionally.
Unfortunately, there is a disconnect between using GIT and using GIT Professionally.
Working with MFA‑enabled AWS accounts from the CLI can be painful; this post walks through the small tool I built to make that workflow bearable.
Simplify your life when using MFA-enabled accounts with AWS profiles by installing this command-line tool.
Install awsmfa from npm or fork the project on GitHub.
Enforcing multi-factor authentication (MFA) on AWS accounts is a security best practice that can provide some usability hurdles for engineers that rely on the SDK and AWS command line tools to get work done.
The typical workflow for working with MFA-enabled accounts is to request a temporary session using the AWS STS service. The STS service will then return a session token which includes temporary credentials as well as a session token. Depending on the use case these data can then be used either in a profile definition, environment variables or as arguments to call AWS Apis that require MFA.
This post is a compact cheat‑sheet for the Vim motions and operators I lean on most when editing code.
In my opinion, the best way to fast-tracking your VIM skill set is to understand some principle concepts.
This post is about adding one long‑term efficiency skill to your toolkit: using Vim motions in your editor instead of living in mouse land.
.
The motivation to write this article is to encourage you to add an efficiency skill to your skill set that will benefit you throughout your entire career as a developer. Let’s set a scene to get started.
Imagine a pleasant Sunday afternoon at home and you are trying to help someone in your family be more efficient by encouraging them to learn how to “copy & paste” with the keyboard.
Your protégé reciprocates with: “I don’t want to remember that “ctrl + v” pastes text, it makes no sense to press V for pasting, it’s too hard for my fingers, and why would I want to bother remembering that? Look, it’s easier to simply copy and paste from the menu with the mouse.”
Knowing what you know about working on computers; what’s going through your head as you hear that?
Right, I think the same thing when developers list their reasons for not wanting to learn VIM commands in their favourite IDE.
Short and sweet: this post is a pointer to the full video + article on hosting JS apps on AWS with CloudFront, S3 and friends without breaking the bank.
Heya, if you are looking for a neat way to host your brand spanking new JS App on AWS on a shoestring budget yet has the big boys' toys for high availability.
Check out the tutorial I posted on YouTube.
.
This is the origin story for the blog: a Friday night detour from Valheim into building a home for scripts, tools and odd bits I want to share (or just not lose).
Friday night and after "investing" 225 hours in Valheim I have finally unlocked the "bordom" achievment. It's a lonely life being the sole viking in a hostile land.
So here I am; switching up my friday nights entertainment by setting up this Blog. An exercise which might well serve double duty as the topic for the first couple of posts.
This should be a nice place to maintain a collection of scripts, tools, videos, rants and other odss and ends.
If the site is found to be helpfull or entertaining all the better.
Here I’m less interested in tooling and more in how to think about pull requests as a learning tool and a way to be a better teammate.
As software developers, we enjoy that feeling of being immersed in the flow, that wonderful state of being where hours whizz by in an instant, and our mental model stands clear; where we can be hyper-productive as long as we can keep the outside world at bay and remain in blissful uninterrupted solitude.
However, building modern software is also a complex team sport where collaboration and continuous feedback loops with fellow developers are key to personal development and high-quality code.
Code reviews are the most obvious contact point with other developers and a foundational process in working towards becoming a part of, remaining in or working towards building a high-performing team that creates code that is stable and fun to work with.
This post captures my setup for using HJKL as arrow keys system‑wide on both Windows and macOS, so my hands don’t need to relearn navigation between environments.
After developing the muscle memory for navigating text with the H, J, K and L keys while developing with VIM or VS Code with the VIM plugin, I now find it very distracting to have to move my hand to use the arrow keys for moving around text or even to just select an option from a drop-down in other applications. It just feels jarring when working.
What I want is an operating system-wide solution that affords me the ability to use H, J, K, L instead of needing to use the cursor/arrow keys; the keys are typically positioned such that they are just too difficult to access without moving the right hand.