jshaver/portfolio
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Fixed some wording

Browse source
This commit is contained in:
John Shaver 2022-07-23 13:31:54 -07:00
parent 3edaa49ce7
commit 49b7a59c05
1 changed files with 30 additions and 26 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

56
index.html
View file

@ -33,19 +33,18 @@
<section class="section about"> <section class="section about">
<h2>About Me</h2> <h2>About Me</h2>
<p class="attention">I'm a full-stack engineer with experience building <p class="attention">I'm a full-stack engineer with experience building
and deploying web based applications from the ground up as well as and deploying web based applications, building out CI/CD pipelines and
debugging and maintaining legacy applications. I am looking for a remote maintaining legacy applications. I am looking for a remote position
position building web based software with a team that embraces remote building web based software with a team that embraces remote work.</p>
work.</p>
<p>I have been working with websites and code since I was a kid and then <p>I have been working with websites and code since I was a kid and then
worked 7 years in technical support where I gained a solid understanding worked 7 years in technical support where I gained a solid understanding
of the web and how it works under the hood. I have spent the last 8 years of the web and how it works under the hood. I have spent the last 10 years
designing, building, deploying and maintaining javascript and typescript designing, building, deploying and maintaining javascript and typescript
applications. I've worked with PHP, NodeJS, React, and Serverless.js. I applications. I've worked with NodeJS, React, and Serverless.js. I
enjoy learning better ways to do things, solving difficult problems and enjoy learning better ways to do things, solving difficult problems and
building software that helps people. I live in Moscow Idaho and my building software that helps people. I live in Moscow Idaho and my
hobbies include Devops, listening to podcasts, playing ukulele and, hobbies include Devops, listening` to podcasts, playing ukulele and,
especially, spending time with my wife and 4 kids.</p> especially, spending time with my wife and 4 kids.</p>
</section> </section>
<section class="section projects"> <section class="section projects">
@ -60,11 +59,12 @@
</div> </div>
<div class="project-info"> <div class="project-info">
<h4>Project Goals</h4> <h4>Project Goals</h4>
<p>Skillabi is a tool to help Higher Education institutionsand to <p>Skillabi is a tool to help Higher Education institutions to find
find skills that are in-demand in the market place so they can skills that are relivant to their curriculum and in-demand in the
adjust they're curriculum to teach those skills. Skills are parsed market place so they can adjust they're curriculum to be more
from course data and then compared with skills job postings data relevant to the developing job market. Skills are parsed from
for relevant occupations.</p> course data and then compared with skills job postings data for
relevant occupations.</p>
<h4>My Contributions</h4> <h4>My Contributions</h4>
<p>I worked on a 2-3 man team to build a prototype using netlify. We then <p>I worked on a 2-3 man team to build a prototype using netlify. We then
@ -73,28 +73,32 @@
of technical debt on the inside.) When it came time to build a of technical debt on the inside.) When it came time to build a
production version, I took over as the technical lead on the production version, I took over as the technical lead on the
project. This included designing a new version of the backend APIs project. This included designing a new version of the backend APIs
and leading the reimplementation the frontend.</p> and leading the reimplementation of the frontend.</p>
<p>The new APIs for storing curricular data and user profiles <p>The new APIs for storing curricular data and user profiles
needed to be secure, easy to use, well tested, well documented, needed to be secure, easy to use, well tested, well documented,
scalable and reliable. We ensured that security was implemeted in scalable and reliable. We ensured that security was implemeted in
the back end first. We used cognito tokens and JWT claims to scope the back end first. We used cognito tokens and JWT claims to scope
user access at the API level on a per user basis. We adopted a user access by role. We designed api search queries for the a
search query language for searching a curricular data that ensured curricular data that ensured the API could be easily expanded and
the API could be easily expanded and would be consistant across would be consistant across endpoints, while still being powerful
endpoints. We implemented the API on AWS serverless lambdas for enought to do all the searching/filtering that would be needed in
the frontend. We implemented the API on AWS serverless lambdas for
scalability and reliability and used typescript on serverless.js scalability and reliability and used typescript on serverless.js
for ease of development.</p> for ease of development.</p>
<p>The new frontend was developed with react, written in typescript <p>The new frontend was developed with react, written in typescript
and served via cloudfront and s3 for scalabilty, reliability and and served via cloudfront and s3 for scalabilty, reliability and
simplicity. I developed the solutions to the most complicated simplicity. It also had to meet the accessiblity requirements of US
problems, including realtime highlighting of skills within a text and UK educational institutions. I was tasked with implementing
area as users type (The parsing of the skills was handled by an some of the more complicated problems, including realtime
external API), and identifying boilerplate text accross many highlighting of skills within a text area as users type (The
courses in a curriculum for parsing. </p> parsing of the skills was handled by an external API), and
identifying boilerplate text accross many courses in a curriculum
for parsing. </p>
<h4>Technologies Used</h4> <h4>Technologies Used</h4>
<p>Typescript, Terraform, Gitlab CI, Fugue, OpenId/OAuth, React, Serverless.js, react-query, JWT, KONG</p> <p>Typescript, Terraform, Gitlab CI, Fugue, OpenId/OAuth, React,
Accessibility, Serverless.js, react-query, JWT, KONG</p>
</div> </div>
</div> </div>
<h3>Skillsmatch</h3> <h3>Skillsmatch</h3>
@ -123,7 +127,8 @@
as they were hired, implementing API tests on our new APIs and as they were hired, implementing API tests on our new APIs and
building out dev ops systems to automatically deploy to AWS.</p> building out dev ops systems to automatically deploy to AWS.</p>
<h4>Technologies Used</h4> <h4>Technologies Used</h4>
<p>React, Cypress, AWS Elastic Beanstalk, Serverless.js, Redux, Docker, Codeship CI</p> <p>React, Cypress, AWS Elastic Beanstalk, Serverless.js,
Accessibility, Redux, Docker, Codeship CI</p>
</div> </div>
</div> </div>
<h3>Dash Drop</h3> <h3>Dash Drop</h3>
@ -147,8 +152,7 @@
Javascript, where needed, to change the structure of the Javascript, where needed, to change the structure of the
interface.</p> interface.</p>
<h4>Technologies Used</h4> <h4>Technologies Used</h4>
<p>CSS and some JQuery</p> <p>HTML, CSS, Javascript and some JQuery</p> </div>
</div>
</div> </div>
<h3>NewVistas Website Platform</h3> <h3>NewVistas Website Platform</h3>
<div class="project"> <div class="project">