DEV Community: DevPool

How to Pass Take Home Coding Challenge

DevPool — Tue, 26 Jul 2022 07:14:11 +0000

The following tips are based on personal experience. Something that I apply all the time and move forward to the next round of an interview every time. I hope this will help you as it helps me!

When it comes to a take-home coding challenge, the first thing that most developers think of is, "Sweet! I can just google for the answer". However, this is where they all fail.

So, how do you pass to take home coding challenge?

1. Take your time understanding the problem, there is no fire.

When I receive a technical challenge, I would read it multiple times and take notes on what has been asked to develop. My notes would consist of what I have to do step by step, so I won't waste time on something that the requirement didn't even ask. For example, this is what my notes would look like:

[✔️] Create a simple table to display information
[✔️] Send a request to API with specific params
[] Do the required task with params
[] Send response back
[] Populate the table with content received from API

After creating the steps, I now have a perfect picture of what the system should do, and I can start building it out! Also, notice how I'm not talking about what tools (language) I'm going to use. You could build the system using any language you want, and the list won't change.

The above list would consist of what the technical spec is asking of me. Nothing more, nothing less, and I will fill confident in the application as I understand the problem.

So if you're wondering what you should do first, take the time to understand the problem and write out the steps you need to take before touching the keyboard.

2. Code it out.

After taking the time to create the above steps, coding out the problem becomes much more manageable and straightforward!

You can now use any language that you're required to use. In this step, I won't be able to recommend what framework or packages you could use since we all specialize or currently using different server-side languages. However, I could tell you my thinking proses.

When it comes to coding, I follow 3 simple steps:

1. Make it to work,
2. Refactor the code, and
3. Fix performance of the code.

These three steps are something that every Software Engineer follows, regardless of what you're working on, and have critical attention to detail.

3. Improve your code.

After you're done, and you think it's working, take a day off and stop thinking about the code.

Every time I step away from code, I always find a piece that I could either improve or find a bag that I didn't catch before. To that point, you want to find as many bugs as possible before submitting it.

Also, I would run a linter on my code to be sure that the entire project looks the same with spacing, line indentation, fix naming convention, file orientation, and etc...

Last but not least, don't forget to include a small readme file that explains what your code does and how someone can run it locally without guessing and looking at your code.

These are the three steps I use when it comes to taking home coding challenges, that I hope will help you too.

If you need more helpful tips and advice, subscribe to my channel DevPool and don't miss future topics.

YouTube - DevPool

Top 10 IT Jobs Without Coding Experience | 6 Figure Non-Coding Tech Jobs

DevPool — Mon, 14 Feb 2022 14:50:40 +0000

What if I told you that there are millions of tech jobs up for grabs that do not require any coding experience?

Tech is estimated to be a $5.3 trillion industry in 2022. With the upcoming age of Software incorporated AI driven cars, blockchain technology, Internet of Things, Metaverse, wearable gadgets, and a lot more, the tech industry is poised to grow rapidly with every passing year.

Tech industry which is already known for the high payouts is expected to get even more lucrative for the employees. Usually when someone talks about tech, people assume a highly technical engineering role that requires sophisticated programming knowledge and some genius level skill set.

However, the fact is that there are millions of jobs in the technology industry that require no-coding experience. In fact, the demand for such roles is increasing with every passing day. Even if we look at the tech industry historically, many people who played a key role in the industry did not do any coding. One of the biggest examples of this is Steve Jobs, the founder of Apple, which as we all know is now the world’s biggest company.

Coders or programmers are a critical element of the tech industry. However, they are not the only element. There are hundreds of other types of jobs related to marketing, sales, design, administration, quality assurance, and many other roles where people are making six figures and in some cases even seven figures. The best part is that you can learn many of the skills required for these non-coding tech jobs within a few months, and get reasonably good at them in a couple of years.

10 – User Experience Designer

Design is everywhere and it plays a critical role in the success of any software or hardware. That is why there is a great demand for designers in the tech industry. During the past few years we have seen an incredible rise in the demand for User Experience or UX designers.

User experience designers apply the principles of computer science, marketing, psychology, and technology to the ways in which different applications, programs, and software function. They create products with the end-user in mind. Their main goal is to increase the user satisfaction by making the different apps, software, and programs more appealing, more intuitive, and easier to use.

