My name is Bartosz Konieczny and welcome to my blog. I'm a software engineer focused mainly on Big Data (Spark, Kafka), JVM platform (Scala, Java) and NoSQL databases (Cassandra, Elasticsearch) topics. I'm a big fan of TDD too.
The main idea behind the posts published here is based on learn and prove that you understood concept. Concretely it means that most of time you'll find some theory, usually at the beginning, followed by some code proofs. I particularly like the idea of learning tests I found in Robert C. Martin book "Clean Code". Shortly speaking, the goal is to test third-part software, something which in TDD we done rarely, with the goal to understand how this software works. Another benefit of it is that you can easily see changes between version. But sometimes it's not possible to define learning tests. In such cases I try to provide another proof: screenshots, videos or metrics.
You can find here a lot of posts that I publish because of some selfish reasons. First of all I wanted to have a centralized place, freely available, to recall the stuff I've already read/tested. Secondly, after reading a lot of more experienced and better engineers than me, I learned that having a blog (or globally explaining technical things) helps to improve programming and interpersonal skills. And finally, for less egoistic reason, through this blog I can give back everything that I learn from the community to the community. I know that maybe some of posts here can be found elsewhere but it's still because of the goal of centralized knowledge place from the first reason.
The topics I focus on can vary on the time. By the past it was a lot of Spring/JPA/Hibernate aspects. Now (since 2015) I'm focused more on NoSQL databases (Cassandra, Elasticsearch) and distributed computing (Hadoop, Spark). Soon I'll try to add some texts about other programming languages that I use and haven't described yet here: Scala and Python. Maybe it'll be as a kind of guide for a Java developer wanting to discover one of them.
The posts are added regularly, once a week. The most often it's one of weekend days but sometimes it can be a different moment. To stay in touch, you can follow waitingforcode on Twitter. If you have some other suggestions about this, feel free to share them with me.
Why waitingforcode.com ? When I was thinking about the domain name for this blog, I was listening my favorite playlist too. Suddenly, an refrain repeating "waiting for" interested me. It was a fragment of Red Hot Chili Peppers song "By the way". Because "waiting for..." plays well with the leitmotif of this blog (learn theory before waiting for code proof), I decided to adopt it as the domain name.
You can find me on:
You can also send me a message if you have some questions about this blog.