Recently, I was working on my code and found myself struggling with it as it did not turn out to be as expected. The code had too many bugs and was not handling all the use cases. I reviewed the code again and again, but still, I was not able to get the desired outcome.

At that moment, I remembered an incident the same morning that turned my mood upside down. I fought with one of my family members in the morning and I was frustrated before I sat down to write code.

There is no proven science behind this judgment, but many practitioners believe that sometimes emotions affect developers’ productivity and code quality.

Further research provided me with an answer. According to the International Journal of Social Science, software developers generally have a higher chance of experiencing stress, fatigue, and burnout than non-tech employees.

If I was in the right frame of mind, to solve the above issue, I would go back to my drawing board and create a well-thought-out plan. Or I would look online for alternative solutions to check similar problems and how other developers solved them.

Influencing Factors on Developer’s Mental Stability

The code doesn’t show emotion and you cannot find out the developer’s emotions while reading the code. However, the ones developing code are humans that do get affected by emotional load. They are in constant touch with the management and team members, stuck with deadlines, and the pressure of releases affects the code quality and productivity.

Stressful Work Environment

Many software developers report about the work culture and environment in their companies that affect their performance. Most of them seem to be contemplating quitting over complaining about mistreatment and micromanagement.

Developers quit their job as they feel unproductive and demoralized. They require constructive feedback, reviews, or appreciation from the management to be motivated to work and produce the best results. Furthermore, if the organization can provide them with opportunities to learn and excel in their skills, who will not be motivated to stay and work for such an organization?

So, motivation is the biggest factor when it comes to being productive and providing better-quality code.

Environmental Factors

How do you prefer to work? Do you like closed, quiet spaces or working together with your team?

Including the work environment, most developers feel distracted due to interruptions in the surroundings. Some prefer to work in closed surroundings rather than open spaces. They can work better in a quiet place instead of working with other teammates with non-stop distractions. However, some prefer to work with teams, share ideas and work to build better code.

Emotional Effects on Developer’s Productivity

A developer requires focused thinking to work productively. Our brain is adaptable and flexible which can take an excessive load for months. However, many modern scientific theories assume that we can only work for 2 to 4 hours in a focused setting. If we try to work excessively for more than 4 hours every day without break then, developers are more likely to get extreme exhaustion.

Happiness: Get into productive mode

Do you enjoy what you work? If yes, then you would feel a surge of energy to be productive and get tons of work done. Similarly, developers who enjoy coding can write multiple lines of code when in a happy and jolly mood.

Happy developers write code efficiently, debug and resolve errors, and develop better solutions.

It has happened to me, when I am tired/stressed or overworking myself, I tend to make more errors. Whenever I checked my work in the morning that I completed at night, I could see many issues that I had to rewrite. At that moment, I thought it would have been better if I had slept and worked early in the morning to save my time and effort spent on the task.

Anger/Arrogance: No one can find mistakes in my code.

It comes as no surprise that anger is one such negative emotion that brings the code quality down. In general, anger is known for its blinding effect so, it makes sense that your code quality goes down when you are not in the right state of mind.

You tend to finish tasks way ahead of the scheduled time, and it always takes more time to make revisions.

You must have come across some complicated code in your daily work life as a developer. The code is written using complicated logic that only they can understand and other developers will not be able to decode. Such code shows the arrogance of the developers.

Sadness: Let’s not get distracted and work

What outcome can you expect from a sad emotion? Not focused? Unable to think clearly?

You may be surprised here to know that sometimes sadness can result in better and cleaner code. Here, sadness often coincides with more focused, cleaner, and better-quality code. Also, fewer mistakes!! Hurray!

But, you don’t need to be sad all the time to write good-quality code. We, humans, can manage our emotions and use them to our advantage.

At the end of the day, you need code that works brilliantly, right?

Decide what emotions you want to show in your code!

So, can you write code out of emotion? It’s a debatable question, but your code will always show some emotion that you are experiencing at the moment. Then, why not leverage positive emotions and use them in the code to show how we feel while writing code?

Some positive emotions you can show are:

Confidence: As fear is shown in the code, you can also show confidence in your code. It will display your skill set and your way of working while writing code. Some practices you can follow:

• Whenever you fix a bug or work on a new feature, always review it before deploying it. Code review will also help you in building your confidence.
• Remove unnecessary code or variables that you don’t need, Clearer code is easier to read and easier to maintain.
• Leave comments on the code to guide people, people spend more time reading code than writing code
• When learning something new, try it out; that is the best way to understand the concept and will give you more confidence to apply it.

Generosity: It is when someone creates a well-written code by rearranging, refactoring, and renaming things such that the code makes sense and also helps the developer to read through the coding process.

• You aim to make your code run smoothly
• You are learning continuously and using modern libraries and modern constructs
• Review the code and take time to remove badly created code and offer to provide new code-creating practices
• Try to leave the code better than how you found it

Humility: A humble code is when a developer who is reading can easily understand what is written. While writing a humble code, always imagine the next reader rather than yourself, so give necessary explanations as needed.

• You can use libraries
• Leave comments wherever necessary
• If you need help, mention the name of the person in the comments. In large organizations, it is common practice to mention who wrote the code and who is in charge of maintaining it so others know whom to contact for assistance

What to do to improve productivity and encourage positive emotions during work?

Though one cannot control emotions, they can affect your mental state in many ways. But, how to stay productive and sane while coding??

1. Get up and Walk!!

Sitting for long hours in an uncomfortable position will lead to squeezed fibers and neck muscles. Try eating nutritious food and adding workouts to your daily routine.

If you are unable to do frequent workouts, just taking a walk around the office from time to time will also refresh you and take your mind away from work. When you expose yourself to fresh air, you allow yourself to inhale more oxygen helping to boost your brain performance. Sitting in a poorly ventilated room hurts and blocks the creative side of the brain.

If you are a person who sits in front of your laptop for long periods of time, then make sure you are sitting in a good seating position, and your workplace is clean and comfortable.

2. Team members for the rescue

The people in your team leave a great impact on your mind and your ability to perform better. It is important to work on team building activities as it results in better performance and results.

If anything is bothering you, you can share it with your team and get your concerns answered. It is essential to maintain emotional balance to avoid sudden emotional outbursts.

However, you need to make sure with whom you are sharing the information. Be careful, as if you just shared the information with someone, it should not be intercommunicated among others by that person. There should be understanding and trust among employees.

And also, remember to be kind if someone approaches you for help, make sure that they leave feeling good about themselves

3. Let’s do multitasking with a plan

When you have 2–3 tasks on your plate that you are unable to focus on either of the tasks. How can you solve the problem while not meddling or messing up any of the tasks?

A simple solution is to make a list of things you are entitled to do, small or big everything. Also, keep adding the tasks as they are assigned to you throughout the day. This way you don’t have to memorize and you can always check your list to see the completed and pending tasks.

4. Switch and come back!

To produce exceptional results, you should not push yourself beyond your working limits. If you need a break, take a break. If you are unable to focus then switch to a task that does not require mental work, to give your mind a break from excessive focus. By doing so, you can come back to your task and work in a better way.

