![]() ![]() It's usually used to avoid committing any intermediary object files and files from the build folder that aren’t useful for other project collaborators.Īt this time, I’m still at the initial stage of the development and haven’t configured a git repository yet. gitignore indicates git which files shouldn’t be added to the commits. Medium browser tab, including a title and an icon defined by the manifest.json. This command automatically set up a development environment, with the following file structure: I created a new React project named Jammit using the following command: npx create-react-app jammit Just recently, I created a React app using the create-react-app command that will serve as an example to illustrate how I approach a project configuration now. Using create-react-app to set up a project Angular projects have a similar tool, known as Angular CLI. After using it to create a simple project, it is quite easy to make upgrades to the app’s underlying infrastructure. It allows the developer to refrain from the configuration and build tools any code project requires, at least to a certain extent. What is create-react-app?Ĭreate-react-app is a method to automatically set up a production-ready React application. ![]() ![]() Two years after, I would like to share some knowledge about this subject with you. That day, I learned a valuable lesson: I had to deeply understand my project's configuration. However, they expect candidates to understand their own work and not do things arbitrarily. They don’t oppose using unofficial setup commands, as is the case of create-react-app,and they are fortunately not looking for people who deeply understand how to configure complex tools like webpack or Babel. I knew how to answer everything about my coding decisions, but unfortunately, I already had made a first bad impression.Ĭompanies are looking for developers that know what they are doing. Just as the serviceWorker, those files were automatically created when I run create-react-app to automatically set up my project and I started to code without paying any attention. “So, what are you testing in this file then?” “Oh at least this one I know!”, I thought. “What is this file for?”, the interviewer asked. I had no idea what he was talking about.Īfter making a fool of myself for starting a technical interview clueless, the following questions were no better. I met all the requirements, I created a usable UI, I polished my code, therefore I was very proud of my solution.Ī senior developer sat with me, with my project open on his laptop, and asked the first question: Why are you using a serviceWorker? The briefing was not complicated and I could use any coding language I wanted.Īfter my delivery, the company scheduled an interview to discuss my solution. Author: Sarah Pflug Copyright: Burst Some Rights ReservedĪ couple of years ago, I was in a recruitment process for a frontend developer position, which included coding a simple project. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |