Skip to content

Instantly share code, notes, and snippets.

View NAlexPear's full-sized avatar

Alex Pearson NAlexPear

View GitHub Profile
@NAlexPear
NAlexPear / .xinitrc
Created January 4, 2018 04:02
.xinitrc for X startup processes
#!/bin/bash
xrandr --output DP-0 --left-of DP-2 --mode 1920x1080 --rate 144.00
xrandr --output DP-2 --mode 1920x1080 --rate 144.00
feh --bg-scale ~/Pictures/forest-left.jpg --bg-scale ~/Pictures/forest-right.jpg
compton -b
exec i3
@NAlexPear
NAlexPear / kitty.conf
Created January 4, 2018 04:00
Kitty terminal configuration
font_family Fira Code
adjust_line_height 120%
background #1d1f21
background_opacity 0.7
window_padding_width 5
color0 #282c34
color1 #cc6666
@NAlexPear
NAlexPear / .inputrc
Created September 8, 2016 17:47
Terminal config file that includes expanded TAB-completion for Mac users.
set completion-ignore-case on
set show-all-if-ambiguous on
TAB: menu-complete
@NAlexPear
NAlexPear / greeting.md
Created September 8, 2016 01:21
A website greeting!

Welcome to Alex's Website!

Alex's face

I like turtles.


Contact Me:

@NAlexPear
NAlexPear / .bashrc
Last active January 26, 2017 23:42
My standard .bashrc for Xubuntu environments
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples
# If not running interactively, don't do anything
case $- in
*i*) ;;
*) return;;
esac
@NAlexPear
NAlexPear / hackathon_instructions.md
Last active December 10, 2015 19:31
Instructor walk-through of how to Hack-A-Thon with Savvy Coders.

#How to Hack-A-Thon ###The Savvy Coders Way


The Halfway Hack-A-Thon and Web Store Hack-A-Thon are both end-of-week, collaborative projects that give students an opportunity to design, plan, and execute projects in a team environment, much like they would see building any other type of product. The goal of each Hack-A-Thon is to foster the following skills through the product development experience:

  1. Understanding of the managed repository/GitHub workflow
  2. Collaboration and compromise between teammates, available tech, and project managers (you!)
  3. Product design from the ground up through user stories and feature sets.

Web Store Hackathon

Get excited, people! Today is the day we finally MONETIZE! We will build either an e-commerce store for our community site or a new hot startup to compete with Amazon.com

Please use the GitHub workflow to initialize a repository and save your progress after each step:

$ git add .
$ git commit -m "add music pages"
$ git push origin master

Halfway Hackathon

Congratulations! Today we are at the halfway point in our class. Let's celebrate with a hackathon! A hackathon is a great opportunity to work on a larger, real-world project, while reviewing and solidifying the core concepts that we've covered in the first half of the course.

Step 1: Make a Plan

  1. Take a few minutes to brainstorm some project ideas. This could be related to your community site, a stand-alone project, or just a crazy mash-up site to help you practice different coding concepts
  2. Review the Step 3: Coding section below to consider the different concepts that we hope to practice during this project.
  3. In your group, hold a standup meeting to present your plan of what you'd like to accomplish, and potential stumbling blocks.
  4. If someone mentions being concerned about a concept that you feel solid on, offer to be a resource for them if they have questions.

Week1:

  1. Markup Languages = ALEX
  2. Styling Web Pages = ALEX
  3. Larger Web Documents = ALEX
  4. Forms & Positioning = JUSTIN
  5. CSS Frameworks = JESSICA

Week2:

@NAlexPear
NAlexPear / WebDesignAgreement_AlexPearson.md
Last active April 9, 2019 19:02 — forked from malarkey/Contract Killer 3.md
The latest version of my ‘killer contract’ for web designers and developers

Between Alex Pearson, an independent Web Developer and you, [customer name]

Summary:

I'll always do my best to fulfil your needs and meet your expectations, but it’s important to have things written down so that we both know what’s what, who should do what and when, and what will happen if something goes wrong. In this contract, you won’t find any complicated legal terms or long passages of unreadable text. We’ve no desire to trick you into signing something that you might later regret. What we do want is what’s best for both parties, now and in the future.

So in short;

You ([customer name]), located at [customer address] are hiring Alex Pearson, reachable at 4910 West Pine Blvd #605, St. Louis MO, to [design and develop a web site] for the estimated total price of [total] as outlined in our previous correspondence. The full list of project specs and requirements are listed later in this contract.