Another way to refresh your mind is to listen to your favorite song while visualizing your goals and dreams. It will help you motivate and work better at your job.

Happy software developers perform better than unhappy ones — Keep them happy and you will get unexpected results.

Follow MoEVing for more informative blogs.

Billions of people use the internet every day and are just a few clicks away from using or downloading your product. What is stopping them from doing so?

If your product is out in the market and still not getting enough attention, it’s time you rebuilt your product content strategy.

We know words make the product readable and consumable. However, the words you use within the product are just as important as the words used to market your product.

Your product content is the driver behind consumer purchase, meaning the user will have a better experience using your product, resulting in better conversion rates.

The Purpose of Content Strategy

Content is usually seen as the afterthought once the product has been developed. It is then incorporated into the design at a later stage that might seem overwhelming to the users. When the content is integrated from the beginning of the product development process, it oozes quality and a satisfying user experience.

Simplicity is the best policy

Let’s make the content as simple and understandable as possible.

“Error Message: The system is facing an error.”

How do we solve the problem as a user? What is exactly the issue? It isn’t clear with this message.

What if the same error message is mentioned as, “Please enter a valid email address.” Now, the user knows where the problem is and how they can solve it.

So, content is central to the user lifecycle of the product. They understand human language, converse with the product, and function accordingly.

Content Strategy to Follow

Understanding the Problems & finding their Solutions: How can your content help solve the problem of the user? Solving users’ problems encourages them to value your product and trust you over others.

Are we unique in our approach?: How is your product unique, and what innovative features does it bring to the table? Can users differentiate between your product and other products available in the market? It is a crucial thing to discuss.

How to make the product relatable to the users?: Are we relating to our audience? With our product, we should be talking directly to our audience. The product is made for the users to use, so content helps them converse with the product.

It comes down to access. Giving the consumer something they can’t get anywhere else.” (Jeffrey Moran)

Creating a Content Strategy for the Product

Content strategy starts with creating the user persona of the product. You first need to know who the users using your product are.

Key components of User Personas

How do we develop a user persona? A user persona is the direct representation of the user using your product. User personas are created to understand how your product can create empathy among your users.

Understanding the user’s demographics:

• Personal and Social background: Age, education, location, and family background
• Professional background: Qualification, Work experience, income, and job titles
• Psychological background: Future goals, psychological journey, hobbies, interests, and opinions.

Such components will help you start analyzing the actual face of the user instead of an abstract. Also, you will understand how your product can add value to their life.

Categorizing the users based on your research

Based on your user research, you will have multiple user personas. Now, you can select similar behavioral patterns among the users to make your ideal user. This way, product features can be prioritized and designed accordingly.

For example, MoEVing app is developed for riders and entrepreneurs owning or running a small fleet of electric vehicles. We research the fleet operators and the riders to understand their work requirements and make our app beneficial for them.

Understanding User’s Expectations of the Product

The basic expectation of a user is that the product works exactly as it mentions to do. The features and actions should function as advertised and lured them to download/purchase your product in the first place.

The product content should be self-explanatory why they should use your product in the first place. As you open the app, the instructions should be self-explanatory and in a language that makes the user with no knowledge of technology understand and use it. If it is difficult, then it doesn’t take seconds for the user to switch to an easy-functioning app.

The more efforts user have to make to use the app, the more chances you are providing them to move to another app.

What else is required to make the users know the benefits of your app?

1. Tell a story about your product.

As per Search Engine Watch, storytelling can give you a conversion rate of about 30%. And cognitive psychologist Jerome Burner said, “the human mind is 22 times more likely to remember facts when it is conveyed via story”.

So why not include a story in our product content?

Product content is all about how creatively you can attract your customer’s attention to engage with your product. The most important part of your product is trust and you can build trust among the customer with the way you can communicate with your consumers.

The way you used to remember every step related to your studies using a story. It’s the same for products. The story makes the product interesting and the user will remember what step to use next.

Note: Tweak your content as per your target audience. You can take inspiration from other product stories but that may or may not align with your product goals. Make sure to align content with your product needs.

2. Content — Translations and aligning with design and content (number of characters)

As a content strategist, your responsibility is to provide content that is understood by everyone.

It’s useful if you thoroughly research the market and check how the players in the market are using vocabulary in their products to attract users. From there, you can invent some uniqueness in your content to differentiate your product from others in the market.

If your app is released in various languages, make sure the option to choose a language is available. The product content strategist can help provide the right vocabulary for the respective language that can be integrated into the app by the developers.

Take a call on what words need to be translated and what should not be. There are some words that can be used as it is for example:

3. Make content reach the audience

Now, you have the designs with you and an idea of how to content should look in the product. It’s time to actually let the content sit within the product while the development process is taking place.

It will:

1. Reduce multiple editings
2. Allow the team to be on the same page relating to the content and what should and should not go in a particular space

If we are including a content writer in the product development, they can help you

• Choosing the best platform to publish the content

Once the content is ready, what is the next step? Where should you put out the content so the audience can actually read it and it is useful for them?

• App usage videos- Publish on YouTube

Youtube is the best platform when it comes to posting videos.

We started the content distribution internally to our riders working with us. We started sending them youtube links so that they can directly view the videos as sharing them on google drive was a fail.

They can watch and share the links among other riders which eventually gives a boost to youtube views and shares.

We have to be sure where our target audience is most active. The user research we did earlier will help us find the platforms where we can find our target audience.

• Understand when there is a need to be descriptive and use short sentences to convey the message

How do you want each of your messages in your product to reach your audience?

Some messages require descriptive sentences when you want to explain a particular word or show them how to fill something which might be new for them. Other messages do not need to be descriptive but short and crisp to attract the attention of the users.

For notifications, there is a limit to the characters, so you need to think of content that suits both character limits and conveys your message.

If you want to know more about product strategy and product content development, follow us for more product-related blogs.

Follow button is right there, and what if you forget to read our blog next time we post? You can subscribe to our mailing list and get blogs directly delivered to your inbox. Better deal, right?

See you next time!

How would you feel if there is a product/website/software without any words and just blank spaces? You will never know what to make of each blank.

Words are the backbone of a product. Users knowingly and unknowingly read the words in the product. Why? That is because the written word allows users to have a conversation with the product.

Writers develop an empathetic relationship with the user. A simple message like, “Thank you for your patience” goes a long way in instilling faith in users’ minds that their time is valued.

Today, we will focus on how writers help in product development and influence product adoption.

Better Writing Better Product Design

For a product to stand out in the market, we need both “narrators” and “creators”. Both are equally important to develop a better product in terms of development, design, and usability.

A good design works well with good writing. When a user has to decode a cryptic message before using features, it leads to an unsatisfactory or stressful user experience. A product is created to solve a user problem. Ultimately, you are solving a big problem that your target user is facing with your product. So, it becomes crucial to have easily consumable content, keeping the audience’s demographics in mind.

The writer’s work is seen through words in the product. However, the writer’s work consists of subject matter and user research, interviewing team members, ideation, testing, documentation, and maintaining the content consistency in the product.

A skill set of content writing, content strategist, copywriting, and digital marketing come together to be used in product writing to create a better product design.

