Mock & Stub and People Management
By: Emil Farisan Singgih
Tags: Software Development

Mock & Stub

Stub is a subtitute object for dependencies that is in a system. Using Stub we dont have to depend on real data. Here is an example of a Stub, when we want to access the student scores data, the function wont access the database to get the data that it want to use, rather the Stub will return a value when the function is called. The data than will be use as a subtitute to the data in the database.

pict from : https://blog.pragmatists.com/test-doubles-fakes-mocks-and-stubs-1a7491dfa3da

Mock is subtitute object that serves to validate a unit test. When undergoing testing, the output of a function will be tested by comparing it with the Mock object. Mock checks if it has been called correctly in a test or not. Therefore, Mock can determin wether a unit test succeed or not.

Here is an example of how i use Stub

People Management

When faced with a tough project, a team must be tough as well as organized. Those are the two qualities things that helps ensure to achieving the best results. This is why People Management is crucial in teamwork. These abilities include speaking ability, management, and also leadership. Different people managed others differently, although it is not my job as a hacker to manage people, but i did learn a thing or two when i was having a chat with our hustler, Rani.

Communicating

When we have a product, we want the user of the product to be able to use the product as they intend to use it in this case the user is the Product Owner. We want to be able to cater the Product Owner’s need, so we communicate with him to ensure that the development is going to the right the direction as he intended. I worked on one of the core feature of the project which is “Forecasting”, the data that the PO wanted displayed on the dashboard is the results of continuous discussion between me and the PO. The first idea of the feature when compared to the current state of the feature is very different as a results of that.

Training

From the start, none of us really know what we’re doing. Except for Satryaji which seems to have a proficiency on DevOps related stuff. So to ensure that the every member of the team know what we are doing. We try to study everything, even if it was not our part of the project work. Doing that really bonds us in the start, and it really paved a way to a very constructive and supportive friendship between the members of the team.

Motivate

Feeling down and just generally unhappy can really hinder progression and could led to unfinished product, buggy features or maybe unprepared sprint. These things happened in teamwork be it because our task are too hard for us, feeling stuck in implementing a feature or just not interested in working on the task given. Keeping the moral up, would result in better progression and just happier working environment.

Recognition

When working in a team, everyone wants to be credited for every thing that they did. Being praised for their contribution felt good. Every member in a team is an asset to an asset to the team and thus recognising their efforts and contributions is an important aspect when it comes to managing people. It also shows that they are given respect by their peers. Personally i’ve been on both ends, since our team is very appreciative of others work. I’ve also appreciate my friends work in the past, because the work that he’s done help me to achieve better results on my task.

These are the things that we (not only the hustler) have to keep an eye on when working as a team. There might be a manager that manages most of the human interactions, but that doesn’t the mean the non-manager should fully rely on the manager. People management is an important piece in teamwork and we all should take part in this.

Thanks for your attention.