Skip to content

How to Build and Grow Your Career Through Networking

This article was written over 18 months ago and may contain information that is out of date. Some content may be relevant but please refer to the relevant official documentation or available resources for the latest information.

When we think about advancing in a software career, we often focus on what we need to do from a technical perspective.

We tend to focus on taking classes, learning new technologies, tackling harder projects in hopes of leveling up as a developer.

But are there other things we are not considering when it comes to building a successful career as a software engineer?

Should we also be focusing on networking and building connections?

What does it really mean to network,and does it actually work?

In this article, I will talk about the power of building meaningful relationships in this industry, and how it can help you achieve your career goals.

What is networking?

The word "networking" often has negative connotations assigned to it. Sometimes people only view networking as "using people for personal gain", or "kissing up to people in exchange for a favor".

People also have the belief that you have to be an extrovert to be able to network properly, and introverts will not be successful in it. But that is not the case at all. I have met plenty of people who were successful in building a network, and classify themselves as introverted.

Networking is the process of building meaningful connections. Good networking involves connecting with someone in a genuine way, and building a relationship over time. Once you have developed a relationship, you can work together to advance your careers.

These relationships can introduce you to opportunities you never knew existed. Your network may also be happy to vouch for you at their current companies, and talk you up to other developers in their inner circles.

How networking helped me in my career

Before I became a software developer, my previous career was in music. I had never coded a day in my life before June 2020, and didn't know the first thing about how to break into the industry.

I decided to teach myself how to code and join a few online communities. I quickly found the value of being involved with a community because I was able to learn from other developers, and understand how the industry worked. My community was able to help me stay away from toxic environments, and provide me with helpful resources that I still use today. My network introduced me to technical writing and software opportunities that I didn't know where possible.

I took the time to learn about the industry, and build relationships with great people. We were able to help each other learn about new opportunities, celebrate each other's wins, support each through the tough times, and help each other grow.

Now that we understand what networking is and why it is important, we need to look at ways to build out a network.

Using Twitter to build a network

Twitter can be a great way to build connections and meet new people in the tech industry. Here are some ways to build connections using Twitter.

Twitter Spaces

Twitter spaces are live audio conversations shared by a group of people. There is a person hosting the space, and a group of speakers discussing a preplanned topic. Listeners also have the opportunity to request to speak, and join in on the conversation.

The topics range from career development, mental health, freelancing, technical writing, web 3, machine learning, and more. These spaces can be as little as 10-20 people or 500+ people.

If you find a space that you are interested in, take a listen and make note of who the speakers are. Give them a follow on Twitter, read up on their profile and reach out through direct message.

In your private message, open with introducing yourself and thanking them for the great advice during the recent Twitter space. Then if you have any follow up questions from the space, drop them in the message.

That could be a great way to initiate a conversation, and you would be surprised how many people will respond back. I have connected with dozens of developers, technical writers, content creators and recruiters through Twitter spaces. Private messaging them was my way to make an initial connection, and we were able to build a relationship from there.

Out of those relationships I have been able to build out my online presence which has led to paid technical writing jobs, podcast appearances, and insider information for new career opportunities.

Publicly sharing other people's work

There have been plenty of times where I have shared other people's articles, courses and open source projects through my personal Twitter account. People put a lot of time and effort into creating good content for the community.

When you take the time to show genuine appreciation for someone else's work, they will take notice of that. You can accomplish this by retweeting's someone else's post with your own commentary, or creating your own post and tagging them in it.

I have personally retweeted and promoted other people's content and had positive responses back. This was also a way for me to initiate a conversation with them and connect with them further on other topics.

Using meetups and online tech communities to build connections

Joining a tech community can be a great way to build relationships. The key is finding a community that is a right fit for you.

My suggestion would be to try out a few different online communities, and see what works for you. You will find some communities to be very active and welcoming while others are toxic.

Once you find a few communities that you enjoy, try to reach out to a few of the members. Learn about their stories and connect with them through private chat. Maybe even try to set up a short meeting with them to ask a few questions or discuss a particular topic.

Most people will be receptive to you reaching out as long as you keep your questions specific and you ask for a short meeting (think 15-20 minutes). If your approach is too vague or open ended, people will be hesitant to respond.