Some of the key elements of their workflow involves conducting user research, using information architecture, using data analytics to strengthen the designs, and prototyping. While the salaries of UX designers greatly depend on their talent, skill level, and experience, a reasonably talented and experienced UX designer can expect to earn upwards of $100,000 a year.

Other than providing you with a lucrative salary, a career as a UX designer can also be quite fulfilling if you have a creative personality. Having good aesthetic sense can give you a great advantage as a UX designer.

9 – System Administrator

System Administrators are the backbone of a company’s IT department. They are also known as Sysadmins. They are responsible from unboxing equipment to setting it up, bringing it to a working condition and then maintaining it. They are responsible for things like taking care of the server, backing up files, creating firewalls to protect the company network, and just about anything that has to do with keeping the company online.

While it definitely sounds like quite a daunting job, the amount of work fluctuates a lot. While the system administrators are extremely busy during the new installations and overhauling of company system, they are not as busy during the regular maintenance.

To become a successful system administrator you don’t necessarily need programming skills. However, you do need to have a wide range of other skills including networking skills, computer science knowledge, and people skills.

8 – Technical Writer

Technical Writer is a great job role for anyone who is good at writing and is tech-savvy. Every piece of software and hardware that is created comes with a certain set of writing. It can be writing within the app, program or software. It can be user manuals, technical reports, press releases, or other types of documents. To become a good technical writer, not only you need to have a good grasp of the language, you also need to thoroughly understand the product and the industry you are writing about. With the increase in the number of software, apps, other digital products, and hardware, the demand for technical writers is increasing with every passing day.

7 – Software Quality Tester

Software quality testers are responsible for making sure that the software products are free from errors, are of high quality, and that they meet their intended purposes. Software quality testers execute a variety of functional, scalability, and stress tests across different customer scenarios to try and find faults in the software.

Their ultimate goal is to identify the faults and enhance the overall quality of the product. The best part is that this job does not require any coding or programming. With the role of software increasing in every sphere of life and with millions of software being made every year, there is a huge demand for the software quality testers. It is yet another profession that promises a six figure salary without any coding or programming experience.

6 – SAP Consultant

SAP is an acronym for systems applications and products. SAP consultants work with businesses to create customized solutions for their specific needs and goals. SAP consultants carefully research the company, its processes, its goals, immediate and future needs, and then they identify the systems, processes, software, and other things that can be improved. SAP consultants specialize in functional or technical areas within the field of data processing. The technical side of SAP requires knowledge of computer science, software development and programming. On the other hand, the functional side of SAP requires knowledge of business and finance.

5 – Technical Recruiter

Recruiters have always been in high demand. The importance of recruiters increases several folds in organizations that need to hire for technical roles. Technical recruiters may not know coding, but they are often the ones selecting candidates for coding as well as non-coding roles in tech companies.

Technical recruiters need to have a fundamental understanding of the technical landscape and they need to be aware of the specific needs with regards to programming languages, software, and prior experience when hiring for a specific role.

The more tech-savvy you are, the more quickly you can expect to master as a technical recruiter. With the situation of “the great resignation” after the COVID crises, the companies in the US and elsewhere are finding it extremely difficult to find the right candidates, and so they are willing to pay heavily to the recruiters who can deliver them results.

With the coming age of AI, Blockchain, and Metaverse, not only the role of technical recruiters will get even more technical, it will become even more high paying as well. So if recruiting is something you are interested in, better get started today.

4 – Digital Marketing Specialist

Digital marketing has emerged as one of the most important and one of the most lucrative tech jobs during the past 10 years. The need for effective digital marketing is being realized by companies of all sizes and all industries. A digital marketing specialist uses various platforms and tools including social media sites, search engine optimization, email marketing, influencer marketing, and paid advertisements to gain new leads and customers. Digital marketers are not only in high demand in full time roles, they are also in very high demand in freelance roles.

3 – Data Analyst

With an ever increasing amount of data, there is a huge demand for data analysts. It is a great role for anyone who loves to play with data. Data analysts basically use different programs and techniques to inspect data in order to discover useful information, draw conclusions and help make smarter decisions.

Data analysts typically take large sums of data and then break it down into usable lists, charts, graphs, and reports. They not only help companies identify the problems, they also help companies find new opportunities and new paths for growth.

