Profile photo
Pieter Rossouw

Senior Developer with 5 years experience in the FinTech space

Really passionate about both software and people. Had my first computer experience at around 2-3 with a then-state-of-the-art Olivetti 286 running at 12MHz in ~1993 and haven't stopped learning. After studying computer science and completing my Master's degree with a focus on drones, wireless mesh-networks, building fault-tolerant architectures and distributed computing, I'm focusing on honing my craft as a software developer in the FinTech space.

Work Availability
Open but not looking
  • πŸ‡ΏπŸ‡¦ South Africa
  • Remote OK
  • Relocation OK
Role Level
  • Senior
Role Preferences
  • Full-time Employment

  • nvm

    Lifesaver when doing Angular/Vue development and need to switch Node JS versions. We've got legacy codebases AngularJS that require Node JS 8, and new SvelteKit ones that want 16 - nvm keeps you sane with these kinds of situations.

  • Bitwarden

    Password manager of choice for all my personal stuff; no fluff - does what you expect and doesn't skip a beat.

  • flameshot

    One of those tools I install first on any new machine - when you need to capture and quickly artefacts from meetings to include in emails, present a specific app behavior/bug, flameshot is the one I go for.

  • Visual Studio Code

    Killer editor, basically the go-to unless I'm doing Java dev - then it's IntelliJ IDEA. Really like the remote development capabilities via SSH/WSL.

  • Nginx Proxy Manager

    Great for homelabs, also cool for learning NGINX configs - don't just set and forget, go behind the scenes and look at the nginx.conf files that are created via this UI.

  • Docker Compose

    A repo isn't complete without a docker-compose.yml file - it should be the entrypoint for new devs to be able to spin up the required stack and learn its components and their interaction. Also great for deployment obviously.

  • Nginx

    Experience using NGINX as a reverse proxy in a containerised environment. Used it to set up path-based routing i.e. requests to / is routed to a landing page, /foo is routed to container A and /bar is routed to container B. I looked at using Traefik instead but NGINX is now "the devil I know".