Require Cross-Communication Among Teams

Communications are crucial for the team to have an engaging discussion. Disagreements and clashes of opinions are part of the conversation, and it is important how the team solve the issues and put their points in a friendly manner. So, the team should communicate, listen to others’ inputs and come up with a collaborative decision.

To perform their duties efficiently, writers should be a part of most communication with other departments.

As a developer, you might miss out on bugs and defects that the writer can identify and report. That’s why writers are required to be kept in the loop so that content is created on time as the feature is released.

Writers Influence Product Adoption

“Understanding a product is as difficult as explaining the product. If you can explain the product in easy terms that means you have understood the product.”

Writers treat the content as a conversation between the product and the users. Writers form direct contact with the actual users and are able to make users understand and use the product with ease in textual or visual form. In fact, writers are the very first user of your product.

So, it makes sense to include writers in product development strategies to help them understand why this feature implements that can be reciprocated in a form that leads to product adoption at a larger scale.

How is it done? Let’s find out.

Re-read, understand and improve the existing content

Writers are provided with product documentation to know the ins and outs of the product.

It’s important for a writer to understand the product and re-read the existing documentation. While reading the documentation, they can find out the flaws and make suggestions for improvement.

Some suggestions could be:

• Remove any repetitious content or information
• Correct the flow of information across topics and features
• Highlight important points and features of the product
• Correct sentence structure and grammatical errors, if any
• Provide suggestions on features that might be useful for the users or missing in the documentation
• Note down questions to ask your team members for any clarifications for a better understanding of the product

Once you have a list ready with you, you can discuss it with your manager, editor, or team members to guide you to improve the content.

Creating Educational Videos and Tutorials for the users

Video marketing has reached a wider audience, and when it comes to learning a skill or learning to use an app/software, there is no other media source better than videos.

The writer’s role does not end with writing about the product. It also includes generating multiple ways to send the content across different platforms.

Short and interesting videos about the product that explains its features can attract users to watch and learn about the product.

Tips to build an interesting educational video script:

1. Research and study well the feature or product you want to explain to the users.
2. Try using the feature/product to help users understand each and every step in a clear manner.
3. Start the script with a basic outline. For example: what features to include and the steps involved in using the product.
4. Now, state the problem, then a solution to that problem you are solving with your product.
5. Once done, start developing the video. (Take help of video editor if needed)

Discovering product issues and providing suggestions for product improvement

Writers collect varying perspectives from product managers, testers, and developers to retain the relevant information and eliminate the other. The internal conversations help give direction to the project and acknowledge the pain points of the product.

When you get used to the product, you can understand why each feature is developed and how it benefits the user. Being the writer and the tester, you can discover issues with the product.

Most writers also do not come with a technical background, so initially, it is challenging to work on a tech product. However, you can try learning basic software terminology to relate to product development and make it understandable for the users.

If you are wondering how a writer can provide technical suggestions, here are some pointers:

• Difficulties you faced while using the feature
• Write descriptive error messages
• Check the content is explanatory and grammatically correct
• Check the UI/UX design if it is easy to use or not

If you have a writer on your team, there will be consistency in the content throughout the product. They can offer to edit and provide suggestions for content and product improvements. With appropriate wordings and descriptive messages, writers make the content easily consumable.

In the next blog, we will look at the types of content that can help in product development, adoption, and marketing. If you are new to product writing, this will be helpful for you. Stay Tuned!

For more details, visit: https://www.moeving.com/join-us/

Note: Nowadays, it is better to use hosted elasticsearch service provided by various cloud services to reduce maintenance and operational overhead.

For this exercise, We will be installing the latest version of Elasticsearch from Archive(tar.gz) which is version 8.2.3 while writing this blog.

Command:

curl -O
https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-8.2.3-darwin-x86_64.tar.gz

This downloads the elasticsearch archive file version 8.2.3.

Once it’s downloaded we can further extract the content with the below Command.

tar -xzf elasticsearch-8.2.3-darwin-x86_64.tar.gz

This will extract `elasticsearch-8.2.3-darwin-x86_64.tar.gz file to folder `elasticsearch-8.2.3`

Now we can go in to the folder by `cd elasticsearch-8.2.3` and `ls` to see its contents.

Till now, we have not done any configuration. For this tutorial, we would not be doing any configuration as we would be running it as a single node cluster on localhost. The configuration is default and comes within the package.

Also, we would be running this on HTTPS. We can have a custom signed certificate, or else while accessing Elasticsearch, it will give errors. Currently, we don't have any signed certificate so we would be accessing it via an insecure method wherever possible.

To start elasticsearch just run

Command.

/bin/elasticsearch

Whenever we run elasticsearch for the first time without editing its configuration and altering custom settings, it will create user elastic which would be a superuser, and auto-generate its password and will display it on the console as logs.

Elasticsearch starting and printing logs on console.

Elasticsearch started and printed user details on the console.

As we can see it has a printed password for the user elastic.

We can save this password to interact with elasticsearch in the future.

We know that starting elasticsearch on the console is of no use as to what will happen once we close the console. The service would terminate. To resolve this issue we can run elasticsearch as daemon service via
Command
`./bin/elasticsearch -d -p pid`

You can run `ps -ef|grep elasticsearch` to check the running daemon service.

If you want to kill the service, you can run
Command `pkill -F pid`

Now we know Elasticsearch is running as a service, but you may be thinking about how to access it? As discussed earlier, Elasticsearch is a rest API or provides a way to communicate through rest API. We will see in short the API's and examples below.

Let's call elasticsearch API to know if it’s running and get some information about it.

HTTP and HTTPS

Before running it elasticsearch, let’s understand HTTP and HTTPS.

HTTP over a secure connection. The only distinction between the two protocols is that HTTPS encrypts both normal HTTP requests and responses using TLS (SSL). Because of this, HTTPS is much safer than HTTP.

An HTTP website’s URL begins with http://, while an HTTPS website’s URL begins with https://.

As we know that we are running elasticsearch in secure mode, hence it can be accessed over HTTPS. However, HTTPS requires a signed certificate which we have omitted currently. We will have to say the HTTPS protocol not to verify certificate while using curl method and we can achieve this by using the insecure tag.

If we would have used a signed certificate we could have accessed elasticsearch via below
Command
curl — cacert $ES_HOME/config/certs/http_ca.crt -u elastic https://localhost:9200

But for now, we would be using,
Command
`curl — insecure -u elastic https://localhost:9200`

It will prompt for the password, we need to provide the same password which we got on the console while running it for the first time.

Now, we can see a JSON response from elasticsearch. There are various details such as cluster name, elasticsearch version, lucene version, name of the node, uuid etc.

INDEX: Static and Dynamic

We know now elasticsearch is running properly, let's play around with it by first creating an Index.

First, let's understand how index is created.

An index in elasticsearch is created via a PUT method.

There are two types of indexes i.e static and dynamic.

In a static index, we pre-define the schema of an index and in a dynamic, we don’t define any schema, it automatically infers a schema from the first document inserted into the index.

Creating an Index

We can create an index solely without any document in it, or we can create an index with a single document.

Here, we will create an index named test-index-000001 simultaneously and add a document to it with the below curl Command

