diff --git a/_posts/2017-03-01-hello-world.md b/_posts/2017-03-01-hello-world.md
index ed93262..add4c56 100644
--- a/_posts/2017-03-01-hello-world.md
+++ b/_posts/2017-03-01-hello-world.md
@@ -7,7 +7,7 @@ published: true
layout: post
post_date: 2017-03-01 09:05:29
---
-I decided to participate in GetNoticed. Short story even shorter, it's about writing OpenSource code and blog about it (and IT).
+I decided to participate in GetNoticed. Short story even shorter, it's about writing OpenSource code and blog about it (and IT).
I chose to make a port of old game - The Settlers II in Elixir. Being more specific I will focus only (or mainly) on backend. Why?
diff --git a/_posts/2017-03-17-introduction-to-integration.md b/_posts/2017-03-17-introduction-to-integration.md
index 310193e..b86961f 100644
--- a/_posts/2017-03-17-introduction-to-integration.md
+++ b/_posts/2017-03-17-introduction-to-integration.md
@@ -27,4 +27,4 @@ Sometimes sharing data is not enough, because data changes may require actions i
It may loosen the coupling, but it's still quite tight. In particular doing things in particular order can lead to muddy mess. While developers know how to write procedures (it's what we do all the time, right?) and it may seem like a good thing it's actually not so good. It's easy to forget that we're not calling local procedure and that it will take more time or can fail due to multiple reasons. Due to this thinking also quite tight coupling arises (as stated before).
-As always, there's always a tradeoff. But do we have the best approach here? Or can we do even better? I'll address these questions in the next post in series.
+As always, there's always a tradeoff. But do we have the best approach here? Or can we do even better? I'll address these questions in the next post in series.
diff --git a/_posts/2017-03-26-integration-series-messaging.md b/_posts/2017-03-26-integration-series-messaging.md
index 9d90710..256ff13 100644
--- a/_posts/2017-03-26-integration-series-messaging.md
+++ b/_posts/2017-03-26-integration-series-messaging.md
@@ -7,7 +7,7 @@ layout: post
published: true
post_date: 2017-03-26 20:50:50
---
-Last time we spoke about some integration methods we can use.
+Last time we spoke about some integration methods we can use.
As we see, there are methods that are not so tight coupled, being able to generate lots of little data packages (like file transfer), easily synchronizable (like shared database), details of storage's structure hidden from applications (unlike shared database) and being able to send data to invoke behavior in other app (like RPI) but with being resistant to failure (unlike RPI).
diff --git a/_posts/2017-04-06-opensettlersii-3.md b/_posts/2017-04-06-opensettlersii-3.md
index f2fa073..265b601 100644
--- a/_posts/2017-04-06-opensettlersii-3.md
+++ b/_posts/2017-04-06-opensettlersii-3.md
@@ -15,4 +15,4 @@ I added encoding of long frames. I did the same thing as in decoding, pattern ma
In tests file I added 2 tests for long frames and changed body: property in input to be binary as well. I think it's starting to be a good time to introduce some struct for my frames, but I will worry about this later. I'm also not happy with return values - they should be more "elixiry", so next step will be worrying about this (with some explanation what does it mean).
-As I dislike post trailers - I'm going to Erlang Factory Lite tomorrow. I will try to write down as much as possible and make a interesting review next week, so stay tuned!
+As I dislike post trailers - I'm going to Erlang Factory Lite tomorrow. I will try to write down as much as possible and make a interesting review next week, so stay tuned!
diff --git a/_posts/2017-04-17-erlang-factory-lite-rome-2017-0.md b/_posts/2017-04-17-erlang-factory-lite-rome-2017-0.md
index 8e7c947..ffd5c58 100644
--- a/_posts/2017-04-17-erlang-factory-lite-rome-2017-0.md
+++ b/_posts/2017-04-17-erlang-factory-lite-rome-2017-0.md
@@ -11,7 +11,7 @@ Week ago I went to Rome to take part in Erlang Factory Lite, and, as promised, h
Starting with venue - it was near the centre of the city, easy to get with decent views. While inside was quite small (not a lot of people were there as well), the outside...
-[caption id="attachment_101" align="aligncenter" width="300"]
What a place to take a break![/caption]
+[caption id="attachment_101" align="aligncenter" width="300"] What a place to take a break![/caption]
@@ -37,7 +37,7 @@ This was talk full with nice theory. Michele defined a formula somethin
Nice thingies:
- - One thing to remember? Read this paper
+ - One thing to remember? Read this paper
- Basically wiki article around this talk
- Duck typing? No! It's untyped and it's fine!
diff --git a/_posts/2017-04-30-erlang-factory-lite-rome-2017-1.md b/_posts/2017-04-30-erlang-factory-lite-rome-2017-1.md
index 58f0767..1c2b13a 100644
--- a/_posts/2017-04-30-erlang-factory-lite-rome-2017-1.md
+++ b/_posts/2017-04-30-erlang-factory-lite-rome-2017-1.md
@@ -7,9 +7,9 @@ layout: post
published: true
post_date: 2017-04-30 22:36:46
---
-Hello for the second (and last) part of EFL Rome2017 post! You can find previous one here
+Hello for the second (and last) part of EFL Rome2017 post! You can find previous one here
Music and Message Passing Concurrency by Joe Armstrong
-Here goes the big name, Joe himself. While it may suggest a lot about music, it was more about messaging and integration. Joe showed how he could remotely control Sonic Pi. He was glad that there's an other way to control a program "than clicking a bloody mouse!".
+Here goes the big name, Joe himself. While it may suggest a lot about music, it was more about messaging and integration. Joe showed how he could remotely control Sonic Pi. He was glad that there's an other way to control a program "than clicking a bloody mouse!".
He did that sending properly coded messages to UDP port. And here it all started. Joe is a big supporter of messaging based communication. API suposes a programming language, so it's not a best way - you're tied to programming language. As the main topic emerged once again - how to integrate and there are some programming languages better to do other things - so you'd naturally like to use them for specific purposes and not be stuck with one.
@@ -19,9 +19,9 @@ You should also treat specific parts/modules/apps like a black boxes - you know
- Pick encoding (XML/JSON/YAML/etc)
- Pick protocol description (RFC/UBF/etc)
-[caption id="attachment_102" align="aligncenter" width="300"]
Some combinations for you to pick from[/caption]
+[caption id="attachment_102" align="aligncenter" width="300"] Some combinations for you to pick from[/caption]
-[caption id="attachment_117" align="aligncenter" width="300"]
With the Joe himself![/caption]
+[caption id="attachment_117" align="aligncenter" width="300"] With the Joe himself![/caption]
Joe picked OSC over TCP/UPD with some English to describe it. OSC is a very simple encoding - and it has "simplicity by design", as Joe said, "if you can't create complex data structures, the interface will be simple and easy to understand".
"if you can't create complex data structures, the interface will be simple and easy to understand"
@@ -51,9 +51,9 @@ He describes himself as a Mad Scientist - and, boy, he is!
Basically it was a little trivia on the Internet and his attempt to do a small replica of it's routing system using Elixir (and nerves). He had 2 RP3s connected, simulating North America and Europe with routing links. There's a bit of how the Internet works and how it connects - he used that common knowledge to simulate it and it worked like a charm. There a code online if you want to look at it!
-[caption id="attachment_103" align="aligncenter" width="300"]
This is the Internet! Be careful not to break it![/caption]
+[caption id="attachment_103" align="aligncenter" width="300"] This is the Internet! Be careful not to break it![/caption]
-The real show started when he took the router, connected third Rasp and added Asia - it all worked! It was a nice show for the Nerves project to show what you can do with them. Funny thing - the most problems, and the slowest part was HTML+JS frontend where all the arrows where hacked as separate CSS elements - so it crashed when connection number rose. Still, great project and you can look at it on github!
+The real show started when he took the router, connected third Rasp and added Asia - it all worked! It was a nice show for the Nerves project to show what you can do with them. Funny thing - the most problems, and the slowest part was HTML+JS frontend where all the arrows where hacked as separate CSS elements - so it crashed when connection number rose. Still, great project and you can look at it on github!
Embrace the Database with Ecto by Josh Branchaud
Basically it was how to use the Ecto and how to query the database. I really don't know if it was the high temperature in the room, or it was just quite obvious to me - but I cannot say that I didn't find anything at all - there was one statement that I won't say if I find true or false - because it's strengh is that it provokes some interesting conversations:
diff --git a/_posts/2017-05-13-elixir-conf-eu.md b/_posts/2017-05-13-elixir-conf-eu.md
index 7434201..677ada5 100644
--- a/_posts/2017-05-13-elixir-conf-eu.md
+++ b/_posts/2017-05-13-elixir-conf-eu.md
@@ -15,7 +15,7 @@ I have some stuff to share, less now, more later when I deep dive into them.
First, there's something called QuickCheck. It's enables to do Property Testing - I'm not feeling comfortable enough with my knowledge of this subject to try explaning it, but I'm looking forward getting to know it more and write about it here!
-Another thing is PureScript (looks like you can read a recommended book here for free!). It's compiled to JavaScript (as all of those new front-end stuff), but apparently you can also compile to Erlang and some other as well! It's influenced by Haskell, more elastic and powerful than Elm (which is easy to learn, but apparently if your app doesn't fit Elm's architecture you will have a lot of pain). I never did anything serious in frontend from start to finish (I did some work with React + Cerebral, but I wouldn't call myself front-end specialist) so I guess this could be an interesting start.
+Another thing is PureScript (looks like you can read a recommended book here for free!). It's compiled to JavaScript (as all of those new front-end stuff), but apparently you can also compile to Erlang and some other as well! It's influenced by Haskell, more elastic and powerful than Elm (which is easy to learn, but apparently if your app doesn't fit Elm's architecture you will have a lot of pain). I never did anything serious in frontend from start to finish (I did some work with React + Cerebral, but I wouldn't call myself front-end specialist) so I guess this could be an interesting start.
Nerves strikes again, as this time distributed computing on Rasps was shown. It's nice to see that this project grows. And also: nice project to get started: make temperature controller for beer fermentation (old fridge, old lightbulb for hear and rasp pi running nerves)!
diff --git a/_posts/2017-09-14-today-i-learned-2.md b/_posts/2017-09-14-today-i-learned-2.md
index 623ce49..b610437 100644
--- a/_posts/2017-09-14-today-i-learned-2.md
+++ b/_posts/2017-09-14-today-i-learned-2.md
@@ -7,7 +7,7 @@ layout: post
published: true
post_date: 2017-09-14 07:00:35
---
-While a back ago I did a little test. I read the Deliberate Vim book, did the exercises and decided to go full Vim. So I installed ViEmu to my VisualStudio 2015. Aaaand had a few struggles. Some shortcuts conflicts that I had to solve manually and still it wasn't so convenient to use.
+While a back ago I did a little test. I read the Deliberate Vim book, did the exercises and decided to go full Vim. So I installed ViEmu to my VisualStudio 2015. Aaaand had a few struggles. Some shortcuts conflicts that I had to solve manually and still it wasn't so convenient to use.
I ended up skipping ViEmu for VS2017. But it didn't last for long - one day I noticed I'm really used to some of the Vim commands and it's more difficult to work now without them. So I did some research, and got a great recipe!
What a place to take a break![/caption]
+[caption id="attachment_101" align="aligncenter" width="300"]
What a place to take a break![/caption]
@@ -37,7 +37,7 @@ This was talk full with nice theory. Michele defined a formula somethin
Nice thingies:
Some combinations for you to pick from[/caption]
+[caption id="attachment_102" align="aligncenter" width="300"]
Some combinations for you to pick from[/caption]
-[caption id="attachment_117" align="aligncenter" width="300"]
With the Joe himself![/caption]
+[caption id="attachment_117" align="aligncenter" width="300"]
With the Joe himself![/caption]
Joe picked OSC over TCP/UPD with some English to describe it. OSC is a very simple encoding - and it has "simplicity by design", as Joe said, "if you can't create complex data structures, the interface will be simple and easy to understand".
This is the Internet! Be careful not to break it![/caption]
+[caption id="attachment_103" align="aligncenter" width="300"]
This is the Internet! Be careful not to break it![/caption]
-The real show started when he took the router, connected third Rasp and added Asia - it all worked! It was a nice show for the Nerves project to show what you can do with them. Funny thing - the most problems, and the slowest part was HTML+JS frontend where all the arrows where hacked as separate CSS elements - so it crashed when connection number rose. Still, great project and you can look at it on github!
+The real show started when he took the router, connected third Rasp and added Asia - it all worked! It was a nice show for the Nerves project to show what you can do with them. Funny thing - the most problems, and the slowest part was HTML+JS frontend where all the arrows where hacked as separate CSS elements - so it crashed when connection number rose. Still, great project and you can look at it on github!