Networking for Developers – part 2: application and transport layers

NOTE: Catch up with the previous posts in this post series:Part 1: Overview The Network Stack has four layers: Application, Transport, Network (or Internet) and Physical. This post will cover the top two layers: Application and Transport and together they help the destination computer identify what type of data it's receiving through the network. The … Continue reading Networking for Developers – part 2: application and transport layers

Check which commands you typed in the command line and don’t repeat yourself!

Recently I needed to repeat a series of long~ish commands in the command line but I never quite memorized them so I ended up resourcing to arrow-up-arrow-up-arrow-up </ad nauseum> until I found the command I was looking for. But there is a better and super simple way: history Typing history in the command line will … Continue reading Check which commands you typed in the command line and don’t repeat yourself!

Docker for development: make local files visible to a container with volume mapping

I wrote a very simple right-to-the-point Docker introduction post if you're new to Docker. If you want to see your code changes applied right away to a running Docker container, you need to make sure to run the container using the share volumes tag: -v (or --volume). The -v tag expects as a parameter the … Continue reading Docker for development: make local files visible to a container with volume mapping

Profiling: check how long it takes to run a Python script

From Python's official documentation: "A profile is a set of statistics that describes how often and for how long various parts of the program executed." Python's standard library provides two implementations of the same profiling interface: cProfile and profile but I always go with cProfile for short scripts because you can invoke it at run time like … Continue reading Profiling: check how long it takes to run a Python script