Merge

CNAME

@@ -0,0 +1 @@
+tannermarino.com

_config.yml

@@ -12,15 +12,15 @@
 
 # theme                  : "minimal-mistakes-jekyll"
 # remote_theme           : "mmistakes/minimal-mistakes"
-minimal_mistakes_skin    : "default" # "air", "aqua", "contrast", "dark", "dirt", "neon", "mint", "plum", "sunrise"
+minimal_mistakes_skin    : "dark" # "air", "aqua", "contrast", "dark", "dirt", "neon", "mint", "plum", "sunrise"
 
 # Site Settings
 locale                   : "en-US"
-title                    : "Site Title"
+title                    : "Tanner Marino"
 title_separator          : "-"
 subtitle                 : # site tagline that appears below site title in masthead
-name                     : "Your Name"
-description              : "An amazing website."
+name                     : "Tanner Marino"
+description              : "The life of Tanner Marino"
 url                      : # the base hostname & protocol for your site e.g. "https://mmistakes.github.io"
 baseurl                  : # the subpath of your site, e.g. "/blog"
 repository               : # GitHub username/repo-name e.g. "mmistakes/minimal-mistakes"
@@ -99,26 +99,29 @@ social:
 
 # Analytics
 analytics:
-  provider               : false # false (default), "google", "google-universal", "custom"
+  provider               : custom # false (default), "google", "google-universal", "custom"
   google:
     tracking_id          :
     anonymize_ip         : # true, false (default)
 
 
 # Site Author
 author:
-  name             : "Your Name"
-  avatar           : # path of avatar image, e.g. "/assets/images/bio-photo.jpg"
-  bio              : "I am an **amazing** person."
-  location         : "Somewhere"
-  email            :
+  name             : "Tanner Marino"
+  avatar           : "/assets/images/profile.jpeg"
+  bio              : "Problem solver."
+  location         : "California"
+  email            : #
   links:
     - label: "Email"
       icon: "fas fa-fw fa-envelope-square"
-      # url: mailto:your.name@email.com
+      url: "mailto:hey@tannermarino.com"
     - label: "Website"
       icon: "fas fa-fw fa-link"
       # url: "https://your-website.com"
+    - label: "LinkedIn"
+      icon: "fab fa-fw fa-linkedin"
+      url: "https://linkedin.com/in/tannermarino"
     - label: "Twitter"
       icon: "fab fa-fw fa-twitter-square"
       # url: "https://twitter.com/"
@@ -127,7 +130,7 @@ author:
       # url: "https://facebook.com/"
     - label: "GitHub"
       icon: "fab fa-fw fa-github"
-      # url: "https://github.com/"
+      url: "https://github.com/tannn"
     - label: "Instagram"
       icon: "fab fa-fw fa-instagram"
       # url: "https://instagram.com/"
@@ -219,10 +222,10 @@ sass:
 
 
 # Outputting
-permalink: /:categories/:title/
+permalink: /:year/:title/
 paginate: 5 # amount of posts to show
 paginate_path: /page:num/
-timezone: # https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
+timezone: America/Chicago
 
 
 # Plugins (previously gems:)
@@ -278,6 +281,8 @@ compress_html:
   ignore:
     envs: development
 
+
+
 
 # Defaults
 defaults:
@@ -290,5 +295,13 @@ defaults:
       author_profile: true
       read_time: true
       comments: # true
-      share: true
+      share: false
       related: true
+  # _pages
+  - scope:
+      path: ""
+      type: pages
+    values:
+      layout: single
+      author_profile: true
+

_data/navigation.yml

@@ -1,12 +1,12 @@
 # main links
 main:
-  - title: "Quick-Start Guide"
-    url: https://mmistakes.github.io/minimal-mistakes/docs/quick-start-guide/
-  # - title: "About"
-  #   url: https://mmistakes.github.io/minimal-mistakes/about/
+#   - title: "Quick-Start Guide"
+#     url: https://mmistakes.github.io/minimal-mistakes/docs/quick-start-guide/
+   - title: "About"
+     url: /about/
   # - title: "Sample Posts"
   #   url: /year-archive/
   # - title: "Sample Collections"
   #   url: /collection-archive/
   # - title: "Sitemap"