Data analysts rely on tools such as Excel, Power BI, Tableau, Python, and Apache Spark during their work to make data more useful. Over the past few years, there has been a consistent increase in the number of data analyst jobs as well as the salaries. This trend is likely to continue.

2 – Sales Specialist

You may have heard from the older folks that sales is the best career ever. And you may even know a few people who made millions off of sales in the 80s or 90s, or even early 2000s. Believe it or not, with the rise of tech, sales have become even more lucrative.
You may be surprised to know that some of the sales folks in tech industry make several times more than the top programmers. Sales people are generally rewarded with commissions and bonuses based on their job performance.

There are a number of different sales categories in tech. You can get into SaaS or Software as a Service sales. You can get into hardware sales, or you can get into different niches of tech related sales, such as mobile, gaming, storage, etc. If you manage to become a successful sales person in tech, you can expect to make millions during your career. However, like any sales job, tech sales require a lot of hard work. It requires extensive research, prospecting, long meetings, and a lot of patience.

1 – Project Manager

If you are looking for a lead role in tech and that too without any coding experience, then becoming a project manager is the right path for you. The way that many of the tech companies operate, gives project managers a unique position of being heavily involved throughout the lifecycle of a product.

Tech companies try to achieve their goals through projects. Typically a project involves creating software, its attachment to hardware, implementation, controlling, updating, and repairing. A project manager leads the entire process, coordinates with different teams, and ensures that the project meets the deadlines as well as the regulatory and the required qualitative standards. Product managers are highly paid individuals and their salaries usually depend on the types of projects they take care of.

For more helpful tips and advice, subscribe to my channel DevPool and don't miss future topics.

YouTube - DevPool

Good To Know JavaScript Array Methods For Any Project

DevPool — Thu, 11 Nov 2021 13:41:13 +0000

In the past, to accomplish a simple task in JavaScript, we would have to use underscorejs or lodash library (just a pain). However, now it's all baked into the language, so you can accomplish a lot with just a one-liner.

The list below helps to start learning new things, but you will need to refer to the documentation since the information below doesn't cover all the functionality for some methods.

.map()

Loops through an array, and performs your logic

const flags = [1, 2, 1, 1, 2].map(
    digit => digit === 2
);

console.log(flags)

// output: [false, true, false, false, true]

.includes()

Checks if a specific value exists in the array

const isFruit = ['apple', 'orange', 'kiwi'].includes("orange")

console.log(isFruit)

// output: true

.filter()

Will update the variable with values that passed the filtering logic

const fruits = ['apple', 'orange', 'kiwi'].filter(
    fruit => fruit.includes('a')
);

console.log(fruits)

// output: ['apple', 'orange']

.some()

Returns a boolean if any of the elements were true

const isEven = [1, 2, 3, 4, 5, 6].some(
    (element) => element % 2 === 0
);

console.log(isEven)

// output: true

.sort()

Will arrange values within the array
Note: Recommending to go over docs on how this method is working

const fruits = ['dragonfruit', 'apple', 'banana', 'cantaloupe'].sort()

console.log(fruits)

// output: ['apple', 'banana', 'cantaloupe', 'dragonfruit']

.forEach()

Loops through the array and performs your logic on each element

const fruits = ['dragonfruit', 'apple', 'banana', 'cantaloupe'].forEach(
    fruit => console.log(fruit)
);

// output:
// > dragonfruit
// > apple
// > banana
// > cantaloupe

.concat()

Combines array elements together into one

const busket1 = ['dragonfruit', 'apple']
const busket2 = ['banana', 'cantaloupe']

const allFruits = busket1.concat(busket2)

console.log(allFruits)

// output: ["dragonfruit", "apple", "banana", "cantaloupe"]

.every()

Checks each of the elements within array, and it returns a boolean based on the implemented logic.

const isLegalAge = [23, 33, 18, 100, 19].every(age => age >= 18)

console.log(isLegalAge)

// output: true

.join()

Connects elements with a specified value and returns a string
****Note: Recommending to go over docs on how this method is working

const fruits = ['dragonfruit', 'apple', 'banana', 'cantaloupe'].join('-')

console.log(fruits)

// output: "dragonfruit-apple-banana-cantaloupe"

.find()

Returns a matching logic value
Note: Recommending to go over docs on how this method is working

const fruit = ['dragonfruit', 'apple', 'banana', 'cantaloupe'].find(
    element => element === 'apple'
);

