Thursday, December 15, 2011

My ubiquitous language


I will start this blog with a small digression (why not?).

Language

This is my very first blog post, and I hope that the fact, that I chose English over my native Polish language won't become curse over the time, and my Readers (yes, I dare to assume that I will get some) won't find too many lexical mistakes here.

The world seems to get smaller and smaller nowadays - we can read articles written by inspirational people just after publishing. We can email with them and read their tweets. We can even meet one of our Gurus[1] at a conference in our very home city... ;)

That's why we have to communicate with other Tech-People with a common ubiquitous language.

Like it or lump it - English is that language. So I decided to write in it.

What will I write about

I am interested in creating simple software that solves complicated problems. I like the idea of Domain Driven Design connected with Command Query Responsibility Segregation principle. I also find useful Event Sourcing and bunch of other stuff related to them.

I am an enthusiast of Software Craftsmanship movement and I believe that it will get more and more followers over time.

I also like learning, so the opportunity to learn something new, always motivates me. I think there is no better way to thoroughly understand something, than trying to teach somebody that thing (this is one of the reasons why I have started this blog).

I'm going to write about all of these things mentioned above, putting them in the real context related to my personal experience. Of course, if I find some other interesting topics to write about, I will do it too.

So, my Dear Reader, wish me luck and don't hesitate to give me a feedback.


[1] Guru (also called Teacher) is an extension of a traditional Dreyfus model of skill acquisition. Basically it is said that an Expert can evolve and became something more. He can adjust himself to anyone's level and transfer the accurate amount of knowledge in a way, that his Listener will understand, or at least accept as inspiring for further explorations.

5 comments:

  1. Congratulations! I cross my fingers for your blog and I wait for next articles. I prefer eventual consistency to eventual inconsistency, however;-) I am a big fan of no-SQL, where weak relations between entities lead to weaker consistency i.e. that there exists an intersection of space and time where the data is consistent. Concerning the "Software Craftsmanship" I also prefer excellent people and average processes to average people and excellent processes. Besides, I would also risk a thesis that great software is created not by a big team but usually by one or two persons. Git is a great example - it is an example of good, disruptive change, regardless of what other people think.

    ReplyDelete
  2. So I will be the first person who wish you good luck! I will read your blog.

    ReplyDelete
  3. Wish you good luck! Great intro. It encouraged me to learn about all (new to me) terms you mentioned. Looks like I found a right place to learn about hi-level magic.

    ReplyDelete
  4. @Kazek, Thanks for that. :) I also prefer eventual consistency, what does not mean, that this blog has to be consistent. ;)

    I am starting to look at MongoDb, so maybe you will be able to give me some advices in near future. ;)

    And I must agree with your thoughts about people and processes. ;) I treat processes as a form of clues rather than imperatives. I hope we will have time to talk about those things soon.

    @Krzysiek,
    Thanks for that - I know You will. ;)

    @Tonual,
    Thanks for wishes! I hope you will find things that will match your interests here. And I won't teach magic... Maybe some little tricks. ;)

    ReplyDelete
  5. Good luck and have fun, bro!

    Looking forward to review more of your posts :P

    ReplyDelete