change permalinks
This commit is contained in:
Lukasz Skotarek
parent
63f9168258
commit
a8f4b86046
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/03/01/hello-world/
|
http://dreat.info/2017-03-01-hello-world/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-03-01 09:05:29
|
post_date: 2017-03-01 09:05:29
|
||||||
---
|
---
|
||||||
|
|
@ -21,4 +21,4 @@ I chose to make a port of old game - The Settlers II in Elixir. Being more speci
|
||||||
<li>It's a scary challenge</li>
|
<li>It's a scary challenge</li>
|
||||||
<li>I love this game</li>
|
<li>I love this game</li>
|
||||||
</ul>
|
</ul>
|
||||||
I will deep dive into details with next posts. Also, expect at least one commit per week! Here's <a href="https://github.com/Dreat/OpenSettlersII">repository </a>for the project on GitHub for you to follow.
|
I will deep dive into details with next posts. Also, expect at least one commit per week! Here's <a href="https://github.com/Dreat/OpenSettlersII">repository </a>for the project on GitHub for you to follow.
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/03/08/opensettlersii-0/
|
http://dreat.info/2017-03-08-opensettlersii-0/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-03-08 07:00:08
|
post_date: 2017-03-08 07:00:08
|
||||||
---
|
---
|
||||||
|
|
@ -29,4 +29,4 @@ This is just a simple project initialization, but it shows the tools Elixir is s
|
||||||
|
|
||||||
Next commits will be more interesting, I promise.
|
Next commits will be more interesting, I promise.
|
||||||
|
|
||||||
<em>*we're talking about 99.9999999% availability/uptime here</em>
|
<em>*we're talking about 99.9999999% availability/uptime here</em>
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/03/12/chicago-vs-london-tdd/
|
http://dreat.info/2017-03-12-chicago-vs-london-tdd/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-03-12 22:04:29
|
post_date: 2017-03-12 22:04:29
|
||||||
---
|
---
|
||||||
|
|
@ -33,4 +33,4 @@ Because maybe there's more to writing tests than just Assert.AreEqual(expected,
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
PS: Both ways are equally important and have their own purpose. Don't just focus only on one and you should be fine.
|
PS: Both ways are equally important and have their own purpose. Don't just focus only on one and you should be fine.
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/03/17/introduction-to-integration/
|
http://dreat.info/2017-03-17-introduction-to-integration/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-03-17 07:00:26
|
post_date: 2017-03-17 07:00:26
|
||||||
---
|
---
|
||||||
|
|
@ -29,4 +29,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).
|
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 <a href="http://dreat.info/2017/03/26/integration-series-messaging/">the next post in series</a>.
|
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 <a href="http://dreat.info/2017-03-26-integration-series-messaging/">the next post in series</a>.
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/03/23/opensettlersii-1/
|
http://dreat.info/2017-03-23-opensettlersii-1/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-03-23 07:00:25
|
post_date: 2017-03-23 07:00:25
|
||||||
---
|
---
|
||||||
|
|
@ -36,4 +36,4 @@ Bytes are represented in Elixir as <<values>>. It's quite useful to
|
||||||
|
|
||||||
As for functional language specific stuff, please take a look at multiple definitions of private method decode_flags. It's the pattern matching on functions (yup, can do it better here) - elixir will look for matching function and will call it. It's simple and quite powerful feature.
|
As for functional language specific stuff, please take a look at multiple definitions of private method decode_flags. It's the pattern matching on functions (yup, can do it better here) - elixir will look for matching function and will call it. It's simple and quite powerful feature.
|
||||||
|
|
||||||
In the next commit(s) and post I will make those encode/decode functions more general to be able to work on all sized frames. And hopefully more ;)
|
In the next commit(s) and post I will make those encode/decode functions more general to be able to work on all sized frames. And hopefully more ;)
|
||||||
|
|
|
||||||
|
|
@ -5,11 +5,11 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/03/26/integration-series-messaging/
|
http://dreat.info/2017-03-26-integration-series-messaging/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-03-26 20:50:50
|
post_date: 2017-03-26 20:50:50
|
||||||
---
|
---
|
||||||
<a href="http://dreat.info/2017/03/17/introduction-to-integration/">Last time</a> we spoke about some integration methods we can use.
|
<a href="http://dreat.info/2017-03-17-introduction-to-integration/">Last time</a> 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).
|
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).
|
||||||
|
|
||||||
|
|
@ -19,4 +19,4 @@ And here messaging comes to play. The rules are simple: you create message, send
|
||||||
<li>Decoupling. Messages will be sent to message channel without knowing almost anything about receiver. The common interface are the types of messages sent, not the bidings between apps. It also allows separation integration developement from application developement.</li>
|
<li>Decoupling. Messages will be sent to message channel without knowing almost anything about receiver. The common interface are the types of messages sent, not the bidings between apps. It also allows separation integration developement from application developement.</li>
|
||||||
<li>Frequent, small messages allow applications to behave almost immediatly by sending more messages.</li>
|
<li>Frequent, small messages allow applications to behave almost immediatly by sending more messages.</li>
|
||||||
</ol>
|
</ol>
|
||||||
And many more we'll explore in the series. Why I will write a series on it? The main disadvantage of messaging is the learning curve. While other methods are fairly easy to use, messaging and async thinking is not something we're used to. But once learned this concepts will help you not only when integrating lots of enormous applications. You can also apply it to "integrate" classes/functions/actors in your code.
|
And many more we'll explore in the series. Why I will write a series on it? The main disadvantage of messaging is the learning curve. While other methods are fairly easy to use, messaging and async thinking is not something we're used to. But once learned this concepts will help you not only when integrating lots of enormous applications. You can also apply it to "integrate" classes/functions/actors in your code.
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/03/31/rabbitmq-vs-zeromq/
|
http://dreat.info/2017-03-31-rabbitmq-vs-zeromq/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-03-31 21:58:32
|
post_date: 2017-03-31 21:58:32
|
||||||
---
|
---
|
||||||
|
|
@ -29,4 +29,4 @@ I decided to go with ZeroMQ for reasons stated above, but there's one more reaso
|
||||||
|
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/04/02/opensettlersii-2/
|
http://dreat.info/2017-04-02-opensettlersii-2/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-04-02 21:05:54
|
post_date: 2017-04-02 21:05:54
|
||||||
---
|
---
|
||||||
|
|
@ -23,4 +23,4 @@ I added 2 tests to correctly decode long frames, for both command and message. W
|
||||||
Now onward to code itself. There's only one public decode function, but it calls one of the private ones depending of the flag. There's a pattern matching on <em>long </em>key, and binary data. As you can see here I used <em>::size </em>accordingly.
|
Now onward to code itself. There's only one public decode function, but it calls one of the private ones depending of the flag. There's a pattern matching on <em>long </em>key, and binary data. As you can see here I used <em>::size </em>accordingly.
|
||||||
What's worth noting is if you want to match against <em>unknown sized</em> binary data you can use ::binary. Here I used it for body and for "rest" in main function - as before getting flags I don't care about size and body.
|
What's worth noting is if you want to match against <em>unknown sized</em> binary data you can use ::binary. Here I used it for body and for "rest" in main function - as before getting flags I don't care about size and body.
|
||||||
|
|
||||||
And that's it! Not a lot, but I learnt a bit when it comes to working with binary data in Elixir and made code a bit "better".
|
And that's it! Not a lot, but I learnt a bit when it comes to working with binary data in Elixir and made code a bit "better".
|
||||||
|
|
|
||||||
|
|
@ -17,4 +17,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).
|
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 - <a href="http://www.erlang-factory.com/rome2017#home">I'm going to Erlang Factory Lite</a> 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 - <a href="http://www.erlang-factory.com/rome2017#home">I'm going to Erlang Factory Lite</a> tomorrow. I will try to write down as much as possible and make a interesting review next week, so stay tuned!
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/04/08/today-i-learned-0/
|
http://dreat.info/2017-04-08-today-i-learned-0/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-04-08 07:00:54
|
post_date: 2017-04-08 07:00:54
|
||||||
---
|
---
|
||||||
|
|
@ -16,4 +16,4 @@ Turns out that around 3.5 you don't have to do it. If you provide class with no
|
||||||
<ol>
|
<ol>
|
||||||
<li>You will lose some of features, like naming, being able to serialize private properties, declaring something as required. While some can be more useful than others in specific scenarios - just ask yourself - should you really send private data? ;)</li>
|
<li>You will lose some of features, like naming, being able to serialize private properties, declaring something as required. While some can be more useful than others in specific scenarios - just ask yourself - should you really send private data? ;)</li>
|
||||||
<li><strong>And this is important!</strong> If you dare to use <em>[DataMember]</em> on <em>some</em> properties - only those will be serialized.</li>
|
<li><strong>And this is important!</strong> If you dare to use <em>[DataMember]</em> on <em>some</em> properties - only those will be serialized.</li>
|
||||||
</ol>
|
</ol>
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/04/17/erlang-factory-lite-rome-2017-0/
|
http://dreat.info/2017-04-17-erlang-factory-lite-rome-2017-0/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-04-17 14:12:07
|
post_date: 2017-04-17 14:12:07
|
||||||
---
|
---
|
||||||
|
|
@ -48,4 +48,4 @@ Basically a explanation how <a href="https://github.com/basho/riak_core">Riak Co
|
||||||
<blockquote>
|
<blockquote>
|
||||||
<p style="text-align: center;"><strong>Always</strong> timeout!</p>
|
<p style="text-align: center;"><strong>Always</strong> timeout!</p>
|
||||||
</blockquote>
|
</blockquote>
|
||||||
<p style="text-align: left;">I've covered 5 out of 9 talks, so there's still material for next part, stay tuned!</p>
|
<p style="text-align: left;">I've covered 5 out of 9 talks, so there's still material for next part, stay tuned!</p>
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/04/23/opensettlers4/
|
http://dreat.info/2017-04-23-opensettlers4/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-04-23 21:35:21
|
post_date: 2017-04-23 21:35:21
|
||||||
---
|
---
|
||||||
|
|
@ -15,4 +15,4 @@ I really need to spend more time. Today I struggled a lot with bitstrings. And s
|
||||||
|
|
||||||
After push thou I saw a better solution - I could do pattern match on functions, so I could eliminate switch. I get a lot of mess with all those maps. I think that rethinking/refactoring it should happen sooner than I initially thought.
|
After push thou I saw a better solution - I could do pattern match on functions, so I could eliminate switch. I get a lot of mess with all those maps. I think that rethinking/refactoring it should happen sooner than I initially thought.
|
||||||
|
|
||||||
Also "size" field seems a bit off. Additionally I don't feel as comfortable enough with specification as I was expecting, so I guess I'll spend some more time with it - this should also get me up to speed.
|
Also "size" field seems a bit off. Additionally I don't feel as comfortable enough with specification as I was expecting, so I guess I'll spend some more time with it - this should also get me up to speed.
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/04/30/erlang-factory-lite-rome-2017-1/
|
http://dreat.info/2017-04-30-erlang-factory-lite-rome-2017-1/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-04-30 22:36:46
|
post_date: 2017-04-30 22:36:46
|
||||||
---
|
---
|
||||||
|
|
@ -63,4 +63,4 @@ Basically it was how to use the Ecto and how to query the database. I really don
|
||||||
<h3 class="talk-title" style="text-align: center;">Monitoring and Pre-emptive support: The road to five nines on the Beam <em>by <span class="modal_speaker_name">Francesco Cesarini</span></em></h3>
|
<h3 class="talk-title" style="text-align: center;">Monitoring and Pre-emptive support: The road to five nines on the Beam <em>by <span class="modal_speaker_name">Francesco Cesarini</span></em></h3>
|
||||||
It was a great talk with a lot of focusing on "no single point of failure" "we need at least 2 of everything". He showed 2 types of monitoring usefulness - you can prevent failures, or do quick post-mortems. With monitoring you can prove your innocence in 1.5 minutes - without trying to replicate the bug and trying to debug. While there's a lot to be said - he said so many cool stories I guess you have to go and give it a listen yourself - <a href="https://www.youtube.com/watch?v=EHqs_RrVMoE" target="_blank" rel="noopener noreferrer">this one seems almost identical.</a>
|
It was a great talk with a lot of focusing on "no single point of failure" "we need at least 2 of everything". He showed 2 types of monitoring usefulness - you can prevent failures, or do quick post-mortems. With monitoring you can prove your innocence in 1.5 minutes - without trying to replicate the bug and trying to debug. While there's a lot to be said - he said so many cool stories I guess you have to go and give it a listen yourself - <a href="https://www.youtube.com/watch?v=EHqs_RrVMoE" target="_blank" rel="noopener noreferrer">this one seems almost identical.</a>
|
||||||
|
|
||||||
And this was it - it was a great experience and possibility to talk with those people was sometimes eye-opening.
|
And this was it - it was a great experience and possibility to talk with those people was sometimes eye-opening.
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/04/30/opensettlers5/
|
http://dreat.info/2017-04-30-opensettlers5/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-04-30 22:37:21
|
post_date: 2017-04-30 22:37:21
|
||||||
---
|
---
|
||||||
|
|
@ -15,4 +15,4 @@ Here's a thing I struggled while doing previous commit - decoding command to som
|
||||||
|
|
||||||
It seems like you have to use <em>::binary-size</em> for the first one, and just <em>::binary</em> for the rest - I may be wrong thou and I will have to research that more in the future.
|
It seems like you have to use <em>::binary-size</em> for the first one, and just <em>::binary</em> for the rest - I may be wrong thou and I will have to research that more in the future.
|
||||||
|
|
||||||
It's slowly starting to be a mess - that's why I refactored enconding a bit to make a use of pattern matching. Not it's more "elixir style". Still I feel the lack of the bigger picture - I guess rushing into it wasn't as good idea as first though ;) I will have to do some more research and maybe a post on a protocol - it will surely help me. For example - turns out that command will never have "more" frames incoming - as you can see in changes in code - now all command have "more" set as false (with is quite redundant).
|
It's slowly starting to be a mess - that's why I refactored enconding a bit to make a use of pattern matching. Not it's more "elixir style". Still I feel the lack of the bigger picture - I guess rushing into it wasn't as good idea as first though ;) I will have to do some more research and maybe a post on a protocol - it will surely help me. For example - turns out that command will never have "more" frames incoming - as you can see in changes in code - now all command have "more" set as false (with is quite redundant).
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/05/13/elixir-conf-eu/
|
http://dreat.info/2017-05-13-elixir-conf-eu/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-05-13 20:00:59
|
post_date: 2017-05-13 20:00:59
|
||||||
---
|
---
|
||||||
|
|
@ -21,4 +21,4 @@ Another thing is <a href="http://www.purescript.org/" target="_blank" rel="noope
|
||||||
|
|
||||||
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)!
|
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)!
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/05/14/opensettlersii-6/
|
http://dreat.info/2017-05-14-opensettlersii-6/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-05-14 20:38:02
|
post_date: 2017-05-14 20:38:02
|
||||||
---
|
---
|
||||||
|
|
@ -17,4 +17,4 @@ This commit is not really that different from other, yet I started using Elixir
|
||||||
|
|
||||||
Also, encoding and decoding version - I have no way of validating it, but I'm not sure if I should. This is one of two things I need to check before proceeding - another one being the Signature - I'm not sure if it's version specific or not, so that's something to get to know before coding it.
|
Also, encoding and decoding version - I have no way of validating it, but I'm not sure if I should. This is one of two things I need to check before proceeding - another one being the Signature - I'm not sure if it's version specific or not, so that's something to get to know before coding it.
|
||||||
|
|
||||||
And that's it for now :)
|
And that's it for now :)
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/05/20/property-testing/
|
http://dreat.info/2017-05-20-property-testing/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-05-20 19:00:38
|
post_date: 2017-05-20 19:00:38
|
||||||
---
|
---
|
||||||
|
|
@ -22,4 +22,4 @@ QuickCheck then generates data, runs n tests using this random data and if it fi
|
||||||
|
|
||||||
While it’s all fun, I’m still not sure what are the cases in a commercial code where this is the best approach. Also, turns out that properties also form kind of patterns – and I’m yet to learn about all this.
|
While it’s all fun, I’m still not sure what are the cases in a commercial code where this is the best approach. Also, turns out that properties also form kind of patterns – and I’m yet to learn about all this.
|
||||||
|
|
||||||
Nevertheless, I’m quite hyped and want to learn more – it seems more of easy to get, hard to master useful tool than a novelty, but only time will tell.
|
Nevertheless, I’m quite hyped and want to learn more – it seems more of easy to get, hard to master useful tool than a novelty, but only time will tell.
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/06/12/end-of-getnoticed/
|
http://dreat.info/2017-06-12-end-of-getnoticed/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-06-12 07:00:19
|
post_date: 2017-06-12 07:00:19
|
||||||
---
|
---
|
||||||
|
|
@ -13,4 +13,4 @@ Hello!
|
||||||
|
|
||||||
GetNoticed competition ended with the start of June. I didn't make it to the finalists' list, but I still am proud that I managed to do something. What's next? Will I abandon writing/coding OSII? Definitely not! I've had some busy time with music, so I stepped back a little, but also "cleared my mind" with something new, which I will write about. I still want to finish at least ZMTP part of OSII, I still want to write - end of competition changes only the recurring times of blog posts. I will try to write at least once a week now - not twice as stated in competition rules.
|
GetNoticed competition ended with the start of June. I didn't make it to the finalists' list, but I still am proud that I managed to do something. What's next? Will I abandon writing/coding OSII? Definitely not! I've had some busy time with music, so I stepped back a little, but also "cleared my mind" with something new, which I will write about. I still want to finish at least ZMTP part of OSII, I still want to write - end of competition changes only the recurring times of blog posts. I will try to write at least once a week now - not twice as stated in competition rules.
|
||||||
|
|
||||||
That's it for now! See you soon! :)
|
That's it for now! See you soon! :)
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/06/23/today-i-learned-1/
|
http://dreat.info/2017-06-23-today-i-learned-1/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-06-23 21:22:01
|
post_date: 2017-06-23 21:22:01
|
||||||
---
|
---
|
||||||
|
|
@ -47,4 +47,4 @@ using (var ctx = new Context())
|
||||||
}
|
}
|
||||||
[/csharp]
|
[/csharp]
|
||||||
|
|
||||||
It's nice and saves some typing! :)
|
It's nice and saves some typing! :)
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/07/02/purescript-the-first-look/
|
http://dreat.info/2017-07-02-purescript-the-first-look/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-07-02 22:13:20
|
post_date: 2017-07-02 22:13:20
|
||||||
---
|
---
|
||||||
|
|
@ -28,4 +28,4 @@ The good:
|
||||||
<li>The community seems small but nice</li>
|
<li>The community seems small but nice</li>
|
||||||
<li>Error messages are really, really helpful!</li>
|
<li>Error messages are really, really helpful!</li>
|
||||||
</ul>
|
</ul>
|
||||||
As you can see, there are way more "goods" than "bads". Should you try it? Definitely? Should you use it in your pet project? Sure! Should you use it in production? It depends ;) After going with dotnet core RC1 in production I'd say "hell yeah" but this requires the team that wants (not "<em>can</em>"; <strong>want!</strong>) to handle it, so my answer here is "it depends". Nevertheless, I'm hyped and will do something more with it, but the break is over and I'm heading back to Beam world now.
|
As you can see, there are way more "goods" than "bads". Should you try it? Definitely? Should you use it in your pet project? Sure! Should you use it in production? It depends ;) After going with dotnet core RC1 in production I'd say "hell yeah" but this requires the team that wants (not "<em>can</em>"; <strong>want!</strong>) to handle it, so my answer here is "it depends". Nevertheless, I'm hyped and will do something more with it, but the break is over and I'm heading back to Beam world now.
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/09/14/today-i-learned-2/
|
http://dreat.info/2017-09-14-today-i-learned-2/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-09-14 07:00:35
|
post_date: 2017-09-14 07:00:35
|
||||||
---
|
---
|
||||||
|
|
@ -17,4 +17,4 @@ If you have anything keyboard-changing installed already (like Resharper) - rese
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Bonus round: For VisualStudio Code - just install a <a href="https://github.com/VSCodeVim/Vim">plugin</a>, it works great!
|
Bonus round: For VisualStudio Code - just install a <a href="https://github.com/VSCodeVim/Vim">plugin</a>, it works great!
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/09/27/today-i-learned-3-solving-comeonin-problems-on-windows/
|
http://dreat.info/2017-09-27-today-i-learned-3-solving-comeonin-problems-on-windows/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-09-27 07:00:52
|
post_date: 2017-09-27 07:00:52
|
||||||
---
|
---
|
||||||
|
|
@ -32,4 +32,4 @@ Here's what you do if you stumble with deps error
|
||||||
</ol>
|
</ol>
|
||||||
And I used the second way while developing something mine. Works like a charm. As for me algorithm didn't really matter (each own has it's own pros and cons) I went with the least problematic one.
|
And I used the second way while developing something mine. Works like a charm. As for me algorithm didn't really matter (each own has it's own pros and cons) I went with the least problematic one.
|
||||||
|
|
||||||
PS: What's funny for some there's no need for being in the same console/repeating those steps, but I wasn't that lucky :(
|
PS: What's funny for some there's no need for being in the same console/repeating those steps, but I wasn't that lucky :(
|
||||||
|
|
|
||||||
|
|
@ -5,7 +5,7 @@ author: dreat
|
||||||
post_excerpt: ""
|
post_excerpt: ""
|
||||||
layout: post
|
layout: post
|
||||||
permalink: >
|
permalink: >
|
||||||
http://dreat.info/2017/12/12/spawnfest-2017/
|
http://dreat.info/2017-12-12-spawnfest-2017/
|
||||||
published: true
|
published: true
|
||||||
post_date: 2017-12-12 20:31:22
|
post_date: 2017-12-12 20:31:22
|
||||||
---
|
---
|
||||||
|
|
@ -21,4 +21,4 @@ Application to monitor plants. We planned to have thermometer and proximity sens
|
||||||
Finally "warning" button is pressed, and buzzer turns on. "Warning" button is a switch, so pressing it again turns the buzzer off.
|
Finally "warning" button is pressed, and buzzer turns on. "Warning" button is a switch, so pressing it again turns the buzzer off.
|
||||||
<p style="text-align: center;"><a href="https://twitter.com/Dreat_/status/939890791115296768" target="_blank" rel="noopener">VIDEO</a></p>
|
<p style="text-align: center;"><a href="https://twitter.com/Dreat_/status/939890791115296768" target="_blank" rel="noopener">VIDEO</a></p>
|
||||||
</blockquote>
|
</blockquote>
|
||||||
See you next year! :)
|
See you next year! :)
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue