
import React from 'react';
import ViewCount from 'ViewCount';
import IncrementViewCount from 'IncrementViewCount';
import Quiz from 'Quiz';
import Question from 'Question';

<IncrementViewCount slug={'how-the-world-wide-web-works'} />
<ViewCount slug={'how-the-world-wide-web-works'} />

# How The World Wide Web Works

Wanting to become a Web Developer is a great challenge to take on. I'm hoping I can help make that journey a little easier. Today we will be going over part one of my Modern Web Development series where we will discuss the basics of web development theory.

We will discuss:

1. What the Web (or World Wide Web)
2. What is the Internet?
3. What is the browser?
4. How does a browser display a website?
5. What is an IP address?
6. What is HTML, CSS and Javascript?

## Video Explanation

Please watch this YouTube video and then answer the quiz below!

<iframe
  width="100%"
  style={{ aspectRatio: '16/9', marginBottom: '32px' }}
  src="https://www.youtube.com/embed/7ivnuLwzWp4"
  title="YouTube video player"
  frameBorder="0"
  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
  allowFullScreen
></iframe>

<Quiz title={'World Wide Web Quiz'}>
  <Question
    title={'What is the World Wide Web?'}
    groupName={'whatIsTheWorldWideWeb'}
    options={[
      'A vast network of physically connected computers used to transfer data and other resources.',
      'An information system allowing web resources to be accessed over the internet.',
      'The mail courier system in the USA.',
    ]}
    answers={['An information system allowing web resources to be accessed over the internet.']}
  />
  <Question
    title={'What is the internet?'}
    groupName={'whatIsTheInternet'}
    options={[
      'An application that allows you to request and recieve websites.',
      'The opposite of the outernet.',
      'A vast network of physically connected computers used to transfer data and other resources.',
    ]}
    answers={['A vast network of physically connected computers used to transfer data and other resources.']}
  />
  <Question
    title={'What is a browser?'}
    groupName={'whatIsABrowser'}
    options={[
      'An application that allows you to request, recieve, and display websites.',
      'A markup language for building documents to display on the web.',
      'A computer that recieves requests from and sends data to other computers.',
    ]}
    answers={['An application that allows you to request, recieve, and display websites.']}
  />
  <Question
    title={'How does a browser display websites?'}
    groupName={'howDoesABrowserDisplayWebsites'}
    options={[
      'MS Paint.',
      'By using HTML, CSS, and JavaScript files to build a copy of the website.',
      'By borrowing the original files of a website from a server.',
    ]}
    answers={['By using HTML, CSS, and JavaScript files to build a copy of the website.']}
  />
  <Question
    title={'What is an IP Address?'}
    groupName={'whatIsAnIpAddress'}
    options={[
      'A unique ID for a machine that the internet uses to locate a machine.',
      'The place where websites are stored.',
      'An alcoholic beverage for software engineers.',
    ]}
    answers={['A unique ID for a machine that the internet uses to locate a machine.']}
  />
  <Question
    title={'What is HTML?'}
    groupName={'html'}
    options={[
      'A protocol used to send hypermedia documents over a network.',
      'Hipsters That Mate for Life',
      'A markup language for building documents to display on the web.',
    ]}
    answers={['A markup language for building documents to display on the web.']}
  />
  <Question
    title={'What is CSS?'}
    groupName={'css'}
    options={[
      'A programming language that powers interactivity on a website.',
      'A style sheet language used to control the presentation of a website.',
      "An error shown when a user Can't See a Site.",
    ]}
    answers={['A style sheet language used to control the presentation of a website.']}
  />
  <Question
    title={'What is JavaScript?'}
    groupName={'javascript'}
    options={[
      'A markup language for building documents to display on the web.',
      'The best work of a writer after he drinks some good coffee.',
      'A programming language that powers interactivity on a website.',
    ]}
    answers={['A programming language that powers interactivity on a website.']}
  />
</Quiz>


How The World Wide Web Works


import React from 'react';
import ViewCount from 'ViewCount';
import IncrementViewCount from 'IncrementViewCount';

<IncrementViewCount slug={'what-i-learned-in-the-first-six-months-as-a-junior-developer-1'} />
<ViewCount slug={'what-i-learned-in-the-first-six-months-as-a-junior-developer-1'} />

# What I Learned In The First Six Months As A Junior Developer: Part 1

I started my journey into web development back in October of 2021 and started my first job as a Front End engineer on May 31st, 2022.
Many out there reading this may be seeing that time-to-job number and raising an eyebrow at it.
Eight months is not a very long time to start learning web development and end with a full time job in the industry, but that's a
whole other article by itself. Today I'm going to be talking about the lessons I've learned in the last six months of my first job as a web dev and hopefully
pass on some knowledge that will help at least one person out there who's searching for or has just started their first job.

## Learn how to learn

Being an engineer - and yes you are or will be one - takes thinking like an engineer. The whole basis around being an
engineer is solving problems. Without us, society would collapse or not exist at all. Now, of course, society would go on without
you or me. Especially at this point in our careers assuming I'm speaking to another junior. I felt completely disposable
when I first joined my team for one simple reason: I did not know what everyone else knew. We were working with Redux,
internationalization, feature flags, multiple portals, a component library and the list goes on and on.... At the time
this gave me the fear that I could be fired at any moment simply for being incompetent, but I stuck my nose down
and just took the time to learn.

I was lucky to have a senior who encouraged me to take this time when I didn't know something. He understood
that I'll work more efficiently with an increase in code quality if I actually understand the tech I'm working with.
The hard part about joining a team, even if you've been developing for years, is the exact stack they use could have parts that are completely
foreign to you. This is when your skill in the ability to learn matters.

When you're presented with a new technology what is your first response? Do you ask a lot of questions? Go to YouTube? Freeze?
These all have their place, even the last one, but if you want to excel and make the most out of your first six months you
need to have an attack plan for learning a new technology. First off, you may want to slow down with the questions. I'll talk
more about this soon, but attempting to figure out the answer on your own first will be incredibly vital to becoming a better
developer and not annoying your seniors and co-workers. Part of learning how to learn will be taking the initiative to sit
down and research. YouTube is a great resource for this, but should seldomly be your first line of offense.

For example, let's say you've never used Redux before and you have no idea what global state management even is. Heading to YouTube
or asking your senior may sound tempting, but there is a better alternative. Going to the documentation of the tech that
you're trying to understand is one of, if not usually, the best source of information. These are the people that wrote the code
behind what you're attempting to learn. Where do you think the YouTubers found the information to make a video on? It's not just
a long line of content creators regurgitating each others words. Most likely they went and read the documentation.

Most of the time this documentation will live on github and have a multiple examples and explanations of what their code does and
how and when to use it. For larger packages like Redux you'll often even see a website with very consumable tutorials from
the authors themselves. If you can master finding and reading documentation early on you'll seriously up the game of what you can
accomplish as a junior.

If no suitable documentation can be found then google and stackoverflow are your best friends. If this is a bug or a question about
something new that you're trying to tackle then most likely you're not the first. Google well and google often. Take the time to learn
even if you feel anxious that you're not pushing code out. Taking the time now will speed up your productivity later and everyone
will be happy. You're not expected to crank out insane code at your first job, so take advantage of that. Relax and learn what you can so
that when expectations start being set, you can reach or even exceed them.


Blog

All Articles

How The World Wide Web Works

What I Learned In The First Six Months As A Junior Developer: Part 1