Seo improvements

.gitignore

@@ -2,6 +2,7 @@ _site
 .DS_Store
 .jekyll
 .jekyll-metadata
+.jekyll-cache
 .bundle
 .sass-cache
 Gemfile

CNAME

@@ -1 +1 @@
-
+www.nickross.site

Dockerfile

@@ -0,0 +1,18 @@
+# Create a Jekyll container from a Ruby Alpine image
+
+# At a minimum, use Ruby 2.5 or later
+FROM ruby:3.0-bullseye
+
+# Add Jekyll dependencies to Alpine
+RUN apt update
+
+WORKDIR /site
+
+# Update the Ruby bundler and install Jekyll
+
+#RUN gem install bundler:2.4.19 
+RUN gem install jekyll:4.3.2 jekyll-feed:0.17.0 jekyll-sitemap:1.4.0
+
+EXPOSE 4000
+
+CMD ["jekyll", "serve", "--livereload", "--host", "0.0.0.0"]

README.md

@@ -1,120 +1,46 @@
-> March, 2016: If you're on an old version of Jekyll Now and run into a) build warnings or b) syntax highlighting issues caused by [Jekyll 3 and GitHub Pages updates](https://github.com/blog/2100-github-pages-now-faster-and-simpler-with-jekyll-3-0), just :sparkles:[update your _config.yml](https://github.com/barryclark/jekyll-now/pull/445/files):sparkles: and you'll be set!
+# Notes on this repo
 
-# Jekyll Now
+### Source
 
-**Jekyll** is a static site generator that's perfect for GitHub hosted blogs ([Jekyll Repository](https://github.com/jekyll/jekyll))
+This was forked from another repo, so keep that in mind.
 
-**Jekyll Now** makes it easier to create your Jekyll blog, by eliminating a lot of the up front setup.
+### Installing & Running
 
-- You don't need to touch the command line
-- You don't need to install/configure ruby, rvm/rbenv, ruby gems :relaxed:
-- You don't need to install runtime dependencies like markdown processors, Pygments, etc
-- If you're on Windows, this will make setting up Jekyll a lot easier
-- It's easy to try out, you can just delete your forked repository if you don't like it
+There is a dockerfile in the repo. A few notes:
 
-In a few minutes you'll be set up with a minimal, responsive blog like the one below giving you more time to spend on writing epic blog posts!
+1. You can just use `build_and_run_server.sh` to run everything. Or...
 
-![Jekyll Now Theme Screenshot](/images/jekyll-now-theme-screenshot.jpg "Jekyll Now Theme Screenshot")
+1. First build the image
+```
+docker build . -t jekyll
+```
 
-## Quick Start
+1. Run the container. The first command does it interactively the second does it via jekyll with an automatic reload
+```
+docker run -it -p 4000:4000 -v ${PWD}:/site jekyll /bin/bash
+```
+```
+docker run -p 4000:4000 -v ${PWD}:/site jekyll 
+```
 
-### Step 1) Fork Jekyll Now to your User Repository
+1. Remember that all pushes to main will end up on github.io and hence `www.nickross.site`
 
-Fork this repo, then rename the repository to yourgithubusername.github.io.
 
-Your Jekyll blog will often be viewable immediately at <https://yourgithubusername.github.io> (if it's not, you can often force it to build by completing step 2)
+### How to update things
 
-![Step 1](/images/step1.gif "Step 1")
+1. Resume should be updated occassionaly -- make sure to remove address
 
-### Step 2) Customize and view your site
+### Some random ruby notes
 
-Enter your site name, description, avatar and many other options by editing the _config.yml file. You can easily turn on Google Analytics tracking, Disqus commenting and social icons here too.
+* Jekyll is the static web site creator
+* `bundle` is something like `pip`, but it allows for local/global versions, so kinda like `pyenv`/`npm`. _This is NOT being used here._
+* There are only a few `gems` being installed in order to run this, all of them are installed via the `dockerfile` which is probably not good practice but works for this purpose.
 
-Making a change to _config.yml (or any file in your repository) will force GitHub Pages to rebuild your site with jekyll. Your rebuilt site will be viewable a few seconds later at <https://yourgithubusername.github.io> - if not, give it ten minutes as GitHub suggests and it'll appear soon
+### How to generate a new section
 
-> There are 3 different ways that you can make changes to your blog's files:
+* Add it to the `_config.yml` under collections
+* Create a new directory with the underscore
+* Create a new top level `md` file which accesses it
+* Add a layout file to (`_layout`) and make sure the layout matches that of the new section type
+* Add it to `layouts/default.html` if you want it in the bar
 
