diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..e2279e2 --- /dev/null +++ b/.gitignore @@ -0,0 +1,70 @@ +# VS Code +.vscode/ + +# bundle.js +public/bundle.js + +# Logs +logs +*.log +npm-debug.log* +yarn-debug.log* +yarn-error.log* + +# Runtime data +pids +*.pid +*.seed +*.pid.lock + +# Directory for instrumented libs generated by jscoverage/JSCover +lib-cov + +# Coverage directory used by tools like istanbul +coverage + +# nyc test coverage +.nyc_output + +# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files) +.grunt + +# Bower dependency directory (https://bower.io/) +bower_components + +# node-waf configuration +.lock-wscript + +# Compiled binary addons (https://nodejs.org/api/addons.html) +build/Release + +# Dependency directories +node_modules/ +jspm_packages/ + +# TypeScript v1 declaration files +typings/ + +# Optional npm cache directory +.npm + +# Optional eslint cache +.eslintcache + +# Optional REPL history +.node_repl_history + +# Output of 'npm pack' +*.tgz + +# Yarn Integrity file +.yarn-integrity + +# dotenv environment variables file +.env + +# next.js build output +.next + +# build directory +dist/ \ No newline at end of file diff --git a/README.md b/README.md index 4c7f4a8..e776539 100644 --- a/README.md +++ b/README.md @@ -1,77 +1,11 @@ -Assignment 1 - Hello World: Basic Deployment w/ Git, GitHub, Glitch -=== +# a1-bwhetherington -*DUE: Thursday, August 29th by 11:59 AM (before the start of class!)* - -This assignment is a "warm-up" exercise. -You will simply deploy the starting Web site that you will use this term to [Glitch](http://www.glitch.com/). - -Treat this assignment as a chance to get up to speed on Git, GitHub, and Glitch. -If you already know these, great. -However, if you're new to them, spend several hours practicing, experimenting, and reading documentation. -In other words, don't just get your website up and done. You will need skills with these tools throughout the rest of the course. - -Assignment details ---- - -Do the following to complete this assignment: - -1. Fork the starting project code in GitHub. This repo contains: - * the server code, `server.js` - * A starting `index.html` file that you will edit as described below - * A package.json file that helps configure Glitch - * This README -2. Edit `index.html` to show the following information about you: - * your name and class at WPI (e.g. class of 2020) Note: Do not put any contact or personal information that you do not potentially want other people outside of this class to see. - * your major(s) and minor(s) - * previous computer science courses that you have taken at WPI - * your experience with the following technologies and methods (none, some, a lot) - * HTML - * CSS - * Java - * JavaScript - * Ruby - * Python - * unit testing -3. Test your project to make sure that when someone goes to your main page, it displays correctly. You can do this locally by simply running `node server.js` from within the assignment directory. - -4. Modify the README file according to the specification below. -5. Commit and push all your changes to GitHub. -6. Deploy your project to Glitch. You can do this by [importing the repo from GitHub](https://medium.com/glitch/import-code-from-anywhere-83fb60ea4875) -7. Ensure that your project has the proper naming scheme (guide follows) so we can find it. -8. Create and submit a Pull Request to the original repo. - -Naming and URL Scheme ---- - -You must use a consistent naming scheme for all projects in this course. -If we can't find it, we can't grade it. - -By default Glitch often assigns your application a random name. To change it, click on the project dropdown menu in the upper left corner of Glitch. You will then see an additional text field displaying the project name in the resulting menu; click here to edit the name. - -The name scheme should be `a1-yourGitHubUsername`. -The `a1` will need to be updated to `a2`, `a3`, and so on in future projects. - -Resources ---- - -If you need a JavaScript/HTML/CSS refresher, see [Technology Fundamentals by Scott Murray](http://chimera.labs.oreilly.com/books/1230000000345/ch03.html#_html) and/or [JavaScript Codeacademy](https://www.codecademy.com/en/tracks/javascript). - -If you need a Git/GitHub refreseher, see [GitHub Bootcamp](https://help.github.com/categories/bootcamp/), the [GitHub Guides](https://guides.github.com/) (especially the ones on Hello World, and Understanding the GitHub Flow, and Forking Projects), and [CodeSchool's Try Git Course](https://www.codeschool.com/courses/try-git). - -Sample Readme (delete the above when you're ready to submit, and modify the below so with your links and descriptions) ---- - -Charlie Roberts -http://charlieroberts-a1.glitch.me - -This project shows ... +[Benjamin Hetherington](http://a1-bwhetherington.glitch.me) ## Technical Achievements -- **Proved P=NP**: Using a combination of... -- **Solved AI**: ... -### Design Achievements -- **Re-vamped Apple's Design Philosophy**: Shown in `style.css`, the code... +- **Custom Server Script:** I solved the problems with the original server script by writing my own from scratch. In addition, it restricts access to only files in the static directory to ensure that people cannot access other files on the server. +## Design Achievements +- **Custom CSS:** I wrote my own CSS for the website. It is admittedly quite simple, but it is something. diff --git a/index.html b/index.html deleted file mode 100755 index 37ac8c3..0000000 --- a/index.html +++ /dev/null @@ -1,28 +0,0 @@ - - -
-- [Self introduction] -
-- [Major and other information] -
-- [Other things] -
- -- Working experience -
-+ Hello, reader! My name is Benjamin Hetherington, and I am a Computer Science major in the class of 2020 at WPI. +
+ +Below are the CS courses I have taken at WPI, as of writing this page (August 2019):
+| Technology | +Experience | +
| HTML | +A lot | +
| Css | +Some | +
| Java | +A lot | +
| Javascript | +A lot | +
| Ruby | +None | +
| Python | +A lot | +
| Unit Testing | +A lot | +
+ I worked for Amazon Web Services in Seattle the summer of 2019. + Specifically, I worked on improving the internal tools for data + scientists on the Amazon Transcribe team. +
++ I worked for Nuance Communications for three summers: 2016, 2017, + and 2018, in both Cambridge and Burlington. While at Nuance, my time + was spent on improving aspects of their MIX tools, which are used + for creating virtual assistants. My work was primarily focused on UI + development. +
++ I worked at Sense Labs in Cambridge during the summer of 2015. My + work focused on investigating how to identify information about the + usage patterns of devices on a local network. +
+