Skip to main content

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

Popular posts from this blog

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 to apply Lean - Kanban for your business

This is the topic of Scrum Breakfast meetup this time, speaker: Ms. Phuong Bui - Technical Project Manager of YOOSE Pte. Ltd. http://www.meetup.com/Scrum-Breakfast-Vietnam-Agile-and-Scrum-Meetup/events/230313727/ Lean comes from Lean manufacturing is a method that focuses on elimination of wastes. In other words, this is a set of principles for archiving the quality, speed and customer alignment. The first time I knew about the term "Lean" is  from the book Software Craftsmanship . Sandro recommends if we want to transform our pet projects into a real business, we should get familiar with Lean Startup concepts. In this talk, Ms. Phuong pointed out some major wastes includes information (ex: unclear requirements), processes (ex: waiting), physical environment and people. Knowing what the problems should be the best way to eliminate them. The difference between  Single item flow and Batch processing is the second main point; and it is the Lean's idea. Batch pr...

The Evolution of Team Collaboration

I n my point of view, if a team has a good collaboration, team members will achieve the following: To be more effective To make work more enjoyable I have been working for a company for nearly four years as an software developer. Working on various projects from maintaining existing systems to developing a substantial product resulted in me moving to new teams three times. Actually, my most stable team lasted only around three years.  Every time I've moved to a new team, I have a chance to work with new members and a new team culture again. Indeed, I realize that there is a process of developing the team collaboration which gets better time by time. I think it is an evolution ! Phase 1: Poorly collaborate For example, that is when the team members have the following issues: Only work on his/her area of expertise Don't communicate to others Be not confident to take on new challages Don't listen to other members. Subsequently, the team ha...

Just another career path

As a software engineer, I recently have heard of a lot of feedback from my colleagues and friends that they don’t see their career path or they don’t know how to move to the new levels in their company. No exception, I used to have that thinking before.  In my opinion, there is a very important reason why people are struggling to find the answer because “career path is not always the job titles”. Normally, each company has its own job titles such as junior-level developer, middle-level developer, senior-level developer, teach lead, software architect, CTO, etc. Hence, it is not true that a job title is reasonable for every company. The interview is often conducted hardly to find a candidate matching the company title. If we have a good enough job title standard, the interview would take place very easily, right? Therefore, I prefer to define my own career path through what skills are gained under a job title. But wait, why do I need a career path? To me, a career is an indispensabl...