37 Tips from a Senior Frontend Developer

The post collects 37 tips from more than 5 years as a software developer. It stresses strong fundamentals in HTML, CSS, and JavaScript, learning by doing, asking for help in the right way, and avoiding blind trust in copied code or online advice. It also argues for shipping done work, breaking tasks down, focusing on value, communication, teamwork, and building depth in one area while continuing to learn.

Reading notes

#

• Master HTML, CSS, and JavaScript before depending on frameworks.
• Understanding how the web works helps you see why there are so many tools in frontend.
• Knowing data structures, algorithms, and their complexities is necessary for more complex programs and to evaluate efficiency.
• Learning by practicing is better than only reading or watching tutorials.
• Asking for help when you get stuck avoids wasting time on problems others have already solved.
• Asking for help the right way includes researching first, understanding the goal, recording failed attempts, and not repeating the same question without noting the answer.
• Do not copy and paste code without understanding it, because that can produce insecure code that is hard to debug and hard to explain.
• Do not apply online advice automatically; you need to see whether the advice fits your context.
• Assume good intentions and trust that the company wants you to succeed, using colleagues as support.
• Prioritizing something finished instead of trying to make it perfect avoids procrastination and excessive complexity.
• Breaking projects into smaller tasks reduces overload, makes PR review easier, and gives a sense of progress.
• Being seen as someone reliable includes knowing how to ask for help when needed and communicate problems.
• Showing enthusiasm at work helps, especially when the person is starting out.
• Staying open to new tools and methods keeps up with frontend’s evolution.
• Mastering development tools, such as the IDE, version control, and browser, speeds up work.
• Writing code that generates value for customers, the company, and stakeholders is the priority.
• Making your own work visible through writing, demos, and other forms of exposure avoids letting it go unnoticed.
• Preferring clear code over “clever” code matters because it is read more times than it is written.
• The manager is presented as an ally who supports growth and goals.
• Helping the manager with tasks such as documentation and support for the work makes it easier to receive support in return.
• Understanding the context of tasks, their value, and their role in the company’s strategy is part of career growth.
• Contributing documentation, demos, and tech talks also improves the team and shows skills.
• Developing depth in a specific area weighs more for promotions than being average in several areas.
• Communication is treated as a requirement for RFCs, demos, and presentations.
• Taking breaks when you get stuck on a problem often brings fresher ideas.
• Working from strengths, instead of insisting on weaknesses, is the suggested strategy.
• Taking ownership of your own career path requires creating a plan for 1, 2, and 5 years.
• Living with other devs helps deal with impostor syndrome and exchange learnings.
• Mentoring younger devs helps you recognize your own knowledge and reinforces your professional position.
• Solving varied problems avoids stagnation and broadens your range of approaches.
• Having mentors helps keep you grounded and avoid mistakes they have already made.
• Choosing a JavaScript framework and mastering it is enough when JavaScript fundamentals are solid.
• Thinking continuously about the user experience involves loading states, feedback, and communication of progress.
• Knowing how to say no helps prioritize requests aligned with your own goals.
• Continuously investing in your own skills is part of a frontend career.
• When there is too much work, reducing features is preferable to sacrificing code quality.
• Understanding and respecting designers, backend devs, and PMs improves collaboration and the work environment.