What are code reviews? Hopefully most of my readers whom are programmers are working in an environment where code reviews are part of the software development process. For those readers who have no idea what those are: code reviews are self-explainatory, it’s a process of reviewing changes (code) submitted by one member by other members working on the same project. Mind you - such reviews were not so popular just a few years back but benefits of including them in software development pipeline made them adapted widely anywhere from open source communities to business teams.

1. What’s CI CI stand for continous integration. The simplest way I could explain what it really is is with an example. Say, you remember when you started your first coding related job, or maybe the second. Hopefully the company/environment provided you with opportunity to review code throughout the team. If so you may have noticed that often it is not the solution itself that takes the most time but the actual codereviews, discussions and merging that is the problem.

1. What’s a hackathon Hackathon’s meaning is partially incuded in it’s name, hack + marathon, marathon of “hacking”. It’s an event where large ammounts of developers/IT/design/management/etc experts meet together to work on a projects with the goal of finishing it in planned hackathon lenght (usually 24-72hrs). Those projects tend to have a theme selected by hackathon organizers, however the exact project ideas come from participants. Is it, like, even popular?

What is this blog about About developer lags. There are moments in your programming life when you need to sit down, perhaps write something down before throwing yourself into coding again. I always called those the dev lags. A lot of the beneficial ones have already been lost, hopefully this blog will save the rest of them. What can you expect: tutorials, related to backend development, answers to less obvious programming questions felietons, articles from the viewpoint of a developer, touching non-technical aspect of the profession blogposts, my experiences from meetups, conferences, or simply articles which I wouldn’t call felietons

1. What’s CI CI stand for continous integration. The simplest way I could explain what it really is is with an example. Say, you remember when you started your first coding related job, or maybe the second. Hopefully the company/environment provided you with opportunity to review code throughout the team. If so you may have noticed that often it is not the solution itself that takes the most time but the actual codereviews, discussions and merging that is the problem.

What are code reviews? Hopefully most of my readers whom are programmers are working in an environment where code reviews are part of the software development process. For those readers who have no idea what those are: code reviews are self-explainatory, it’s a process of reviewing changes (code) submitted by one member by other members working on the same project. Mind you - such reviews were not so popular just a few years back but benefits of including them in software development pipeline made them adapted widely anywhere from open source communities to business teams.

What are code reviews? Hopefully most of my readers whom are programmers are working in an environment where code reviews are part of the software development process. For those readers who have no idea what those are: code reviews are self-explainatory, it’s a process of reviewing changes (code) submitted by one member by other members working on the same project. Mind you - such reviews were not so popular just a few years back but benefits of including them in software development pipeline made them adapted widely anywhere from open source communities to business teams.

1. What’s CI CI stand for continous integration. The simplest way I could explain what it really is is with an example. Say, you remember when you started your first coding related job, or maybe the second. Hopefully the company/environment provided you with opportunity to review code throughout the team. If so you may have noticed that often it is not the solution itself that takes the most time but the actual codereviews, discussions and merging that is the problem.

What are code reviews? Hopefully most of my readers whom are programmers are working in an environment where code reviews are part of the software development process. For those readers who have no idea what those are: code reviews are self-explainatory, it’s a process of reviewing changes (code) submitted by one member by other members working on the same project. Mind you - such reviews were not so popular just a few years back but benefits of including them in software development pipeline made them adapted widely anywhere from open source communities to business teams.

1. What’s a hackathon Hackathon’s meaning is partially incuded in it’s name, hack + marathon, marathon of “hacking”. It’s an event where large ammounts of developers/IT/design/management/etc experts meet together to work on a projects with the goal of finishing it in planned hackathon lenght (usually 24-72hrs). Those projects tend to have a theme selected by hackathon organizers, however the exact project ideas come from participants. Is it, like, even popular?

Foreword I may not be the most experienced developer who takes care of recruitment process. At the same time the experience I have gained so far makes me a good source of information about conducting and attending interviews. Please, keep in mind that this article is written from the perspective of developer and not a recruiter before reading any further. Note: I didn’t want to bring any specific programming language to this post as I strongly believe what I am going to talk about applies to all of the languages.

Backstory I, like many other developers, started my adventure with programming without any good reason. Some of us started early while some of us started late in our lives. At the same time nearly all started out simply because “it seemed like a fun thing to do”. Just like that - “it was fun to do so I did it”. I was lucky enough to own a really low-budget PC as a kid.

