-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex_old.html
60 lines (47 loc) · 3.02 KB
/
index_old.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<link rel="stylesheet" type="text/css" href="css/rabelle3-style.css">
<!-- replace Skillcrush with your name here -->
<title>Rabelle's Advice For Newbies</title>
</head>
<!-- replace skillcrush with your name here -->
<body class="rabelle-advice">
<header>
<a href="../index.html">Back to Main Page</a>
<h1>Hi my name is Rabelle and I have some advice for you!!!</h1>
</header>
<section>
<div class="advice">
<h4>Work Methodically</h4>
<p>When you start programming your first web app you are doing something that you have never done before. It's a new challenge, a new opportunity, and in the case of software development, something so specific that it's probably never been done before.</p>
<p>Working methodically will help keep you from getting confused and will allow you to build upon your newly learned skills, line upon line and precept upon precept. If you try to jump ahead into something that you don't understand too soon, you might find yourself frustrated and stuck. Unless you have a good mentor who can step in and offer advice on where you went wrong, you may have to scrap your entire project and start over. </p>
<h4>Test Code Often</h4>
<p>Checking your work often is an important part of methodical programming. This means building your application one piece at a time.</p>
<ul>
<li>First you might write a line of code to print. (test it)</li>
<li>Then you might add some i/o. (test it)</li>
<li>Then you might try adding some variables, (test it again).</li>
<li>Add a method (test)</li>
... you get the idea...
</ul>
<p>As you add each new piece of complexity to your program you need to continue to test to make sure that the entire program still works. </p>
<p>By programming methodically, when your code ceases to work (and it WILL cease to work at some point), you can simply comment out the most recent change and test the code again. If it works, then you know that the most recent line of code is the culprit.
</p>
<p>On the other hand, if you make too many changes at once you can find yourself in the predicament on not knowing exactly which piece of code broke your program. </p>
<h4>Don't Re-Invent the Wheel</h4>
<p>While writing your own original code can be fun and exciting, sometimes the method you need has already been written. It's often quicker and easier to look online and find some good, working sample code, play with it and customize it, but when it's obvious your borrowing code, don't forget to acknowledge your source. </p>
<p>Thanks Peter Wolf for your lovely style-sheet! It was a great jumping off point!</p>
</div>
</section>
<footer>
<!-- replace Skillcrush with your name here -->
<p>© Copyright Rabelle Rouser 2019.</p>
<a href="skillcrush101/index.html">Check out my SkillCrush 101 Website</a>
<a href="WHHOA/home.htm">WHHOA</a>
<a href="WH/index.html">WH</a>
<a href="app/index.html">Bootstrap 4 Datatable with Buttons</a>
</footer>
</body>
</html>