curl — insecure -u elastic -X POST “https://localhost:9200/test-index-000001/_doc/?pretty" -H ‘Content-Type: application/json’ -d’
{
“@timestamp”: “2099–11–15T13:12:01”,
“message”: “GET /search HTTP/1.1 200 1070000”,
“user”: {
“id”: “kimchy”,
“name”:”ravindra”
}
}
’

Note: When the document is added to a resource it’s via POST method

We will get a success message.

It states that the result is created and the document ID is automatically created and assigned.

Now let's check what schema elasticsearch inferred from the document with below Command

curl — insecure -u elastic -X GET
“https://localhost:9200/test-index-000001/_mappings?pretty" -H ‘Content-Type: application/json’

Note: GET method is used for information and data retrieval.

We can see from the response that it has inferred string as text which is equivalent to string in elasticsearch, but it also copied the data as keyword and stored it as keyword i.e static value.

Let's understand the difference between keywords and text.

• Text is where elasticsearch does messaging i.e use of tokenizer’s analyzers and etc and then store the content.
• Keyword is where it stores data to do exact matching and aggregations on it but no partial matching.

We will read about mappings in upcoming tutorials.

Adding the document

Let us move ahead and add one more document to elasticsearch:

curl — insecure -u elastic -X POST “https://localhost:9200/test-index-000001/_doc/?pretty" -H ‘Content-Type: application/json’ -d’
{
“@timestamp”: “2099–11–15T13:12:01”,
“message”: “GET /search HTTP/1.1 200 1070000”,
“user”: {
“id”: “izzy”,
“name”:”moeving”
}
}
’

Now we have added two documents, let us check the count of documents in index via below
Command

curl — insecure -u elastic -X GET “https://localhost:9200/test-index-000001/_count?pretty" -H ‘Content-Type: application/json’

From above we can see it shows the right count which is 2.

Now we have added two documents one with user.name as moeving and one with ravindra

Let us write a very simple query to fetch a document that matches user.name with ravindra.

curl — insecure -u elastic -X GET “https://localhost:9200/test-index-000001/_search?size=20&pretty" -H ‘Content-Type: application/json’ -d’
{
“query”: {
“term”: {
“user.name”: “ravindra”
}
}
}
’

And we can see we got the result very fast in 439 milliseconds (field name = took)

In hits.total.value, it shows the total result count which is 1, and i.e is what we searched for.

