This post is my reflection after spending time working in the industry as a professional and my experience active in several student organization when I was in college.

This post is written for software engineer, developer, programmer who adopt automated test in their development workflow.

In technology and science, sometimes we use abstraction to make things manageable to be discussed, to be solved (if it a problem), and to operate. I remember one of my Professor when I was in college often called something a black box to define a theoretical object that we (student) are not fully understood or object of study. That is when I was in college taking engineering physics program, but now I am in software development field. We use abstraction to make things more manageable, to operate complex infrastructure, to build complex business logic on top of relational database, etc, you name it.

Introduction to Four-layer model of microservice ecosystem

Intro

I work in Software industry especially in software development field. Here, I don’t know why the term “best practice”, “pattern vs. anti-pattern” seems filling many books, articles, conference talk, even in your hiring interview. Those words seems overrated. I prefer to call the so-called “best practice” as “good practice”, why? It is because when I say good practice, I want to bring context to whom I talk. I want to say that this is good in this context, even if its work good in almost any cases, I can’t say this as best practice because in some particular context there should be any better solution/approach/practice to solve the problem.

Intro