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 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.

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.

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.