One panelist became a web developer without knowing any JavaScript
A backend developer with no JavaScript experience joins a Bloomberg video team and learns the stack through code reviews and a mentor, while another engineer helps take HBO Max from the US to more than 60 countries. Moderated by Pooja Malpani, Head of Engineering at Bloomberg Media, this panel asks what web development really involves today. So what separates developers who thrive in a field that changes almost weekly?
Hear how practising engineers get hired, ramp up, launch safely and keep learning in web development
Pooja Malpani, Head of Engineering at Bloomberg Media, moderates a panel with Bloomberg engineers Jenny and Abhilasha and Warner Bros. Discovery engineer Chi on what web development involves today. The panelists argue that the field is broad, fast-changing and open to newcomers, and that mentorship, testing discipline, curiosity and strong fundamentals matter more than any single framework.
“I think, um, sometimes folks, um, forget that fundamentals are so much more important than picking a particular platform or a particular framework.”
“Because the problem is not of having enough information or training material, the problem is that there's too much.”
What you will learn
Map the scope of web development, from infrastructure, APIs and databases to front end, accessibility and diverse devices.
Ramp up in an unfamiliar stack by leaning on an onboarding buddy, a mentor and reviews of teammates' pull requests.
Plan launches around heavy testing, phased releases, blameless reviews, caching, bottleneck checks and mobile performance.
Choose JavaScript or Python as a first language when moving into web development from another field.
Rely on fundamentals and your professional network to stay current and to keep imposter syndrome from holding you back.
Key takeaways from the speaker
Challenges in the field
Scope of Web Development
How to land a job in Web Development
Details
Level
All levels
Format
Panel
Technical depth
Introductory technical
For
Student, Early career, Career changer
Length
38:35
Published
July 2022
Questions this talk answers
How do you ramp up quickly in a first web development job?
Abhilasha credits an onboarding buddy who became her mentor, Bloomberg's new hire training, and studying teammates' pull requests during code review. Contributing to a real project from scoping to release also helped her learn fast.
What should you check before launching something new on the web?
Jenny stresses testing, including with testers unfamiliar with the application, phased feature releases and a no-blame approach to bugs. She also checks scalability, caching, stack bottlenecks and whether the site works on a slow mobile network.
How do you stay up to date with web development technologies?
The panel recommends internal communities such as Slack channels and guilds, conferences, and discussing what you learn with colleagues. Malpani notes the problem is too much information, so leaning on your network to curate makes sense.
Can someone from a non-tech job move into web development, and which language should they start with?
Yes: Jenny's team includes a former actor and an opera coach who switched through a bootcamp and self-teaching. She suggests JavaScript, or React for front end curiosity, and Python for those drawn to back-end work.
How does a tech lead's role differ from a developer's?
Jenny says tech leads take the lead on architecture, mentor other developers and improve internal developer workflow. Malpani adds that they look at the project as a whole, set the tech strategy and define the modules others build.
About this talk
Why is web development interesting? What are the challenges in the web world and how is it evolving? How do you become a great web developer? Join to hear multiple perspectives and answers to these questions and more from experienced web developers and senior managers.
Fundamentals over frameworks and imposter syndrome (65 s)
I want to say hi to everyone here. My name is Tuja Malpani. I support the Media Engineering Group at Bloomberg. I'm joining you today from a small conference room in our headquarter office in New York City. At Bloomberg, my teams are responsible for a lot of the tech systems needed to author and share news, data, video, and other content with consumer audiences, as well as syndication partners around the world. To elaborate, this includes all the tech systems used by our newsroom, you know, editors, journalists, and other members to draft news stories, to distribute the content to the various clients, including web, mobile, connected devices, and also other ways of engaging users, like via newsletters, podcasts, live streaming, et cetera. The teams also support Bloomberg's marketing websites, various Bloomberg
philanthropy sites, Bloomberg Connects, and infrastructure. Prior to Bloomberg, I led the subscriptions and user management at HBO. We redesigned the backend services to ensure that HBO could scale to meet the growing streaming demand. This is back in 2015, when the app then had really not been built with the kind of scale that HBO was starting to see. So my team was brought in to modernize the entire application where we containerized, used Kubernetes, moved to the public cloud, moved to the public cloud, availed of the auto scaling, broke down our monolith into microservices, the full mix to ensure that we could seamlessly trade, you know, scale for high traffic shows like True Detective or Game of Thrones.
Prior to that, I worked on Skype for Business for almost 10 years. So in short, I've been in the, you know, web development space for a long time, for nearly 22 years. Outside of this, I'm also very active in the various diversity and inclusion circles. I'm coaching, mentoring, and sponsoring, and they're all three different things, leaders, both inside and outside Bloomberg. It is my pleasure to introduce the panel on web development trends.
Today, hopefully you're here for the for that session. If not, come along for the ride, you'll perhaps learn a few things that you can take back. I'm joined by three strong technical leaders, and I let them introduce themselves. Jenny, would you mind starting? Sure. Hi, everyone. My name is Jenny. The team that I lead is part of the Bloomberg Marketing Engineering team. Like Pooja mentioned earlier, we support over 100 marketing websites that are both the main products of Bloomberg, the company culture, Bloomberg Industry Group, and Bloomberg Philanthropy websites. My team is full stack. So we deal with anything from the Kubernetes infrastructure that our websites are hosted on, to a server-side code, to a server-side code, to a server-side code, to a server-side code, to a server-side code. So what we're going to do here for that session?
Hello, everyone. My name is Jenny. Hi, everyone. My name is Jenny. The team that I lead is part of the Bloomberg Marketing Engineering team. Like Pooja mentioned earlier, we support over 100 marketing websites that are both the main products of Bloomberg, the company culture, Bloomberg Industry Group, and Bloomberg Philanthropy websites. My team is full stack, so we deal with anything from the Kubernetes infrastructure that our websites are hosted on, to the server-side code, and the front-end components that are involved in that as well. I started at an interactive agency about 10 years ago. Oof, I need to date myself there.
And I worked at various companies and brands like CBS News and Space.com. I did web development work, especially for their content-rich websites. I became a manager about a little over two years ago, and it's been a fun ride so far. Over to you, Abhilasha. Thanks, Jenny. Hi, all. I'm Abhilasha, and I'm a full stack developer at Bloomberg, and I'm currently part of the Bloomberg Multimedia Engineering team.
Our team is basically responsible for serving all the content, all the multimedia content that you see on Bloomberg.com, as well as its customer-facing sites. So be it like the images, videos, even the audience that you see on Bloomberg.com, are managed and handled by our team. Being a full stack, I think I get to work on very diverse technologies, ranging from JavaScript frameworks like NextJS, to even working on applications based on Spring Framework for Java.
So I joined Bloomberg two years back, fresh out of college. This was my first job in the States. So it was a very nice experience. But despite being here for two years, I feel like I get to learn something new even every day. Apart from that, so let me share this, like I received the opportunity to work with Bloomberg through a similar tech conference for women.
So today I'm glad that as well as excited that I get to contribute back to this community by sharing my experience as a web developer so far and with you all. So yeah, with that I'll pass on to Chi. Hi, I'm Chi. I'm from Wanda Brother Discovery, which is a newly formed company through the recent merger of Wanda Media and Discovery, two very popular content and streaming service providers.
I've been working on backend service for the past five years on HBO Max and its earlier version, HBO Now and HBO Go. HBO Max is one of the major streaming service in the market. We currently have more than 76 million subscribers and support a wide range of clients, including web apps and all major devices. I am leading the partner integration team, which defines how we integrate with external partners, such as video program distributors, telecoms and other business partners to create a seamless user experience on subscription, registration, authentication and authorization for HBO Max on all devices.
The team plays a very key role for the growth of HBO Max, both domestically and internationally. Before joining HBO in Wanda Media, I worked on assistive technology, language modeling, language database tour, text predictions and text input SDK for mobile device and automobile. Before that, I have worked on UI framework architecture and design for Android device in HTC.
And before HTC, I worked on video injection for MSN video and video audio codec for Windows at Microsoft. So you can see in summary, I have had a wide range of product ownership experience in multiple industries. I have worked with global teams and business partners across North America, Latin America, Europe and Asia. Web development certainly is one of my favorite areas. Thanks.
Awesome. Jenny, maybe we'll start with you. What does web development mean to you? Yeah, web development means, you know, anything and everything that has to do with the internet. It goes from the infrastructure that stands up the websites, the backend code that provides the API connection to the database. Oh, yeah. Don't forget about the database. I mean, that's, you know, where you store your content and the information that you need.
Front end is also a huge part of web development and there is new technology almost weekly, especially to keep up with the innovations that's been happening from all aspects of web development. In my opinion, web dev is this moving well of new creations, which can be both complex and simplistic. You know, in terms of simplistic, we have new languages that give web development a lower bar of entry, especially for students.
Well, web applications can be created to power huge marketing campaigns like sending emails, keeping track of the email opens and deliveries in the millions. Also taking into consideration of the users who will be using the product, right? It could be anywhere from figure out solutions for low bandwidth, accessibility, all different kinds of browsers and devices and even cultural differences.
Now people view a web application. There's endless possibilities and I can't wait to see what else we can do and what problems we can solve for. Sounds like a lot. But you also mentioned that it can be simple. So hopefully some of that comes through in the subsequent questions or discussion. Abhilasha, how did you become a web developer?
That's a good question. So I'm going to be honest here and say that I did not plan on becoming one. It just happened by accident. But now I'm so glad that it happened. So to tell you my story, I had always been a backend developer before joining Bloomberg and had no experience with JavaScript frameworks, you know, which are the bread and butter of a web developer.
But one of the advantages of joining Bloomberg as an entry level hire is that we are given this opportunity to choose our own team after the new hire training. So I was I meant by choosing my team. I was sure about one thing that I was open to learning new technologies. But at the same time, I wanted to make sure that I choose a team whose products appeal to me as a user to.
So when I came across this team called multimedia engineering, I was really blown away by the really cool products like, you know, video player, which is used on everything that you see on all the video pages that you see on Bloomberg dot com. And not just that, they also have they also manage the infrastructure as well as applications related to entire video streaming pipeline.
So I was really interested in that. I was nervous that I did not know JavaScript, but at the same time, I was really curious to learn how, you know, how to develop these web applications that support such a high traffic website like Bloomberg dot com, which receives, I think, around a million users every day. So with that, I decided with that thought in mind, I decided to join this team.
And that's that's how my journey to become a web developer began. So I think you would agree with me, Pooja, that, you know, most of the web developers are born in a similar fashion through their love for the web products that they are developing, as well as the curiosity to learn some the new things work behind the scenes.
Sounds like a very happy accident to me, Abhilasha. Expanding on that, you said you got the job almost by happenstance. Once you got the job, did you have to hit the ground running? If so, how did you manage that? So, yeah, like I mentioned, I had never worked with JavaScript frameworks before, and I was a bit nervous.
But at the same time, I was curious and very willing to learn new technology. So so that's so I one of the selling points I feel about Bloomberg as an organization is its mentorship culture. Right. When I joined the team, I was given an onboarding buddy who also later on became a mentor and I gained so much knowledge from him.
So he was always there to help me out whenever I had doubts. He also exposed me to various communities and guilds that we have within our organization. And as well as he also helped me, you know, by scheduling regular catch up sessions with me to make sure like I'm doing all right with the code base. So all of that really helped me ramp up real quick with the tech stack of our team.
But other than that, I would also like to mention that Bloomberg provides this new entry level new hire training to all the new hires, which helps you gain a lot of knowledge, not just related to web development, but also software development in general. So again, that helped me gain a bit more knowledge about how industry processes work and how development process works in general.
Another thing I think I would like to mention is that which helped me a lot in becoming familiar with the tech stack was just going through the whole code review process. I learned a great deal about new technologies, not just technologies, but libraries, you know, new techniques and even new design patterns. So just looking at my teammates for a full request.
And at the same time, I was able to also broaden my own skill set. And it also helped me ensure that, you know, I was following the same good coding practices and my own full requests too. So I think all of this helped me set up the floor, you know, where I can be productive most of the time.
So apart from all of this, I also feel like I joined Bloomberg at a very good time because my team had just begun working on this cool new project called Quick Take, which is an OTT brand under Bloomberg, which also has its 24/7 live stream. So we were supposed to make video pages for it. And even though I was new on the team, I was given this opportunity to contribute in all stages of this app development, right from beginning from, you know, having meetings with stakeholders and designers to scope out the technical requirements till, you know, jumping on to a meeting to release the application actually in production.
So I think that was overall a really good experience for me. And it helped me understand the different ins and outs of the entire web development process at such a large scale. So I think to conclude, I would say overall the support and encouragement that I received from the team, as well as being able to be part of such a large scale project right from the beginning, helping hit the ground running.
What you said about learning from your teammates, you know, code reviews, looking at their pull requests, I think that that can't be understated. And I feel the same about learning from your teammates design, you know, design reviews as well, system design reviews. So really the scale, the learning can be scaled if it's not just the projects that you're working on, but also, you know, from the projects that your colleagues are working on.
I'm glad you shared that. So moving on, why is web development interesting? Chi, based on your experience, is this something you would recommend? And you mentioned in your intro that this is an area that you're very interested in. But would you recommend this to, you know, the up and coming software developers or web developers? Yeah, web development is very interesting.
First and foremost, web development is a fast growing industry. There are tons of high paying jobs opportunities. Website is a basic need in almost every company and business. Everywhere and all the companies are hiring. Secondly, the work on web development can provide great satisfaction and a feeling of accomplishment. The release cycle of web products is usually very frequent.
I'm from like all different industries or have experience with other industries. A lot of web products, they follow the CI/CD method, which means continuous integration and continuous deployment. You will be able to see the impact of your work right away. You could be enabling users to reach truthful news and information from all over the world so that people can think and care beyond their daily lives.
You could be creating more entertainment content for users to enjoy and relax. You could be helping with education by providing students access to high quality videos and curriculums during the pandemic. You could be helping people to find the closest hospital or specialist during emergency. You could be making a platform for people to champion their brilliant and pro ideas.
You could also be building systems and tools fundamentally to help companies of different sizes to grow. So there are endless web applications. You could be contributing something really meaningful to the society while enjoying coding and web design. Finally, as what Jenny just mentioned, web development involves a variety of technology. From user interface design, front-end development, mobile development, backend development, database, data analytics, and more.
A lot of challenges in web development are open-ended. So it provides spaces for creativity and innovation. You will have a lot of choice to learn continuously and also expand your skill set. I would highly recommend a career on web development. Besides everything I just mentioned just now, it is also a tech area that is very easy to enter currently.
There are a lot of online classes, forums, blogs, and training. Once you join a company and start working on real products, you will be able to learn from peers, from internal training. Like what has been mentioned in Bloomberg, right? And also the project you are working on. So it doesn't take a long time for you to grow to become experts in the field of your interest if you are motivated.
Yeah. Chi, can you share a hard problem that you are trying to solve? For the past year at WarnerMedia, one of our focus is on global expansion of HBO Max. We launched a product in Latin America and Europe growing a landscape of HBO Max from US only to more than 60 countries. There are different privacy and legal compliance in different countries.
There are also different like a subscription model and different type of distributors in different countries. So again, I'm leading the partner integration and the focus on registration, authorization and subscription. So our system needs to be aligned with local compliance. At the same time, we need to make it very easy to integrate with local business partners. Another thing is the traffic pattern our product has, especially during popular shows and live sports, require the backend service not only need to be highly scalable and designed for partition tolerance, but also need to be strong at like for the tolerance and keep balance between consistency and availability to handle both external and internal dependency.
There is no like absolute correct answer. That's why all the challenges are kind of open and we are trying our best to use the best like architecture in the industry, trying to achieve to achieve the best to provide the best experience for the user. That's what makes the job interesting, right? You don't have a playbook. You have to problem solve and kind of innovate on a continual basis.
Cool. Abhilash, what are some things that we need to be excited about in this space? Oh, there are so many things I could think of. Like Jenny mentioned earlier, the world of web development is constantly changing. And, you know, that's why you keep seeing a continuous flow of new apps and websites. I think this also gives rise to new languages, frameworks and libraries.
Like what was existing few years back might not exist now or like there are like new things that are coming up to replace that. So I feel as a web developer in today's fast moving landscape, keeping an eye on these changes is really important because when no one can predict the future, it's important to be in tune with where the industry is moving so that it helps you identify the right technologies that you would want to use in your future projects.
So having said that, I think amongst all the things out there, personally, I feel like single page and progressive web application development has been gaining a lot of traction, especially because today's users are all about simplicity, but as well as speed. And at the same time, making sure that the application that you're developing has to be mobile friendly.
So that is something that I'm really excited about. And apart from that, I also recently read an article that during the PyCon 2022 conference, Anaconda announced a new framework for PyScript, which allows you to use Python on the web development, like web, using standard HTML. I think up until now, I had always seen Python being used and backend and, you know, for machine learning applications.
However, now with PyScript, I think it opens a lot of opportunities and avenues, you know, giving the developers best of both worlds. So I'm really excited to see how we can leverage this to make new, interesting and innovative apps, even within our organization. And I think that's what I really like about the space, that it is constantly evolving and there's always something new to learn.
Yeah, it doesn't sound like you're going to get bored anytime soon. Jenny, as somebody who has seen and done web development for several years, what are some things that you have to pay attention to when you're launching something new? Yeah, that is a really good question. Yeah, and one of the things that we heavily concentrate on is testing, testing, testing.
You're never able to cover every interface, but at least you know what works, you know, testing a QA, test on fraud, get testers who aren't familiar with the application. So you'll see how what kind of workflow that they use or what kind of pattern do they follow. It's also, you know, okay to iterate, especially having phases of feature releases.
You don't have to be stuck in the never ending project to fix every little bug. I just have to set the expectations and the priorities and go from there. You know, last thing is, at least a part of testing is, you know, it's not a blame game. Things happen, right? So it doesn't matter where the bug come from, how it exists.
You should work together to fix the issue and then just push forward. On the more technical side, consider scalability and performance. You know, how many visitors are you going to get on the website or your app per hour, per minute, per day? You know, are you set up for DDoSing? Are you making sure that your website can scale quickly, automatically or manually?
How fast is your website? Have you taken into consideration of being able to cache your website? And that could improve both your performance and scalability. Think about, you know, where your bottleneck is on your stack. Maybe your database isn't scalable. And how do you accommodate that? Look at which part of the website slows down, right? Think about, is it a slow core in your database?
Is it being able to fetch multiple requests? Or maybe you're just getting a slow response back from the server. For you to just take each piece and see what you can improve on. And the last question, which everybody has been mentioning because, you know, everyone has this, is, is it mobile friendly? Everyone's got a phone, right? What if you're in the middle of the jungle with 3G network and you really didn't know if this plant that you just touched was poison ivy?
So, you know, this goes back to testing at the end of the day. Yeah, I've heard some, some teams do this thing called blameless postmortems, you know, when there is a customer impacting issue. And I like that phrase because it's less about, you know, finger pointing and less about who caused, who potentially could have caused the outage, but more about what systems went down.
What were the gaps in our processes that led to this happening and how can, you know, how can we avoid this in the future, in the future? And you do want to create spaces for, I'm guessing, having these conversations because that's how you solidify your systems. But also you want to take away the potential of this becoming a blame game, like you said, Jenny.
Well, I would love to hear more and web development is a topic that could benefit from a deeper conversation. But in the interest of time, could you each share some advice for upcoming web developers? And after that, we'll take questions from the, from our attendees. Sure. I think I can go first. I feel like someone had, you know, given me this advice right at the beginning of my career, I would have benefited so much from it.
But now that I have this opportunity, I would suggest all of the upcoming web developers to always network. I think network is networking is really important. You know, you shouldn't be limited to interacting with just your team. You should go out, participate in girls and tech communities within your organization. This will not just help you be on par with, you know, other exciting things that other teams in your organizations are developing, but also help you expand your network.
The more people you meet, I think the more things you learn from them. So even attending conferences like this also helps network and helps you stay on top of the latest industry trends. So that is really important, I guess. Apart from that, I think what really benefited me as well as finding a good mentor early on in my career.
I learned a great deal just from the experiences that was shared by my mentor with me. Often, you know, it used to happen that they would have already seen a problem that I'm trying to solve and discussing it with them helped me not reinvent the wheel. At the same time, I feel analyzing the way their thought process works was also something that I benefited from because it helped me strengthen my own thought process too.
I think apart from this, lastly, I would suggest that, you know, whenever you're developing a web application, make sure that you're interested in it as a user too. This not only makes the development process much easier and fun for you, but at the same time helps you understand the impact that you're making on the community with the application that you're developing, which helps you feel good about what you're doing at the end of the day.
So yeah, that would be my suggestion. I go next. So the advice I want to give is go out of your comfort zone. Try new things. It is important to build the technique breadth and keep up with the latest technology advancement. Take challenge. Don't fail to, don't be afraid to fail. You practice your problem solving skills and critical thinking.
They always will benefit you long term, no matter which particular area, eventually you will choose to stay longer. And always keep the passion and curiosity. Another very important thing is seek out a work environment that encourages you to learn new things. Also has the culture or the work environment. You need to have the culture and people in place to support you, for you to get over the hurdles when you need it.
So, I mean, I actually gave a very detailed example, right, from her own experience. And so that's be a sponge and learn as much as you can from people around you and from the project you are working on. Don't just focus on the task you get. You want to have a bigger view of the whole project, the product and the company, other teams, what they are doing, right?
And then be confident and proactive also in discussion. Share your ideas and knowledge. Don't be shy. Yeah, I completely agree with you. You know, don't be afraid to ask questions and definitely reach out to your fellow engineers. When you're thinking about joining a new company or team, definitely bring out your communication style with the team and make sure that they're more than happy to help you mentor as you start out.
You know, those are some very important things, right, that you can think of as a non-technical aspect of it. And then the last thing for me is really just, you know, read and write documentation. It might not be the most fun thing in the world, but it's definitely very useful. You'll look like you've done your homework, especially before you start asking questions.
In the future, you and your team will definitely thank you, especially when some people may have forgotten what they were. So, you know, definitely keep those things in mind. Thank you. Let's answer some questions from our attendees. Sarah Ferguson asks, Abhilaksh, this question is for you. How long do you spend on reviewing other people's code on a weekly basis?
That's a good question. So I do not have like a fixed time slot. It also depends on the number of pull requests that have been opened, right? But I make it a point to, you know, reserve at the, like, in the entire day, I at least try to reserve the last one hour just to like go through other people's code so that I'm not blocking anyone from, you know, merging the pull request and they have the reviews on time.
So that helps me. Also, like, I feel like at the end of the day, after I'm done with all the meetings, I'm mostly saturated to work on programming or like coding or work on my own pull requests. So that's why I reserve that one hour to be productive, but at the same time help others get unblocked by doing the pull repairs.
I hope that answers your question. Cool. Next question is for you, Jenny. Viralakshmi Prabhu asks, as a lead developer, what are your responsibilities in comparison to a developer on your team? She's trying to understand how to demarcate the roles of a tech lead and a web developer. Yeah, so there is definitely a difference in responsibilities between a tech lead and a developer.
So I'll just kind of say that I'm more of a team leader, software manager, and I lead my team. There are definitely tech leads on my team that do architecture, for example, especially when the product is starting out. They're mentoring other developers as part of that. And then they also could be kind of improving internal developer workflow.
I mean, those three are all open to all developers on the team. But you can distinctly see the difference between someone's taking the lead on a project and someone who is participating in the project. So I would say those are the three big things of differences between a tech lead and, you know, just a regular web developer.
Cool. I'll chime in and add that the tech lead or the architect I've observed looks at the project as a whole, comes up with a tech strategy and sometimes even helps define what the, you know, constituting modules are, which then can be rolled out to other developers on the team. Next question. And I think this may have been answered.
The question's from Preeti Chandira Sekaran. I apologize if I, if I didn't pronounce that right. But the question is, how do you stay up to date on all the different technologies involved in web development? I think Abhilasha answered this question with sharing, participating in tech communities, skills, going to conferences like this one. But I don't know, Chi or Jenny, if you wanted to add anything more to that.
Actually, I mean, our company, I think in all companies, there are some like, we use Slack. So there are some like Slack channel, the peers around you actually will have some discussion. Like the people look at different like blogs, attend different conferences and people will share if they found something interesting. I think that would be because, I mean, website, again, there are so, so many information.
Sometimes it's hard, especially if you just enter this area, right? So I would say start from the community, like you have the access and also you can discuss with people who may have read the same article and have been working on the same project, the product with you, right? And you can like come together to brainstorm, maybe like it applies to some part of the project.
And then you can even take an initiative to try to propose some idea. Yeah. Because the problem is not of having enough information or training material, the problem is that there's too much. And so leaning on your network to be able to curate makes sense. Another advice is that you're spending a lot of your valuable time attending this particular conference, listening to a bunch of sessions, make some notes, see what you have learned.
And then maybe discuss it with a group of friends or colleagues or, or a network. And as a, as a way of discussing, you internalize a little bit more. And I encourage those attending conferences in general to do that. Even, even not teams where you go learn something, come back and share. And then hopefully you create a culture where others do the same with you.
Revathi Raj has a question. How difficult is it for someone who's experienced in a non-tech job move to web development? Would you recommend any particular language that's easy to start with like JavaScript or Python? I can take that question. I have two people on my current team who is an actor and an opera coach. So they decided to switch over to web development and, you know, wanted to go through bootcamp and, you know, another person went through self-taught too.
Two amazing engineers. I think it's totally okay. I mean, I think a lot of people have done it. And, you know, from my discussions with them, you know, they, they said it's, it's a lot of similar similarities, right? There's discipline that's involved in, in, in their previous career and their current career. And it's really just kind of your mind thing in a different pattern logically, you know, especially for coding.
In terms of what kind of languages I would suggest starting with, I would say JavaScript is a really big one. It's a great entry language. You can start even with react if you wanted to, if you're curious about front end components. Even vanilla JavaScript, right? Just throwing something in the console log of, you know, Chrome is literally writing JavaScript because you're coding already.
Python is a great one too. I think there's a minimal entry point that way. If you have a little bit more curiosity towards back end coding, if you want to, maybe you really want to decide, you want to read through an Excel document and you want to kind of build out how to do that. Python. Perfect for that.
So just start with something small, maybe, uh, something you can, you think you can make more efficient and then look up how to do it and just start coding. Yeah. Um, I, I, I, there are, there are a few more questions, but since we have two more minutes, uh, I'll, I'll add to what, uh, Jenny said and also touch upon Shinesha John's question about imposter syndrome.
Uh, it's okay. It's okay to not have a conventional, you know, uh, or what we call a traditional, uh, path to tech, which has been pursue a degree in computer science. And then, you know, uh, uh, take a job in, uh, software development. Instead, it could be, um, I, I think, uh, Jenny mentioned bootcamp. It could also be, uh, you know, learn your, learn your software fundamentals.
I think, um, sometimes folks, um, forget that fundamentals are so much more important than picking a particular platform or a particular framework. Um, because frameworks are going to come and go, uh, and once you have, have a strong base, you can always build on top. Uh, and that also helps you build confidence, perhaps helps combat imposter syndrome a little bit.
Having said that, imposter syndrome is a, it's syndrome is a real thing that we all face across all our disciplines. And so just be mindful if you're feeling it, many others in your place are feeling it too. And just, just, you know, I guess, force yourself to keep marching on forward, knowing that it's natural. It's something that, uh, everybody goes through, but don't let that hold you back.
Um, in the interest of time, I think we have to stop now, but, uh, if you have more questions, I want to continue the conversation. We're all on LinkedIn. Uh, we invite you all to reach out or you can also reach out to us in the Hopin network. Thank you all. Thank you, Chi, Jenny and Abhilasha for joining.
Thanks. See you, folks. Enjoying the comfort.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Article based on this talk
Why web development rewards curiosity more than any single framework
A Bloomberg Media panel moderated by Pooja Malpani explains how web developers get hired, ramp up, launch safely and keep learning.
In short
Web development is broad, fast-moving and unusually open to newcomers, according to a panel moderated by Pooja Malpani, Head of Engineering at Bloomberg Media. Her panelists, engineers from Bloomberg and Warner Bros. Discovery, argue that curiosity, mentorship, testing discipline and strong fundamentals matter more than mastering any one framework.
Key takeaways
Challenges in the field
Scope of web development
How to land a job in web development
A field that spans the whole stack
Malpani opens with her own path: nearly 22 years in web development, including Skype for Business at Microsoft and leading subscriptions and user management at HBO, where her team containerized services, adopted Kubernetes, moved to the public cloud and broke a monolith into microservices so the app could scale for shows like Game of Thrones. She then introduces three panelists: Jenny, who leads a full stack team supporting more than 100 Bloomberg marketing websites; Abhilasha, a full stack developer on Bloomberg's multimedia engineering team; and Chi, who leads partner integration for HBO Max at Warner Bros. Discovery.
Asked what web development means, Jenny describes everything from the infrastructure and back-end APIs to the database and a front end where new technology arrives almost weekly. She also points to the human side: low bandwidth, accessibility, many browsers and devices, and even cultural differences in how people use an application.
"In my opinion, web dev is this moving well of new creations, which can be both complex and simplistic." (7:23)
Learning on the job
Abhilasha's route into the field was unplanned. A backend developer with no JavaScript framework experience, she chose Bloomberg's multimedia engineering team after new hire training because she loved its products, such as the video player used across Bloomberg.com.
"So I'm going to be honest here and say that I did not plan on becoming one. It just happened by accident." (8:39)
She ramped up through an onboarding buddy who became her mentor, internal communities and guilds, regular catch-ups, and above all the code review process, where reading teammates' pull requests taught her new libraries, techniques and design patterns. Joining the QuickTake video project at its start let her take part in every stage, from scoping requirements with stakeholders and designers to the production release. Malpani adds that learning scales when it comes not only from your own projects but from colleagues' code and system design reviews.
Why the work is worth it, and where it gets hard
Chi recommends web development without hesitation. She describes it as a fast-growing field with many well-paid opportunities, where CI/CD release cycles let developers see the impact of their work right away, whether that is delivering news, entertainment, education or help finding a hospital. Because so many problems are open-ended, she says, there is constant room for creativity and learning.
Her own hard problem is the global expansion of HBO Max from the US to more than 60 countries. Her team has to align registration, authorization and subscription systems with local privacy and legal rules while making integration easy for local partners, and design back-end services that survive traffic spikes from popular shows and live sports while balancing consistency and availability.
"There is no like absolute correct answer." (19:32)
Trends and launch discipline
Abhilasha says keeping an eye on new languages, frameworks and libraries helps developers pick the right tools for future projects. She is most excited about single page and progressive web applications, driven by users' demand for simplicity, speed and mobile-friendly design, and by PyScript, which she read had been announced by Anaconda at PyCon 2022 to let developers use Python on the web with standard HTML.
Jenny's launch advice starts with "testing, testing, testing", including bringing in testers who do not know the application so the team can see real workflows. She favours phased feature releases and refuses to treat bugs as a blame game. On the technical side she checks expected traffic, protection against DDoS, auto scaling, caching, database bottlenecks and slow server responses, and whether the site works on a weak 3G connection.
"You don't have to be stuck in the never ending project to fix every little bug." (23:00)
Malpani links this to blameless postmortems, which focus on which systems and processes failed rather than on who caused an outage.
Advice for newcomers and career changers
The panelists' closing advice is consistent. Abhilasha urges developers to network beyond their own team, find a mentor early and build applications they care about as users. Chi encourages leaving your comfort zone, not fearing failure, choosing a work environment that supports learning and looking beyond your own tasks to the whole product. Jenny adds: ask questions, check how a team mentors newcomers before joining, and read and write documentation.
In the audience questions, Abhilasha explains that she reserves the last hour of her day for reviewing others' code so she does not block teammates. Jenny says tech leads take the lead on architecture, mentoring and developer workflow. On switching careers, she points to two engineers on her team who were an actor and an opera coach.
"I have two people on my current team who is an actor and an opera coach." (34:53)
She suggests starting with JavaScript, or Python for those drawn to back-end work. Malpani closes on imposter syndrome, reminding viewers that a nontraditional path into tech is fine and that fundamentals outlast frameworks.
"I think, um, sometimes folks, um, forget that fundamentals are so much more important than picking a particular platform or a particular framework." (37:22)
Watch the talk
Trends in Web Development, moderated by Pooja Malpani, 39 minutes: https://www.womentech.net/video/trends-in-web-development-pooja-malpani
About the speaker
Pooja Malpani is Head of Engineering at Bloomberg Media, where she leads the engineering team responsible for consumer media, marketing and data visualization, including Bloomberg.com, consumer mobile applications and connected devices. Before Bloomberg she led the Purchase and Identity engineering teams for HBO Go and HBO Now, and she earlier spent nine years at Microsoft working on Skype for Business and Skype for consumers.
Questions this talk answers
How do you ramp up quickly in a first web development job?
What should you check before launching something new on the web?
How do you stay up to date with web development technologies?
Can someone from a non-tech job move into web development, and which language should they start with?
How does a tech lead's role differ from a developer's?
Drafted with AI from the talk transcript. Editor review pending.
Frameworks and ideas mentioned
CI/CD
Microservices
Blameless postmortems
Single page applications
Progressive web applications
Resources mentioned
JavaScript
React
Python
PyScript
Cite this talk
Pooja Malpani. "Trends in Web Development." WomenTech Network, 2022. https://www.womentech.net/video/trends-in-web-development-pooja-malpani