Hello, dear Reader! I apologize for a such loud title of the article, but you should know how it's important for me to engage the readers to discussion. Not so long time ago, I decided to systemize my knowledge of object oriented programming in Scala. That was awesome idea! And now I want to share with you all mini-topics which I underlined as important, but many developers forget about them.
I enrolled to Functional Programming in Scala specialization on Coursera. It consists of 5 courses which will take around 180 days. First course in the specialization is Functional Programming Principles in Scala. I already completed the first week and learned some stuff about recursive functions. So It's time to share some knowledge.
That's not a secret that Scala is very popular programming language in BigData industry. And you may heard before that Scala is a data-centric programming language. This means not more, that with its help you can work with a data more easier comparing with other languages. Important roles in this play two Scala features: case classes and case objects.
For a long time I couldn't understand currying functions in Scala and how they work. That was really horrible! Because occasionally I met the currying functions in the code and wasted too much time to read them. So finally I decided to learn how it works and where could be applied.
Scala combines two programming paradigms: object oriented and functional. As a result you get best from the two worlds. From the one side you can describe models as objects, from the other side you can apply functions to them. And as you may guess, it's really awesome! Let's discover today basics of Scala functions.
Nothing is perfect in the world, except a football skill of Leo Messi. Yeah, maybe not always but in most cases it's impossible to create an ideal process. But I'm not scared to talk about my vision of a perfect test automation in a context of a software development. My work experience gives me confidence in this question. So I'm starting!
It doesn’t matter what position you occupy in IT, you can be a software developer or DBA, but you need to know how a good bug report looks like. If you are from the QA department, you need to pay extra attention to this post. The theme of the article is the creation of bug reports. In this short article I will explain what is a bug report, from what parts it should consist and what is the purpose of each field in the report.