#DFUncensored - Huy N.

Duy Nguyen  –    –  

Huy N. - How I ended up being here

A brief intro on yourself and how you choose Dwarves Foundation in the first place?
My name is Huy. I’ve worked as a Backend Engineer for three years already. Back then, I got introduced to Dwarves Foundation through Thach Le, an old friend and also a former Dwarf.

What keeps you here this long?
I think there wouldn’t be so many opportunities out there to experience. At DF, I got to work overlap on different types of work and up to several domains. Other companies might tie me to backend work only, which sucks. So I think what sticks me here is the chance to experience. One other reason is the environment I’m surrounded by: Supportive teammates and a BOD who recognizes even the tiniest effort.

You also work as an Engineering Ops, so how is your typical workday looks like?
I barely count the hours. But my recent routine starts at 8AM due to a remote working schedule. It took me an hour for breakfast and got prepared. Then I start the work at 9, stop for a 30-minute lunch at 12, and get back to work until 6PM. Then I take a long break for dinner and family gathering, get back to clean up some small task, and finish by 10PM. I guess my day transpires for 10 to 11 hours.

Sounds pretty long. Have you ever thought that you’ve been forced to OT?
There is a formula for this. Distance = Speed x Time. By distance, I mean the year we are willing to spend for this job. For example, I’ve been in this industry for 3 years, but another Engineer has been here for 10 years already. Technically, I can never compare that time to him. To reach the distance he has gone, I must put double, maybe triple of the time to speed up. That’s how we shorten the distance and grow up faster. 8 hours a day is still good, as long as you make every minute count.

A product crashes in the middle of the night and must be fixed in short notice. If your team happens to deal with that, and your teammate requests an OT payment to get the job done. What would you do?
Being in charge of a product means it’s your responsibility to make it work. That is off the negotiation. If my teammate refuses to work without an OT, that reveals his poor work ethic. I don’t mind the hot fixes. As a leader, my responsibility for the product is bigger than anyone else. But that will change my judgment on that teammate, and in future cases, I might refuse to work with that guy.

I can tell your mindset is quite different from other developers at your age. Do you think that what helps you earn what you’re having now?
I think attitude and mindset play vital parts at the early stage of every career. It even outweighs the skills. Skills upgrade your ability up to 20%, but attitude and effort bring you to wherever you want. Effort doesn’t work unless your attitude towards the job is positive. Skills become useless once your attitude is out of control.

Between an intern with a good background and an intern with a proactive mindset, your choice?
Lol, needless to say, I’ll go with a cool mindset. For the record, my background didn’t stand out. I started from the network then turned into programming, and I made it happen. Education can’t speak much for a person. Processing a cool mindset is easier than working with someone who refuses to think out of the box. My team is an example, I picked out the right heads, and they still stick with me through the times.

Why Software Engineering (SE) instead of other majors?
Because SE makes a killing, I’m telling you. Back in college, I had 2 options. One was to follow Chemistry, and the other was IT. But after full consideration, IT seemed to bring more chances to earn a better living. I’ve always wanted to be financially autonomous since I was a little kid, so I’ll grab any opportunity that stops by.

Have you ever had a second thought on SE after a long time running with it?
I always tell the juniors, chasing after money is not a wrong choice. It's a solid motivation. But I hope they can find other targets to make the job more meaningful. It doesn't have to be a huge one, but it should be inspiring enough to push them to grow. At this moment, I'm happy with what I do. Build useful tools that bring impact to others. Of course, I still make money out of it, but it'll be more fun once you know your work matters to people.

I heard you mentioned the real meaning of being a SE. Can you give us a broader view?
The meaning of SE is to support other industries, I believe. It tackles their problem and makes it better, such as reducing operating costs or resolves social issues. For me, SE means more than just a mundane programming service. Once you develop a product, it should come with long-term value. It’s our job to advise the best solution and must be customer-oriented, rather than being a short-term service provider.

In your view, what makes an excellent engineer?
Logic must be the most essential qualification. The nature of SE is all about coding and data processing, which requires logical thinking and the ability to catch-up quickly. Software changes really fast. Programming languages and industry trends move constantly. If you can’t adapt, the chance of being left out is inevitable.

Would you prefer to work with an experienced engineer with 1 language only or a flexible one with the knowledge of multiple languages?
Each language solves a different problem. That depends on the need of projects. For instance, Goland helps developers to collaborate effectively. Software written in Golang can be pushed on Cloud and better make its way to the open-source market.

Ruby or Node.JS is simpler and faster to code a product. These languages will be used for projects with a short development time. So basically, I don’t care how many languages an engineer can code. Their logic and their roadmap for the project will raise my eyebrows. I’ll give a pass if a CV portraits the person’s level of professionalism. A direct interview will reveal more about the person himself.

Many developers out there compare their paycheck from different companies. Some of them claim that the income of engineers is higher than in other jobs. Do you agree?
IT indeed makes more money than other jobs, due to its high demand for product development. But for the comparison part, I think it’s better to think this way. Focus on the income we earn from now until retirement, instead of the monthly payroll number. Some choose a different job because they wish to optimize their current payroll. Others, like me, will prefer to maximize the final income. My first years after graduation were spent on learning, experiencing, and skill upgrading to better boost up the self-value. Depending on the goal, people have their type of approach.

So what if you’re put between a company with a great offer; and a company with a lower paycheck but more chance for self-development?
Damn, this is hard. I guess if the value of the 2nd company is bigger than their offer, I’ll go for them. But if at that time, my goal is to earn as much as I can, the 1st one will be my option.

During your time as a leader, do you have any difficulties working with teammates who are older than you?
I’ll be lying if I say there is no pressure. There is. As I’m younger than them, sometimes it’s hard to give feedback and judgment. But people are very open to receiving feedback since they know that it makes things better. Personally, I don’t care much about their age or expertise. I value their ideas and vice versa. All decisions will be made out of data and working processes with no bias of external factors. I find it lucky that every team in this company lives by that code.

Have you ever gone through a team conflict?
Lol definitely, but we try our best not to make it a problem. Conflicts of ideas happen all the time, yet we understand that's what it takes for good business. What's done is done. We don't keep score or let it bother us much. Even after a harsh meeting, we can still sit back, have lunch, and shoot the breeze like usual.

Do you have to stand up and solve the conflict, or will people work it out on their own?
Usually, we make sure everyone gets on board with the resolution and call it a day. Once you put the project as the top priority, it'll be easier to keep things sane. No ego or bias on the table.

Any advice for the soon-to-be engineers?
Spend more time on it, especially when you're a junior. It's a win-win trade-off. The more time you put on, the better value you make. Guess that's my wrap for this whole sharing, after all.

Work with us

Drop us a message if you need any helps from the Dwarves

Let's build something