It also provides the score which is hits.max_score 0.69 (you may be thinking it was an exact match so why the score is only 69%, not 100%, that's because of the analyzer used on the text field. If we search the same thing on the keyword field i.e user.name.keyword maybe we get 100%, we will talk about the relevance algorithm in upcoming tutorials)

The actual data is stored in hits.hits.0._source.

For looping one can loop in hits.hits and then retrieve _source for actual data.

Listing all the indexes

What if we had multiple indexes and wanted to list all indexes with the count of their names?

We can get this via below
Command

curl — insecure -u elastic -X GET “https://localhost:9200/_cat/indices?v&pretty" -H ‘Content-Type: application/json’

We can see we only have one index right now with the name test-index-000001 having 2 documents and its storage size 11.3kb.

Deleting an Index

Let us see how to delete an index.

Note: Always use this command consciously as it does not prompt and deletes the index once fired.

curl — insecure -u elastic -X DELETE “https://localhost:9200/test-index-000001?pretty" -H ‘Content-Type: application/json’

Here we use DELETE method

We got an acknowledgment as true that the index is deleted.

In a Nutshell

Now, we have learned how to install elasticsearch, how to run elasticsearch as a daemon, and use some of its features such as creating an index, inserting a document, searching documents, listing all indexes, and deleting the index.

Do let us know if you have any queries related to elasticsearch, we will quickly respond to you.

Written By:

The digital world needs faster service and even faster results. From employees to customers, everyone would like to get the results within seconds of their search.

Elasticsearch helps store, analyze, and search huge volumes of data in real-life to provide relevant answers within mili-seconds. How? Because it searches an index rather than the text itself, it can produce quick search results.

Let us understand in detail what ElasticSearch is and How you can use it for your technological advantage?

What is Elasticsearch?

Built on the Java-based search and indexing technology Apache Lucene, Elasticsearch is a distributed, open-source search and analytics engine.

Elasticsearch offers high availability, security, a snapshot/restore module, powerful search, and aggregation functionality, distributed cluster features, sharding for Lucene indexes, and other data management tools.

Why Elasticsearch?

It began as a scalable version of the Lucene open-source search platform and later included support for scaling Lucene indices horizontally. With the help of Elasticsearch, you can store, search, and analyze massive amounts of data fast and in close to real-time, with results arriving in milliseconds.

Instead of using tables and schemas, it employs a structure based on documents and has robust REST APIs for storing and querying the data. Elasticsearch can be conceptualized as a server that can respond to JSON requests with JSON data.

Traditional SQL database management systems aren’t particularly built for full-text searches, and they definitely struggle with loosely structured raw data stored outside the database. Fast access to and processing of semi-structured and unstructured data in a dispersed setting is a key concern that Elasticsearch directly addresses. Using the same hardware, Elasticsearch queries that would take more than 10 seconds to complete will return results in less than 10 milliseconds.

Elasticsearch uses optimized data structures for different data kinds to offer good read and write performance. For instance, Elasticsearch uses so-called inverted indexes to facilitate quick full-text search. These indexes include a list of the distinct terms used in each document as well as a list of every document where each word is used.

With cutting-edge binary search algorithms, Elasticsearch is also ideally suited for geographical and numerical data (BKD trees).

When Elasticsearch does an indexing operation, it transforms unstructured data from a message or logs files into internal documents and stores them in a basic data structure akin to a JSON object. Each document consists of a straightforward set of correlating keys and values; the keys are strings, and the values might be strings, numbers, dates, or lists. Elasticsearch isn’t a relational database, so RDBMS concepts typically won’t apply, it’s important to keep in mind.

When switching from conventional databases, normalization is the most crucial concept that you must abandon. Denormalizing your data is crucial because joins and subqueries are not supported natively by Elasticsearch.

Elasticsearch can handle petabytes of data and scale up to thousands of computers. Its complex, a distributed architecture is the direct cause of its vast capacity. The user of Elasticsearch can be blissfully ignorant of almost all automation and complexity supporting this distributed design.

Explaining Index Modules

Index modules control every aspect of an index and are created per index.

1. Documents: JSON, which is the universal internet data transfer format, is the fundamental informational unit that may be indexed in Elasticsearch as documents. A document can be compared to a row in a relational database, representing the entity you’re looking for. A document in Elasticsearch can be anything that has structured data that has been encoded in JSON, not only text. Data can be in the form of numbers, strings, or dates. Each document has a special ID and a certain data type that identifies the type of entity it is. A document might be a log entry from a web server or an article from an encyclopedia, for instance.
2. Indices: A collection of documents with similar traits is called an index. In Elasticsearch, an index is the highest level entity that can be searched against. The index can be compared to a relational database schema’s database in terms of structure. An index usually contains documents that are all logically related. You can have an index for Customers, one for Products, one for Orders, and so on in the context of an e-commerce website. When indexing, searching, updating, and deleting operations are carried out on the documents contained in an index, that index is referred to by a name.
   2.1 Mappings: This is a schema of a document, where field structure and data types are defined.
   2.1.1 Dynamic: One of the most important features of Elasticsearch is that it tries to get out of your way and lets you start exploring your data as quickly as possible. To index a document, you don’t have to first create an index, define a mapping type, and define your fields — you can just index a document, and the index, type, and fields will display automatically. The automatic detection and addition of new fields are called dynamic mapping. The dynamic mapping rules can be customized to suit your purposes.
   2.1.2 Static: You know more about your data than Elasticsearch can guess, so while dynamic mapping can be useful to get started, at some point you will want to specify your own explicit mappings.
   2.2 Settings: All the settings related to the index goes here, which can dictate how many shards, and replica’s should an index have once to define the retention policy here, besides this any custom data manipulation setting goes here such as tokenizers
3. Inverted Index: A mapping from content, such as words or numbers, to their locations in a document or set of documents is stored in an index data structure known as an inverted index. Simply put, it is a data structure that resembles a hashmap and guides you from a word to a document or web page. The brain of search engines is the inverted index. A search engine’s main objective is to deliver quick results while locating the documents that contain our search terms.

Understanding Elasticsearch Ops Modules

• Shards: Elasticsearch offers the option to divide the index into numerous sections known as shards. Each shard functions as a complete, independent “index” in and of itself and can be hosted on any cluster node. Elasticsearch can guarantee redundancy, which both guards against hardware failures and increases query capacity as nodes are added to a cluster, by distributing the documents in an index across multiple shards and distributing those shards across multiple nodes.
• Cluster: A collection of nodes with the same “cluster.name” attribute is referred to as an “Elasticsearch cluster.” A cluster automatically rearranges itself to distribute the data among the available nodes as nodes enter or leave it. You have a cluster of one node if you are running a single instance of Elasticsearch.
• Replicas: Replica shards, also known as “replicas,” are copies of your index’s shards that Elasticsearch lets you create in any number. A replica shard is essentially a duplicate of a primary shard. One primary shard is home to each document in an index. Replicas offer redundant copies of your data to safeguard against hardware failure and expand capacity to handle read requests like document retrieval or search.
  Replication has two functions, the primary one is to ensure high availability in the event that nodes or shards go down. Replica shards are never allocated to the same nodes as the primary shards in order for replication to even function if something goes wrong.

RDBMS EQUIVALENT OF ELASTICSEARCH

ELK STACK

ELK STACK consists of three parts, one we already talked about Elasticsearch other two are Logstash and Kibana.

Logstash: A lightweight, open-source server-side data processing pipeline called Logstash, enables you to gather data from various sources, transform it as you go, and send it where you want it to go. Elasticsearch, an open-source analytics and search engine, uses it most frequently as a data pipeline. Logstash is a well-liked option for loading data into Elasticsearch due to its tight integration with the platform, robust log processing capabilities, and more than 200 pre-built open-source plugins that can help you quickly index your data. It’s a kind of ETL tool for Elasticsearch.

Kibana: On top of the Elastic Stack, Kibana is a free and open frontend application that offers search and data visualization capabilities for data that has been indexed in Elasticsearch. commonly referred to as the ELK Stack charting tool.

Elasticsearch Usage

Elasticsearch is used for a number of applications, some of them are:

1. Application Search
2. Analytics
3. Fuzzy Searching
4. Autocomplete and Instantsearch
5. User-Defined Searches
6. Log Analytics
7. Security Analytics
8. Business Analytics

Many More…

In a Nutshell:

It can be a lot of Information to understand when starting with Elasticsearch and difficult to comprehend the basic philosophy from blank. Here we tried to provide a brief Introduction to Elasticsearch, such as what is elasticsearch, when to use elasticsearch, why elasticsearch, and what are certain terms and components in Elasticsearch, so that it can make you comfortable taking decisions and bring you closer or make you familiar with Elasticsearch.

Next, we will discuss how can we install and search for queries using elasticsearch. Stay Tuned!!

Written By:

Follow for more informative and insightful blogs.
For more information, visit MoEVing and get moving.

What does a Principal Software Engineer do?

As per the definition,

“A Principal Software Engineer is a technical professional who develops, documents, and tests software to make sure software meets the business goals and end-user requirements. They carry out technical strategies to enhance efficiency and integration and provide technical guidance to the development team.”

And Why hire a Principal Software Engineer?

Principal Software Engineers offer an upper hand in the technical aspects of software development. We require them to:

• Make quick architectural-based decisions
• Prevent technical debt by foreseeing the correct technical approach
• Become great mentors to software engineers

Aditya, a new addition to the Tech Team brings 17 years of technical industry experience to MoEVing. He joined as a Principal Software Engineer, and we ensure that our product is in experienced hands.

Let’s hear from Aditya about his experiences and any learnings he can offer to people starting with software engineering roles.

1. Tell us something about yourself and your connection with science?

Science and technology are Aditya’s best friends.

“I was always interested in science and technology as a child, and I decided to work in either theoretical science or applied science. Initially, when I gave the exam, I had to choose between aeronautical physics and computers, and I went ahead with computers.

I have enjoyed programming since school, and I was interested in its mathematics and theoretical aspects.”

Aditya has worked as a software engineer for prestigious companies such as Microsoft, Huawei, McAfee, Agoda, and Pitney Bowes.

Other than software and tech, he finds interest in music, traveling, reading, playing drums, and admiring nature.

2. What does a typical workday for a Principal Software Engineer look like?

Primarily, I work as a backend developer.

The feature I am working on is Driver onboarding, where drivers can register themselves through our MoEVing app.

Apart from that, I am looking at existing backend projects including, MoEVing charge, DevOps, and infrastructure on AWS and data warehouse, mostly on backend API and database, etc. These are some things I work on a day-to-day basis typically.

Also, I attend meetings with team members where coordination is required on the projects.

3. Who is your inspiration? What inspires you or motivates you to do what you are doing?

“Study nature, love nature, stay close to nature. It will never fail you.” — Frank Lloyd Wright

I was also interested in mathematics and fascinated with the works of Ramanujan, and he inspired me to study mathematics.

If I talk about MoEVing, we are in the EV space, which also inspired me as it would actually make a difference to fossil fuel-based automobiles. With the transition to electric vehicles, there will be an improvement in air quality and a reduction in environmental pollution.

4. According to you, why is technology valuable in today’s world?

Technology is valuable as long as it leads to evolution, consciousness, knowledge, and wisdom for the human race.

It gives a wide berth to people and expands their awareness levels. The information is readily available and accessible to people due to the internet.

There are other technologies like automobiles and aircraft which also contribute to world development.

5. What’s the coolest as well as the hardest part of your job?

The Coolest part 😎

We are making an impact from the ecological standpoint, most importantly, making life better for drivers and people working on the ground. It’s an honor to work for people and help in improving their lives. Apart from that, it’s always cool to learn new tech and meet cool people within the team.

The Hardest part 😓

Sometimes there are quite a lot of open issues that one has to keep track which is also a challenge in itself. In a startup environment, one has to be more dynamic. It can be a tedious task, but apart from that, it is all part of fun and games.

6. What technologies have you worked on, and what do you expect to work on in MoEVing?

So far, I have worked with various technologies. I started with Java, moved to C++, and worked for a long time with C sharp, Javascript, and PHP. Also, I have practical experience with react and MODJS.

And with MoEVing, I have a fair idea of the technologies and languages I will work on. I am working with Python on the backend. I might work with Javascript, SQL, DevOps, and big data in the future.

I expect to continue working on the same technologies and also looking for a chance to explore new technologies like Rust and other programming technologies in the future.

7. How do you like the work culture? What do you find most interesting about working at MoEVing?

I love the work culture at MoEVing. People are friendly and easily approachable. There are no barriers to communication.

We can work at a flexible pace. Apart from synchronization meetings, there is a lot of flexibility in how one arranges their space.

The environment is anti-corporate. The culture is dynamic that is intentional because we don’t want to move in a very rigid manner.

One advice on remote working,

In a remote environment, one has to be self-disciplined and proactive while communicating with others. It’s better to over-communicate than under-communicate. In face-to-face meetings, one ends up communicating all the time. So, we have to take initiative to do that in a remote environment.

8. What are some of the specific advice related to a career path in software engineering that you give the future MoEVers?

As for the career path is concerned, it is too early to say what one really wants out of their career. Sometimes, as time goes by, people change their opinion.

So, I would say, people should not make any pre-conceived notions and explore all possibilities and make an informed decision on what they see they can do down the line.

9. Any learnings you want to impart to the generation from your experience?

Be honest and sincere in whatever you do.

Do something and do it well, or don’t do it at all.

Everybody makes mistakes, the only thing is, one has to learn from them and never repeat them.

One should define what one considers success is. It won’t be something that other people think is a success. One’s definition of success would be different from others.

Go with what your heart tells you where other people may be saying something else, but you know what your heart says.

If you want to be a part of a leading team and grow along with experienced and supportive mentors, join us now.

The offsite meetings offer an excellent opportunity for the tech team to understand the operations closely. It provides an insight into the ground-level operations and poses a question, how can tech ease their workload?

Pune was the first site operational when MoEVing started its journey. We began with our first client with 5–5 2W and 3W electric vehicles. Now, we have 1000+ electric vehicles (Both 2W and 3W).

We have seen immense growth in the last year, and we want to expand to 10x this year. Manually, it is impossible to track 1000 or 10,000 vehicles, that’s where tech comes into the picture. Technology can help them onboard as many vehicles as required with ease and convenience and help drivers perform their day-to-day functions comfortably.

Interaction with Drivers — Retaining and Empowering them

Driving became a source of livelihood for people who lost their job during the lockdown. Even people from educated backgrounds entered the field to earn money.

Therefore, we aim to offer them an opportunity to empower themselves and make a sustainable living.

After recruitment, we onboard the riders, provide the necessary training and assign them to respective clients. Once the 3-day training is over, they can officially start their work.

What is the training comprised of?

Vehicle Operation

Vehicle maintenance

Vehicle Charging

Vehicle Safety

Customer handling

Battery maintenance

Using the MoEVing App

From loading and unloading to delivery of goods, the entire thing is done by the driver. Moreover, they are also in charge of charging their vehicles.

In short, he is the owner of the vehicle.

Our second DCO (Driver-Cum-Owner) in Pune is a 20-year-old boy who started working at MoEVing during the lockdown. It’s been a year, and he bought a 3W with us and intends to buy another EV in the near future.

MoEVing is his first workplace as a rider. Before this, he was studying, but due to COVID, he started working at MoEVing when he saw this as a good opportunity to earn some money. He finds the responsiveness of EVs excellent and is assured that he can make more money while driving EVs.

Fleet Operator- Challenges

One of our fleet operators in Pune was previously working in the employee transportation business. There, he had 40–50 diesel vehicles linked to big companies that help employees travel conveniently.

During the lockdown, they saw a surge in the EV industry and wanted to join the revolution where they saw MoEVing using EVs for goods supply.

The first challenge they faced is to deal with the drivers’ mentality. The process is different from previous work, so they had to make them understand to treat EVs as their own vehicle.

Another challenge is tracking the data of their 50–100 vehicles, which is a tedious task when done manually. Here, tech can help them track and store the data conveniently reducing manpower and man-hours.

Managing Entire Hub

We have scaled up in last-mile delivery, and our next target is to manage the entire hub.

Problem statement:

Suppose you have deployed 10 vehicles to the customer hub, but the customer receives a demand exceeding 50–100 vehicles. So, like MoEVing, there will be another service provider fulfilling the demands.

However, we do not have total control over the hub to deploy 100% of our electric vehicles.

Solution:

Our solution is to convert the customer hub on our vehicles only and become fully dependent on us.

Why do we aim to covert the hub? If a driver is absent for some reason, the customer had to look for another driver to complete the order. However, when we handle the entire hub, and the customer had 150–200 orders a day to complete, our operations team will get the orders delivered. The 100% dependency is on MoEVing from the vehicle, and rider to order delivery.

It’s a new challenge where we learn new things.

Brainstorming Sessions With Team

We ended our offsite meeting with a brainstorming session with Jaya Jha, Chief Product Officer.

The sessions aimed to identify the loopholes and how tech can help run operations smoothly.

As a tech team, we can develop a number of things as we get ideas and suggestions from the users and operations team. However, we have to prioritize crucial tasks and spend time on features beneficial to the users.

We need to define strategies while building a feature on how it can benefit and ease the work of our users, especially Drivers. Our motive is to make their life simpler where they can comfortably get slots on the app.

Jaya also discussed how as a team we can collaborate and make things work virtually so that one’s work should not affect the other even if we work in unison.

We tend to organize tech offsite regularly to ensure tech is aligned with our ground-level operations.

Also, it offers a great opportunity for team bonding and getting to know one another. In this virtual working environment, we make sure team members meet and greet each other once in a while.

Want to be a part of MoEVing and collaborate with your abilities?

Apply right here: https://www.moeving.com/join-us/.

In any industry, people working behind the company are as important as the company itself. They deserve appreciation as they add value to the company with their contribution.

We introduced you to the hidden gems, the innovators of MoEVing behind Product Development in the previous blogs. Then, we were a small team with big ambitions and now we have grown into a big team with even larger goals to create an EV ecosystem that can impact the lives of many people and the environment.

We are a team of developers, designers, and content creators who are ambitious, hard-working, and committed to the profession.

Let us introduce you to the rest of our team and understand how they like working at MoEVing? Oh, and future MoEVers, we all have a small message for you as well. Read on to know more.

Anuroop Reddy, Product Designer

MoEVing’s vision intrigued me towards electric mobility, and it’s something I haven’t tried my hand at before. I believe the time is right, in fact, critical for electric vehicles, and I want to be a part of an organization where I can design products for the future.

MoEVing offered me a platform to take responsibility for multiple tasks and wear multiple hats. I was the first product designer hired by the company. It induced a sense of motivation to build a product beneficial for the user. Also, I got all the support from the people after joining and, that’s something I am really fond of.

Every day I am learning from work and my colleagues. I have hired people, interviewed them, onboarded them. And, the reason I was able to do so was that my managers showed faith in my capabilities.

Message to Future MoEVers

I have worked in fin-tech, data scraping, e-commerce, and multiple domains, but EV mobility offers a different feeling when you design for them.

Even though we have a small team, the efficiency and communication are highly effective. Also, in a start-up, the employees who are working from the initial periods of product building will have the best moments in their life and when the start-up becomes a unicorn. It gives them meaning, a sense of accomplishment, and MoEVing is one such start-up.

It’s just the beginning!

Venkatesh Seshadri, GM Software Quality

MoEVing is one of the handful few businesses that are trying to change the narrative when it comes to Environment and Climate change. There is a need for a radical change in the mindset of people to even start moving towards a sustainable environment.

By being part of MoEVing, I feel I am contributing to the cause in a big way.

By adopting technology to build a holistic platform for EV mobility, MoEVing has put a bold step forward, towards the initiative. The team here makes me feel welcome and supportive in playing my role to achieve the desired organizational outcomes.

Message to Future MoEVers

MoEVing is a company that values the opinion of its employees. It has found ways to communicate about the overall strategy being adopted to achieve desirable outcomes.

There is clarity of thought & purpose when it comes to an individual’s work, and I believe this helps in achieving optimal productivity & a work-life balance. You will find that you have plenty of options to grow professionally.

Priti Sehrawat, Content Manager

The unsatisfactory experiences in professional life build a generic perspective towards corporate work culture. You have this notion that what if this place turns out to be the same as the previous one. No one knows the answer, but you have to take a risk.

I took a risk but it was worth it because the company not only offered me a platform to prove my abilities but also gave me opportunities to widen my skill set. Including writing, I am learning about technology and product development, and I am enjoying it.

I was aware of almost every niche in writing except EV and tech as they were out of my comfort zone. But, when this opportunity came, it was a challenge that made me ask myself, can I ever work in this field? At that time, I didn’t know the answer, but now I can proudly say, yes, I can.

Message to Future MoEVers

At MoEVing, I met individuals with great minds and great abilities to manage a remote team with patience and resilience.

If you wish to work in an environment that provides you with a wide berth to grow and take opportunities, MoEVing is the best place to work. Being a start-up, there will be challenges in your way, but the colleagues will make it fun for you to work and enjoy those challenges.

Even if you are working independently on your task, it’s all about team efforts, and they are always there to support and help you out.

Uttam Kumar P, Software Engineer

At MoEVing, you have the flexibility to complete your projects. Although we do have time constraints, the management offers freedom and flexibility to the developers to decide the timeline. We have the liberty to come up with ideas and decide ways to implement them.

We get all the support from the team members that shows the supportive side of the team. Also, the friendly culture lets you engage with them, and the team members are there to help you out with problems at any point during your work.

When it comes to leadership, we have very good leaders, especially Jaya, our Chief Product Officer. She is very firm and gives us the right advice if we are out of context. It shows great leadership qualities that people have in this company.

Message to Future MoEVers

If you are motivated to work in a company that offers great scope in the future, you should join MoEVing. We are in the initial stages, but in the coming years, I believe we can become a big company in the EV and tech industry.

Shahrear, Software Engineer

My journey at MoEVing started as a freelancer. Before MoEVing, I was working in a settled and well-established company in Dhaka. The decision to switch to MoEVing as a full-time employee was not sudden as I contemplated all the use cases of what can go wrong.

But, I had faith in MoEVing that it would grow one day, and what I would be learning in a start-up would not have been possible in any well-established company. So, here I am.

With the number of learning opportunities I have got here, I have grown as a professional. I am working on the backend, AWS stuff, and data warehousing that I haven’t done before, so it is a platform for me to explore new technologies and learn about them.

Message to Future MoEVers

What you are doing is making an impact on people’s lives, and you can do much for the user’s benefit.

I joined because I believe in its mission. You can join any big MNC where you will be working on a particular project and within a particular area. There is not much room to grow and learn. On the other hand, a start-up offers you to work in multiple areas. A start-up is a growing place where you can contribute your ideas to different departments.

Shekh Md Kibria, Software Engineer

MoEVing has an excellent culture to work and maintain a work-life balance at the same time. The space and work atmosphere is something I enjoy at MoEVing. Moreover, the work and the goal towards which the company is working lured me to the company.

Since I started working at MoEVing, I have seen growth in my work. It made me closer to my dream plan to become a backend architect/solution architect and design a backend system.

MoEVing is a fast-growing company, and the product MoEVing is building is beneficial for billions of people. Thus, I would like to provide my contribution to the product.

Message to Future MoEVers

If you are looking for a company culture where you have a work-life balance and where you can directly apply your knowledge to practice and learn in the process, then MoEVing will be a very good option for you.

So, what’s your plan now? Do you want to be a part of a team that boasts hard work and determination towards success? If so, then let’s come together and reach great heights.
Join MoEVing!

Talent wins the game, but teamwork and intelligence wins championships — Micheal Jordon

In today’s edition of innovators spotlight, we have Shahrear, a Software Engineer at MoEVing sharing his delightful experience working with us.

Shahrear recently joined MoEVing as a full-time employee after working as a freelancer. Shahrear’s dream plan is to establish his own business. Till then, he wants to learn and build skills to make his dream plan successful. He believes in learning new things and is always ready to take up new challenges.

Let’s dive into the engaging and fun conversation with Shahrear to know about him more personally and professionally.

Was the transition in the work environment different at MoEVing from where you were working before?

It wasn’t difficult, but of course, the environment was different. I was working in Bangladesh, an old company set up in 2000. Here, it is a startup, where things are fast-pacing, and it keeps evolving. But I am enjoying it as there are a lot of learning opportunities for me.

Also, I am used to the remote working environment as I was working remotely in my previous company. After 10–15 days of joining, COVID happened, and the rest is history.

The change in the working environment at MoEVing was good for me as it comes with growth and development.

My Journey to Become a Software Engineer!

I did my graduation from the University of Dhaka in Computer Science. Since the beginning, I have aspired to be a software developer. Previously, I was working as a software engineer here in Bangladesh.

After some time, I, along with my friends, started working as a freelancer. I was a freelancer in MoEVing before switching to a full-time employee. The whole transition was new for me. As I was working in a settled and established company and MoEVing is a start-up. So, it made me ponder how things will go once I switch. However, I had faith in MoEVing that it will grow one day and that faith made me join here as a full-time employee.

Strong Connections Stay Longer!

Never Lose Connections with your old Friends — You never know when and where you might need them! That’s why we say, Stay Connected!

Shahrear and Kibria are college friends and also worked in the same company. Shahrear came to know about MoEVing from Kibria. (if you haven’t read the blog about Kibria, you can check here)

Shahrear told,

“Kibria started working here at MoEVing first, and then he referred me. We went to the same university, we were in the same batch and worked together in the same company previously.

We have been together since the first day of university, and we are still very good friends, that’s why I am here. He said it can be a good opportunity then I connected with Jaya, Ashish, and other colleagues. That’s how I got to know about it.”

The Typical Work Day

At 11 AM, every morning, we have a daily stand-up meeting to discuss our previous tasks and what are the next tasks that we need to work on. This is the time to address the issues we have faced in our work and resolve them. We strategize and prioritize our work based on the next release.

Later, I attend other meetings if there are any and get back to work on my coding. After lunchtime, I work on my tasks. The remote working however is great but it also gives you the leisure to take breaks between tasks. Sometimes, I work late after 6 PM. As a freelancer, I used to work at night after my full-time job, but I am working on improving my habit (:sweat_smile:).

The Best Part of Working at MoEVing

I got a lot of learning opportunities, and here, I am working on different stack technologies. I am working on the backend, AWS stuff, and data warehousing that I haven’t done before, so MoEVing has offered a platform for me to explore the latest technologies and learn about them.

I have learned a number of skills after joining here. For example, in the task of data warehousing, I had theoretical knowledge but no practical experience. Here I was able to apply it practically, and it enabled me to expand my skill set. Currently, I am working on a payment rollout that is helping me to broaden my knowledge in the area.

Furthermore, the management is good and gives us ample time on the tasks and deciding what technology or software to use before jumping to a conclusion, so there is a seamless process that I really like.

Stuck in a Problem? Ask away your colleagues!

I try my best at first to solve the problem on my own. My mantra is to divide and conclude, divide and find the solution to the problem. If I am unable to do so, then I talk to my teammates. I do not hesitate to ask whenever I have issues. That I feel is important because remote working limits communication on multiple levels that we are trying to erase and build a smooth communication platform to build greater products.

For example, I was once stuck in a problem with the notifications feature. The problem was when I was working locally it was operating well, but on the server, it was not functioning. Then I pulled Kibria in to find out what I was doing wrong then we found out the problem was not from our end but the server.

So, team members are always there to help you out. If there is any problem where I need help with coding and development, I connect with Ramya and Kibria. We also talk with Ashish about tech-related issues. For decision-making, Jaya is always here to help us.

My Father — My Motivator

I did my high school and college from a village, and then after that, I was able to get into Dhaka University, so it was a big deal for me. From my previous background, my father has always advised me to do better in life. He is my teacher, and he has always shown faith in me that I can work on my dreams. I get the courage and motivation from my father.

What’s the most favorite thing you enjoy doing outside your work?

I love to watch movies, TV series, and documentaries. I love to travel and explore new restaurants. I have even traveled to India on a 14 days tour. I visited Shimla, Manali, Agra, Delhi, and Kolkata. I liked Shimla and Manali the most as the environment was very nice and I haven’t been to the mountains before. Also, we visited by train, and it was a very long journey, but we had company, so we enjoyed it.

Message to Future MoEVers,

What you are doing is making an impact on people’s lives, and you can do so much for the user’s benefit at MoEVing.

I joined here because I believe in its mission, and it will grow one day. You can join a big company, they already have built products in place, and you might have a limited berth to learn. However, if you join a start-up, you will have multiple responsibilities and opportunities to work on. Here, you have opportunities to contribute in different tech areas.

Are you interested in working with us to show us your expertise and learn new skills? Visit the careers page right away and check out the open positions.

That’s how employers can retain their employees by providing a culture of freedom of opinions and growth opportunities.

Today, we are going to introduce you to one of our employees, Kibria.

Kibria joined MoEVing as a consultant/freelancer, and after working for 3–4 months as a freelancer, he is now a full-time Software Engineer at MoEVing. His transition has been great, and he finds it quite amazing to work at a place where he can accomplish his dream plan.

Coming from Bangladesh, a completely different ground, was he able to adjust to the new working environment at MoEVing? In conversation with Kibria, let us walk you through his journey at MoEVing to understand his thoughts and working lifestyle.

Journey to Become a Software Engineer

“After my graduation in 2020 in Computer Science at the University of Dhaka, I worked as a multiplayer backend server developer at TigerIT Bangladesh Ltd. From there, my career as a software developer began and I am moving towards my goal each passing day at MoEVing.”

Kibria comes from Bangladesh with a different background, culture, and work-life experience. At first, it is natural to think he had some challenges adjusting and engaging with people in the company. But, that’s not the case.

In a conversation with him, he mentioned,

“I find it quite comfortable working with people in the company. I like the company culture and especially, the work-life balance. Further, the work we are doing that benefits our users lured me to the company. I am enjoying the space and work atmosphere.”

The Transition from Freelancer/Consultant to a Full-Time Employee

I was doing my full-time job in Bangladesh and also doing some freelance work after graduation as a software developer on Upwork and Freelancer.com. The work was mostly project-based, and I didn’t have any actual profile on any of the platforms. So, my friend created one profile, and out of curiosity, I thought of applying to companies, and there I found out about MoEVing and joined as a freelancer.

After working for 3–4 months as a freelancer, I decided to join as a full-timer as it was difficult to work for two companies. During the day I was working for the company in Bangladesh and at night as a freelancer so I had no time left for my family and myself so I decided to join as full time here.

Since I started working at MoEVing, I have seen growth in my work. My dream plan is to become a backend architect/solution architect and design a backend system where it can handle billions of requests from different users across the world.

In that sense, I am growing since I joined MoEVing. Also, the company has offered me the opportunity to work as a backend developer that helps me move closer to my dream plan.”

How about the Work-Life Balance?

Work-life balance is quite important to keep your sanity intact!

“The work-life balance is pretty good as we strictly maintain the working hours and everyone encourages you to work only during the working period. Also, the opportunity here at MoEVing is good as it’s a fast-growing company, and the product MoEVing is building is beneficial for billions of people. Thus, I would like to provide my contribution to the product.”

The best advice I have ever received is to never give up and dream big. I don’t give up very easily, and if I start something and try to achieve a goal, I will keep pushing myself to the edge until I am satisfied to produce the best outcome of the work I am doing.

Also, I think that if you dream big, then you are more inspired and motivated to achieve your goal, otherwise, you will be restricted in a particular area.

So, dream big and achieve big.

How to Approach a Problem in Kibria’s way!

When I come across a problem first, my first step is to go through the requirements of problems. After that, I try to think about all the use cases that can be the cause of the problem. I try to come up with a vague solution to how I would solve the problem given the cases I have to handle considering the requirement. Then I start the implementation of the problem.

If I am unable to solve the problem, I generally talk to teammates and if we cannot come up with the solution, we approach our tech lead.”

Only Work? No, Kibria has its own way of relaxation and entertainment.

I love to watch movies and web series. I watch Hollywood movies and TV series. Sometimes, I do watch some Bollywood movies and Tamil movies. I remember Hera Pheri and Phir Hera Pheri as two iconic Bollywood movies that I watch to have a laugh and relax my mind.

A message to Future Team Members from Kibria,

Dear Future MoEVers,

If you are looking for a company culture where you have a work-life balance and where you can directly apply your knowledge and also learn in the process, then MoEVing will be a very good option.

So, do you want to be a part of our next project? Check out MoEVing Careers for any open position in your field! Do read how our app came about to get a sneak peek into our product.