Pragmatic developer

Today, I want to tell you about planning our goal. Why we need to plan our goal and what we should do during the planning. What we need to do during the planning? In my opinion, We should ask to three questions. What we want to do, why and how. The answers to that question will be our plan. Easy, right? I think not, because a lot of time we don't know what, why and how. What? This is globally goal. This should be measurable. Why? We should be able to define the end of this goal. Bad example for that is I would like learn English language, because when is the end of this? When I can talk to other people using English? Maybe when I can write posts on the blog using English? I think you understand now. If you want to learn English you should define your goal like, I would like to write an article about goal without a dictionary. I think this is a good goal. Why? A lot of people skip this step. I think this step is very helpful. We will better understand myself or other people wh

Hi everyone. I was in the programming school and the members asked me a lot about how learn that all knowledge of programming? I had a little advice for them. A lot of people start by reading books and documentation. Sometimes they do tutorials. Yes, this is helpful, but it is only for beginners. If you want to learn more, if you want find something new, I have a solution for you, which is not tiresome. This way of learning is very motivating and interesting for me. Local meetup You can rise your knowledge during talk with the experts or aficionados. They like to share its knowledge. They like to talk about solutions, problems or projects. This knowledge a lot of time is unique and you won't get it anywhere else. Meetups are often loose (pizza, beer, talks). That is a good time to talk with more experienced people. If you want to find some meetups in your town, you should start from the www.meetup.com site. Comapny events A lot of corporations organize the events, where their

Hi, I had a problem with plan my life. Why? I did a lot of tasks every day, but I still stand in the same place. I change my mindset and it is working now. I change a lot of tasks to goal. This method can be used in Scrum, so I want to share you my think. Difference I am starting from show you my definitions of task and goal. The goal for me is the result, which I want to get. For example: I would like to write the application for team cup foosball using Django. The task for me is the piece of way to get the goal. For example: Watch tutorial for creating an application using Django or prepare use cases for application. Why goal is better? Goal has a value. We should focus on a goal, because when we get that we get a value. Of course, sometimes our tasks have the values too, but the core of value is in goal. The value for a lot of tasks is our goal. Example: I want to watch tutorial for creating an application using Django, because I would like to write the application for team cu

Hi everyone. A little bit time before, I have to work with legacy code. I need to extract the two from a lot of functionality. Of course the other functionality can work too. I need only change the way how it works and replace a kind of connection to database, servers and other applications. I made a mistake and I want to share my conclusion for it. How will I do it today? I will get a knowledge. I will get the use cases. I will validate the knowledge with the code and the use cases. I will change only fragment of code, where I must change. The end. Why? Get a knowledge I started from getting a knowledge from my colleague. I ask a lot of questions, get information about core functionality and what they want. If you worked with legacy project you know that knowledge is very poor. My first mistake was I didn't verify that knowledge in the code. I started working with code and three days later I got the blocker. I couldn't do it like I wanted, so next time I will try t

Hi, everyone. I was on a lecture about "Don't change project, change your project." This was interesting, but I saw a bigger problem. The problem is not on the project, the problem is in us. I want to tell you something about my thought. The main problem A lot of people say that Scrum doesn't work, the project is bad, the business is stupid. You know that, right? I think everything can be changed, but how? We always should start from us. We need change our mindset. After it, we can change the problems around us. To confirm my words, I ask you some question. Why your Scrum doesn't work? Maybe you are not agile? Who writes your project now? Why you still write a bad code on this project? Why new part of code you don't write separately? If your business is stupid, why you don't teach it? Why you don't want to help your business to get knowledge? Why you are not a smart business? I think you never think about what should you change in yourself for reso