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

My must-have apps for daily work

There is no doubt that cool apps can help us be more productive and enjoyable at work. For the time being, I really love the following apps which are used by me almost every day. 1. A personal Kanban In fact, a personal kanban is the most useful app for me. Why does it matter? It is not just a to-do list, but it keeps me motivated every day because it helps me be able to know what my "big picture" is. I usually set up my plans together with a path to reach them. KanbanFlow is my preferred tool. KanbanFlow 2. A terminal Needless to say, a terminal is a must-have app for every developer, especially the ones use macOS/Linux. Due to its importance, I love to decorate and enhance it to be super exciting with various tools such as iTerm , oh-my- zsh , and thefuck . ;) iTerm + oh-my-zsh 3. A documentation "ecosystem" As a developer, I can not remember all things that I have experimented a day. Moreover, a document is really useful for sharing an...

Regex - Check a text without special characters but German, French

Special characters such as square brackets ([ ]) can cause an exception " java.util.regex.PatternSyntaxException " or something like this if we don't handle them correctly. I had met this issue. In my case, my customers want our application should allow some characters in German and French even not allow some special characters. The solution is that we limit the allowed characters by showing the validation message on GUI. For an instance, the message looks like the following: "This field can't contain any special characters; only letters, numbers, underscores (_), spaces and single quotes (') are allowed." I used Regular Expression to check it. For entering Germany and French, I actually don't have this type of keyboard, so I referred these sites: * German characters: http://german.typeit.org/ * French characters: http://french.typeit.org/ Here is my code: package vn.nvanhuong.practice; import java.util.regex.Matcher; import java.util...

Changing source code at run-time with Service Locator pattern

I have a service to get some data but the result can be different basing on where the implementation is. Technically, I have two or more concrete implementation of an interface and I am able to switch using these concrete classes at run-time. That means I have a place to configure it without re-deploying the application. In order to overcome this issue, I use Service Locator design pattern and here I only care about two advantages below: Encapsulating the specific implementation, we just declare the name and don't care about the implementation of the service. Changing the implementation at run-time. Client : an object that invokes the services via Service Locator Business services : services that is used by Client.

My 2017 Review

Passion for System Design After finishing a one year project, my longest stable team (lasted for 3 years) was separated into two smaller teams. Sadly, but that was a good chance for me to become a key member in my new team. My preferred skills were about system architectures; therefore most of the tasks of building the application structures were handled by me. In order to enhance my design system skills, I have spent much my time for reading books closely after work. These following books help me a lot. - Object-Oriented Thought Process | Matt Weisfeld - Head First Design Pattern | Elisabeth Freeman and Kathy Sierra - Java 8 in Action: Lambdas, Streams, and Functional-style Programming | Alan Mycroft and Mario Fusco Junior Technical Architect I was requested to join a technical architect team (aka Team. Alpha) where I actually had gained experiences almost on interviewing candidates for my company (lol). Besides, I noticed myself must improve the skills of convinci...

The culture war at the heart of open source

I enjoyed reading this post: https://words.steveklabnik.com/the-culture-war-at-the-heart-of-open-source Here is my highlight: If you ask a random developer what “open source” means to them, you won’t often hear “software that follows the Open Source Definition.” If you ask them “what’s the difference between free software and open source software,” you’ll often hear “aren’t those the same thing?” or “you can charge money for open source software, it’s not always free.” You may even hear “it’s on GitHub.” In brief, there was a man Richard Stallman (and his team) starting a project called "GNU Project" in 1983. This project was about to develop a free software system. The term "free" here meant "freedom", not only about the price. The Free Software Foundation appeared to support this project. But then, the term "free software" was so ambiguous. "In addition, the ambiguity of the term “free software” was seen as discouraging busine...

vhandit

Search This Blog