Projects to Work On – the AI Recommendations

Vini Motta decided to use AI on ipSpace.net content to find what it would recommend as the projects to work on in order to become employable in 2025. Here are the results he sent me; my comments are inline on a gray background.

Network Automation with Python
Project: Automate basic network tasks like device configuration, backup, or monitoring using Python scripts.
Depending on your programming background, Ansible might be a better starting point. Also: potential Python tools/libraries to use.
BGP Fundamentals and Route Manipulation
Project: Build a small BGP lab to demonstrate routing policies, route filtering, and BGP path selection. You can showcase both internal and external BGP scenarios.

Before someone starts the “we don’t need no routing in SD-WAN world” mantra, have you ever looked at how you connect to any reasonably-sized public cloud ;)

Also, there’s a great tool that allows you to run free BGP labs in GitHub Codespaces, or master BGP using a long sequence of structured lab exercises?

Docker Networking
Project: Set up a Docker environment where you manage networking between containers, perhaps integrating with an overlay network or using Docker’s built-in networking capabilities.

Docker is obsolete according to the gospel of K8S evangelists, but we keep using it everywhere, so this probably makes sense as well. You could use this Vagrantfile and other examples from the same repository to get you started.

Also: containerlab.

Kubernetes Networking
Project: Create a Kubernetes cluster and demonstrate network policy enforcement, service discovery, and load balancing within the cluster.

I have this one on my to-do list for ages (current excuse: waiting for clabernetes to come out of beta).

There are several good tutorials describing how to build a K8S cluster between Vagrant-controlled virtual machines, and a lovely (free) webinar to get you started.

Anything Else?

I would add networking in public clouds to the list. The public cloud to work on depends on your geography and environment. I would start with AWS, but Azure tends to be more popular in some enterprise environments.

When you open that can of worms (and decide it’s time to move beyond ClickOps), you’ll quickly get into infrastructure-as-code waters and start working with tools like Terraform or Pulumi. Also, check out my AWS and Azure examples if you get stuck.

Add comment
Sidebar