Introduction

Question 1

web developers

Answer 1

build and maintain websites

Question 2

Front end developer

Answer 2

Actual visuals of a website, navigation, and interface.
Typically use HTML, CSS, and JavaScript.

Question 3

Back end

Answer 3

Guts of the application, the foundation of what the front relies on, typically use Java, Python, Ruby and JavaScript

Question 4

Full-Stack developers

Answer 4

combination of back and front end

Question 5

Large tech companies

Answer 5

More hard to get into, but offer superior pay and opportunities

Question 6

Freelancer

Answer 6

You find your own work but have to manage your time between coding, and dealing with managing your wage and hours

Question 7

Startups

Answer 7

More wild and offer lower salaries but more company equity

Question 8

Consultant

Answer 8

Good balance between work and life. More focused on coding and less on the hustle.

Question 9

Web developer

Answer 9

Usually involved in old companies and offer good work and life balance but is the most slow.

Question 10

Tools of the trade: Text editor

Answer 10

simply, a place where you can edit text

Question 11

Tools of the trade: Command Line Interface (CLI)

Answer 11

A more complex GUI that allows you to interact with your computer, Like powershell.

Question 12

Tackle the unsexy fundamentals

Answer 12

things like testing, data modeling, architecture and deployment

Question 13

solution vs best solution

Answer 13

make sure your code isn’t held by duct tape but is iron clad

Question 14

breaks good or bad?

Answer 14

Good, they are necessary for learning

Question 15

diffusion only occurs when you are?

Answer 15

not focused on the problem. and instead you are doing another task and allowing your brain to think for you

Question 16

debugger

Answer 16

explains a role/ what a line of code does

Question 17

step over (debugger)

Answer 17

it shows you what the line of code did

Question 18

step into (debugger)

Answer 18

goes into how the code function gives you what i did

Question 19

How to ask a question

Answer 19

ask how to solve the problem. avoid asking how to solve the solution to said problem.

Question 20

how to ask a question 2

Answer 20

check your code and ensure it is not a typo and make sure you tried every solution.

Question 21

how to ask a question 3

Answer 21

always add enough context

Question 22

when to ask for help

Answer 22

try 10 minutes of troubleshooting on your own AFTER you feel like you should ask for help.

Question 23

google questions you may want to include are

Answer 23

a partial error message, and the software name

Question 24

Ask your question—but phrase it differently

Answer 24

Instead of asking your question directly, ask “Has anyone has seen this problem?” or “Can anyone point me in the right direction?”

Question 25

guide as to what ur question should include

Answer 25

What version of the software are you running?
What’s your operating system?
What exactly are you trying to do that won’t work? Is the problem uniform or erratic?
What’s the exact error message? When did it arise?
What exactly don’t you “get”?
Can you provide a sample code, ideally with line errors where the error occurs?