![]() For me, JavaScript Weekly is the single best resource since it combines articles and news from the whole ecosystem. In my opinion, the best way to find such articles is via email newsletters which will also help you stay up to date. But then, to go deeper, you need to read the documentation and a lot of articles. This may sound like basics, but I've seen so many apps with huge components.Īnd when it comes to learning resources, I think the best way to start with something new is an online course (e.g. Making them super-small will force you to come up with the most logical component structure with a lot of reused parts which will make the application much easier to maintain. Make sure your components are as small as possible - no more than three HTML elements. I would advise front-end developers not to rush into implementation but take your time to analyze the screens you get from designers and think about what is the best way to structure your application and how you would split it into components. What tips can you give for faster and easier frontend development? Especially when I see them typing JS imports manually while doing a live demo on a tech talk. I don't get why most developers prefer VS Code. But when I try to use Visual Studio Code from time to time, I'm always surprised how far behind it is in this area, even with all available plugins. The way this IDE (Integrated Development Environment) can handle JavaScript, TypeScript, Angular, and Vue.js code refactorings and move code pieces around is just astonishing. Having your components used outside of an application also forces you to make them truly reusable and avoid unnecessary dependencies on other parts of the app.Īnd when it comes to coding, the single tool that saves me the most time is WebStorm. It is especially useful when developing a UI library since it also serves as a testing ground and documentation base for components. It allows me to develop reusable UI components in isolation outside of the actual application and then share them with designers to get their feedback. I use Storybook in almost every project where a designer is involved. What’s your tool stack, and what do you like about it most? I only apply different styles to them based on the screen size, otherwise developing and maintaining the application becomes really hard. And I try to use the same components for desktop and mobile as much as possible. ![]() So now, I always ask for both the desktop and mobile design versions before I start on the implementation. It introduces a lot of unnecessary rework, and it's super time-consuming to implement something like that and then make the app switch between desktop and mobile versions seamlessly when resizing the browser window. I often receive the desktop version of a given application, implement it, and later get the mobile version with a completely different UX. What’s the number one problem you face in your work, and how do you solve it? This way, it's also easy to apply design changes later on as you only need to change it in one place in the code and it will get propagated everywhere. I create global SCSS variables for colors, repeating dimensions, etc. Instead, I try to deliver the same result with the least amount of CSS code possible. We usually collaborate using one of the work tools that allow me to quickly inspect various design elements, measure distances between them, and see the corresponding CSS code. I find that communication with your designer is especially important at this stage when working on projects with really tight budgets. I study the requirements, identify the most complex parts of the implementation, and communicate my findings back to the designer so they can modify the design. Typically, I start by analyzing the work handed off to me by a designer. They are often complex products where a deep understanding of a given framework is needed in order to deliver a result that is both easily maintainable and doesn’t suffer from any performance issues. I usually work on web applications built using one of the leading JavaScript frameworks - Angular, React or Vue. Describe your typical workflow for us, Tomas. He specializes in building single-page applications (SPAs) and enjoys transforming beautiful designs into smoothly-working products used by many people. Recently, he has been working remotely as a contractor for various companies worldwide. ![]() Freelance Software Developer Tomas is a full-stack developer with 15 years of experience in coding.
0 Comments
Leave a Reply. |