To succeed as a developer, I believe that the quality of your code and your personality are both important. This means not just meeting feature requirements, but also paying attention to the structure of the code. This kind of developer pays close attention to implementing best practices. Moreover, developers also need to give and receive objective feedback. This feedback isn't personal, but instead aimed at improving the team processes. Through trusting each other, we're able to grow as a team. My biggest area of growth as Front-end Lead at Arc has been in making technical decisions: identifying issues, discussing potential solutions, and analyzing the pros and cons of each option. Our team culture of deep discussion means we learn a lot from each other, and develop a thorough understanding of issues in both breadth and depth. The whole team is enabled to make both big and small decisions that impact different areas of the product. Because we use well-established processes to determine trade-offs, we’re able to make these decisions with confidence.
As a Front-end Developer with a business background, I love how developers are pulled in early during the product development phase. We work in close-knit product teams with the PMs and designers to understand what our users’ pain points are and how we can solve them at Arc/Codementor. Looking through user research and product related analytics, we develop a hypothesis to work with. Joining in the product discovery process creates a more engaging development process. One of my most memorable challenges was being able to see through the launch of a brand new product, DevProjects — from brainstorming a mere concept, iterating through rounds of product related discussions, to developing the MVP. It's also always exciting when our designer revealed her brand new product designs!
As a Senior Front-end Developer at Codementor, I truly believe that respect is the core value of our team. Respecting others and trusting in their knowledge enables us to focus on problems that need to be solved, and the mission in front of us. We also spend a lot of time optimizing our work processes. Although this might increase the time spent on the planning phase, we're able to work more efficiently and concentrate on what really matters. After more than three years with Codementor, I've learned the best way to get promoted is to take on more responsibilities. Don't be afraid of taking on new challenges! And don't worry if you encounter something you don't understand, because your teammates will have your back. As a team, we work together to make decisions, and figure out the best way to help you reach your goals. Learning from each other means we constantly grow stronger as a team.
I'm proud to say that we have a strong development team. We're always examining our product, and seeking to continuously improve it. For example when choosing a technology, the Back-end team considers the requirements and restrictions (e.g., time, cost, product progression, etc.) as a whole. We try our best to digitize these factors to help us evaluate possible outcomes. At the same time, code quality and system structure are also taken into account, in order to reach the best solution. This process means we can deliver satisfying results to our product team — and our users! The Back-end team at Codementor's biggest challenge is the payment connections in our platform. Developer payout methods include Stripe, PayPal, Payoneer, and Transferwise. When we're integrating different third-party payment services, data consistency is essential. Faced with this project, we brainstormed as a team, discussed ideas, and ultimately came up with a solution that fixed this issue.
What really stood out when I joined the team is that everyone likes the product, enjoys their work, and loves to share knowledge. Also, compared to previous teams I've worked with, the Arc engineering team is very open to discussion. We make sure each team member understands what we're working on, and why decisions are made. I also receive a ton of feedback on my code, along with heaps of tips from teammates that help me improve. The best thing about joining Arc, though, is the flexibility. Working remotely means I save time on commuting, and instead can spend it on more meaningful things. Plus our team really cares about each other. We intentionally check in with each other's happiness levels, and always lend a hand if someone needs to adjust their work hours or tasks. Recognizing the human element a team, and genuinely implementing it in the workplace is the key to empowering a great team.