There is a diverse array of communities that range from web development, data science, game development and more. You can even find communities geared towards specific cultures, genders, and other demographics.

It is important to remember that not everyone you reach out to will respond back. It is possible that they were busy, and missed your message or are simply not interested in connecting. Try not to take it personally and keep reaching out to other people. There will be plenty of people that do want to connect with you and share their stories.

Conclusion

There are plenty of ways to connect with other people in the tech industry that can be beneficial for your career growth. Try to explore a variety of online and offline venues to meet new people and connect. Social media platforms, meetups, and conferences are just a few places to build connections and grow relationships over time.

I am someone who transitioned from being a classical musician to working as a software developer in large part because of my network. They were very supportive of my software journey and I was supportive of theirs. We continue to help each other out, and support each other throughout our careers.

It doesn't matter if you are just starting out or 20 years in the industry, we all need a network of people around us to help us grow and thrive.

This Dot is a consultancy dedicated to guiding companies through their modernization and digital transformation journeys. Specializing in replatforming, modernizing, and launching new initiatives, we stand out by taking true ownership of your engineering projects.

We love helping teams with projects that have missed their deadlines or helping keep your strategic digital initiatives on course. Check out our case studies and our clients that trust us with their engineering.

You might also like

What is Pair Programming and How Can It Help You Grow as a Developer cover image

What is Pair Programming and How Can It Help You Grow as a Developer

Pair programming is when two developers work together on the same section of code to solve problems and build better software. But why is this technique so popular and how can it help you grow as a developer? In this article, I will break down how pair programming works, and explain why it is beneficial to your growth as a software engineer. Who invented pair programming? Pair programming was invented by software engineer Kent Beck as one of the core principles in Extreme Programming. Extreme Programming (XP) is a set of practices and values to help create high quality software and increase productivity and collaboration on development teams. Since software development is a collaborative effort, having two developers working through a problem will be more effective than one person trying to solve it on their own. How does pair programming work on a project? In pair programming, you will have one person who is coding, and another person who is observing. The person who is coding is known as the driver, and their responsibility is to execute those lines of code. The person observing is known as the observer or navigator and their role is to come up with strategies for improvement and catch errors in the code. It is common for the pair to switch between the two roles during a session. 4 Reasons to Practice Pair Programming There are many benefits to engaging in pair programming. I am going to list four reasons why you should participate in a pairing session. Better code quality You can easily spend hours debugging a problem and trying to find a solution on your own. But sometimes, you need a fresh set of eyes that can help you identify a solution much faster. Another advantage of pair programming is hearing another developers' perspective on possible optimizations to your code. A good way to look at this would be a live coding review from a peer to help you improve on code quality. Learning from Other Developers One of the things I enjoy about pair programming is the ability to learn from other developers. In my pair programming sessions, I have learned about new techniques, new tools for optimizing my development environment, and keyboard shortcuts to make my life a little bit easier. This is also an opportunity to learn more from my coworkers, hear their perspectives on software, and see how they tackle issues. Better Team Collaboration Great software is never built by just one person. It is a collaborative effort made by many individual contributors working together as a team. Pair programming is a great way to build up a healthy team collaboration and create high quality results. It is also a great way to learn more about your teammates' coding styles and approaches so you can effectively work with them. Building up technical communication skills All developers need to learn how to effectively communicate their ideas and technical approach to their team. Pairing with another developer can help you practice your communication skills. You will learn pretty quickly if other developers can understand you, or if you need to work on different ways to communicate your thoughts properly. When Should You Engage in Pair Programming? Not all situations will call for a pair programming session. If you are working on a small bug fix that you can tackle pretty quickly, there probably isn't going to be a need to bring in another developer. But if you are brand new to a codebase, that can be a great opportunity to pair with someone more comfortable with the project. I have paired with developers new to a project and helped them get better acquainted to the codebase and answer their questions concerning the project. I have found that pair programming has helped them onboard faster to a project then if they just tried to figure out everything on their own. It really depends on the situation on whether or not it is appropriate to pair with someone. From my experience, if I am working on new features or learning a new technology, I will try to pair with another developer and learn from them. Things to avoid when pair programming There are some key things you want to avoid doing when pairing with another developer. Avoid passive aggressive comments Comments like, "I wouldn't have picked that complicated solution" or "what a unique variable name" will usually lead to an unproductive pairing session. It is better to be constructive and say things like "this solution can be better optimized for x,y,z reasons" or "this variable name is more descriptive and will help developers understand your code better". By providing constructive feedback with actionable items, the developer that is coding can understand the reasons for the change and not feel personally attacked. Overzealously Correcting the Developer Who is Coding If you are in the observer role, let the other person code for a little bit, and give them a chance to fix their own errors. If you interject every two seconds, then you are robbing them of that opportunity to learn and fix their own mistakes. There is always a delicate balance between when to inject and when not to. The more you are involved with pairing sessions, the better you will know when to provide feedback. Having One Person Dominate the Pairing Session In effective pairing sessions, two developers collaborate and share ideas to create stronger software solutions. This process does not work if one person is sharing all of their ideas, and the other is just silently coding away. The pair should be able to both share their ideas, ask questions, and arrive at a solution together. Is Pair Programming Only Used on the Job? I don't believe that you should wait to start pair programming until you get your first software job. If you plugged into a good tech community and have built relationships with people, you can reach out for pairing sessions. I am involved with the Virtual Coffee community, and they have a help and pairing channel in Slack where people can ask questions and pair with each other. I have also paired with other developers on issues or new features for open source projects with which I was involved. How to Overcome the Fear of Pairing with Someone I know a few developers who are afraid to pair with someone else because they don't feel like adequate developers, and fear judgement from their peers. If you are in a healthy team environment, these pairing sessions can help you realize that your teammates do value your contributions to the project. This could be a great way to grow and build your confidence as a developer. My advice would be to reach out and take that first step to pair with your teammates even if it is a little scary. It could help you work through issues of imposter syndrome and build deeper relationships with your coworkers. Tools for effective pair programming There are many great tools out there that enable two developers to work on the same codebase remotely. Here is a list of some tools to consider for your next pairing session. - Atom's motepair package - Visual Studio Code's Live Share extension - Remote Collab for Sublime Text - CodeSandbox live Conclusion No matter where you are at in your career, everyone can benefit from pair programming. I encourage you to reach out to your coworkers, or developers in your community, and start pairing with them....

