forked from Codi-T03/HTML-Challenge
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathfatina-html2.html
More file actions
188 lines (145 loc) · 5.63 KB
/
fatina-html2.html
File metadata and controls
188 lines (145 loc) · 5.63 KB
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
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
<htm>
<head>
<style>
html,
body {
width: auto;
height: auto;
}
* {
font-family:monospace;
box-sizing: border-box;
scroll-behavior: smooth;
}
h1 {
text-align: center;
padding-top: 4%;
padding-bottom: 2%;
}
.p1 {
text-align: center;
padding-bottom: 2%;
}
.container {
width: 100%;
min-height: 100vh;
display: inline-block;
padding: 6%;
}
nav {
background-color: rgb(23, 24, 49);
}
.bar {
list-style-type: none;
align-items: center;
overflow: hidden;
color: white;
}
li {
float: left;
}
li a {
display: block;
padding: 8px;
text-decoration: none;
color: white;
}
.image {
height: 550px;
width: 750px;
display: flex;
align-items: center;
}
.image1 {
height: 150px;
width: 250px;
}
.routine {
display: block;
}
.codi {
text-decoration: none;
color: rgb(223, 26, 164);
}
.codi:hover {
color: yellow;
}
footer {
background-color: rgb(23, 24, 49);
width: auto;
height: 11px;
color: white;
display: flex;
justify-content: space-between;
align-items: center;
padding: 1.3em;
}
</style>
</head>
<nav>
<ul class="bar">
<li><a href="#home">Home</a></li>
<li><a href="#news">News</a></li>
<li><a href="#contact">Contact</a></li>
<li><a href="#about">About</a></li>
</ul>
</nav>
<header>
<h1><b><u> What Does A Software Developer Do?</u></h1>
<p class="p1"><i>A software developer is a broad term that applies to
people who think of, design, and build computer programmes and applications.
<br>They can work on mobile or desktop systems and build underlying systems for tech and companies.</i>
</p>
</header>
<body>
<div class="container">
<img class="image"
src="https://cdn-employer-wp.arc.dev/wp-content/uploads/2022/04/good-software-developer-1128x635.jpg"
alt="a web developer">
<p>
<h2><u>A Day In The Life</u></h2>
Before we dive into a day in the life of a software developer, we should add two disclaimers:<br>
Obviously, the job varies day-to-day. <br>
Also, every company has its own culture and quirks. We’ll start with some context for project work.
</p><br><br><br><hr><br>
<img class="image1"
src="https://assets.website-files.com/634681057b887c6f4830fae2/6367ddc0a0bbe102f1a93463_6259f8788137b3417d1e0e41_software_eng_routine.png"
alt="developer daily steps "><br>
<ul class="routine">
<li>A good developer is not only being a great programmer but also possessing great habits.</li><br>
<li> Sleeping properly plays a big role in your productivity for the day that is coming.</li><br>
<li>Be physically active. </li><br>
<li>Don't overwork.</li><br>
<li>Increase your knowledge each day.</li><br>
<li>F-O-C-U-S.</li><br>
</ul>
<br><br>
<hr>
<h2>
<b><u>Daily Routine of a Software Developer</u></b>
</h2>
<p>
So your day might break down like this:<br>
9 am: Come in, check emails, arrange short, medium and long-term to-do lists, organise meetings<br>
10 am: Standup meeting, coordinate day and organise collaboration <q>if any</q><br>
Then it’s into project work: Carry out coding, problem-solving and development.
<br>At various points, you will ask for advice <q>or give advice</q>.
<br> Depending on the environment,
you
might chat or send a message via Slack or IRC <q>a form of chat popular among software devs</q>.<br>
If members of your team are free, you might go to a whiteboard together or sit together and then diagram
and
work out a solution. <q>Then you might possibly go back to struggling!</q>
Depending on the company, after you find a solution, you’d usually create a “change request” or “pull
request”<br> summarising changes proposed, which someone else would review.
<br> They might have ideas or solutions of their own.
This would probably bring you to lunch. Often, the afternoon is when meetings are held, and longer-term
projects are discussed.
</p>
</div>
</body>
<footer>
thank you for visit our page
<a class="codi" href="https://codi.tech/">Codi Tech.</a>
</footer>
</html>