console.log(fruit)

// output: 'apple'

.findIndex()

Returns an index number of the first matching element value
Note: Recommending to go over docs on how this method is working

// array element        0            1         2        3
const fruitIntex = ['dragonfruit', 'apple', 'banana', 'kiwi'].findIndex(
    (element) => element === 'banana'
);

console.log(fruitIntex)

// output: 2

.indexOf()

Returns an index of the first matching element value
Note: Recommending to go over docs on how this method is working

// array element          0           1        2           3
const fruitIntex = ['dragonfruit', 'apple', 'banana', 'cantaloupe'].indexOf('banana')

console.log(fruitIntex)

// output: 2

.fill()

Replaces specified index value with a new value.

Note: Recommending to go over docs on how this method is working

// fill with 'orange' position 3

// array element     0             1        2           3
const fruits = ['dragonfruit', 'apple', 'banana', 'cantaloupe'].fill('orange', 3)

console.log(fruits)

// output: ["dragonfruit", "apple", "banana", "orange"]

.slice()

Will cut and store the specified index values into a new variable.

Note: Recommending to go over docs on how this method is working

// array element     0            1        2           3
const fruits = ['dragonfruit', 'apple', 'banana', 'cantaloupe'].slice(2)

console.log(fruits)

// output: ["banana", "cantaloupe"]

.reverse()

Will revert array values

const fruits = ['dragonfruit', 'apple', 'banana', 'cantaloupe'].reverse()

console.log(fruits)

// output: ["cantaloupe", "banana", "apple", "dragonfruit"]

.push()

Will add one more element to the end of the array

const fruits = ['dragonfruit', 'apple', 'banana', 'cantaloupe']

console.log(fruits.push('orange'))

console.log(fruits)

// output: 
// first console:  5
// second console: ["dragonfruit", "apple", "banana", "cantaloupe", "orange"]

.pop()

Will remove the last element from the array

const fruits = ['dragonfruit', 'apple', 'banana', 'cantaloupe']

console.log(fruits.pop())

console.log(fruits)

// output:
// first console:  "cantaloupe"
// second console: ["dragonfruit", "apple", "banana"]

.shift()

Will remove the first element from array and could be stored into a new variable

const fruits = ['dragonfruit', 'apple', 'banana', 'cantaloupe']

const shiftedFruit = fruits.shift()

console.log(fruits)

console.log(shiftedFruit)

// output:
// first console:  ["apple", "banana", "cantaloupe"]
// second console: "dragonfruit"

.unshift()

Will prefix new element to the array

Note: Recommending to go over docs on how this method is working

const fruits = ["apple", "banana", "cantaloupe"]

console.log(fruits.unshift('dragonfruit'))

console.log(fruits)

// output:
// first console:  4
// second console: ["dragonfruit", "apple", "banana", "cantaloupe"]

If you want to know more about some of the methods, I recommend going to MDN Web documentation.

For more helpful tips and advice, subscribe to my channel and don't miss future topics.

YouTube - DevPool

How To Be Good At Coding

DevPool — Tue, 17 Aug 2021 15:23:23 +0000

A lot of new developers wonder, how to be good at coding. To be honest, all what is takes is patience and ________________ .

For more helpful tips and advice, subscribe to my channel DevPool and don't miss future topics.

YouTube - DevPool

How To Land Your FIRST Web Developer Job In 1 Month

DevPool — Mon, 02 Aug 2021 16:08:05 +0000

The following tips helped me to land my first junior full-stack position in one month back in 2016. Even though I did only 4/7 tips, but that's because I was completely new to the game, and it felt less "competitive" than it is today. The following tips were thought out based on what I did personally in the past and what I've learned/witnessed by working in the field for over 5 years now.

Let's start with the most apparent/easy one first.

Having a Portfolio

Back when I was applying for my first junior web developer position in 2016, I didn't have a website because it didn't "feel" necessary or competitive as it is today for a lot of new developers.

There are many more self-taught developers, graduates from colleges, and coding bootcamps, and the chances of them having a portfolio are high. So little by little, I'm starting to believe that having a portfolio could help you stand out and maybe land on the interview. But at the end of the day, your interviewer will judge you based on your skills and not if you have a portfolio.
Publicly Available GitHub Projects

