diff --git a/posts/embedded_logging.rst b/posts/embedded_logging.rst
new file mode 100644
index 0000000..afee87f
--- /dev/null
+++ b/posts/embedded_logging.rst
@@ -0,0 +1,17 @@
+.. embedded_logging:
+
+Embedded Logging
+================
+
+.. post:: 10, June 2025
+    :tags: diy, docker, embedded, development, advice
+    :category: Projects
+    :author: len0rd
+
+I often encounter situations in embedded development where I need to roll my own solution for logging on an MCU. The standard quick-fix to this challenge is for your application to tie a UART to printf and listen there during runtime. While this is a good start, getting embedded code to a production state will often require more.
+
+In my first fulltime job out of college, the senior engineers who mentored me came up with a simple but flexible solution for logging on an embedded platform which I still use to this day. Here's a quick summary of how it works and how you can implement it.
+
+Support multiple output streams
+-------------------------------
+
diff --git a/posts/simple_release_versioning.rst b/posts/simple_release_versioning.rst
new file mode 100644
index 0000000..5ed4e34
--- /dev/null
+++ b/posts/simple_release_versioning.rst
@@ -0,0 +1,14 @@
+.. simple_release_versioning:
+
+Release Versioning In C/C++ Projects
+====================================
+
+.. post:: 10, June 2025
+    :tags: diy, docker, embedded, development, advice
+    :category: Projects
+    :author: len0rd
+
+
+- this is geared towards projects that use languages that dont have a standardized approach to versioning (c,cpp)
+- simple version.json in repo root that is used as a the single source of truth
+- generate version.cpp via cmakes tools