Every day we live in our IT world, where we have certain laws and rules. But what if we look beyond our industry? Construction, automotive, philosophy, business close to us and more: would we find there anything useful for us? Maybe some of them already exists with us and spotting them may help us communicate with people outside of IT? During this lecture we’ll consider this and try to look at it through our prism.
Most of developers work on web, mobile or desktop applications, but in today's world software is everywhere - also in aeroplanes, space shuttles, medical equipment or nuclear power plants. How software development in these fields differs from everyday applications? How developer's work looks like when he must comply with restrictive regulations? During my talk I will answer these questions using my experience in the field and references to normative documents. I will also analyse some software errors causing loss of human life and destroying equipment worth millions of dollars. I hope that this presentation will be useful to every developer and will help you to create safer and more reliable software.
Working with legacy code is a challenge, but it's a one worth taking. It will test your programming skills and experience, but you can really grow as a software engineer when working with it. As with any hard challenge, it's really easy to make mistakes, and I have my fair share of experience when working with legacy projects and making those mistakes.
During this talk I'm giving you an opportunity to learn from my experiences. I will share my problems when working with legacy codebase and what would I do today to fix them. I'll share good practices and resources, with examples of course.
Programming today is very different from programming of 20 years ago. Developers have to face the technological revolution and its new challenges. These challenges often require a completely different set of competences than in times when distributed programming was not as common as it is today.
During my presentation, I will describe my journey as a programmer with over 25 years of experience in the industry, who can boldly say "I like my job". I will recount my ups and downs that I’ve went through, and the lessons I’ve learned along the way. I will speak about the challenges and professional traps in my career.
I will also try to answer the question: What is the difference between "being a programmer" and "working as a programmer"? Is the programmer a profession or a vocation? Does good knowledge of technology mean being a good programmer? Or maybe a perfect knowledge of a particular language makes a great developer a great person? How to determine the profile of your skills, limitations and potential directions of professional development?