A User Guide To Working With Huong

Introduction

I write this user guide to help us (you and me) have a good collaboration at work. I hope you also share yours.

How I view success

We all feel passionate and happy at work.
We all enjoy discussing transparently.
We take it easy to give and receive feedback.
After all, we together develop and bring valuable applications to users.

How I communicate

I mostly prefer a face-to-face conversation.
Just leave me a message on Slack if you don't want to come to my desk.
For a big topic which takes more than 30 minutes, we should have a meeting.
Only send me emails only if stuff is very formal or out-of-office hours

Things I do that may annoy you

I do practice the Pomodoro technique so that sometimes you see me in the "do not disturb" mode.
Often to make things clear, I am at ease talking frankly with you.

What gains and loses my trust

It is easy to gain my trust when you commit to what you say. You show your passion and endeavors to achieve that.
It is easy to lose my trust when you don't focus on your work. You affirm what you haven’t experienced. For instance, you have never tested your implementation on the servers but you say you have done it.

My strengths

I know a good product is built by a well-collaborated team. I do care about teamwork.
My passion is to bring valuable products to users. I do care about both the technical and business of applications.
I motivate myself to expand my skill set every day to make better applications. I am a fast learner and my skills are wide.
I adopt the grit mindset. I believe I can solve most of the problems with my perseverance.

My growth areas

Development skills (Backend and Frontend)
- After graduation, I began building enterprise web applications using Java as a primary programming language. For most of the projects, I used the JSF framework and Axon.ivy platform. I had nearly 5 years of experience in this field.
- Currently, I am using JavaScript as my primary programming language. I enjoyed reading You Don’t Know JS.
- In my spare time, I am also learning Android to develop my side projects.
Operation skills (DevOps)
- I gained some fundamental knowledge about Computer Networks and Telecommunications such as operating systems, IP addresses, and security in the university as it is my major.
- I have been working with some tools: Jenkins, Docker, OpenShift, AWS.
Soft skills:
- I keep learning English for a good communication skill
- I work together, observe, and grow my teammates to enhance my leadership skill.
- I follow Buddhism (especially Zen/Thiền) as my philosophy. I believe everything in this world is connected. I no longer struggle to answer the kind of questions “Who am I? Why am I here?”. Some of my best friends are atheists, Protestants, and Catholics; we all feel happy when talking about our own beliefs.
Computer science
- Architectural design: from the level of code to systems.
- In my spare time, I enjoy spending time with some friends to take research and build side projects using facial technology (a field in Computer Vision).
- Cryptography is also my interest. Currently, I also spend some time to build a pet called FIDO2 Authenticator.

References:

https://lg.substack.com/p/the-looking-glass-a-user-guide-to

https://roadmap.sh/

https://github.com/devradar/devradar

Comments

The HelloWorld example of JSF 2.2 with Myfaces

I just did by myself create a very simple app "HelloWorld" of JSF 2.2 with a concrete implementation Myfaces that we can use it later on for our further JSF trying out. I attached the source code link at the end part. Just follow these steps below: 1. Create a Maven project in Eclipse (Kepler) with a simple Java web application archetype "maven-archetype-webapp". Maven should be the best choice for managing the dependencies , so far. JSF is a web framework that is the reason why I chose the mentioned archetype for my example. 2. Import dependencies for JSF implementation - Myfaces (v2.2.10) into file pom.xml . The following code that is easy to find from http://mvnrepository.com/ with key words "myfaces". <dependency> <groupId>org.apache.myfaces.core</groupId> <artifactId>myfaces-api</artifactId> <version>2.2.10</version> </dependency> <dependency> <groupId>org.apache.myfaces.core<...

How I did customize "rasa-nlu-trainer" as my own tool

Check out my implementation here Background I wanted to have a tool for human beings to classify intents and extract entities of texts which were obtained from a raw dataset such as Rocket.chat's conversation, Maluuba Frames or here . Then, the output (labeled texts) could be consumed by an NLU tool such as Rasa NLU. rasa-nlu-trainer was a potential one which I didn't need to build an app from scratch. However, I needed to add more of my own features to fulfill my needs. They were: 1. Loading/displaying raw texts stored by a database such as MongoDB 2. Manually labeling intents and entities for the loaded texts 3. Persisting labeled texts into the database I firstly did look up what rasa-nlu-trainer 's technologies were used in order to see how to implement my mentioned features. At first glance rasa-nlu-trainer was bootstrapped with Create React App. Create React App is a tool to create a React app with no build configuration, as it said. This too...

The power of acceptance test

User Story is the place PO gives his ideas about features so that developers are able to know what requirements are. Acceptance tests are these show the most valuable things of the features represented by some specific cases. Usually PO defines them, but not always. Therefore, refining existing acceptance tests – even defining new ones that cover all features of the User Story must be a worth task. Acceptance test with Given When Then pattern If we understand what we are going to do, we can complete it by 50% I have worked with some members those just start implementing the features one by one and from top to down of the User Story description. Be honest, I am the one used to be. What a risky approach! Because it might meet a case that is very easy to miss requirements or needs to re-work after finding any misunderstood things. I have also worked with some members those accept spending a long time to clarify the User Story. Reading carefully of whole User Story by defining...

Improving the execution time of CI pipelines

Executing a large number of tests, especially integration tests, takes a lot of time. For instance, the pipeline of one of our projects for each Pull Request previously took nearly 30 minutes, including over 1 thousand test cases. This article guides you through several good techniques that we have discovered and applied to improve the time-consuming process. Parallel stages Analyze the current phases in your pipeline and categorize them in parallel. For example, we can separate the build and verify code of Node.js and Maven modules simultaneously in our Jenkins pipelines. Please mind using the setting failFast whether you want to abort the pipeline immediately. Read more: Parallel stages with Declarative Pipeline 1.2 (jenkins.io) Parallel test execution If you use Maven, t he plugin maven-failsafe-plugin is used to execute integration tests during phases integration-test and verify the build lifecycle. It allows us to execute tests in parallel. There are many settings related ...

Mindset at work

Fansipan mountain As a mentor, I always give to my new members the following practices as my advice for mindset at work. “A over B” means while there is value in the items on the right, we value the items on the left more. Solution over Technology We should approach to solve the problems rather than depending on technologies. The technology limitation should not our excuse to reduce the quality of the feature. For example, we’re strong at React, but we are willing to learn a new framework Meteor due to customer needs. We are software engineers, we are good at problem-solving. Technologies are our toolbox. Contribution over Complaint When we encounter and find pain-in-the-ass issues such as lacking documentation, old frameworks/libs, lacking testing, etc.. we try our best to resolve them! Refer to The Boy Scout Rule: “Always leave the campground cleaner than you found it.” Collaboration over Following Sometimes you even need to consult customers to bring great custom...

vhandit

Search This Blog