<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blogs on Kai Striega</title><link>http://kaistriega.com/blog/</link><description>Recent content in Blogs on Kai Striega</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 27 Oct 2024 13:51:52 +1100</lastBuildDate><atom:link href="http://kaistriega.com/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Processes, Threads, Oh My!</title><link>http://kaistriega.com/blog/low-level-fundamentals/processes-threads-oh-my/</link><pubDate>Sun, 27 Oct 2024 13:51:52 +1100</pubDate><guid>http://kaistriega.com/blog/low-level-fundamentals/processes-threads-oh-my/</guid><description>TLDR# Processes and threads are an integral part of programming They are an essential tool in any developer&amp;rsquo;s toolbox Processes is how the OS represents a running program. Threads are how the computer groups together instructions from your program and executes them You can have multiple processes and threads At least one thread runs inside each process Tradeoffs of processes vs threads are: Processes are slower to create than threads Processes own their memory, threads share memory between them It is easy to make very difficult to debug errors with threads Introduction# I have a friend who is currently trying to transition into software engineering.</description></item></channel></rss>