Sinh Tran is a TA for CS 6300: Software Development Process. Keep reading to learn more about Sinh!
What do you do professionally?
I’m currently working as Engineering Manager at Postclick, building and mentoring a team of engineers to utilize best practices of software engineering.
Why do you TA for OMSCS?
Prior to becoming an OMSCS TA, I already did a lot of knowledge sharing and inspiration by writing articles and speaking at conferences (DroidConf, DevFest, etc.), so TA-ing for OMSCS is just another way for me to do knowledge sharing and inspiration. But more than that, as a master student (in contrast to PhD), it’s quite hard to build a lasting relationship with the professor and other awesome people in the teaching staff. Becoming a TA gives me the opportunity to “hang out” with this group of highly knowledgeable and motivated people. In short, it’s about building a quality network relationship.
What is your advice for future OMSCS students?
Thinking about whether taking OMSCS is worth your time before applying, and even during the journey. Don’t fall into the sunken ship fallacy. I’m completely happy with my journey, but I also know others who are miserable, but hang on just because of the time they have already invested. For me, it would be a lose-lose situation, in which the students just lose more time, while GaTech/OMSCS has more detractors (instead of promoters).
What's your preferred programming language, and why?
Flutter is my preferred technology to work with. It’s built on top of Dart language. To be honest, Dart is not among my most favorite programming languages (that would be TypeScript for high-level, Python for academia and data processing, and Rust for low-level). However, Flutter as a framework blows away any potential disadvantages of the language, and just let us (that is: me, my software engineer peer, my UX/designer peer, my PM peer, altogether) enjoy the realization of our idea in record time, without compromise of code or product quality. It is because, as a software engineer, I have always valued a quick feedback loop. Before Flutter, I could only achieve a quick feedback loop during my coding with non-UI behavior through TDD. Any change in UI was tedious for me individually, and then (and also because of it) there were tensions between engineers and UX. Then came React Fast Refresh, which had some shortcomings but was a big leap. And now with Flutter, it’s like a dream come true. Instead of having a contentious relationship, engineers and UX/designers now have the same joy working with pixel-perfect products effortlessly.
Find Sinh on...
LinkedIn: https://www.linkedin.com/in/truongsinh
Twitter: https://twitter.com/truongsinhtn
Personal Website: https://developers.google.com/community/experts/directory/profile/profile-truongsinh-tran-nguyen
