9 files changed, 48 insertions, 48 deletions

diff --git a/.jekyll-metadata b/.jekyll-metadata
index ac5a60c..5faba49 100644
--- a/.jekyll-metadata
+++ b/.jekyll-metadata
diff --git a/_posts/2015-11-10-software-development-pitfalls.md b/_posts/2015-11-10-software-development-pitfalls.md
index b10ebc0..5e7279c 100644
--- a/_posts/2015-11-10-software-development-pitfalls.md
+++ b/_posts/2015-11-10-software-development-pitfalls.md
@@ -6,15 +6,15 @@ description: Couple of observations regarding project management.
 
 **Table of contents**
 
-- [Initial thoughts](#initial-thoughts)
-- [Ping emails](#ping-emails)
-- [Everybody is a project manager](#everybody-is-a-project-manager)
-- [We are never wrong](#we-are-never-wrong)
-- [Micromanaging](#micromanaging)
-- [Human contact - no need for it!](#human-contact---no-need-for-it)
-- [MVP is killing innovation](#mvp-is-killing-innovation)
-- [Pressure wasteland](#pressure-wasteland)
-- [Conclusion](#conclusion)
+1. [Initial thoughts](#initial-thoughts)
+2. [Ping emails](#ping-emails)
+3. [Everybody is a project manager](#everybody-is-a-project-manager)
+4. [We are never wrong](#we-are-never-wrong)
+5. [Micromanaging](#micromanaging)
+6. [Human contact - no need for it!](#human-contact---no-need-for-it)
+7. [MVP is killing innovation](#mvp-is-killing-innovation)
+8. [Pressure wasteland](#pressure-wasteland)
+9. [Conclusion](#conclusion)
 
 ## Initial thoughts
 
diff --git a/_posts/2017-01-12-gce-aws-docker-and-why-i-choose-classic-vms-and-digitalocean.md b/_posts/2017-01-12-gce-aws-docker-and-why-i-choose-classic-vms-and-digitalocean.md
index 20dc928..29a3124 100644
--- a/_posts/2017-01-12-gce-aws-docker-and-why-i-choose-classic-vms-and-digitalocean.md
+++ b/_posts/2017-01-12-gce-aws-docker-and-why-i-choose-classic-vms-and-digitalocean.md
@@ -6,10 +6,10 @@ description: Reasons why I choose DigitalOcean for my project
 
 **Table of contents**
 
-- [Docker tools and complexity that comes with it](#docker-tools-and-complexity-that-comes-with-it)
-- [Lack of real life examples of Docker in action](#lack-of-real-life-examples-of-docker-in-action)
-- [Ease of deployment](#ease-of-deployment)
-- [Where to go from here](#where-to-go-from-here)
+1. [Docker tools and complexity that comes with it](#docker-tools-and-complexity-that-comes-with-it)
+2. [Lack of real life examples of Docker in action](#lack-of-real-life-examples-of-docker-in-action)
+3. [Ease of deployment](#ease-of-deployment)
+4. [Where to go from here](#where-to-go-from-here)
 
 I have been developing a product for the past few months and one of product’s requirement is the ability to automatically scale quickly on system’s demand.
 
diff --git a/_posts/2017-03-07-golang-profiling-simplified.md b/_posts/2017-03-07-golang-profiling-simplified.md
index c6cf78e..2b5a262 100644
--- a/_posts/2017-03-07-golang-profiling-simplified.md
+++ b/_posts/2017-03-07-golang-profiling-simplified.md
@@ -6,12 +6,12 @@ description: Golang profiling made easy
 
 **Table of contents**
 
-- [Where are my pprof files?](#where-are-my-pprof-files)
-- [Why is my cpu profile empty?](#why-is-my-cpu-profile-empty)
-- [Profiling](#profiling)
-  - [Memory profiling](#memory-profiling)
-  - [CPU profiling](#cpu-profiling)
-  - [Generating profiling reports](#generating-profiling-reports)
+1. [Where are my pprof files?](#where-are-my-pprof-files)
+2. [Why is my cpu profile empty?](#why-is-my-cpu-profile-empty)
+3. [Profiling](#profiling)
+  1. [Memory profiling](#memory-profiling)
+  2. [CPU profiling](#cpu-profiling)
+  3. [Generating profiling reports](#generating-profiling-reports)
 
 Many posts have been written regarding profiling in Golang and I haven’t found proper tutorial regarding this. Almost all of them are missing some part of important information and it gets pretty frustrating when you have a deadline and are not finding simple distilled solution.
 
diff --git a/_posts/2017-04-17-what-i-ve-learned-developing-ad-server.md b/_posts/2017-04-17-what-i-ve-learned-developing-ad-server.md
index f98808b..1cb3ba1 100644
--- a/_posts/2017-04-17-what-i-ve-learned-developing-ad-server.md
+++ b/_posts/2017-04-17-what-i-ve-learned-developing-ad-server.md
@@ -6,12 +6,12 @@ description: Lessons I learned developing contextual ad server
 
 **Table of contents**
 
-- [Aggregate everything](#aggregate-everything)
-- [Measure everything](#measure-everything)
-- [Cache control is your friend](#cache-control-is-your-friend)
-- [Learn NGINX](#learn-nginx)
-- [Use Redis/Memcached](#use-redismemcached)
-- [Conclusion](#conclusion)
+1. [Aggregate everything](#aggregate-everything)
+2. [Measure everything](#measure-everything)
+3. [Cache control is your friend](#cache-control-is-your-friend)
+4. [Learn NGINX](#learn-nginx)
+5. [Use Redis/Memcached](#use-redismemcached)
+6. [Conclusion](#conclusion)
 
 For the past year and half I have been developing native advertising server that contextually matches ads and displays them in different template forms on variety of websites. This project grew from serving thousands of ads per day to millions.
 
diff --git a/_posts/2017-04-21-profiling-python-web-applications-with-visual-tools.md b/_posts/2017-04-21-profiling-python-web-applications-with-visual-tools.md
index 146bc31..864e4a5 100644
--- a/_posts/2017-04-21-profiling-python-web-applications-with-visual-tools.md
+++ b/_posts/2017-04-21-profiling-python-web-applications-with-visual-tools.md
@@ -6,9 +6,9 @@ description: Missing link when debugging and profiling python web applications
 
 **Table of contents**
 
-- [Simple web-service](#simple-web-service)
-- [Visualize profile](#visualize-profile)
-- [Update 2017-04-22](#update-2017-04-22)
+1. [Simple web-service](#simple-web-service)
+2. [Visualize profile](#visualize-profile)
+3. [Update 2017-04-22](#update-2017-04-22)
 
 I have been profiling my software with KCachegrind for a long time now and I was missing this option when I am developing API's or other web services. I always knew that this is possible but never really took the time and dive into it.
 
diff --git a/_posts/2017-08-11-simple-iot-application.md b/_posts/2017-08-11-simple-iot-application.md
index 68d6e70..4c506f3 100644
--- a/_posts/2017-08-11-simple-iot-application.md
+++ b/_posts/2017-08-11-simple-iot-application.md
@@ -6,14 +6,14 @@ description: Develop simple IOT application with Arduino MKR1000 and Python
 
 **Table of contents**
 
-- [Initial thoughts](#initial-thoughts)
-- [Simple Python API](#simple-python-api)
-  - [Basic web application](#basic-web-application)
-  - [Web application security](#web-application-security)
-  - [Simple API for writing data-points](#simple-api-for-writing-data-points)
-- [Sending data to API with Arduino MKR1000](#sending-data-to-api-with-arduino-mkr1000)
-- [Data visualization](#data-visualization)
-- [Conclusion](#conclusion)
+1. [Initial thoughts](#initial-thoughts)
+2. [Simple Python API](#simple-python-api)
+  1. [Basic web application](#basic-web-application)
+  2. [Web application security](#web-application-security)
+  3. [Simple API for writing data-points](#simple-api-for-writing-data-points)
+3. [Sending data to API with Arduino MKR1000](#sending-data-to-api-with-arduino-mkr1000)
+4. [Data visualization](#data-visualization)
+5. [Conclusion](#conclusion)
 
 ## Initial thoughts
 
diff --git a/_posts/2018-01-16-using-digitalocean-spaces-object-storage-with-fuse.md b/_posts/2018-01-16-using-digitalocean-spaces-object-storage-with-fuse.md
index af9a2c4..dc2b90c 100644
--- a/_posts/2018-01-16-using-digitalocean-spaces-object-storage-with-fuse.md
+++ b/_posts/2018-01-16-using-digitalocean-spaces-object-storage-with-fuse.md
@@ -6,12 +6,12 @@ description: Using DigitalOcean Spaces Object Storage with FUSE
 
 **Table of contents**
 
-- [Is it possible to use them as a mounted drive with FUSE?](#is-it-possible-to-use-them-as-a-mounted-drive-with-fuse)
-- [Will the performance degrade over time and over different sizes of objects?](#will-the-performance-degrade-over-time-and-over-different-sizes-of-objects)
-        - [Measurement experiment 1: File copy](#measurement-experiment-1-file-copy)
-        - [Measurement experiment 2: SQLite performanse](#measurement-experiment-2-sqlite-performanse)
-- [Can storage be mounted on multiple machines at the same time and be writable?](#can-storage-be-mounted-on-multiple-machines-at-the-same-time-and-be-writable)
-- [Observations and conslusion](#observations-and-conslusion)
+1. [Is it possible to use them as a mounted drive with FUSE?](#is-it-possible-to-use-them-as-a-mounted-drive-with-fuse)
+2. [Will the performance degrade over time and over different sizes of objects?](#will-the-performance-degrade-over-time-and-over-different-sizes-of-objects)
+        1. [Measurement experiment 1: File copy](#measurement-experiment-1-file-copy)
+        2. [Measurement experiment 2: SQLite performanse](#measurement-experiment-2-sqlite-performanse)
+3. [Can storage be mounted on multiple machines at the same time and be writable?](#can-storage-be-mounted-on-multiple-machines-at-the-same-time-and-be-writable)
+4. [Observations and conslusion](#observations-and-conslusion)
 
 Couple of months ago [DigitalOcean](https://www.digitalocean.com) introduced new product called [Spaces](https://blog.digitalocean.com/introducing-spaces-object-storage/) which is Object Storage very similar to Amazon's S3. This really peaked my interest, because this was something I was missing and even the thought of going over the internet for such functionality was in no interest to me. Also in fashion with their previous pricing this also is very cheap and pricing page is a no-brainer compared to AWS or GCE. [Prices are clearly and precisely defined and outlined](https://www.digitalocean.com/pricing/). You must love them for that :)
 
diff --git a/_posts/2018-08-05-the-bullshit-web-developments-pov.md b/_posts/2018-08-05-the-bullshit-web-developments-pov.md
index 18b2732..8816b4b 100644
--- a/_posts/2018-08-05-the-bullshit-web-developments-pov.md
+++ b/_posts/2018-08-05-the-bullshit-web-developments-pov.md
@@ -6,12 +6,12 @@ description: State of front-end development and what this does to the future of
 
 **Table of contents**
 
-- [Initial thoughts](#initial-thoughts)
-- [Front-end frameworks](#front-end-frameworks)
-- [Obsolescence to the rescue](#obsolescence-to-the-rescue)
-- [Unnecessary complexity](#unnecessary-complexity)
-- [Speed of development trumps code quality](#speed-of-development-trumps-code-quality)
-- [Load times of most popular websites](#load-times-of-most-popular-websites)
+1. [Initial thoughts](#initial-thoughts)
+2. [Front-end frameworks](#front-end-frameworks)
+3. [Obsolescence to the rescue](#obsolescence-to-the-rescue)
+4. [Unnecessary complexity](#unnecessary-complexity)
+5. [Speed of development trumps code quality](#speed-of-development-trumps-code-quality)
+6. [Load times of most popular websites](#load-times-of-most-popular-websites)
 
 ## Initial thoughts