-  #   url: /sitemap/
+  #   url: /sitemap/

_includes/analytics-providers/custom.html

@@ -1,3 +1,3 @@
 <!-- start custom analytics snippet -->
-
+<!-- Cloudflare Web Analytics --><script defer src='https://static.cloudflareinsights.com/beacon.min.js' data-cf-beacon='{"token": "43792c0c8225470c85adc8a6d656b295"}'></script><!-- End Cloudflare Web Analytics -->
 <!-- end custom analytics snippet -->

_includes/archive-single.html

@@ -31,7 +31,7 @@ <h2 class="archive__item-title" itemprop="headline">
       {% endif %}
     </h2>
     {% if post.read_time %}
-      <p class="page__meta"><i class="far fa-clock" aria-hidden="true"></i> {% include read-time.html %}</p>
+      <p class="page__meta">{{ post.date | date: "%B %d, %Y" }} | <i class="far fa-clock" aria-hidden="true"></i> {% include read-time.html %}</p>
     {% endif %}
     {% if post.excerpt %}<p class="archive__item-excerpt" itemprop="description">{{ post.excerpt | markdownify | strip_html | truncate: 160 }}</p>{% endif %}
   </article>

_pages/404.md

@@ -0,0 +1,6 @@
+---
+title: That's a 404
+permalink: /404.html
+---
+
+## You were just exploring, right? Refer to the navbar to get back on track.

_pages/about.md

