A lot of the time we are coding it can be sporadic. We know what we want to do and we have the idea in our heads. So we go right on ahead and start to code our function/algorithm etc. However, what usually ends up happening is we have bugs and the code is not structured correclty. What this does it make us not only debug and console.log() many of things but we also waste time restructuring and debugging (and scratching our heads). Well a great way to have what you want your function to do and solve is by first writing pseudo code!
Technical challenges can be hard especially because you never know what you’re going to get. You can end up having to solve a problem over zoom in front of another developer, you can have a take home project that can range from solving a simple problem to creating a whole project, or you can even just have a technical talk where you’re asked a series of questions. Regardless, theirs tons of ways you can stand out especially when it comes to take home projects.
As you create a website theirs a ton of features that you will have available. The common CRUD (create,read,update,destroy) actions will usually be implemented. Not only those actions but a great deal of others like contacts, information, alerts, social media links etc. Theirs a ton of reasons why you could add icons to all of them. Icons could be used for people who have difficulty reading, i.e understanding your websites language if no other options are available, or to add big symbols to make whatever you’re trying to say stand out for things like small screens, and finally just to plain spruce up your code. Icons can make a boring navbar that just says Home and Contact and give it a sleek modern feel with icons of a house and envelope. Below is just a few examples that I’ve encountered before that you can use.
When working with large amounts of data things can get messy quick. Most likely, you want your user to be able to see a list of all blog posts, recipes, images and be able to select one. But what happens when there’s 100+ recipes? A user could endlessly scroll down to find the one they want, but it would be a lot easier for them to just search through them all! A user technically then would be able to “filter” through all of them based on key words, letters, numbers during their search. I had a similar situation in my Vue.js project and I’m going to show you a simple and easy solution with my own personal example. You might already have you data fetched and in its appropriate place and just need a search bar. For this example I’m going to do it from start to finish to make sure it is a fully understood process.
When making our code we want to adhere by the don’t repeat yourself rule (DRY). As I go about a project I realize very quickly when something like a function, a state object, or even CSS is being re-used multiple times in different classes and components. Before getting to work on exactly how to clean up the code, I continue the project as usual and take a note of everything I’m noticing. I then at the end of the day go back and find a way to make those more DRY. One great quick way is to use mixins. According to the official Vue.js website, the definition of Mixins are “Mixins are a flexible way to distribute reusable functionalities for Vue components. A mixin object can contain any component options. When a component uses a mixin, all options in the mixin will be “mixed” into the component’s own options.”.