Type-interference is a great programming feature that helps coders write clean, readable code in a reasonable amount of time. Learn more here.
Writing type-safe language while maintaining less boilerplate code is an important aspect of programming languages in terms of developer’s productivity. Because type-safe code is less error-prone and less boilerplate code leads to more readable code, both together means reduced development time. Type-inference is a great programming language feature that maintains this balance.
Developers usually read more often than write. Thus, even if the source code will end up being processed by the computer, most of the time our focus is putting it into more human-readable form. At some point, we pay attention to the UX principles, like:
Humans have a limited attention span, so source code should help to spend this attention wisely. Information comes at a cost, so the longer the code is, the more overwhelming it is to read.
Sometimes, less means more. Short code may look brilliant, but it amplifies the time that others must spend on it. We should provide just enough information. Implicit values, if we do not abuse them, are the fix for this.
Vert.x can lend a hand with helping your microservices find each other. See how to get it set up and what it can do for your software.
Remember the Unix philosophy “Do one thing and do it well?” That is the philosophy of microservices. In software development, it is a common practice that when the same functionality is seen in the different parts of the application, it is abstracted away as another component.
This article shows you how to launch Vert.x, the toolkit for creating reactive apps on the JVM, in a dynamic way.
Vert.x started back in 2011 and it was one of the first projects to push the reactive microsystem model of the modern applications that need to handle a lot of concurrency. Since back then, people have developed best practices from writing good quality code using Rxfied Vert.x, RxJava’s Observable, and JoinObservable to its deployment using Docker, Kubernetes, or Swarm. Vert.x does not restrict developers to obey certain rules and standards, therefore, it is a better fit for our current Agile environments and Lean Entreprises. Thus, Developers like us, who are keen on freedom, can try new ways of doing things. With that in mind, we did not want to launch our microservices in statically defined ways. So in this article, I want to introduce how we launch the Vert.x in a dynamic way and in the coming days we want to publish series of articles about how we use brand new methods related to things like service discovery and deployment.
See how Vert.X, its Service Directory component and its eventbus work to get services talking to one another on both single or multiple JVMs.
In my previous article, I explained the Service Discovery in Vert.x and introduced an example of transparent remoting using Service Discovery. Transparent Remoting is a remote method invocation that looks like a local method invocation. In the other words, we have a plain Java interface and its proxy implementation at the client side. In the meantime, we have stub at the server side, where the actual implementation runs. With Service Discovery in Vert.x, we can obtain service references using its service name so that we no longer need to care whether a service runs locally or remotely. However, Location Transparency in Vert.x is a very important topic, and I am going to explain it in detail in this article.
In my previous post, I focused on the philosophy of the PSPO I (Professional Scrum Product Owner) exam and mentioned about to whom this exam is related to (https://www.linkedin.com/pulse/professional-scrum-product-owner-pspo-exam-story-i-ali?trk=prof-post). In this continuation post, I will touch the methods of studying, sources that needed to be studied and reply the question how you should study to guaranty to get the certificate. You can achieve the information about concept of the exam, application steps and tips about the exam in this article. I prepared my advices point by point to create the functionality of a to do list. When you mark as done to all bullets and read over first episode of the post, you can take the exam confidently.
I mentioned about the Product Owner role in the organizations, incorrect decisions about this positioning and responsibilities of the Product Owner in the period of agile transformation in last month’s blog post. You can find it from the following link (https://www.linkedin.com/pulse/organizasyonlarda-%C3%BCr%C3%BCn-sahibi-rol%C3%BCn%C3%BCn-ali-saracoglu). This month, I will focus on the exam, that proofs the ability of the candidates about Scrum Product Owner, and answer the questions of; the index of the exam, fits for whom, application lifecycle, tips and the tricks about the exam.
What is PSPO I exam?
Firstly I should remind that, ‘PSPO I’ has no prerequisite to enter the online exam just like ‘PSM I’. You need to answer the 80 questions %85 correctly in 60 minutes. Because certification does not have expiration date, owner of the certificate does not need to collect any point or pay money to renew the certificate. When you pass the PSPO exam, Scrum.org announces you as a Professional Scrum Product Owner in their website https://www.scrum.org/Assessments/Certification-Lists .
Scrum processes on three main role that are Scrum Master, Product Owner and Development Team, which constitute “Scrum Team”. In this article I will be specifically focusing on the Product Owner role in the companies which transformed their organizational structure into Agile from traditional Project Management methods and address the conflicts which people are facing after repositioning their Project Manager Role. Organizations which are not able to fully integrate all its units to the Scrum fail to execute the Scrum Method due to lack of information, education and invented definitions such as “Project Owner”. Thereof, the consequences and execution are more likely against to the Scrum logic.