How to Avoid Common Pitfalls and Ace Your Take Home Assignment cover image

How to Avoid Common Pitfalls and Ace Your Take Home Assignment

During the interview process, you might be asked to complete a short take home assignment. This usually consists of building out a small project with required tasks to be completed in a set time frame. This is a popular way to test an applicant's skills and assess how they can tackle problems. But what is the best way to approach a take home assignment and what are some common pitfalls people run into? In this article, I will provide tips on how to ace your take home assignment and move to the next round of interviews. I will also provide tips on how to avoid common mistakes with the take home projects. What does the take home project entail? The take home project offers a chance for the prospective employer to see how you approach building out real world applications. For the frontend, you might be asked to work with an API and display some results in a table or card layout. You might also be asked duplicate a web page from a Figma design and add some functionality like search or pagination. For the backend, you will be tested on your knowledge of server side logic, and be asked to design some APIs. There will be a list of criteria that you have to meet by a set deadline. There will also be notes on hosting your app and which libraries and frameworks you are allowed to use, if any. If you want to see examples of take home projects, then please take a look at the following links: - freeCodeCamp take home projects - Github search results for take home projects Make sure you understand the project requirements Before you start building out the project, it is important that you understand all of the project requirements. If you need any clarifications, please ask and do not make assumptions. You don't want to fail a project because you misunderstand the directions. This is also a good chance to see how well the company communicates project details to you. If they are able to offer up clear directions and answer any clarifying questions, that is a good indicator of what it will be like to work for them. If they are not able to provide clear directions and have poor communication skills, then that can also be a sign of what it would be like to work there. Plan out your time efficiently Time management is crucial when it comes to take home projects. Since you only have a short amount of time to build the project, it is important that you first plan out how to build the basic structure. You will need to identify which parts of the project will require the most attention and how long it will realistically take do each component of the project. It is important to account for the time it will take to fix bugs and other unexpected issues during the development phase. Once you have mapped out how long it will take to build a basic prototype, you will need to look into adding extra features to help you stand out in the applicant pool. You will need to decide on which features to add and how long it will take to successfully build it out. Try not to fall into the trap of underestimating how long a feature will take to build. If it doesn't look feasible in your alloted time frame then it is best to rethink it or leave it out completely. Make sure to adhere to best practices and focus on clean code The goal of these projects, is to get a sense of your coding style and technical skill level. This is your chance to ensure that your work adheres to best practices and is clean and readable by other developers. You want to make sure that you are doing things like using clear concise variable and function names, adhering to the KISS and DRY principles, and optimizing your code so it runs efficiency. Your potential employer is not looking for perfect code and understands that you are working under a time constraint. But they do want to get a sense of your code quality and the type of work you might contribute to a project. Do the best you can to write clean readable code while still making sure the basic functionality is in tact. Avoid over engineering your project Take home projects can offer a great opportunity to develop your skills and demonstrate what you can do. But it is important that you do not over engineer your application because it sends the wrong message to potential employers. There is no reason to over complicate your code and stuff you application with tons of extra unnecessary libraries and frameworks. Remember that employers will ask you about your code and technology decisions and if there doesn't seem to be a clear reason behind your decisions, then it can be seen as a negative. Make sure to document your work Documentation is an important part of any software project and you need to be able to demonstrate that in your take home assignment. Make sure to have a detailed readme including your architectural and design decisions, features of the application, testing, how to run the app locally, and a list of the technologies used. You can also include a section on features you would have liked to build if you had more time. By providing a documented project, employers will learn about your thought process and get a sense of how you approach problem solving. Should you include testing in your take home project? I think you should definitely include some testing in your take home assignment. During your planning stage, you will need to set aside some time for coming up with test cases and deciding on which testing tool you will use. If you are new to testing, try to include some small tests to communicate to your potential employer that you understand testing is part of the job. If you are a more experienced developer, your employers will expect you to include testing. How should you approach styling? Even if you are not a natural born designer, it is still important to create a clean professional looking design. It is fine if your design is simple because they are not testing you on your original design abilities. Just make sure that your project is responsive and has good UI/UX. If you are allowed to use CSS frameworks like Tailwind CSS or Bootstrap, then it will make designing your app a little bit easier. How long should a take home project take? Most companies will give you a timeline to complete the project and submit it. In my opinion, 3-5 days is a good range to complete the assignment. If the employer is expecting you to take a couple of weeks or more to do the assignment, then that is a sign they are not respecting your time. There have been a lot of stories of people spending 40-60+ hours on a take assignment and still not getting the job. If you receive an assignment where it is obvious it will take an excess amount of time to complete, then you might consider reassessing the situation and possibly not moving forward with the interview. Conclusion Take home projects can be a great alternative to the typical Leetcode style interviews. This is a chance for you to show off your technical skills amd build an app in the process. It is important that you meet all of the requirements and add some extra functionality to stand out in the applicant pool. Also make sure to document your solution and test out your project before submitting it. I hope you enjoyed this article and best of luck on your future interviews...