-> 1. Edit files within your new username.github.io repository in the browser at GitHub.com (shown below).
-> 2. Use a third party GitHub content editor, like [Prose by Development Seed](http://prose.io). It's optimized for use with Jekyll making markdown editing, writing drafts, and uploading images really easy.
-> 3. Clone down your repository and make updates locally, then push them to your GitHub repository.
-
-![_config.yml](/images/config.png "_config.yml")
-
-### Step 3) Publish your first blog post
-
-Edit `/_posts/2014-3-3-Hello-World.md` to publish your first blog post. This [Markdown Cheatsheet](http://www.jekyllnow.com/Markdown-Style-Guide/) might come in handy.
-
-![First Post](/images/first-post.png "First Post")
-
-> You can add additional posts in the browser on GitHub.com too! Just hit the + icon in `/_posts/` to create new content. Just make sure to include the [front-matter](http://jekyllrb.com/docs/frontmatter/) block at the top of each new blog post and make sure the post's filename is in this format: year-month-day-title.md
-
-## Local Development
-
-1. Install Jekyll and plug-ins in one fell swoop. `gem install github-pages` This mirrors the plug-ins used by GitHub Pages on your local machine including Jekyll, Sass, etc.
-2. Clone down your fork `git clone https://github.com/yourusername/yourusername.github.io.git`
-3. Serve the site and watch for markup/sass changes `jekyll serve`
-4. View your website at http://127.0.0.1:4000/
-5. Commit any changes and push everything to the master branch of your GitHub user repository. GitHub Pages will then rebuild and serve your website.
-
-## Moar!
-
-I've created a more detailed walkthrough, [**Build A Blog With Jekyll And GitHub Pages**](http://www.smashingmagazine.com/2014/08/01/build-blog-jekyll-github-pages/) over at the Smashing Magazine website. Check it out if you'd like a more detailed walkthrough and some background on Jekyll. :metal:
-
-It covers:
-
-- A more detailed walkthrough of setting up your Jekyll blog
-- Common issues that you might encounter while using Jekyll
-- Importing from Wordpress, using your own domain name, and blogging in your favorite editor
-- Theming in Jekyll, with Liquid templating examples
-- A quick look at Jekyll 2.0’s new features, including Sass/Coffeescript support and Collections
-
-## Jekyll Now Features
-
-✓ Command-line free _fork-first workflow_, using GitHub.com to create, customize and post to your blog  
-✓ Fully responsive and mobile optimized base theme (**[Theme Demo](http://jekyllnow.com)**)  
-✓ Sass/Coffeescript support using Jekyll 2.0  
-✓ Free hosting on your GitHub Pages user site  
-✓ Markdown blogging  
-✓ Syntax highlighting  
-✓ Disqus commenting  
-✓ Google Analytics integration  
-✓ SVG social icons for your footer  
-✓ 3 http requests, including your avatar  
-
-✘ No installing dependencies
-✘ No need to set up local development  
-✘ No configuring plugins  
-✘ No need to spend time on theming  
-✘ More time to code other things ... wait ✓!  
-
-## Questions?
-
-[Open an Issue](https://github.com/barryclark/jekyll-now/issues/new) and let's chat!
-
-## Other forkable themes
-
-You can use the [Quick Start](https://github.com/barryclark/jekyll-now#quick-start) workflow with other themes that are set up to be forked too! Here are some of my favorites:
-
-- [Hyde](https://github.com/poole/hyde) by MDO
-- [Lanyon](https://github.com/poole/lanyon) by MDO
-- [mojombo.github.io](https://github.com/mojombo/mojombo.github.io) by Tom Preston-Werner
-- [Left](https://github.com/holman/left) by Zach Holman
-- [Minimal Mistakes](https://github.com/mmistakes/minimal-mistakes) by Michael Rose
-- [Skinny Bones](https://github.com/mmistakes/skinny-bones-jekyll) by Michael Rose
-
-## Credits
-
-- [Jekyll](https://github.com/jekyll/jekyll) - Thanks to its creators, contributors and maintainers.
-- [SVG icons](https://github.com/neilorangepeel/Free-Social-Icons) - Thanks, Neil Orange Peel. They're beautiful.
-- [Solarized Light Pygments](https://gist.github.com/edwardhotchkiss/2005058) - Thanks, Edward.
-- [Joel Glovier](http://joelglovier.com/writing/) - Great Jekyll articles. I used Joel's feed.xml in this repository.
-- [David Furnes](https://github.com/dfurnes), [Jon Uy](https://github.com/jonuy), [Luke Patton](https://github.com/lkpttn) - Thanks for the design/code reviews.
-- [Bart Kiers](https://github.com/bkiers), [Florian Simon](https://github.com/vermluh), [Henry Stanley](https://github.com/henryaj), [Hun Jae Lee](https://github.com/hunjaelee), [Javier Cejudo](https://github.com/javiercejudo), [Peter Etelej](https://github.com/etelej), [Ben Abbott](https://github.com/jaminscript), [Ray Nicholus](https://github.com/rnicholus), [Erin Grand](https://github.com/eringrand), [Léo Colombaro](https://github.com/LeoColomb), [Dean Attali](https://github.com/daattali), [Clayton Errington](https://github.com/cjerrington), [Colton Fitzgerald](https://github.com/coltonfitzgerald), [Trace Mayer](https://github.com/sunnankar) - Thanks for your [fantastic contributions](https://github.com/barryclark/jekyll-now/commits/master) to the project!
-
-## Contributing
-
-Issues and Pull Requests are greatly appreciated. If you've never contributed to an open source project before I'm more than happy to walk you through how to create a pull request.
-
-You can start by [opening an issue](https://github.com/barryclark/jekyll-now/issues/new) describing the problem that you're looking to resolve and we'll go from there.
-
-I want to keep Jekyll Now as minimal as possible. Every line of code should be one that's useful to 90% of the people using it. Please bear that in mind when submitting feature requests. If it's not something that most people will use, it probably won't get merged. :guardsman:

_career/2020_03_31_Covid.md

@@ -0,0 +1,49 @@
+---
+layout: careers 
+title: Data Science, Jobs and COVID
+date: March 31, 2020 
+mathjax: true
+---
+
+Alumni of [USF's Masters of Data Science program](https://www.usfca.edu/arts-sciences/graduate-programs/data-science) began reaching out with job concerns right around the end of March. While many (luckily) were unaffected, a number of students lost jobs or were told that there jobs were in jeopardy.
+
+The following email is advice that I sent to them at this time. I think that has some (generally) good advice for data scientists when faced with economic uncertainity. I did some light editing from my original email, but the content remains the same. 
+
+
+A couple of things in these crazy times:
+
+* First off, be safe!
+* A number of alumni have reached out either b/c they recently were let go or because they are worried as they may soon be.
+* If you are hiring, please be active -- let other alumni know! I'm also happy to share any jobs.
+
+
+I also wanted to say a few thoughts that I've been sharing over the last few weeks that are especially pertinent now. Note that all of the below is IMO, take it with a grain of salt, its my biased perspective and based on people I hang around.. I mean "zoom" with. ugh.
+
+Even before covid/corona many companies had started shifting their hiring away from the super-cities (SF / Seattle / Los Angles). This was primarily due to the cost of running operations in these locations. We have already seen companies take a few different approaches to this, but there was already a shift occuring before the virus.
+
+Some companies had started offering incentives for people to relocate outside of SF and a few companies we know had stopped backfilling positions in the bay area. If someone in their SF office quit, they would post that job posting only in their other locations.
+
+The virus has sped this up.
+
+Companies are still hiring currently, but they are being careful about it. Already some current students are getting interviews, but the number is (unsurprisingly) a lot less than previous years.
+
+The trend in DS has become much more technical over the last few years and interviewing is reflecting that. If you haven't opened leetcode, hit up your SQL, etc. then when applying for IC positions you'll be at a disadvantage. Technologies like Docker, git, spark are all the rage and having experience (and maybe a git repo or two using them as a side project) isn't going to hurt.
+
+So, some advice, if you think you may be interviewing soon:
+
+* Update your docs (resume, cover letter, linkedin, git repo). Be ready now with them.
+* Refresh your memory, invest in some more tech skills. Make sure you have your skills up to date with whatever job you are applying for.
+* Be prepared for doing all of your interviews via video conference. Do you have a good set up at home? Internet? Microphone / headphones / background?
+
+And, when you look for jobs, three important things:
+
+1. Consider expanding your search outside of the bay area / seattle / los angeles / super-city. I expect a lot of the hiring that occurs over the next year to be outside these locations and in historically underappreciated markets.
+1. Consider expanding your search horizontally. If you had a DS role that was really technical, maybe put in some time and start applying for more software development roles. If you had a data scientist job, would you be willing to apply to be a data analyst? I know that this suboptimal, but when things get tight, 1 job > 0 jobs.
+1. Consider what your domain expertise is (especially if you have been working for a few years). When things get tight, most companies default to hiring people with known expertise. If you have some of that, make sure to show it on your resume / cover letter.
+
+One thing to keep in mind during this is that it is a _major_ event: you aren't alone. This means that lots of other people are in the same shoes and information is a bit more forthcoming. 
+
+For example, [layoffs.fyi](http://layoffs.fyi), has been doing a good job or keeping up to date with companies that are laying people off and providing links to lists of companies that are still hiring (click on layoff tracker -> list of companies still hiring).  If you find yourself unemployed, check out their site as the lists are constantly being updated.
+
+One of their links is to this website ([candor.co](https://candor.co/hiring-freezes/)) which contains information on both companies which are hiring and which are not. The data is crowdsourced, for better and worse, meaning that you should take it with a grain of salt. 
+

_career/2020_04_03_OPT.md

@@ -0,0 +1,10 @@
+---
+layout: careers 
+title: A Data Driven Apporoach to Filing out your OPT 
+date: April 4th, 2020 
+mathjax: true
+---
+
+[Geoffrey Hung](https://www.linkedin.com/in/geoffreyhung/) and I wrote an article, published on medium about how best to fill out your OPT form. This article is primarily aimed at graduate students on F1 visas who are filling out I-765 forms. The article includes estimates of when forms may be processed by USICS based on historical data.
+
+The article can be found [here](https://medium.com/@geoffreyhung/how-to-fill-opt-starting-date-this-year-data-approach-83b3198b2419)