Javier Honduvilla Coto

Something I found incredibly frustrating when I started programming was that I could not spend more time building projects and instead had to fight with errors that seemed like a distraction.

Sampling profilers periodically fetch the stacktrace of the application under observation.

Or, speeding up writing binary data in Go by 14x.

Most software writes to disk at some point but in some cases nothing cleans up the stale data that won’t ever be read again.

open and Python TL;DR: Misusing Python’s open and the interaction of CPython’s GC and UNIX semantics can lead to unexpected results!

GDB has an amazing feature that allows to run arbitrary functions on a target process.

Working on some eBPF / BCC script that fetches the stacktraces of processes that receive deadly signals I saw dozens of segfaulting Java processes.

This summer, while working on my internship project, I realised that an internal CLI tool was taking too long to run.

Some weeks ago I started doing a side project in C.

Some days ago I was wondering how Linux decides which process to kill when free memory is running low.