When I was applying for my first junior full-stack position, I had two available projects on my GitHub. A small frontend application and a full web app with complex features. I confidently explained each technology I used, why I wrote the code the way I did, how I built my schema, and how I imported the data in (this part is called fixtures, but I didn't know about it back then).

My projects aimed directly at becoming a full stack developer, so I already knew what jobs to apply for and where I will stand out.
Optimize Your LinkedIn For Recruiters To Find You Faster

LinkedIn is the tool that recruiters use religiously to find candidates for new open roles. If you don't have a LinkedIn profile, create one. If you have one, but it's empty, it's time to update it with your projects, languages/frameworks that you know, or what to be proficient in. Use an "About You" section if you haven't done so. The more information you have on your profile, the higher the chance of finding you because it is all based on keywords. Also, it doesn't mean you have to mention all languages and frameworks (then you will look like the master of none).
Attend Hackathons

There are multiple reasons why you would want to attend a hackathon. But one of the main reasons you want to consider is because many tech professionals are attending it. Some of them go there to have fun, and others could be looking for new developers to fill in a role they have open at a company they work at. Also, if you're a self-taught developer or graduate from a coding bootcamp, you may not have as many professional contacts. So this is the perfect way to get to know more people within your field.
Prepare For An Interview

When I was writing my first resume, I didn't have a link to my portfolio, GitHub, or even my LinkedIn!

But it had all the essential information that a recruiter/employer wanted to see. I had a summary that underlined what I was looking for and where I see myself heading in the future. Highlighted my strength, technical skills, and a lot more (I have a video on this. If you haven't seen it yet, I have it available on my YouTube channel DevPool). You also want to go over the interview stages (screening, coding, and behavioral). Each of them is important because if you passed the coding, it doesn't mean that the company will hire you if you didn't pass the behavioral.
While Waiting Try To Upskill

You could work on a new project using new technology, but if you already have like 100, should you be working on 101?

The best way to upskill your skills is to work. Now hold up, isn't this what we are trying to do? Yes, and there are jobs that you can start applying for. The only important thing you will be getting out of it is building something real users are using. You've probably guessed that I'm referring to non-profit organizations. You can include that into your resume and start applying for jobs again as you're working there. The difference now is that the recruiter or an employer cannot say, "you don't have working experience".
Repeat

I remember when I applied to 10 jobs a day minimum, which would lead to a lot of rejections. I had no idea what I was doing because it was my first time, but I would ask for feedback on what I did wrong and see how I could improve. The fact that I was applying to many jobs per week helped me fix many mistakes much-much faster than I anticipated. So by the time I was reaching the end of the month, I was able to get several offers to choose from.

There is the say "repetition is the key," and it's there for a reason.

These are the seven tips that I hope can help some get that junior developer job much faster than you thought.

For more helpful tips and advice, subscribe to my channel DevPool and don't miss future topics.

YouTube - DevPool

How to Build REST API Using Node Js Feathers Framework

DevPool — Mon, 26 Jul 2021 15:31:15 +0000

This article will create a simple REST API vehicle system with full authentication and CRUD (create, read, update, delete) capabilities.

We will be creating a simple vehicle API support.

Our Use Cases:

As a user, I should be able to register.
As a user, I should be able to login.
As a user, I should be able to perform any CRUD operations on the vehicle data.
- create
- read
- update
- delete

Project Setup

mkdir vehicle-api
cd vehicle-api
feathers g app

As you're answering the above questions, you'll notice that you can create your application using TypeScript and not JavaScript, or we can select any other database type.

For simplicity, I went with yarn, JavaScript, and NeDB, but if you're planning to use npm, TypeScript, or Postgres/MongoDB, you can do so.

Next, open your project with an editor of your choosing (I'm personally going with VS Code)

To run the application, run the appropriate package manager command that you've selected. In this case:

yarn dev

and you should be able to see this page in your browser:

Congratulations!
You've set up your first Feathers application, and here is the tree structure of our project:

You can find more information how what do this files do in here: https://docs.feathersjs.com/guides/basics/generator.html#the-generated-files

Notice how under 1 minute, we've generated an application with a full authentication implementation and our first user service has full CRUD capabilities.

So how do we communicate with our backend if we don't have a frontend?

Whenever we work on the API, engineers would use a tool called Insomnia or Postgres (in this example, I'll be using insomnia). Overall it will enable us to send and get a response from our API without running the frontend.

What we want to do next is to create "register" and "login" requests in our insomnia workspace.

In my workspace, I'll be creating a new folder, "Authentication," that will contain "register" and "login" requests.

Register

After sending the request, we should see the following:

Login

After sending the request, we should see the following:

If you see the same thing, then your authentication is set up correctly!

Since the basics of our applications are set up and running, it's time to create our vehicle service.

To do that, run the following command and answer all of the questions in the same way as we did it right from the beginning:

feathers g service

And if you look under the services/model folder, we now have a vehicle implementation that we can perform entire CRUD operations on.

At this point, our REST API is fully ready to take in some data and perform the entire CRUD operation on our new vehicle service!

Let's create a few records to demonstrate that.

Oh no, what happened here!? We're getting an error message "Not authenticated."

That's the expected behavior because our system is saying that "you're trying to access an endpoint when you are not authenticated." Translation, not logged in.

So let's send the request with the generated token from before and try to resent the request

At this point, we can now save a record into our DB.

Let's create few more records and get all vehicles:

At this point, our Update and Delete will look very similar.

Additional Recourses:

If this was your first RESTful API build, unfortunately, I didn't explain models, why we named our folders "Authentication" or "vehicles" in our insomnia, and what some of the things are. Thankfully, I do have a video where I give more information for beginners as I'm building out the API:

https://youtu.be/H0KhcB3D8aQ

Feathers Documentation:

https://docs.feathersjs.com/guides/basics/generator.html

Conclusion

We just created our first RESTfull API using FeatherJs framework WooHoo! I hope this tutorial was helpful for some of you. We did many things, and it could be a lot at first and could be confusing at the beginning. But to be honest, once you master this, you will realize that we have created an amazing backend with many complex pieces, and we can create all of it unless 2 minutes. So big congrats to you on getting to the end of this tutorial!

If you have any questions, feel free to leave a comment or you can find me on my YouTube channel DevPool

YouTube - DevPool

4 JavaScript Projects To Build FAST And Get Hired In 1 Month

DevPool — Wed, 14 Jul 2021 15:31:42 +0000

If you're starting to apply for your first web developer junior position, then you might want to consider building out one of the 4 (if not all) projects.

Why?
The projects were thought out based on daily tasks that many web developers (including seniors) face every day.

1. Consume API (Backend)

When you consume someone else's API, you are talking to a third party outside of your system. You could choose what type of data you want to get, should you validate it, how do you want to store it in your database, etc.

This is where you could throw in your imagination and do whatever you want with the data. You could also perform a small CRUD system once you've retrieved the data.

To give you an idea, you could consume Yelp or SpaceX API (but there is a lot more out there):

SpaceX API
https://docs.spacexdata.com/

Yelp API
https://www.yelp.com/developers/documentation/v3/get_started

2. 10 Hour Challenge (Frontend)

This is my personal favorite if you're planning to be a front-end developer.

Within 10 hours, you should build a single-page application using a framework that you've never used before. It has to be responsive, look good/decent, and deployed onto a hosting service.

Having something like on the resume will impress every person on the interview as you will demonstrate how fast you can learn, implement, and not get destructed in the process. But again, the key is to finish it in 10 hours.

3. Building Blog Post (Frontend, Backend)

You've probably heard this already, but there is one key element that many developers don't implement.

When we build projects with X number of records on a single page, we follow a specific process that allows us to load a specific number of records instead of loading all records at once. This process is called pagination.

Have you seen something like this at the bottom of any e-commerce website? Well, that is pagination! So when you are building out a blog page, you're focusing on implementation the pagination functionality.

Suppose you don't have a blog, no problem. You could talk to Yelp API or the database that you've built for the first project.

4. Hotel System (Frontend, Backend)

This one will be a bit more complex and time-consuming as you will be building out the frontend, backend, database, and most importantly, building out the features.

Every hotel has a specific number of available rooms, included in the packages (this is up to your imagination), for how long the guest will be staying, and a lot more.

Don't go overboard and build out the Hilton system, but focus on maybe 3 to 4 features that you know could be fun to demonstrate during the interview and do small calculations.

These are the four projects that could help you stand out during the interview and help you to land a job much faster than you think. You may not even get a coding challenge because you will demonstrate excellent work (that's what happened to me).

For more helpful tips and advice, subscribe to my channel and don't miss future topics.
YouTube - DevPool

Why Docker?

DevPool — Sat, 26 Jun 2021 16:49:29 +0000

Before I talk about Docker, let me give you a common problem in software development that developers used to have.

Let’s say a developer who just finished developing and testing a new feature worked fine on their environment. But when the same code reached production, suddenly, the system crashed. One of the possible reasons is that the development and production environments are different from each other.

Before Docker, developers would use Virtual Machine to create a virtual environment to ensure that the developer’s station matches the production server. The problem with that is now we are wasting resources and not able to usefully our Disk Space, Memory, Processing Power, and more.

Docker is different to set it up and use. It is installed directly onto the user’s machine, and developers can install multiple containers responsible for their microservice. As you can see, we didn’t have to allocate any of the resources for our containers, and it will automatically use what it needs for the need of an application.

We can now have our code base with all the tools running equally on any environment with that setup.

In conclusion, if you were to start to work on the project, I would recommend using Docker as it will remove the environmental issues.

For more tips, subscribe to my channel and don't miss the future topics.
YouTube - DevPool

5 Reasons Why I Love Being a Web Developer

DevPool — Sun, 16 May 2021 22:00:16 +0000

Suppose you are looking into a career change or in school for software development. But you are not sure if Web Development is the right choice. As a Full Stack Software Engineer, I have thought of 5 reasons why I love Web Development, and hopefully, it will help you answer some of your questions.

1. Web Developers Are In-Demand:
Your friends want a website, startups need a website, big companies need developers who can support and build new features in their existing website. Moreover, web technology allows developers to build not only websites but they could also build apps for smartphones or create system applications. Since web development becomes more flexible, businesses come up with more use cases to solve specific problems. Still, unfortunately, there are not enough developers who can build and maintain the codebase. As you are reading this, you have probably noticed that there are a lot of open jobs. So if you are planning to become a web developer, after 4 to 6 months (depending on the learning path you took), you could get your first web developer job.

2. It Provides Good Salary:
To look at this data more accurately, I would recommend using Glassdoor or Indeed to get a more accurate number based on your location. But depending on your location, Junior Web Developers could get a minimum of $45,000 annually, and Senior Developers could get around $120,000 annually. The other reason why you should be using Glassdoor and Indeed is that you want to get an idea of what other people in your area are getting so you can negotiate your salary much better during the interview. Your salary will also depend on what language and side of web development you have chosen. So when you are comparing, I would recommend comparing Backend vs Frontend vs Full Stack Developer salaries.

3. You Can Choose How You Want To Work:
One common path that we all take is working 9 to 5, and we are happy with that. But what if working full time is not for you or let's say you got a lot of time to kill after hours, what do you do? A lot of web developers would use that time to look for a client and have hustle on the side. It's a common thing among web developers, and by doing that, they are making extra money on the side. If your freelance path looks successful and profitable, you could make that into your full-time job and register yourself as a business. But this is something you would have to look into as this depends on your location.

4. Web Development Has A Big Choice Of Languages:
We got PHP, NodeJs, Python, Java, C#, Deno, Ruby On Rails, etc. Each one of them is different and has its own purpose or could open up other options for you. For example: if you are planning to learn NodeJs, since it's built on JavaScript, you can take that skill and apply it both on Backend and Frontend. In comparison, PHP can only be used on the Backend side. Now you might be thinking, "why should I learn PHP if I can use it only on the backend?". PHP has been around for a long time now, so many enterprise companies and corporations are built on PHP. When you decide what language you should focus on, I recommend doing a little research on the most common or popular language in your area. It will help you find a job much faster (and you won't be wasting time learning something you don't need).

5. You can choose on what side of web development you want:
Whenever I say "I am a Web Developer", it could be unclear to other developers because there are three main parts to it. I could be a Frontend, Backend, or Full Stack Software Developer. We have a preference on what it is we want to focus on, so a lot of people choose only one. As Frontend Developer, you will most likely use only one framework: ReacJs, Vuejs, Angular, etc (depending on the company stack). Frontend doesn't have business logic. As a result, it's much simpler to work with. On the other hand, Backend is much more complex because that's where a lot of business logic goes. You will have to consider many things like security, performance, and scalability of the application that you are building. Full Stack Software Developer is a combination of Frontend and Backend. As you can see, you don't have to know how web development works to 100%. You can always choose the side that looks most appealing to you, and if you want to expand the knowledge, the option is always there.

These are my top 5 significant reasons why I love Web Development. If you want to know more about it, I would recommend taking a look at and subscribing to my YouTube channel DevPool as my goal is to help beginners and juniors to succeed in the tech industry. If you are looking for some mentorship, I also have TechDevPool 1 on 1 session tailored for you where I use my years of experience and point you in becoming a Web Developer in a matter of months, not years.

YouTube - DevPool

TechDevPool - 1 on 1 Tailored Sesssion

How many hours per day you should spend learning programming

DevPool — Sun, 02 May 2021 20:00:03 +0000

As a Fullstack Software Engineer, I have already walked the path of learning. I wanted to share some of my tips, what I have witnessed from others and what worked for them.

1. Every number is different for each person:

Anyone can sit and start learning to program, but each person will arrive at the destination based on the path they took and if they had any help on the way. I have seen people taking almost a year and some just about 4 months to become web developers and find their first job. People that took a long time to learn had to make a lot of try and error, and unfortunately, no one was there to guide them. So if you are starting in web or software development in general, don't get discouraged because it's taking you a long time to understand a topic. But use this as an opportunity to learn and perhaps try to find a mentor who walked that path and can guide you.

2. Consistency is the key:

If you have decided to become a web developer (or any software developer), give yourself a deadline and how many hours you can allocate a day to work toward that goal. Now, this part is very important, ready? Be honest with yourself. If you say 12 hours a day and your deadline is 6 months from now. Can you study every day for 12 hours consistently for 6 months? Well, first, you shouldn't do that, so be reasonable and very critical of this part as you may discourage or burn yourself out halfway.

3. Be patient:

Like for anything in life, you need to be patient about the process. 4 months or 1 year, and it will take time one way or the other. All you can do is prepare and have fun while doing it. There is nothing much to say about this one, but it is essential to point that out since many of us want to get to the destination fast and forget that it takes time, and you do need patience for this.

These are my top 3 points that should help you predict how many hours you may need before getting that first job. You can subscribe to my channel DevPool as my goal is to help beginners and juniors succeed in the tech industry.

YouTube - DevPool

Things I Wish I Knew When I Started Programming

DevPool — Thu, 08 Apr 2021 13:47:13 +0000

This time I am doing things a bit differently. I have created a video on "Things I Wish I Knew When I Started Programming" instead of writing a blog.
Hope you all like it and below are the main 3 points:

1 Been a perfectionist is not the way to go

2 Knowing tech is not everything

3 Things change fast

Tips To Find Your First Junior Software Developer Position

DevPool — Sun, 28 Mar 2021 00:59:42 +0000

1. Search by language or framework:

The first time when I was looking for a Junior Web Developer position, I would type something like "junior web developer", and the result would consist of languages that I didn't want to specialize in or not all junior positions would come up as a lot of companies don't have the same job title. So I changed my strategy a bit by searching for the language or framework I wanted to specialize in. By doing that, I was able to filter out all the jobs that I didn't want to apply for or shouldn't even waste my time looking at it in the first place.

2. Tailor your skillset to job market demand:

Once you followed the first step and found a few awesome jobs, it's time to compare them to each other. As you compare them, look at the most common things first and make them your #1 priority. If you want to be a frontend developer and see that ReactJs is the most common framework that companies are asking for, consider putting more of your focus and efforts into ReactJs technology. This approach can help you filter out things that you don't need to spend weeks or months studying.

3. Sharpen your skills by setting challenges for yourself:

About every experienced developer would say that you need to work on a project that could help you progress, and they are not wrong. However, how do you track your progress? In my case, I gave myself 10 hours to develop a project using technologies and technics that I have never used. The goal was to develop a single-page application using AngularJs (when it was hot), make it responsive, functional, and beautiful UX/UI, and deploy it onto a server. I was able to accomplish it all in 8 hours and prove it during the interview. Working on a project for more than 2 to 3 months just become an unpaid job.

These are my top 3 points that helped me get my first Junior Full Stack Developer position. But are there more tips for it? 100% yes, and you can find them on my YouTube channel DevPool. Subscribe to my channel as my goal is to help beginners and juniors succeed in the tech industry.

YouTube - DevPool