diff --git a/_posts/10-01-01-Caching.md b/_posts/10-01-01-Caching.md
new file mode 100644
index 0000000..d4d22c4
--- /dev/null
+++ b/_posts/10-01-01-Caching.md
@@ -0,0 +1,3 @@
+# Caching
+
+PHP applications on their own are relatively slow, but thankfully there's various (easy) ways to speed things up by using caching on various levels.
\ No newline at end of file
diff --git a/_posts/10-02-01-Bytecode-Cache.md b/_posts/10-02-01-Bytecode-Cache.md
new file mode 100644
index 0000000..1c35c10
--- /dev/null
+++ b/_posts/10-02-01-Bytecode-Cache.md
@@ -0,0 +1,17 @@
+---
+isChild: true
+---
+
+## Bytecode Cache
+
+When PHP file is executed, under the hood it is first compiled to bytecode (also known as opcode) and only then, the bytecode is executed.
+If PHP file is not modified, then bytecode will always be same, which means that compilation step is a waste of CPU resources.
+
+This is where Bytecode cache comes in - it prevents redundant compilation by storing bytecode in memory and reusing it on successive calls.
+Setting up bytecode cache is a matter of minutes and your application will speed up significantly, there's really no reason not to use it.
+
+Popular bytecodes caches are:
+
+[APC](http://php.net/manual/en/book.apc.php)
+[xCache](http://xcache.lighttpd.net/)
+[Zend Optimizer+](http://www.zend.com/products/server/) (part of Zend Server package)
\ No newline at end of file
diff --git a/_posts/10-01-01-Libraries-and-Frameworks.md b/_posts/11-01-01-Libraries-and-Frameworks.md
similarity index 100%
rename from _posts/10-01-01-Libraries-and-Frameworks.md
rename to _posts/11-01-01-Libraries-and-Frameworks.md
diff --git a/_posts/11-01-01-Resources.md b/_posts/12-01-01-Resources.md
similarity index 100%
rename from _posts/11-01-01-Resources.md
rename to _posts/12-01-01-Resources.md