How to Handle Uploaded Images and Avoid Image Distortion cover image

How to Handle Uploaded Images and Avoid Image Distortion

When you are working with images in your application, you might run into issues where the image's aspect ratio is different from the container's specified width and height. This could lead to images looking stretched and distorted. In this article, we will take a look at how to solve this problem by using the object-fit CSS property. A Look Into the Issue Using the "Let's Chat With" App Let's Chat With is an open source application that facilitates networking between attendees for virtual and in-person conferences. When users sign up for the app, they can join a conference and create a new profile with their name, image, and bio. When the team at This Dot Labs was testing the application, they noticed that some of the profile images were coming out distorted. The original uploaded source image did not have an aspect ratio of 1:1. A 1:1 aspect ratio refers to an image's width and height being the same. Since the image was not a square, it was not fitting well within the dimensions below. ` In order to fix this problem, the team decided to use the object-fit CSS property. What is the object-fit CSS property? The object-fit property is used to determine how an image or video should resize in order to fit inside its container. There are 5 main values you can use with the object-fit property. - object-fit: contain; - resizes the content to fit inside the container without cropping it - object-fit: cover; - ensures the all of the content covers the container and will crop if necessary - object-fit: fill; - fills the container with the content by stretching it and ignoring the aspect ratio. This could lead to image distortion. - object-fit: none; - does not resize the content which could lead to the content spilling out of the container - object-fit: scale-down; - scales larger content down to fit inside the container When the object-fit: cover; property was applied to the profile image in Let's Chat With, the image was no longer distorted. ` When Should You Consider Using the object-fit Property? There will be times where you will not be able to upload different sized images to fit different containers. You might be in a situation like Let's Chat With, where the user is uploading images to your application. In that case, you will need to apply a solution to ensure that the content appropriately resizes within the container without becoming distorted. Conclusion In this article, we learned about how to fix distorted uploaded images using the object-fit property. We examined the bug inside the Let's Chat With application and how that bug was solved using object-fit: cover;. We also talked about when you should consider using the object-fit property. If you want to check out the Let's Chat with app, you can signup here. If you are interested in contributing to the app, you can check out the GitHub repository....

