Interview with a web developer from Youtube

It would be impossible to deny the massive impact that the video-sharing platform in the technology industry has had on moving the internet forward regardless of your position on video torrent. From pushing the video limits of the browser to pushing ads through WebSocket to prevent ad blockers from detecting them, you need to be clever to innovate at the web’s bleeding edge.
I’ve been fortunate enough recently to meet a Web Developer at Youtube’s biggest video-sharing platform. I wanted to learn about software, how to develop internet APIs, and how to function on the video-sharing platform. Love! Enjoy!
Note: The video-sharing platform industry is very competitive, so they couldn’t answer a few questions. I respect their need to be close to the vest to keep their tricks. the video-sharing platform features a lot of graphic content.
First and foremost welcome to Kenya. How do you find your visit here in Kenya so far?
Haha! Thank you. Actually I love Kenya. The Weather Is awesome and guys are fantastic. Last week when I visited Watamu in Mombasa I was received with a warm heart. I love it here.
Do you use lots of placeholder images and videos during the development process? How far is the content and experience of the end product from the development?
When we develop the sites, we do not use placeholders! Ultimately, what matters is the code and functionality, at this point, we are very used to the interface. At first, there’s a bit of a learning curve, but we’ve all got used to it quite quickly.
When it comes to cam streams and third-party ad scripts, how do you mock such important, dynamic resources during site and feature development?
The player is divided into two components for development. The key feature is introduced by the basic player and fires events. Development takes place in a cleanroom. We want to run those third-party scripts and ads for integration on the sites so that we can find problems in the process as early as possible. We will work with advertisers for special circumstances to enable us to manually trigger events that can normally be random. Probably an average website has at least one video, GIF ads, a few cam performer previews, and other video thumbnails.
Why do you calculate the quality of the page and why do you manage the page as effective as possible? You can share any tricks?
We use a variety of measurement devices. Our player reports statistics back to us on the quality of video playback and general use of a third party RUM program for general performance on the web. WebpageTesting private instances in the open AWS data centers for script tests. It is mostly used to see what might have happened at a given time. It also allows us to see the “waterfall” from various locations and suppliers.
I must assume that the video player is the most important and complex feature on the front end. From embedding video ads, marking video moments, changing video speed, and other features, how do you maintain this asset’s performance, functionality, and stability?
We have a dedicated team working exclusively on the video player, whose first objective is to track performance and efficiency on an ongoing basis. We use almost everything we have at our disposal to do so; browser performance tools, web page tests, metrics, etc. A good QA round guarantees reliability and performance for any changes we make.
How many people are there on the video team? How many developers at the front are on the team?
I ‘d say given the size of the product the team size is lean to average.
During your time working on adult websites, how have you seen the front-end landscape change? What new Web APIs have made your life easier?
I’ve definitely seen a lot of improvements on every aspect of the frontend world; from plain CSS to finally using LESS and Mixins, to a flexible Grid system with media queries and picture tags to accommodate different resolutions and screen sizes jQuery and jQueryUI are slowly moving away, so we’re going back to more efficient object-oriented programming in vanilla JS. In some instances, the frameworks are also very interesting. We love the new IntersectionObserver API, which is very useful for a more efficient way of loading images. We have started playing with the Picture-in-Picture API to have that floating video on some of our websites, mostly to get user feedback.
Looking forward, are web APIs changed, improved, or even developed that you would love?
Many of them we would like to see modified or improved; Beacon, WebRTC, Fetch and Service Workers:
Beacon: some IOS issues where it doesn’t quite work with pageHide events Fetch: No download progress and doesn’t provide a way to intercept requests
WebRTC: Simulcast layers are limited even for screen share if the resolution is not big enough
Service Workers: Making calls to navigator.serviceWorker.a register isn’t intercepted by any service worker’s Fetch event handlers throughout the past few years
WebVR has been growing — how useful is WebVR in its current state and how much effort do adult sites put into promoting VR content? Do haptics play a role on your websites is WebVR?
We are researching web XR and how best to respond to evolving cases of spatial computing use, and we need to support creators and consumers as the largest distribution platform, but they want to experience our content.
But in these new media, we are still exploring what content and platforms should be like. We were the first major platform to support VR, computer vision, and digital artists, and will continue to push innovative and transparent web technology. Functionality restricted by the operating system and browsers types mainly. iOS vs Android is the perfect example when it comes to a completely different set of access and features.
Some iOS mobile devices, for instance, do not allow us to have a custom video player while they force the native QuickTime player in Fullscreen. This must be taken into account when developing new ideas. On the other side, Android gives us full control and we can move our apps into fullscreen mode.
Adaptive streaming in HLS is another example as well, IE and Edge are picky when it comes to HLS streaming performance, because we need to avoid some of the lower values, otherwise the video will stutter and have errors all the time.
What is the minimum current browser support for the adult sites that you are working on? Will Internet Explorer have been phased out?
We have been supporting IE for a very long time, but for anything older than IE11 we recently dropped support. With it, we also stopped working with Flash for the video player. We are focusing on Chrome, Firefox and Safari mainly.
More broadly, can you share something about the stack of the typical adult site? Front-end and/or server? What libraries do you use?
All of our websites are based on the following:
Nginx
PHP
Memcached and/or Redis
MySQL
Where appropriate, other technologies such as Varnish, ElasticSearch, NodeJS, Go, Vertica will be used.
We’re mostly running vanilla javascript for frontend, we’re slowly getting rid of jQuery and we’re just starting to play with frameworks, mostly Vue.js.
From the viewpoint of an outsider, adult sites are usually very similar: lots of video thumbnails, aggregated video content, cam performers, advertising. We work very hard to give each brand some uniqueness at different levels; content library, UX and features sets, and across a lot of different algorithms.
Before applying and interviewing for your current employer, what were your thoughts on potentially working on the video-sharing platform? Did you have any hesitation? If so, how were your fears to put rest?
It never really annoyed me, it was so appealing at the end of the day. The idea that millions of people might interact with features that I’ve been working on was motivating. That proved to be true very quickly, I was super proud the first time I worked on it, and I told all my friends to check it out! It is also promising that video-sharing will never die for job stability!
Sharing that you are working on the video-sharing platform may not be the same as working at a local web agency as far as the end product is concerned.
Do you hesitate to tell people that you are working for the giant video-sharing platform?
I am very proud to be working on these products, those close to me are aware of them and fascinated by them. It’s always a wonderful source of conversation, jokes, and it’s really interesting.
Having worked in agencies outside the video-sharing platform, does the atmosphere differ when working on adult sites?
Here the atmosphere is very relaxed and pleasant. I don’t note any major differences in other companies about the work culture, other than the fact that it’s much larger here than everywhere I’ve previously worked.
Being a front-end developer, with which teams are you working closely? What are the most common methods of daily communication?
We deal with backend designers, QA testers and product managers on an equal footing-most of the time we just go up and talk to each other’s desk. If not, it’s very popular to chat (MS Teams). Then the emails will arrive.
Finally, is there anything you’d like to share on the video-sharing platform as a front-end developer?
It’s really exciting being a part of creating how users experience such a widely used product. We are generally at the forefront of trends and big changes in tech as they roll out, which keeps it fun and challenging.
Interview end
I was enlightened by our interview. I was a little disappointed that while designing apps and models, they didn’t use photos. It’s exciting to see that with WebXR, WebRTC, and Intersection Observer, Youtube continues to push the web’s bleeding edge. I was also pleased to see that the current set of web APIs is considered sufficient to start dropping jQuery.
I wish I could get more specific tech tips out of them; in particular, performance and clever hacks. I’m sure that behind their source code there’s a wealth of knowledge to learn! What questions were you going to ask?