@@ -0,0 +1,10 @@
+---
+permalink: /about/
+title: About
+---
+
+## Hey there.
+
+I'm Tanner. I'm a Software Engineer at PlayStation, working in San Diego. I enjoy learning new skills to solve technical challenges. Previously I worked as a Software Engineer at Union Pacific. I've also been the Assistant Director for [IfThen](https://www.ifthentech.com/) and co-organizer for [EBCT 2019](https://ebct2019.com/) Conference. 
+
+I graduated from the University of Nebraska-Lincoln in May 2019 with a Bachelor of Science in Computer Science. While studying, I was the Founding Director for [CornHacks](https://cornhacks.com/) and the President of the [CSE Advisory Board](https://unl-csesab.com/). 

_posts/2018-12-10-Weaponizing-Technology-Microsoft-Leads-Silicon-Valley-Down-Grim-Path.md

@@ -0,0 +1,13 @@
+---
+title: "Weaponizing Technology: Microsoft Leads Silicon Valley Down a Grim Path"
+categories: [programming oversights, weaponizing technology, labor]
+tags: [war, Microsoft, augmented reality, AI]
+---
+
+Joshua Brustein, in his [article](https://www.bloomberg.com/news/articles/2018-11-28/microsoft-wins-480-million-army-battlefield-contract) “Microsoft Wins $480 Million Army Battlefield Contract,” discusses the technology Microsoft will be supplying to the United States Army. The contract includes 100,000 HoloLens augmented reality headsets to “increase lethality by enhancing the ability to detect, decide and engage before the enemy.” This development is particularly troubling for what it could mean for the future of Silicon Valley. This step not only illustrates Microsoft leading the technology sector into the military-industrial complex, but also Microsoft’s disregard for employee’s choice in the work they do. Brustein writes about “earlier this year, hundreds of Microsoft workers signed a petition criticizing a contract with U.S. Immigration and Customs Enforcement.” Despite worker objections, Microsoft is [continuing](https://www.nytimes.com/2018/04/04/technology/google-letter-ceo-pentagon-project.html) to work with the government. Technology workers have demonstrated they do not want to build products used for waging war. Earlier this year, about 4,000 Google employees signed a petition demanding “a clear policy stating that neither Google nor its contractors will ever build warfare technology”. 
+
+The technology industry is responsible for creating many of the tools we use today. Yet, these workers are against creating tools of mass destruction. The line drawn here is simple: these engineers, scientists, and designers want to build a better world. They have built instant messaging, wireless video calling, and portable, high quality cameras that can withstand daily uses and drops. Developing technologies designed to do harm is more than they signed up for. While discussing the ethical considerations of war is beyond the scope of this article, employees deserve to have a say in what they are building. 
+
+The other issue at hand with this development is what it could lead to. In Burstein’s article, Microsoft’s President and Chief Legal Officer, Brad Smith, said "Artificial intelligence, augmented reality and other technologies are raising new and profoundly important issues, including the ability of weapons to act autonomously. As we have discussed these issues with governments, we’ve appreciated that no military in the world wants to wake up to discover that machines have started a war. But we can’t expect these new developments to be addressed wisely if the people in the tech sector who know the most about technology withdraw from the conversation.” Unfortunately, Smith’s last sentence is incorrect. It is possible to have a conversation about how society wants to use these advanced technologies without creating them first. Essentially, it appears Smith is saying “Create weapons now, ask questions later.” This is similar to Silicon Valley’s “Move Fast and Break Things” mantra, which Facebook is seeing the fallout for now. This time, we should learn from their mistakes and be considerate of the implications of the technology we create.
+
+The ultimate issue with the contract lies in the technology itself. It is easy to see what could go wrong with augmented reality powered by artificial intelligence: the AI could mistakenly categorize an unarmed civilian as hostile, the augmented reality device could malfunction and cause a soldier to make the wrong lethal decision, the facial recognition could be incorrect, and the list goes on. There’s also the issue of the technology falling into the hand of an oppressive regime, or the devices being hacked while soldiers are in the field. Fortunately, there is still time to have a conversation about these technologies before they are created and used. There is limited time to make a change, but change is still possible and necessary to create a better world.

_posts/2018-12-3-Problematic-AI-Police-Body-Cam-Videos.md

@@ -0,0 +1,8 @@
+---
+title: Problematic Uses of AI in Interpreting Police Body-Cam Videos
+categories: [software bias, programming oversights]
+tags: [AI, police]
+---
+In their [article](https://spectrum.ieee.org/computing/software/the-trouble-with-trusting-ai-to-interpret-police-bodycam-video) “The Trouble With Trusting AI to Interpret Police Body-Cam Video”, Dan Greene and Genevieve Patterson detail how a company, Axon, is using AI to interpret police body-cam video. When considering the usage of artificial intelligence in real-world applications, it is important to consider how this tool will be trained. Not just any data can be fed into the AI: the automated image-classification system can only learn from the data it is given. If there is incorrect or biased data, the result is an AI that will be incorrect and have a bias. If the dataset is incomplete, more problems can arise because there will be situations the AI hasn’t learned yet. All of this is further exacerbated by the mere fact that any AI system is error prone because it cannot be 100% accurate in all instances. The authors note that even if police know of these possible errors, “they might suffer from ‘automation bias,’ a tendency for people to accept a computer’s judgments over their own because of the perceived objectivity of machines.” Unfortunately, machines cannot be objective: they are created and maintained by humans, who have unconscious biases. In academia and research, AI experts deal with these problems by making their work open to the public, so it can be scrutinized by other experts and improved upon. Unfortunately, Axon and other companies have no obligation to do that. These kind of closed AI systems can further “rapidly degenerate” because mistakes that are not corrected can be used to train the system, further amplifying biases and creating unreliable results. 
+
+Essentially, it appears the body-cameras police wear are a black box: the camera provides input, and certain events may be flagged that can result in police action. Since this technology is proprietary, it causes issues of accountability and transparency. It is impossible to determine if the AI is making correct suggestions to police, or if police are taking actions guided by a malfunctioning AI. There are other implications of using AI-powered body-cams as well. Axon is actively developing facial recognition for the body-cams. This means in the not-so-distant future, these body-cams could identify people in public, then record the time and location they were spotted. The government would have access to a database with information on where and when they can find individuals of interest. On the other hand, when the facial recognition makes a mistake, it could lead police to arresting the wrong individual. If the technology remains proprietary and the police do not publish detailed records of how the technology impacts their decisions, the public would be faced against a surveillance system that lies outside of their control. Except, the government would not be in control of this system: the technology is Axon’s. Axon’s technology could lead to the arrests of innocent individuals, or worse. Axon could further increase their profits by selling information about people from their database to advertisers. In the event the database is leaked or hacked, people’s location information would be exposed. This information cannot be changed like a password or credit card; location information contains human behaviors and habits.