Yuk Update: ResQVision, ResQTwin, whats been going on, and going forward
Hello folks, after half a year of absence from yukblog, im finally back, and with some spicy updates too.
To explain my-reasonable absence, I have been working my very first tech job! I’m now a research engineer at ResQVision, and have been working remotely for about 5 months by now.
It has definitely been an experience, 5 months ago I was at a really difference place, probably a pretty bad place. But well im not gonna get into that in this post, what matters more is, I thought of myself as more of a gamble, no experience, still have a degree to work towards-and still is, and all that people really had going for was the TrafficLab3D project when it comes to assessing my technical talent.
Well I shouldn’t underestimate myself that much, there was at least something people could use as reference I guess, still honest about the gamble thing too, cause tbh, I was considering my psyche at the time too.
But well, nowadays, I think im doing a lot better now.
My first tech job, and landing it
It was summer 2026, it was around when I was trying to finish my finals, and for my course, I also needed to complete an internship somewhere for credits. For my peers, they would go on to Vietnamese companies around and usually take the internship onsite. For me, well ill be honest at first I wasnt really interested if i was gonna have to go to a Vietnamese place, I was genuinely planning to just go home for the summer, continuing to develop TrafficLab and add more to my personal branding and blog.
For some context, around this time I did decided to publish about my TrafficLab3D project, more specifically on X and on Reddit, im pretty sure during this period, TrafficLab was promoted by like one of those bot like X account that just post github links. But the point is, while TrafficLab and multiple of my demos and guide on Youtube for it has been out for awhile, i still felt reluctant to post them on platforms like X and Reddit, more specifically subreddits like r/ComputerVision and such. Its because like, I knew it could be better, I knew there are things in TrafficLab that I could have made better (It was a bit of a time crunch bc it doubled up as a project for my advanced computer vision course finals, prof did gave me a A+ for it though hehe). Anyway, because I-myself, knew it could be better, so I postponed from really doubling down on it, as if I think everyone else were also thinking like me, only see its flaws and shortcomings.
So yeah to recap, that is how I was thinking, nothing complicated or an emotional lesson here I just said fuck it ill post them anyway, if they critisize ill listen, and what do you know, it kinda blew up on Reddit, but more importantly, multiple opportunities were cold emailing me around the same time.
There was 3 notable candidates after I filter them down: a con-tech (construction tech) company based in the middle east which were honestly closest to big tech, they were huge, had crazy funding, scale, and reach as well, even had an office in SF, and the other 2 were both Australia based start-ups, and considering where I was, when I was, and my immediate constraints (mostly the fuckass degree im shackled to), I decided to went with where I am now: ResQVision.
Across all the “interviews” that I went to, like none of them ask me much of coding tbh, no leetcode, minimal coding questions, they mostly care about 2 things: who i am, and TrafficLab, and yeah interviews in double quotes, because they were more casual talks and back and forth, they were some of my first time using English for my career so I was kinda nervous.
What I’ve been doing: ResQTwin
Interest of Digital Twin Technology
Most of the companies that approached me had a similar pitch: they wanted to do something that relates to digital twin, and my TrafficLab project translate almost directly: a 3D geo-referenced representation of a site (or at the very least a geo-referenced representation that can be presented on a 2D map) that is updated by real sensors, and again most related to TrafficLab, that would be existing CCTV cameras.
Each of the companies work in completely different domain for eachother, but the demand for a digital twin updated by real sensors were common amongst all of them.
And for RQV, that would be maritime (maritime: water environment basically - beaches, rochshores, ports, even swimming pools) digital twin. And their immediate use case and environment would be New South Wales rockshores in Australia.
So in the Oceania people have this recreational sport called rockfishing, where they basically fish in the ocean, usually on rockshores, its usually more exiciting, and more dangerous compared to say fishing in a pond on a boat or something, the ocean can be relentless and unforgiving, an unexpected swell can overwhelm fisherman in a blink, knocking them off their footing, and then the force of it retreating will drag them down into the ocean and it wouldnt be just a matter of trying to get back up, it will continue to drag you down, all while sharp rocks that can even have barnacles shred your efforts of trying to get climb back.
ResQTwin: Maritime Digital Twin
So yeah basically, what I was trying to do was create a digital twin of said rockshores, updated by cameras observing the fisherman, RQV already had the tech to alert when a dangerous situation were to occur, and the digital twin’s job was to identify where that incident occured, and in the future, potentailly predicting when such an incident could occur.
Other than that, just having a digital twin of a site in general is useful, consider it a shared geospatial representation that can ingest or publish all kinds of data and have all kinds of use cases, for the maritime domain, that can be anything from SAR (search and rescue), to analytics, prediction, reporting, and of course, visualization, a picture tell a thousand words after all.
And after about 5 months, I was basically able to successfully bring the digital twin project into production, code named “ResQTwin”
So for this post, I wont really go into detail of the technicalities of ResQTwin, what I can say that it is v0, it seems to have been working well enough for v0, and I will definitely be continuing to improve it to match my evolving standard, and of course, the requirement of the customer as well
Here are some more visuals for ResQTwin:
- First, the proof of concept, though it was similar in idea to TrafficLab, the execution and conditions were actually pretty different:

- At this early stage, the concept was codenamed “ResQLocate”, and then, development demos that followed the proof of concepts, codenamed “ResQTwin”.
- And finally, with help from my senior manager, we managed to bring ResQTwin v0 into prod (I also almost bring my first memory leak into prod :>, luckily we did had a dev server, and my manager helped me indentify and resolved it before it hit prod)



And ResQTwin was even showcased at a parliment meeting, I heard that people was pretty interested in the technology!


Going forward
Welp, hopefully this update was a good read after disappearing for 6 months, part of why it took so long was maybe because I wanted to like prove myself or something, but now, after v0 is in prod and will continue to grow, and now that I have a real module that im responsible for in production, I think im feeling a lot better now, definitely dont feel the gamble mentality as much anymore, but there is still work to do, and im trying to navigate it as well, maybe ill talk about those stuff in follow up posts, about like AI-assistend engineering in 2026-2027, about careers of CS students, and maybe even about things that are unique to my circumstances, being a Vietnamese who wants to leave and havent been able to find luck in the academic path for it.
With all that being said, I do intend to be more active on my blog and socials now, lets just wrap it up, I feel alright now, thanks folks, until next time.