“Music and code have a lot in common,” freeCodeCamp’s Jessica Wilkins on what the tech community is doing right to onboard new software engineers cover image

“Music and code have a lot in common,” freeCodeCamp’s Jessica Wilkins on what the tech community is doing right to onboard new software engineers

Before she was a software developer at freeCodeCamp, Jessica Wilkins was a classically trained clarinetist performing across the country. Her days were filled with rehearsals, concerts, and teaching, and she hadn’t considered a tech career until the world changed in 2020. > “When the pandemic hit, most of my gigs were canceled,” she says. “I suddenly had time on my hands and an idea for a site I wanted to build.” That site, a tribute to Black musicians in classical and jazz music, turned into much more than a personal project. It opened the door to a whole new career where her creative instincts and curiosity could thrive just as much as they had in music. Now at freeCodeCamp, Jessica maintains and develops the very JavaScript curriculum that has helped her and millions of developers around the world. We spoke with Jessica about her advice for JavaScript learners, why musicians make great developers, and how inclusive communities are helping more women thrive in tech. Jessica’s Top 3 JavaScript Skill Picks for 2025 If you ask Jessica what it takes to succeed as a JavaScript developer in 2025, she won’t point you straight to the newest library or trend. Instead, she lists three skills that sound simple, but take real time to build: > “Learning how to ask questions and research when you get stuck. Learning how to read error messages. And having a strong foundation in the fundamentals” She says those skills don’t come from shortcuts or shiny tools. They come from building. > “Start with small projects and keep building,” she says. “Books like You Don’t Know JS help you understand the theory, but experience comes from writing and shipping code. You learn a lot by doing.” And don’t forget the people around you. > “Meetups and conferences are amazing,” she adds. “You’ll pick up things faster, get feedback, and make friends who are learning alongside you.” Why So Many Musicians End Up in Tech A musical past like Jessica’s isn’t unheard of in the JavaScript industry. In fact, she’s noticed a surprising number of musicians making the leap into software. > “I think it’s because music and code have a lot in common,” she says. “They both require creativity, pattern recognition, problem-solving… and you can really get into flow when you’re deep in either one.” That crossover between artistry and logic feels like home to people who’ve lived in both worlds. What the Tech Community Is Getting Right Jessica has seen both the challenges and the wins when it comes to supporting women in tech. > “There’s still a lot of toxicity in some corners,” she says. “But the communities that are doing it right—like Women Who Code, Women in Tech, and Virtual Coffee—create safe, supportive spaces to grow and share experiences.” She believes those spaces aren’t just helpful, but they’re essential. > “Having a network makes a huge difference, especially early in your career.” What’s Next for Jessica Wilkins? With a catalog of published articles, open-source projects under her belt, and a growing audience of devs following her journey, Jessica is just getting started. She’s still writing. Still mentoring. Still building. And still proving that creativity doesn’t stop at the orchestra pit—it just finds a new stage. Follow Jessica Wilkins on X and Linkedin to keep up with her work in tech, her musical roots, and whatever she’s building next. Sticker illustration by Jacob Ashley....

Let's innovate together!

We're ready to be your trusted technical partners in your digital innovation journey.

Whether it's modernization or custom software solutions, our team of experts can guide you through best practices and how to build scalable, performant software that lasts.

Prefer email? hi@thisdot.co