1. What’s a hackathon Hackathon’s meaning is partially incuded in it’s name, hack + marathon, marathon of “hacking”. It’s an event where large ammounts of developers/IT/design/management/etc experts meet together to work on a projects with the goal of finishing it in planned hackathon lenght (usually 24-72hrs). Those projects tend to have a theme selected by hackathon organizers, however the exact project ideas come from participants. Is it, like, even popular?

1. What’s a hackathon Hackathon’s meaning is partially incuded in it’s name, hack + marathon, marathon of “hacking”. It’s an event where large ammounts of developers/IT/design/management/etc experts meet together to work on a projects with the goal of finishing it in planned hackathon lenght (usually 24-72hrs). Those projects tend to have a theme selected by hackathon organizers, however the exact project ideas come from participants. Is it, like, even popular?

Foreword I may not be the most experienced developer who takes care of recruitment process. At the same time the experience I have gained so far makes me a good source of information about conducting and attending interviews. Please, keep in mind that this article is written from the perspective of developer and not a recruiter before reading any further. Note: I didn’t want to bring any specific programming language to this post as I strongly believe what I am going to talk about applies to all of the languages.

What are code reviews? Hopefully most of my readers whom are programmers are working in an environment where code reviews are part of the software development process. For those readers who have no idea what those are: code reviews are self-explainatory, it’s a process of reviewing changes (code) submitted by one member by other members working on the same project. Mind you - such reviews were not so popular just a few years back but benefits of including them in software development pipeline made them adapted widely anywhere from open source communities to business teams.

1. What’s CI CI stand for continous integration. The simplest way I could explain what it really is is with an example. Say, you remember when you started your first coding related job, or maybe the second. Hopefully the company/environment provided you with opportunity to review code throughout the team. If so you may have noticed that often it is not the solution itself that takes the most time but the actual codereviews, discussions and merging that is the problem.

What are code reviews? Hopefully most of my readers whom are programmers are working in an environment where code reviews are part of the software development process. For those readers who have no idea what those are: code reviews are self-explainatory, it’s a process of reviewing changes (code) submitted by one member by other members working on the same project. Mind you - such reviews were not so popular just a few years back but benefits of including them in software development pipeline made them adapted widely anywhere from open source communities to business teams.

1. What’s CI CI stand for continous integration. The simplest way I could explain what it really is is with an example. Say, you remember when you started your first coding related job, or maybe the second. Hopefully the company/environment provided you with opportunity to review code throughout the team. If so you may have noticed that often it is not the solution itself that takes the most time but the actual codereviews, discussions and merging that is the problem.

Wait, what? Yeah, your goalkeeper. Surprised? If you are a developer there’s a great chance that you are underestimating the role of QA in development process. The less experience you have the more the chance is. But hey, that’s natural you know. You will grow to love them on your first major, ekhm, bug on production. Bugs on production never happen to me! Maybe, or perhaps you just ignore the pingpong you usually play with your QA tester.

What are code reviews? Hopefully most of my readers whom are programmers are working in an environment where code reviews are part of the software development process. For those readers who have no idea what those are: code reviews are self-explainatory, it’s a process of reviewing changes (code) submitted by one member by other members working on the same project. Mind you - such reviews were not so popular just a few years back but benefits of including them in software development pipeline made them adapted widely anywhere from open source communities to business teams.

1. What’s CI CI stand for continous integration. The simplest way I could explain what it really is is with an example. Say, you remember when you started your first coding related job, or maybe the second. Hopefully the company/environment provided you with opportunity to review code throughout the team. If so you may have noticed that often it is not the solution itself that takes the most time but the actual codereviews, discussions and merging that is the problem.

Wait, what? Yeah, your goalkeeper. Surprised? If you are a developer there’s a great chance that you are underestimating the role of QA in development process. The less experience you have the more the chance is. But hey, that’s natural you know. You will grow to love them on your first major, ekhm, bug on production. Bugs on production never happen to me! Maybe, or perhaps you just ignore the pingpong you usually play with your QA tester.

What are code reviews? Hopefully most of my readers whom are programmers are working in an environment where code reviews are part of the software development process. For those readers who have no idea what those are: code reviews are self-explainatory, it’s a process of reviewing changes (code) submitted by one member by other members working on the same project. Mind you - such reviews were not so popular just a few years back but benefits of including them in software development pipeline made them adapted widely anywhere from open source communities to business teams.