text:
**AwesomeSchedule for Asia Pacific University (Backend)**
----
  This is the documentation for the AwesomeSchedule Backend API. This returns the weekly schedule of a specific intake in a JSON format. I've decided to open source this for noobs like me.

* **URL**

  https://awesome-schedule.herokuapp.com/api/

* **Method:**

  `GET`

*  **How to query**

   - To obtain the schedule of the week for a specific intake

     `https://awesome-schedule.herokuapp.com/api/schedules/DATE_OF_MOMDAY_OF_WEEK/INTAKE_CODE`

   - To obtain the list of intakes available

     `https://awesome-schedule.herokuapp.com/api/intakes/list`

* **Success Response:**

  *Schedule of the week for a specific intake*

  * **Code:** 200

    **Content:**
    ```
    [{
        "DATE": "DAY DD-MM-YYYY",
        "INTAKE_CODE": "Your Intake Code Here",
        "TIME": "Time Class Starts - Time Class Ends", // Time is in 24 hour format eg. 08:30
        "CAMPUS": "NEW CAMPUS or TPM",
        "ROOM": "B-05-08",
        "MODULE_CODE": "BM012-4-0-EAP-T-2",
        "LECTURER": "AUDREY LINDA FERNANDO"
    }]
    ```

  *List of intakes*

   * **Code:** 200

     **Content:**
     ```
     [
     "AFCF1702AS",
     "AFCF1702ICT",
     "AFCF1705AS",
     "AFCF1705ICT",
     "AFCF1709AS",
     "AFCF1709ICT",
     "AFCF1711AS",
     "AFCF1711ICT",
     "AFCF1801AS",
     "AFCF1801ICT",
     "APT1F1709BIT",
     "APT1F1709CYB",
     "APT1F1709FRC",
     ...
     ]
     ```
* **Error Response:**

  Most Common Errors:

  *Invalid Date*
  * **Code:** 404

    **Content:** `{ error : "Date not in database" }`

  OR

  *Invalid Intake Code*
  * **Code:** 404

    **Content:** `{ error : "Intake not found in database" }`

* **Sample Call:**

  Sample Request:

  `https://awesome-schedule.herokuapp.com/api/schedules/2018-04-30/UCFF1804CT`

  Sample Response:
     ```
    [{
        "DATE": "MON 30-04-2018",
        "INTAKE_CODE": "UCFF1804CT",
        "TIME": "08:30 - 10:30",
        "CAMPUS": "NEW CAMPUS",
        "ROOM": "B-05-08",
        "MODULE_CODE": "BM012-4-0-EAP-T-2",
        "LECTURER": "AUDREY LINDA FERNANDO"
    },
    {
        "DATE": "MON 30-04-2018",
        "INTAKE_CODE": "UCFF1804CT",
        "TIME": "10:35 - 12:35",
        "CAMPUS": "NEW CAMPUS",
        "ROOM": "B-04-10",
        "MODULE_CODE": "BM012-4-0-EAP-T-3",
        "LECTURER": "AUDREY LINDA FERNANDO"
    },
    {
        "DATE": "WED 02-05-2018",
        "INTAKE_CODE": "UCFF1804CT",
        "TIME": "16:00 - 18:00",
        "CAMPUS": "NEW CAMPUS",
        "ROOM": "Tech Lab 4-03",
        "MODULE_CODE": "CT004-4-0-EWA-LAB-2",
        "LECTURER": "MARY DIANA STEPHEN PAULRAJ"
    },
    {
        "DATE": "THU 03-05-2018",
        "INTAKE_CODE": "UCFF1804CT",
        "TIME": "08:30 - 10:30",
        "CAMPUS": "NEW CAMPUS",
        "ROOM": "B-04-10",
        "MODULE_CODE": "BM002-4-0-COS-T-1",
        "LECTURER": "DR. SARVINDER KAUR SANDHU"
    },
    ...
    ]
    ```

* **Notes:**

  If you believe there can be improvements, feel free to submit a pull request.

  Do not hesitate to email <a<EMAIL_ADDRESS>  I'll ignore your emails if you send any questions about this project to my other emails.

repository: El-Zwali/AwesomeScheduleBackend

repo_name: El-Zwali/AwesomeScheduleBackend


text:
# Galaxy Quest scoring system

## Demo

This prototype requires Python 3 with the `skimage` package (and `matplotlib`)
installed. Type the following to launch the demo:

```
git clone https://github.com/PillarsOfCreationTeam/scoring.git
cd scoring
python3 -m http.server --cgi 8000
```

Then, the demo will be available at `http://localhost:8000`.

## Description

This is a scoring system prototype for the Galaxy Quest game (see main repo).
In this game, users will help NASA to identify galaxy boundaries and nebula
axes, i.e., tasks that may be difficult for AIs, are quite *human readable*.

The scoring system is based on the *wisdom of the crowd*. For each Hubble image,
the backend stores a mask that is a moving average of the individual draws. The
game rewards users that are able to match their draws with the masks, thus
earning *Hubble time* to continue the game exploration.

For example, this is the status of the mask for the
[NGC 5972](http://hubblesite.org/image/3531/gallery) galaxy after a test with
52 participants:

![Galaxy with mask](/../master/examples/galaxy-mask.jpg?raw=true)

In a real implementation, there could be a tier-based, or reputation-based,
weighting system in which best performing players would have more influence on
the mask of new images.

license: MIT

repository: PillarsOfCreationTeam/scoring

branch_name: refs/heads/master

extension: md

license_type: permissive

repo_name: PillarsOfCreationTeam/scoring


text:
---
title: Hackathon agenda
menu_title: Agenda
menu_icon: clock
---

## Day 1

{:.agenda}
Time (BST)    | Activity | Where to go
------------- | -------- | -----------
09:15 – 09:30 | Zoom meeting opens for informal networking | Zoom main room
09:30 – 10:00 | **Hackathon welcome**
Dann Mitchell (Bristol MOAP Chair) | Zoom main room
10:00 – 11:55 | **Breakout groups**
Project team introductions and role/task allocation | Zoom breakout rooms
12:00 – 12:30 | **Yoga with Cara**
Take some time away from your keyboard | Yoga Zoom meeting
12:30 – 13:30 | Lunch break |
13:30 – 16:30 | **Breakout groups**
Continue working on projects | Zoom breakout rooms
16:30 – 17:00 | **End of day tidy-up**
Write up
Commit your changes to GitHub
Tidy Group Workspace | Zoom breakout rooms
17:00 – 17:25 | **Group updates**
90 seconds per group
Zero or one slide 😊
What you hope to achieve during the hackathon | Zoom main room
17:25 – 17:30 | **Close of day** | Zoom main room

## Day 2

{:.agenda}
Time (BST)    | Activity | Where to go
------------- | -------- | -----------
09:15 – 09:30 | Zoom meeting opens for informal networking | Zoom main room
09:30 – 10:00 | **Welcome talk**
Kate Robson-Brown (Jean Golding Institute Director, University of Bristol) | Zoom main room
10:00 – 11:55 | **Breakout groups**
Recap and continue working on projects | Zoom breakout rooms
12:00 – 12:30 | **Yoga with Cara**
Take some time away from your keyboard | Yoga Zoom meeting
12:30 – 13:30 | Lunch break |
13:30 – 14:00 | **Top tips from a Data Specialist**
James Thomas (Jean Golding Institute) | Zoom main room
14:00 – 16:30 | **Breakout groups**
Continue working on projects | Zoom breakout rooms
16:30 – 17:00 | **End of day tidy-up**
Write up
Commit your changes to GitHub
Tidy Group Workspace | Zoom breakout rooms
17:00 – 17:25 | **Group updates**
90 seconds per group
Zero or one slide 😊
How things are going; what problems you have faced | Zoom main room
17:25 – 17:30 | **Close of day** | Zoom main room

## Day 3

{:.agenda}
Time (BST)    | Activity | Where to go
------------- | -------- | -----------
09:15 – 09:30 | Zoom meeting opens for informal networking | Zoom main room
09:30 – 11:55 | **Breakout groups**
Continue working on projects | Zoom breakout rooms
12:00 – 12:30 | **Yoga with Cara**
Take some time away from your keyboard | Yoga Zoom meeting
12:30 – 13:30 | Lunch break |
13:30 – 15:30 | **Breakout groups**
Final steps and ensure code/data/outputs are saved | Zoom breakout rooms
15:30 – 16:00 | **End of day tidy-up**
Write up
Commit your changes to GitHub
Tidy Group Workspace | Zoom breakout rooms
16:00 – 17:00 | **Groups presentations**
3 minutes per group
Show us your notebooks! 😊
What you have achieved; key outputs; next steps | Zoom main room
17:00 – 17:15 | **Close of the Hackathon and next steps** | Zoom main room

branch_name: refs/heads/main


text:
# npm-whoshiring [![Build Status](https://travis-ci.org/hemanth/node-npm-whoshiring.svg?branch=master)](https://travis-ci.org/hemanth/node-npm-whoshiring)

> Shows a table of currently open jobs listed in npm.com.

## Install

```sh
$ npm install --save npm-whoshiring
```

## Usage

##### Node.js

```js
whosHiring(function(err, jobs) {
// Rest of your logic to play with jobs.
});
```

##### CLI

```sh
$ npm install --global npm-whoshiring
```

__GIF FTW:__

![](https://raw.githubusercontent.com/hemanth/node-npm-whoshiring/master/hiring.gif)

## License

MIT © [Hemanth.HM](http://h3manth.com)

repository: hemanth/node-npm-whoshiring

gha_language: JavaScript

repo_name: hemanth/node-npm-whoshiring


text:
# Space Suit Diagnostics

## Features

- [X] 🤩 Page Transitions, component-based (with no-js support)
- [X] 👮♂ 'IntersectionObserver', component-based (with polyfill)
- [X] 🌿 React Context for global UI state, with SSR
- [X] 💅 ['styled-components'](https://www.styled-components.com/) v4
- [X] 💯 Optimized with [Google Lighthouse](https://developers.google.com/web/tools/lighthouse/) (including test)
- [X] 🔥 Code Splitting of CSS and JS (component based)
- [X] 🔪 Inline SVG support
- [X] ⚙ One config file for site-wide settings
- [X] 💙 Most social + meta tags in one component
- [X] 🖼 All favicons generated, only one icon file needed
- [X] 🌐 Offline support
- [X] 📄 Manifest support
- [X] 🗺 Sitemap support
- [X] 📱 Generated media queries for easy use
- [X] 😎 [Prettier](https://prettier.io/) for code style
- [X] 👷♂ [CircleCI](https://circleci.com/) support
- [X] 🐙 Schema JSONLD
- [X] 🔎 ['size-plugin'](https://github.com/GoogleChromeLabs/size-plugin) to keep an eye on your bundle sizes
- [X] 👨🏫 ESLint (based on ['eslint-plugin-react'](./.eslintrc))

Do you have suggestions or feedback? [Open an issue](https://github.com/fabe/gatsby-universal/issues/new)!

## Usage

[![Deploy to Netlify](https://www.netlify.com/img/deploy/button.svg)](https://app.netlify.com/start/deploy?repository=https://github.com/jschmidtnj/spacesuits)

'''bash
# Installation with 'gatsby-cli'
gatsby new my-site https://github.com/jschmidtnj/spacesuits

# Installation with 'git clone'
git clone my-site git@github.com:jschmidtnj/spacesuits.git
cd my-site
yarn install

# To develop
yarn develop

# To build
yarn build

# To test SSR (for Lighthouse etc.)
yarn ssr

# To format JS (precommit)
yarn format

# To generate favicons (included in 'build')
yarn build:favicons
'''

## Configuration

Find the site-wide configuration in 'site-config.js'.

'''js
module.exports = {
  siteTitle: 'Space Suit Diagnostics',
  siteTitleShort: 'SpaceData',
  siteDescription: 'Space Suit Diagnostic Data.',
  siteUrl: 'https://spacesuit.site',
  themeColor: '#000',
  backgroundColor: '#fff',
  pathPrefix: null,
  logo: path.resolve(__dirname, 'src/images/icon.png'),
  social: {
    twitter: 'gatsbyjs',
    fbAppId: '966242223397117',
  },
};
'''

> 🚨 Don't forget to update your 'robots.txt' inside 'static/'!

## Folder structure
'''bash
├── gatsby-browser.js # Specify how Gatsby renders pages in the browser
├── gatsby-config.js # Gatsby config, mostly taken from 'site-config.js'
├── gatsby-node.js # Modify webpack config
├── gatsby-ssr.js # Specify how Gatsby builds pages
├── site-config.js # Global settings for the whole site, used by multiple scripts
├── content # Content & data, in both json and markdown
├── src
│   ├── components
│   │   ├── head # All meta tags etc.
│   │   ├── io # Intersection Observer component, uses render props
│   │   ├── layout # Layout component
│   │   │   ├── layout.css.js # .css.js for component's 'styled-components'
│   │   │   └── layout.js
│   │   └── transition # Page Transition component, used by Gatsby APIs
│   ├── constants # Site-wide constants (breakpoints, colors, etc.)
│   ├── containers # Container components if store is needed
│   ├── helpers
│   │   ├── schemaGenerator.js # Generates JSON-LD schema.org snippets
│   │   └── mediaTemplates.js # Creates media queries for styled-components
│   ├── images # Images needed by the site/theme (not content)
│   ├── pages
│   ├── store # Store and provider of a React.createContext instance
│   └── global.css.js # Global CSS
└── scripts
    ├── lighthouse.test.js # Tests the site specified inside 'site-config.js' with Google Lighthouse (WIP)
    └── favicons.js # Generates favicons and manifest using one png only.
'''

repository: jschmidtnj/SpaceSuits

repo_name: jschmidtnj/SpaceSuits


text:
# ASP.NET Web Forms – Intro

# Table of Contents
- [Introduction to ASP.NET Web Forms](#intro)
- [Web Forms Basic Components](#components)
- [ASP.NET Sumator – Demo](#sumator)
- [ASP.NET Page Execution Model](#execution)
- [Postbacks and VIEWSTATE](#viewstate)
- [ASP.NET Page Directives](#directives)

#  What is ASP.NET Web Forms?
- **ASP.NET Web Forms**
  - Web application development framework
    - Renders HTML content at the server-side
    - Combines C# with HTML for dynamic content
    - Component-based, event-driven model
  - Created by from Microsoft in 2002
  - Powerful, but complicated, very mature
  - Weak control over the output HTML
  - Web Form == composition of nested controls in ASPX page

# ASP.NET Web Forms Benefits
- Separate presentation from code
  - Code behind, unlike PHP (mixed code + HTML)
- Component-based development (like JSF)
  - Event-driven architecture
  - Object-oriented approach
- Code compilation (instead of  interpreter)
- Built-in state management (session, app, …)
- Many others (data binding, validation, master pages, user controls, authentication, etc.)

# ASP.NET Web Forms Architecture

# HTML vs. ASP.NET Web Forms
- Traditional Web pages (static HTML)
  - Consist of static HTML, images, styles, etc.
  - Execute code on the client side (JavaScript)
  - Need lots of AJAX to become dynamic
- ASP.NET Web Forms
  - Execute code on the server and render HTML
  - Extensive use of server-side components
  - Allow easy integration with databases

# ASPX: Separate Visualization from Business Logic
- Old-fashioned Web development mixes HTML and programming code in single file (like PHP)
  - Hard to read, understand and maintain
  - Often leads to spaghetti code
- ASP.NET Web Forms splits the Web pages into two parts:
  - **.aspx** file containing HTML for visualization
  - "**Code behind**" files (**.aspx.cs**) containing the presentation logic for particular page

- Class generated from the **.aspx** file does not derive directly from **Page** class
- Derives from class defined in the "code behind", where it is easy to add methods, event handlers, etc.
- Using "code behind" separates the presentation logic from UI visualization
- System.Web.UI.Page
- TestForm.aspx.cs
- TestForm.aspx

#  Web Forms Basic Components
- **Web Forms**
  - XML-based files describing the Web UI
- **Web Control**
  - The smallest part we can use in our Web application (e.g. text box)
- **"Code behind"**
  - Contains the server-side C# code behind pages
- **Web.config**
  - Contains ASP.NET application configuration

# Web Forms
- An **ASP.NET Web Form** is a programmable Web page (**.aspx** file)
  - Acts as a Web-based user interface (UI) of the ASP.NET Web Forms applications
  - XML-based language, like XHTML
  - Consists of HTML, C# code and controls
  - Executed at the server-side by ASP.NET
  - Rendered to HTML by the ASP.NET runtime
  - Have complex execution model (many steps)

# ASP.NET Web Form – _Example_
- The functionality of the Web form is defined by attributes: **Page**, **Codebehind**, **Inherits**

```cs
<%@ Page Language="C#"
  Codebehind="TestWebForm.aspx.cs"
  Inherits="FirstApp.TestWebForm" %>
<!DOCTYPE html>
<html>
  <head><title>First WebForm</title></head>
    <form ID="FormTest" runat="server" …>
      <asp:Label ID="lbl" runat="server">…</asp:Label>
      <asp:TextBox ID="textCustomerName" runat="server"
        Text="Customer Name: ">…</asp:TextBox>
      <asp:Button ID="btn" runat="server" …></asp:Button>
    </form>
</html>
```

Always put **ID="…"** and **runat="server"** for the ASP.NET controls!

# ASP.NET Web Controls
- ASP.NET **Web controls** are the smallest component part
- Deliver fast and easy component-oriented development process
- HTML abstraction, but has server-side properties and events
  - Rendered as HTML (+ CSS + scripts)

```cs
<asp:Button runat="server" ID="btn"
   Text="Click me!" OnClick="btn_Click" />
```

# Web.config
- The configuration file for ASP.NET application
- Text based XML document
- **Web.config** defines:
  - Connection strings to any DB used by app
  - Security settings and membership settings
  - Whether debugging is allowed

```cs
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <system.web>
  </system.web>
</configuration>
```

Minimal Web.config should look like this

#  Your First ASP.NET Web Forms Application – Sumator
- Steps to create a simple ASP.NET Web application:
  - Start Visual Studio
  - Create “New Web Application”
  - Add two text fields, a button and a label
  - Handle **Button.Click** and implement logic to sum of the values from the text fields
  - Display the results in the label

#  ASP.NET Execution Model
- First call to particular page

- Any other call after the first

# The ASP.NET Controls Tree
- When requested an ASP.NET Web form is parsed by ASP.NET and converted to a tree
  - Also called a **controls tree** (XML tags are turned into a tree of controls)

# ASP.NET Page Lifecycle
- At each request to a Web Form:
  - The form is created (a page instance)
  - The VIEWSTATE is restored (the state of each control, sent from the browser)
  - The page and control events are executed
  - The VIEWSTATE is saved in a hidden field
  - The form is rendered as HTML
  - The form is unloaded (destroyed)
- Important: page instances do not survive the next HTTP request!

# ASP.NET Page Lifecycle Events
- Web forms and controls have lifecycle events:
	1. **PreInit**
	1. **Init**
	1. **Load** (load data from DB)
	1. (control events are executed here, e.g. **Click**)
	1. **PreRender**
	1. **Render**
	1. **Unload**

#  Page Postbacks and VIEWSTATE
- **VIEWSTATE** preserves the state of a Web control into a serialized, encrypted hidden field
- **Postback** in ASP.NET means submitting a Web form to the server (i.e. **HTTP POST** request)
  - Executed when a server-side event is raised
    - E.g. a button is clicked or a checkbox is checked
  - VIEWSTATE preserves the page and controls state
    - Almost all control properties: color, position, width, height, etc.
    - The text in the control is posted with the form

#  ASP.NET Page Directives
- Provide control over many options affecting the compilation and execution of the web form
- Important directives:
  - **@Page** – main directive of the page
  - **@Import** – imports a namespace into the page
  - **@Assembly** – attaches an assembly to the form when it is compiled
  - **@OutputCache** – controls the ability of the forms to use cache
  - **@Register** – registers a user control to be used in a web form

# The @Page Directive
- Defines a form-specific (**.aspx** file) attributes used by the ASP.NET runtime
- Important attributes:
  - **AutoEventWireup** – auto-bind the controls' events to appropriate methods in the code
  - **Culture** – a culture used at page generation
  - **UICulture** – a culture for the data visualization
  - **Language** – code language (C#, VB.NET, …)
  - **Codebehind** – the code-behind file

- Important attributes:
  - **Debug** – whether the page is compiled with debug symbols in it
  - **EnableSessionState** – whether a session is supported
  - **EnableViewState** – whether to use "view state" or not
  - **ErrorPage** – a page to which to redirect in case of unhandled exception

# ASP.NET Web Forms – Intro
- http://academy.telerik.com

# Free Trainings @ Telerik Academy
- "Web Design with HTML 5, CSS 3 and JavaScript" course @ Telerik Academy
    - html5course.telerik.com
  - Telerik Software Academy
    - academy.telerik.com
  - Telerik Academy @ Facebook
    - facebook.com/TelerikAcademy
  - Telerik Software Academy Forums
    - forums.academy.telerik.com

path: /02. ASP.NET-Web-Forms-Intro/README.md


text:
# BusMall User Stories

As a developer, I want to break down the test into many small steps so that I can account for all of the variables within the game

As a developer, I want to analyze each small step of the game to get rid of inconsistencies and make the game as simple as possible.

As a marketer, I want the game to be consistent no matter who the user is so that each time it's ran we are collecting the same data and not worrying about inconsistencies.

As a marketer, I want the results of the test to be displayed in a clear and concise format so that we can easily analyze the data

As a user, I want the test to be easy to work through so that I can focus on the pictures not on how to work the test.


text:
kiji-platforms
==============

This repository contains Kiji "Hadoop platform" definitions. Several artifacts
are published in the org.kiji.platforms groupId; each of these is a Java
project that contains no code; but each contains dependencies on versions of
Hadoop and HBase that are known to work well together.

Kiji supports running on a variety of Hadoop distributions. At runtime, based
on the Hadoop and HBase jars in the `HADOOP_HOME` and `HBASE_HOME`
directories, Kiji will determine what compatibility layer to load in order to
work with different platforms.

Usage
-----

When you compile and test your application, you should do so against the
version of Hadoop that you intend to run. Your project should declare
provided-scope dependencies on KijiSchema, as well as a support platform. For
example, to run on CDH5.1:

    <dependencies>
      <dependency>
        <groupId>org.kiji.schema</groupId>
        <artifactId>kiji-schema</artifactId>
        <version>1.6.0</version>
        <scope>provided</scope>
      </dependency>

      <dependency>
        <groupId>org.kiji.platforms</groupId>
        <artifactId>kiji-cdh5-1-platform</artifactId>
        <version>1.4.0</version>
        <scope>provided</scope>
      </dependency>
    </dependencies>

Available platforms
-------------------

To ensure platform compatibility with Kiji, applications should compile and
deploy against a Hadoop version specified in a Kiji platform definition. The
following platform definitions are provided:

* kiji-cdh5-1-platform (Latest CDH5.1 update)
* kiji-cdh5-0-platform (Latest CDH5.0 update)
* kiji-cdh4-4-platform (Latest CDH4.4 update)
* kiji-cdh4-3-platform (Latest CDH4.3 update)
* kiji-cdh4-2-platform (Latest CDH4.2 update)
* kiji-cdh4-1-platform (Latest CDH4.1 update)

See the `example-application-pom.xml` file for an example.

Test platforms
--------------

Many Kiji components provide test frameworks for writing unit or integration
tests against interactions with Kiji, and Hadoop. To use these test frameworks,
depend on the corresponding `kiji-<version>-test-platfrom` in `test` scope.

Platform compatibility
----------------------

All versions of KijiSchema may not work against all Hadoop platform versions.
The version of KijiPlatforms depended on by the KijiSchema version should contain
only compatible version.

Library dependencies
--------------------

Libraries which rely on KijiSchema or other Kiji dependencies should include a
dependency on the `kiji-compile-platform` in `provided` scope and
`kiji-test-platform` in `test` scope. This will supply the required
dependencies at compile time while allowing downstream applications the
flexibility to specify a different HBase and Hadoop version at runtime. See the
`example-library-pom.xml` file for an example.

Maven usage notes
-----------------

If you depend on such a module, you can use the `mvn -f example-application-pom.xml dependency:tree`
command to visualize the actual dependencies being used:

    [INFO] org.kiji.foo:foo:jar:1.0.0-SNAPSHOT
    [INFO] ...
    [INFO] \- org.kiji.platforms:kiji-cdh4-platform:jar:1.0.0:provided
    [INFO]    +- org.apache.hadoop:hadoop-client:jar:2.0.0-mr1-cdh4.1.2:provided
    [INFO]    |  +- ...
    [INFO]    +- org.apache.hadoop:hadoop-core:jar:2.0.0-mr1-cdh4.1.2:provided
    [INFO]    |  +- ...
    [INFO]    +- org.apache.hadoop:hadoop-minicluster:jar:2.0.0-mr1-cdh4.1.2:provided
    [INFO]    |  +- ...
    [INFO]    \- org.apache.hbase:hbase:jar:0.92.1-cdh4.1.2:provided
    [INFO]       +- ...

repository: kijiproject/kiji-platforms

repo_name: kijiproject/kiji-platforms


text:
# Simple Modular Quiz (Challenge #1)

###### Application Type: Console Application
###### Time: 2 hours
###### Max points: 100
###### Example Count: 1

## Information
Following this challenge you will learn:
- Basic file reading
- How to make a console application
- How to write modular systems

The project must contain the following features:
- An easy way to add multiple questions (using files)
- A way to stop the program by sending a specific String (the string should be "stop" with the quotes)
- A way of letting the user know how many questions they answered (this can be indicated by a small number at the end of the question, something like (5/7)).

**Note:** In order to mark this challenge as completed you shouldn't use any external help sources. If you are stuck, please go to the "Tips" section below.

**Note:** You may also check the example [here](Example).

## Points
If you would like to award yourself a score, here is a table to follow:
| **Requirement**                                                                                | **Points** |
|-------------------------------------------------------------------------------------------------------|------------|
| The system can be stopped using the keyword "stop".                                                   | 15         |
| There is an easy way of adding new questions.                                                         | 25         |
| The program shows the user how many questions they answered and how many they have left.                                                         | 10         |
| You took less than 2 hours to write this program.                                                     | 10         |
| The program doesn't have any errors.                                                                  | 15         |
| You tested the program with the values specified in the "Testing" section and it responded correctly. | 15         |
| You took less than 10 attempts.                                                                       | 10         |

**Note:** The maximum points you can get is **100**. There are some requirements that can deduct points. You can't deduct more points than the requirement is offering. For instance you can only offer a penalty of up to 10 points for taking more than 2 hours.
- For each attempt after 10 you can deduct 5 points.
- For each 15 minutes after 2 hours you can deduct 5 points.
- For each test that failed you can deduct the number of points specified.

## Testing
##### Test 1 (15 points)
- Create a question called "Do you like apples?".
- Create a question called "Do you like oranges?" right after the "Do you like apples?" one.
- Start the program and answer to the apples question, then check if the program asks you the "Do you like oranges?" one.

## Tips
1. You should use the Scanner class to read the data from the console.
2. You should use a special character to divide the questions.

gha_license_id: MIT


text:
---
pageTitle: About
layout: markdown
---

# About Me

## Professional life

Howdy! My name is Dustin. I'm a Design Technologist working on the Design System at [Indeed] where we like to say - We help people get jobs! Before finding design systems, I was a [Drupalist] working on Very Large Websites™ for media brands and universities you've definitely heard of.

Before realizing HTML and CSS could pay the bills, I was an aspiring filmmaker who enjoyed the more technical aspects of audio / video editing and visual effects.

## The other 128 hours of the week

I'm a lifelong cyclist who has recently rediscovered riding on dirt. I've got a [dentist quality mountain bike][yeti] and a [gravel bike][niner] that isn't quite as fancy, but it still feels like I have wings on the downhills.

I also have a pretty stacked [garage gym][fringesport] where my friends and I lift [heavy things][rogue] and put them back down again. Mostly powerlifting with some strongman aspirations and a dash of HIIT on the weekends to work the beach muscles.

I like to tinker with [Arduino adjacent][ada] electronics and [3d printers][prusa]. When public gatherings were more common, I helped run [dorkbot Austin][dorkbot] for several years and had a part in getting [SXSW Create][sxswcreate] off the ground.

## On the road again

After a few years in Boston, I'm back in Austin, eating all of the tacos I can get my hands on. One of these days, I'm going to buy some land in Vermont or New Mexico with my closest friends and enjoy a pastoral lifestyle with high speed internet.

New England has the best sandwiches, but the Southwest has the best tortilla based foods.

[drupalist]: https://drupal.org
[indeed]: https://indeed.com
[yeti]: https://yeticycles.com
[niner]: https://ninerbikes.com
[fringesport]: https://fringesport.com
[rogue]: https://roguefitness.com
[ada]: https://adafruit.com
[prusa]: https://prusa3d.com
[dorkbot]: https://dorkbot.org
[sxswcreate]: https://hackaday.com/2015/03/17/sxsw-create-atx-hackerspace-area/

branch_name: refs/heads/primary

gha_language: Nunjucks


text:
---
date: 2021-09-17T14:40:17.773Z
slug: llnn-unmaker-en
typeName: Review
title: '"Unmaker" By LLNN'
subTitle: Post-Apocalyptic Sounds From Copenhagen
seoTitle: '"Unmaker" By LLNN – Post-Metal Review'
description: "There is an album release coming up on September 24 that you
  shouldn't miss in any case: \"Unmaker\" by LLNN is a textbook example of dark
  and heavy post-metal. If you are enthusiastic about this genre, you should
  definitely check out this monolith."
image: https://storage.googleapis.com/cardamonchai-media/2021-11-20/llnn-jpg-imagine-181818_000000_1024_768/640.webp
copyrigt: LLNN
ogImage: https://storage.googleapis.com/cardamonchai-media/2021-11-20/llnn-fb-png-imagine-282828_454545_1200_628/640.webp
labels:
  - Copenhagen
  - Unmaker
  - Post-Music
  - Pelagic
  - Review
  - Reviews
  - Bands
focusKeyword: LLNN
advertisement: false
affiliate: false
language: en
languageLink: /2021/09/llnn-unmaker/
---

**There is an album release coming up on September 24 that you shouldn't miss in any case: "Unmaker" by LLNN is a textbook example of dark and heavy post-metal. If you are enthusiastic about this genre, you should definitely check out this monolith.**

The first song, "Imperial", is resonant and threatening, complex and energetic. Rigid and heavy basses alternate with droning guitar riffs. It puts you in a certain kind of mood and captivates you from the start.

## "Chaotic times bring dark sounds"

The next song is called "Desecrator". LLNN sound designer Ketil G. Sejersen describes it like this:

> "In chaotic times, chaotic sonic vibrations sprout in the form of pulverising energy, desperation and heaviness. This song is all about that."

![LLNN – "Unmaker"](https://storage.googleapis.com/cardamonchai-media/2021-11-20/llnn1625512125413194-jpg-imagine-080808_2c241d_440_440/640.webp "LLNN – \"Unmaker\"")

That doesn't only sound crass – it is. The second track on the record lacks ear protection in its 4:13. It picks up the listener in this one place where we all are right now: On a wave of confusion and doubt, uncertain what awaits us behind the next corner. At the same time, it is a gutural invitation to dive further into the sound underground of LLNN and explore the darkness and heaviness that awaits us there.

## Claustrophobia and futurism

With the next song, "Obsidian", I have finally landed in the futuristic world of LLNN. The track pictures an intense future that is still ahead of us. I can see the dense, claustrophobic crawlspaces and corrosive scanner lights that the band had in mind when they composed it in my mind's eye.

"Vacuum" then takes it up a notch. With its 2:12, the mystical sounding track is the most compact one on the record. It seems like some riddle to me. A drilling drone spreads out and captures my attention. In terms of sound, "Vakuum" is an absolute masterpiece – I would love to listen to it as a score for a dystopian short movie – delusions of persecution included. I particularly like the shouts here. They suddenly appear, only to disappear into the mist again.

"Scion" begins with dramatic vocals. There is no room for a long intro here. What needs to be said needs to be said. Nevertheless, the song doesn't fall through the cracks. For me, it is the continuation of its predecessor and the perfectly overdriven highlight of the record. I can hear Amenra here, but also [Year Of No Light](/2021/05/year-of-no-light-consolamentum-en/) and influences from the industrial niche.

## "Unmaker" tells many stories

I like how the record develops. I can hardly add anything to the words of singer and guitarist Christian Bonnesen about the next song, "Interloper". LLNN have put his words to music perfectly:

> "It's a song about feeling worthless. Forever doomed to sit with the kids at the dinner table, fed with scraps from banquets of kings."

![LLNN](https://storage.googleapis.com/cardamonchai-media/2021-11-20/llnn-1-jpg-imagine-182828_4c453a_1024_768/640.webp "LLNN")

Each song tells its own story. Altogether, this creates a monumental epos that you definitely should listen to in one piece sometime soon.

## "Division" and "Forger" set the pace

"Division" pushes the tempo and pulls me even closer to the abyss. Damn, how I wish to experience this track live on stage. While I'm writing this, I am picturing the dust kicking up under the feet of the stomping audience.

"Forger" kicks off at full speed, metallic and angry – raw and wonderful. It is followed by the longest song on "Unmaker" with 6:03. It melodically sticks to the storyline and, after a short, almost contemplative opening, immediately ramps up to the usual heaviness, alternating with exciting phases of calm. It is precisely this alternation of solid plateaus and thoughtful moments that makes the track my favourite on the album.

![LLNN](https://storage.googleapis.com/cardamonchai-media/2021-11-20/llnn-2-jpg-imagine-2838c8_6d7adf_1024_768/640.webp "LLNN")

The next song, "Tethers", is an excellent transition – it sets another contrasty landmark. Finally, "Resurrection" provides a dignified epilogue, which seems like the landing after a years-long exploratory flight through the depths of space full of dangerous encounters and adventures.

With their third album, LLNN have done everything right. "Unmaker" fits into the year 2021 perfectly, and it will still bring us a lot of joy in the future.

## LLNN - about the band history

In the past, the band from Copenhagen has already played concerts at Roskilde, Roadburn and [ArcTanGent](/2019/09/arctangent-festival-2019-2/) Festival. Also, among other things, they have been on tour through Europe with Bison. So LLNN is by no means a blank slate in the post-music scene.

After their first album, "Loss", they recorded a split EP with Wovoka. Then, in 2018, they released their second album, "Deads". It was was already more complex than their first LP and paved the way for the upcoming new record "Unmaker", which will be released next week.

The band members report that with "Deads", they further explored the fusion of guitar, bass and synthesizer layers. With their new record, they have clearly perfected this skill.

I like that the tracks on "Unmaker" still don't seem too overloaded or dense at all. Instead, they blast properly, telling stories from a post-apocalyptic world between science fiction, horror and film noir/psycho road movie.

## LLNN – "Desecrator"

<YouTube id="dWW1E6lzNog" />

repository: matthias-reis/carda-gatsby

gha_language: HTML

repo_name: matthias-reis/carda-gatsby


text:
# FA20-CS121-fastai

Harvey Mudd College FA20 CS121 Section 2: Deep Learning Classification
of Art Pieces

## About

This repository contains the fast.ai models and training output that
is used in our [web app](https://github.com/kiphenglim/FA20-CS121).

## Source Data

We trained using data from the
[cs-chan/ArtGAN](https://github.com/cs-chan/ArtGAN) dataset. The
ArtGAN ReadMe links to a site where a large photo dataset can be
downloaded. Within the ArtGAN Github itself, there is are CSV files
for artist, genre, and style which you will also need.

## Usage

Once you have these things on your local computer, you can run our
three cleaning scripts: clean_artist_csv.py, clean_genre_csv.py, and
clean_style_csv.py. Each of these scripts will produce a new CSV where
the entries in the CSV only contain rows that reference photos that
are obtained from the photo download mentioned above. We found some
inconsistencies between the CSV and photo downloads that neccessitated
this extra step.

After this, you can run classify_artist.py, classify_genre.py, and
classify_style.py using fast.ai. Each of these scripts will output a
model, a confusion matrix, and a photo of the top losses. The top
losses and confusion matrix are both saved as images in the local
directory. Additionally, the top losses is saved as a list inside a
console.txt file along with some other useful output for
debugging. These models can then be used to predict the artist, genre,
and style of paintings.

gha_language: Python


text:
teamspeak

Built-from-source container image of TeamSpeak

	docker pull quay.io/ricardbejarano/teamspeak

## Features

* Pulled from official sources during build time
* Built `FROM scratch`, with zero bloat
* Reduced attack surface (no shell, no UNIX tools, no package manager...)
* Runs as unprivileged (non-`root`) user

## Tags

### Docker Hub

Available on Docker Hub as [`docker.io/ricardbejarano/teamspeak`](https://hub.docker.com/r/ricardbejarano/teamspeak):

- [`3.13.7`, `latest` *(Dockerfile)*](Dockerfile)

### RedHat Quay

Available on RedHat Quay as [`quay.io/ricardbejarano/teamspeak`](https://quay.io/repository/ricardbejarano/teamspeak):

- [`3.13.7`, `latest` *(Dockerfile)*](Dockerfile)

## Configuration

### Volumes

- Mount your **database** at `/data/ts3server.sqlitedb`

***Note:** do not mount at `/data`, you will override some runtime dependencies.*

repository: ricardbejarano/teamspeak

repo_name: ricardbejarano/teamspeak


text:
# VNC open

The five compiled files must be here:

- vncconfig.exe
- vncviewer.exe
- winvnc4.exe
- logmessages.dll
- wm_hooks.dll

## First variant

Download and install VNC open from [here](https://archive.realvnc.com/download/open/).
Install the program, find the above files and copy them into the folder
[/path/to/WirelessDisplay/ThirdParty/Windows/VNCopen]

## Second variant

If provice a copy of the above files here:

[https://github.com/lzukw/Third-party-tools](https://github.com/lzukw/Third-party-tools)

Just clone or download the repository and find the files in the folder [VNC4].
Then copy or move them to [/path/to/WirelessDisplay/ThirdParty/Windows/VNCopen].

repository: lzukw/WirelessDisplay

repo_name: lzukw/WirelessDisplay


text:
# Getting Started

[![CircleCI](https://circleci.com/gh/ahmednafies/covid.svg?style=shield)](https://circleci.com/gh/ahmednafies/covid) [![codecov](https://codecov.io/gh/ahmednafies/covid/branch/master/graph/badge.svg)](https://codecov.io/gh/ahmednafies/covid)

Python SDK to get information regarding the novel corona virus provided by Johns Hopkins university

![corona.jpeg](img/corona.jpeg)

Full code on [github](https://github.com/ahmednafies/covid)

## Requirements

    python >= 3.6

## How to install

    pip install covid

## Dependencies

    pydantic
    requests

## How to use

    from covid import Covid

    covid = Covid()
    covid.get_data()

repository: hellosaumil/covid

repo_name: hellosaumil/covid


text:
### Shell Lab
The requirements for this lab were to create a basic shell that can run commands, handle input redirection, and simple piping

### How to run
./shell.py or python3 shell.py will run the shell. ./testShell.sh ./shell.py will run the tests

### Commands
* 'exit' to exit the program
* 'cd' to change directories
* '>' handles output redirection
* '<' handles input redirection
* '|' handles piping


text:
---
layout: post
title: 'Introducing Scabbard: Easily visualize Dagger 2 dependency graphs'
description: An IntelliJ/Gradle plugin to easily visualize and understand Dagger 2 graphs from within IDE.
date: 2019-12-28 09:43 +0800
categories: [Android, Dagger, Library]
image : /assets/images/scabbard-banner.png
---

I am excited to announce [Scabbard](https://arunkumar9t2.github.io/scabbard/), a tool to visualize Dagger 2 dependency graphs. Here's Scabbard in action:

<video width="100%" controls>
  <source src="https://arunkumar9t2.github.io/scabbard/video/scabbard-demo.mp4" type="video/mp4">
  Your browser does not support the video tag.
</video>

Here is an advanced example from [Google's I/O 19](https://github.com/google/iosched) app:

<video width="100%" controls>
  <source src="https://arunkumar9t2.github.io/scabbard/video/iosched_appcomponent.mp4" type="video/mp4">
  Your browser does not support the video tag.
</video>

Apart from ensuring runtime safety, one of the advantages of a compile-time framework for dependency injection is that the entire graph of dependencies can be known at compile time even before binary is generated. This enables features like compilation errors when there are missing bindings which is a very good step towards reducing developer mistakes. But the cost we pay for that is the mental effort of knowing all the bindings, knowing current scope, navigating errors to make dagger happy etc. Very soon we realize there is a visualization problem here and it is evident from many dagger tutorial articles which tries to visualize the dagger structure in their own ways to convey the message. I tried to tackle this problem with Scabbard.

### Download

Please follow [Getting Started](https://arunkumar9t2.github.io/scabbard/) guide on the project website to start generating graphs right away. Hopefully you would have graphs by the time you finish reading this article.

### Features

* **Visualize** entry points, dependency graph, component relationships and scopes in your Dagger setup.

* **Minimal setup** - Scabbard's Gradle plugin prepares your project for graph generation and provides ability to customize graph generation behavior.

* **IDE integration** - Easily view a `@Component` or a `@Subcomponnet` graphs directly from source code via gutter icons (IntelliJ/Android Studio).

* **Supports** both Kotlin and Java.

### How it works

In order to get to the point shown in above videos, Scabbard has 3 different components working together.

* **Scabbard Processor** - A `BindingGraphPlugin` which is provided as part of [Dagger SPI](https://dagger.dev/spi.html). It receives callbacks from Dagger's main compiler about graph information and is responsible for generating `png` images and `dot` files.

* **Scabbard Gradle Plugin** - A gradle plugin to abstract away internal implementation details required in setting up the above processor and also acts as an API to configure Scabbard behavior. Being a Gradle plugin allows it do stuff that is otherwise not possible with pure annotation processors.

* **Scabbard IntelliJ Plugin** - An IntelliJ plugin to link generated graphs back to their source code. This plugin also sets up stage for building any additional UI tools based on Dagger information in the future.

### Goals

For Scabbard, I had the following goals in mind.

* Establish ability to build informational tools with Dagger graph information - as mentioned above the IDE and Gradle plugins work together with shared knowledge to provide UX improvements. This can be easily extended to build additional tools (~~like linking `@Inject` with bindings~~ this feature is now natively [available](https://medium.com/androiddevelopers/dagger-navigation-support-in-android-studio-49aa5d149ec9) as part of Android Studio since 4.1 Canary 07.).
* Easy to use visualization - Scabbard aims to be simple to setup and tries to abstract away the internal implementation details involved in graph generation
* Readable Graph information - it is very easy to end up in complicated graph diagrams which is technically correct but hard to decipher due to their complexity especially in large projects like _Grab's_. To tackle this, Scabbard splits the graph by `@Component` and `@Subcomponent` to keep the graphs small and understandable.
* Opionated strucure - internal dagger representation can be inferred and represented in many different ways, Scabbard aims to start with a base representation and evolve it based on community feedback.

### Tech Stack

#### GraphViz

[GraphViz](https://www.graphviz.org/) is a popular tool for drawing graphs and Scabbard primarly uses it for generating images. In addition to `png` files, Scabbard generates a raw `dot` file which can be analyzed in variety of tools ([Gephi](https://gephi.org/) etc).

#### Kotlin

Project is fully written in Kotlin and it enabled me to build better APIs (DSL) allowing me to concentrate on expressing the graph cleanly instead of worrying about API specifics. Scabbard also ships a `dot-dsl` artifact for writing dot files easily with Kotlin, example:

{% include images_phone_screenshot.html url="https://github.com/arunkumar9t2/scabbard/blob/main/docs/images/dot-dsl.png?raw=true" caption="Dot-dsl for constructing dot files in Kotlin"%}

### Cheat sheet

Below is the example `AppComponent` used as a base for building graph and its attributes (please `Open in new tab` for better quality). There is a plan to provide a better detailed cheat sheet to help in understanding the graph better, contributions welcome!

{% include images_center.html url="https://arunkumar9t2.github.io/scabbard/images/dev.arunkumar.scabbard.di.AppComponent.svg" %}

### Highlights

There are a lot to cover, below are some selected highlights and examples.

#### Interactive Graphs with SVG

> Available since 0.2.0

Scabbard utilitizes hyperlinks available as part of SVG spec and enables navigation between `@Component` and `@Subcomponent` as shown below.

<video width="100%" controls>
  <source src="https://arunkumar9t2.github.io/scabbard/video/svg_sample.mp4" type="video/mp4">
  Your browser does not support the video tag.
</video>

#### Visualizing errors

Scabbard can highlight `Missing Bindings` in red color which can be easily used to point to why the error arises. Requires [full binding graph validation.](https://arunkumar9t2.github.io/scabbard/configuration/#enable-full-binding-graph-validation)

{% include images_center.html url="https://github.com/arunkumar9t2/scabbard/blob/main/docs/images/missing-binding.png?raw=true" caption="Missing bindings"%}

#### [Google IO 2019](https://github.com/google/iosched)

{% include images_center.html url="https://arunkumar9t2.github.io/scabbard/images/com.google.samples.apps.iosched.di.AppComponent.svg" caption="AppComponent"%}

#### [Plaid](https://github.com/android/plaid)

{% include images_center.html url="https://arunkumar9t2.github.io/scabbard/images/io.plaidapp.dagger.HomeComponent.svg" caption="HomeComponent"%}

### Summary

Overall I am excited to share Scabbard with you and it has been challenging project with lots of stuff learnt particularly dagger internals. Hopefully it is helpful. Would love to hear feedback and iterate on this further. Please share your thoughts in the comments or [Github issues](https://github.com/arunkumar9t2/scabbard/issues), or on [Twitter](https://twitter.com/arunkumar_9t2).


text:
### Inventory File

The Ansible inventory is described [here](http://docs.ansible.com/ansible/intro_inventory.html).

For Neus, the inventory contains the following options:

#### CI Tools

Below is a list of options in the CI Tools inventory files.  Some of the options are only applicable to silver of gold blueprints.

| parameter | required | default | choices | comments |
|--------|--------|--------|--------|--------|
| ansible_port | yes | 22  |  | The Ansible ssh port. |
| jenkins_port | yes | 8080 |  | Default port used by Jenkins. |
| database_port | yes | 3306 |  | Default port used by MariaDB. |
| nexus_port | yes | 8081 |  | Default port used by Nexus. |
| gogs_port | yes | 3000 |  | Default port used by GOGS. |
| sonar_port | yes | 9000 |  | Default port used by SonarQube. |
| tgt_platform | yes | docker |

docker

vm

ec2

 | docker: uses Docker containers to test the build scripts
 vm: deploys to VMs, also use `-k` with `up.sh` to ask for password
 ec2: deploys to Amazon Web Services (AWS) Elastic Cloud Compute (EC2) |
| ci_a_ip | when tgt_platform is *vm* | | | Set to the IP address of the VM for ci-a |
| ci_b_ip | when tgt_platform is *vm* | | | Set to the IP address of the VM for ci-b |
| ci_dit_ip | when tgt_platform is *vm* | | | Set to the IP address of the VM for ci-dit |
| ci_c_ip | when tgt_platform is *vm* | | | Only available in `silver` or `gold` blueprints; set to the IP address of the VM for ci-c |
| ci_d_ip | when tgt_platform is *vm* | | | Only available in `gold` blueprint; set to the IP address of the VM for ci-d |
| ci_e_ip | when tgt_platform is *vm* | | | Only available in `gold` blueprint; set to the IP address of the VM for ci-e |
| pamm | yes | no |

yes

no

 | When set to `yes` the PAMM seed will be imported into GOGS and a build job will be created in Jenkins to build the PAMM seed. |
| jamm | yes | no |

yes

no

 | Not yet available. |
| scm | | gogs |

gogs

rtc

 | flags the type of source control to use:

gogs: for local Go Git Repository

rtc: for an external connection to Rational Team Concert

 |
| blueprint | yes | |
bronze

silver

gold
 | Set to blueprint, do not change the value. |

#### PAMM

| parameter | required | default | choices | comments |
|--------|--------|--------|--------|--------|
| tgt_platform | yes | docker |

docker

vm

ec2

 | docker: uses Docker containers to test the build scripts
 vm: deploys to VMs, also use `-k` with `up.sh` to ask for password
 ec2: deploys to Amazon Web Services (AWS) Elastic Cloud Compute (EC2) |
| pamm_a_ip | when tgt_platform is *vm* | | | Set to the IP address of the VM for pamm-a |
| instance_type |when tgt_platform is *ec2* | t2.micro | | AWS EC2 instance type. |
| region | when tgt_platform is *ec2* | eu-west-1 | | AWS region. |
| tag_name | when tgt_platform is *ec2* | pamm-a | | EC2 instance tag name. |
| vpc_subnet_id | when tgt_platform is *ec2* | | | Set to AWS account vpc subnet. |
| zone | when tgt_platform is *ec2* | eu-west-1b | | AWS zone. |
| blueprint | yes | | | Set to blueprint, do not change the value. |

repository: ndeaks/neus

repo_name: ndeaks/neus


text:
---
layout: "unit"
title: "Guide Entry 05.02.03"
path: "/curriculum/guides/2005/2/05.02.03.x.html"
unitTitle: "Teaching Voice through Latina and African American Literature"
unitAuthor: "Kristen J. Grandfield"
keywords: ""
recommendedFor: "Recommended for English and Language Arts, grades 11-12."
---

Guide Entry to 05.02.03:

This curriculum unit is designed for high school students to read, write and discuss voice by reading Latina and female African American literature. Voice is a literary device used by authors to convey a particular mood or tone in his/her writing. The tone and mood are created by word choice and fluency; elements that make writing such a deliberate and precise act.

This unit uses the writing of Sandra Cisneros, Julia Alvarez, Nikki Giovanni and Ntozake Shange and asks students to identify elements of voice in each of the writer's work.  Students will also write personal vignettes, poems and responses using the selected pieces as models. The goal of the unit is to have students recognize voice and the techniques writers use to create their voice and message. Students will produce a portfolio of their best work based on their understanding of voice and the writers.

(Recommended for English and Language Arts, grades 11-12.)


text:
# MagicMirror-Modules-Thingiverse Change Log

All notable changes to this project will be documented in this file.
This project adheres to [Semantic Versioning](http://semver.org/).

## [1.1.1] - Released

### Bug Fixes

- Fixed issue where the `page` variable would be set to `0` and sent in the API request, resulting in no data.
- Added validation ensuring that `things` are only set to an array, not data.

## [1.1.0] - Released

### Features

- Added a `category` property, allowing users to display things based on a specific category.
- Added a `isFeatured` property, allowing users to display things that were / are featured on Thingiverse.
- Added a `numThingsDisplayed` property, allowing users to display 1, 3, or 5 things at any given time.
- Added a `searchBy` property, allowing users to display either newest things, or popular things.
- Added safety checking and fallback, such that if there is an error pulling things for a category, it will revert to displaying popular / newest things, whatever your config is set to.
- Added alt image text in the event the thumbnail image could not be displayed.

### Bug Fixes

- Removed the QR Code display from the module, QR Code generation was not properly working.
- Fixed issue where, when all things had been displayed and the next things were getting ready, the screen would be blank.

## [1.0.0] - Released

First public release

repository: appdevelopmentandsuch/MMM-Thingiverse

repo_name: appdevelopmentandsuch/MMM-Thingiverse


text:
# Code-Quiz

This is [a JavaScript Quiz](https://luketeal.github.io/Code-Quiz/).

The project uses HTML, CSS, and JS as a codebase largely pulling froom Bootstrap for styling.

## Repository Contents
The repository includes

* Two HTML files:
    * One for the [Home page](./index.html) and;
    * One for the [Highscores](./highscore.html) page;
* The [CSS](./assets/css) code;
* Two JavaScript files:
    * One for the [Home Page](./assets/js/script.js); and
    * One for the [Highscores](./assets/js/scripthighscore.js) page;
* [GIF](./assets/images) of intended functionality.

## Objectives

The web app presents the user with a series of questions about JavaScript, evaluates the answers and calculates and saves the users scores into a highscores list.

## Instructions

1. Select "Begin" from the home page
    * A timer will begin presenting the user with time left in the quiz
2. Answer the questions presented
    * Incorrect answers deduct 10 seconds from the timer
3. The quiz ends when the timer reaches zero or all the questions are answered
    * Any unanswered questions are considered incorrect.
4. The user may save their score locally by typing in their initials when presented with their score and selecting "Submit"
5. On the Highscores screen the user may clear the scores from their local storage
6. The user may navigate between the home page and highscores page at any time from the links in the header.

## Screenshot
The image below show's the web app's appearance and functionality:

![A GIF of the intended functionality showing the user selecting the "begin" button and answering the questions and saving a highscore.](./assets/images/mockup.gif).

## Credits
* The HTML is styled primarily using Bootstrap v5.0.0-beta3
* Normalize v8.0.1.css downloaded from Nicolas Gallagher's github page

repository: luketeal/Code-Quiz

repo_name: luketeal/Code-Quiz


text:
# ChangeLog
>Please update with changes to keep everyone up to date with the module, thank you! ;) We use [Semantic Versions](http://semver.org/spec/v2.0.0.html).

## Unreleased 00/00/0000

## Version 0.0.1


text:
# webpack-build-speed-testing

Code to test webpack's build time.

## Development

To add devDependencies, use `yarn install` (**Recommended**) or `npm install`.

## Plugins

Webpack's document says we can speed up our building process with DllPlugin, which can be found here: [DllPlugin](https://www.google.co.jp/url?sa=t&rct=j&q=&esrc=s&source=web&cd=4&ved=0ahUKEwjw_cGPtp_UAhVCNbwKHeYLA90QFgg5MAM&url=https%3A%2F%2Fwebpack.js.org%2Fplugins%2Fdll-plugin%2F&usg=AFQjCNGRClmGtJChARntRrMvocsIJfSLzw&sig2=2jUBiyJqqEv6U16D7nATlg).

Besides, HappyPack is a great tool to speed up our building process. You can find it here: [HappyPack](https://github.com/amireh/happypack).

## Build

By default, `npm run build` will build without plugins.

If you want to build with Happypack and DllPlugin, just pass a `dll` param:

``` bash
npm run build dll
```

If you are told you haven't permissions to execute the script, run the code below:

``` bash
$ chmod +x ./script/build.sh
```

## License

Released under the MIT license.


text:
# Russell Lab - Matrix-Vector Laboratory Tools

_This crate is part of [Russell - Rust Scientific Library](https://github.com/cpmech/russell)_

Work in progress...

This repository is a "rust laboratory" for vectors and matrices.

Documentation:

- [API reference (docs.rs)](https://docs.rs/russell_lab)

## Installation

Add this to your Cargo.toml:

```toml
[dependencies]
russell_lab = "0.1"
```

repository: cpmtester/russell

repo_name: cpmtester/russell


text:
## Process Some Strings

There are tons of useful standard library functions for strings. Let's try and use some of
them!

You may or may not need to convert from &str to String.

For the compose_me method: You can either use the format! macro or convert the string
slice into an owned string, which you can then freely extend.

There is more than one way to solve this task!

repository: jetbrains-academy/rustlings-course

path: /Common Collections/Strings/Process Some Strings/task.md

gha_language: Rust

repo_name: jetbrains-academy/rustlings-course


text:
## Modification fo server.json

`wsPort` in `servers.json` is replaced with `clientPort` since the protocol supported in Pomelo is not only websocket yet and the `wsPort` which means 'websocket port' is not suitable anymore.

And a new field `frontend` is imported to indicate a server is whether a frontend server or backend server which is checked by the `wsPort` whether is specified in the previous versions. So for the frontend servers *MUST* set the `frontend` to true while the backend servers could set it to false or leave it empty by default.

For example, in [lordofpomelo](https://github.com/NetEase/lordofpomelo), the modification of [servers.js](https://github.com/NetEase/lordofpomelo/blob/master/game-server/config/servers.json) is as below:

connector server configuration：

```
"connector": [
  {"id": "connector-server-1", "host": "<IP_ADDRESS>", "port": 3150, "clientPort": 3010, "frontend": true},
  {"id": "connector-server-2", "host": "<IP_ADDRESS>", "port": 3151, "clientPort":3011, "frontend": true}
]
```

gate server configuration：

```
"gate": [
  {"id": "gate-server-1", "host": "<IP_ADDRESS>", "clientPort": 3014, "frontend": true}
]
```

And remember to modify the dependecies of the `wsPort` in the codes. Such as replace the `res.wsPort` with `res.clientPort` in [gateHandler](https://github.com/NetEase/lordofpomelo/blob/master/game-server/app/servers/gate/handler/gateHandler.js#L29).

##Configuration of connectors

The code based on socket.io in the previous version can be ported to 0.3 version without any modification.

To use the new connector which based on socket and websocket, just only need to add a simple configuration in the `app.js` as following:

```
app.configure('production|development', 'connector', function(){
  app.set('connectorConfig', {
    connector: pomelo.connectors.hybridconnector,
    heartbeat: 3,
    useDict: true,
    useProtobuf: true,
    checkClient: function(type, version) {
    	// check the client type and version then return true or false
    },
    handshake: function(msg, cb){
      cb(null, {/* message pass to client in handshake phase */});
    }
  });
});
```

More details of connectors, please refer to [New features of Pomelo 0.3](https://github.com/NetEase/pomelo/wiki/Pomelo-0.3-new-features).

##Configure route compression
Route compression support compress the route to a 2 bytes integer at transport time. User can open this function without change any code.  The below code is how to open the route compression function at app.js:

```
  app.set('connectorConfig', {
    connector: pomelo.connectors.hybridconnector,
    heartbeat: 3,
    useDict: true,
    handshake: function(msg, cb){
      cb(null, {/* message pass to client in handshake phase */});
    }
  });
```
The 'userDict : true' means to open the route compression. The default route compression will compress all the system generated routes, like 'area.playerHandler.move' etc.

To add the dictionary for user defined route, like 'onMove', 'onAttack', you need to add all the use defined routes at the /game-server/config/dictionary.json file, the format of the file is as follow:

```
[
	"onDropItem",
	"onAttack",
	"onDied",
	"onMove",
	"onUpgrage",
	"onPickItem",
	"onRevive",
	"addEntities",
	"onRemoveEntities",
	"onPathCheckout"
]
```

For more information of route compress, see [pomelo data compression protocol](https://github.com/NetEase/pomelo/wiki/Pomelo-data-compression-protocol).

##Protobuf encode config
In pomelo 0.3, we support message compression based on protobuf. The protbuf encode protocol will reduce the message size dramaticly, comprae to JSON format. The average compressed rate is 20% in the demo lordofpomelo.

To use the protobuf fuction, you need to open it in app.js, the config is as follow:
```
	app.set('connectorConfig',
		{
			connector : pomelo.connectors.hybridconnector,
			heartbeat : 3,
			useProtobuf : true,
			handshake : function(msg, cb){
				cb(null, {});
			}
		});
```
The 'useProtobuf:true' is the flag, after set that, pomelo will transport the protos data to client, and open protobuf decompress function.

After set the protbuf flag in app.js, to encode a message with protobuf, all you need to do is to add the protobuf protos in the proto file. There are two porotos files in pomelo:  /game-sever/config/serverProtos.json and /game-server/config/clientProtos.json, which means Server->Client message and Client->Server messages, the content format is as follow:

```
"onMove" : {
    "required uInt32 entityId" : 1,
    "message Path": {
      "required uInt32 x" : 1,
      "required uInt32 y" : 2
    },
    "repeated Path path" : 2,
    "required uInt32 speed" : 3
  },
  "onAttack" : {
    "required uInt32 attacker" : 1,
    "required uInt32 target" : 2
  }
```
To get more information about protobuf compression, you can see [Pomelo compression protocal](https://github.com/NetEase/pomelo/wiki/Pomelo-data-compression-protocol), and [Pomleo-protobuf module](https://github.com/pomelonode/pomelo-protobuf).

##Building system for Javascript client

In Pomelo 0.3, we import the [component](https://github.com/component/component) system to manage the client Javascript libraries. And the client Javascript codes would be downloaded from `github` repository directly when building the client system.

The client building system is composed by the `component.json` description file and the `local/` directory under the `web-server/publilc/js/lib/`.

`component.json` in `public/js/lib/` describes the global component information of the client which points to the `local/` folder and contains a local component named `boot`.

Contents of `public/js/lib/component.json`

```
{
  "name": "pomelo-client",
  "description": "pomelo-client",
  "local": [ "boot" ],
  "paths": [ "local"]
}
```

And the `loacl/` folder contains the local components description. These is only one local component in the client system which named `boot` and located in `public/js/lib/boot/`. And the `boot` local component mainly includes two files: `component.json` and `index.js`.

The `boot/component.json` is a component description file like the one in `npm` and it mainly describes the base information and dependencies of the local component.

The conents of `boot/component.json`:

`component.json` is used to describe

```
{
  "name": "boot",
  "description": "Main app boot component",
  "dependencies": {
    "component/emitter":"master",
    "NetEase/pomelo-protocol": "0.3.x",
    "pomelonode/pomelo-protobuf": "*",
    "pomelonode/pomelo-jsclient-websocket": "master",
    "component/jquery": "*"
  },
  "scripts": ["index.js"]
}
```

There are several tools located in `web-server/bin/` to help to build the client system.

`bin/component.sh` - install and build the client codes. It would fetch the latest codes from github and build the client.

Usage:

Input the command below in the `web-server` directory.

```
sh bin/component.sh
```

`bin/build-component.sh` - build the client system. It would only build the client from the local files and would not fetch them from github.

For development, developers can modify the local files and build the new client by typing the following command in the `web-server` directory.

```
sh bin/build-component.sh
```

More detail about component system, please refer to [component](https://github.com/component/component).

repository: hexcola/pomelo

repo_name: hexcola/pomelo


text:
---
hrs_structure:
  division: '1'
  volume: '4'
  title: '14'
  chapter: '237'
  section: 237-6
type: hrs_section
tags:
  - Government
menu:
  hrs:
    identifier: HRS_0237-0006
    parent: HRS0237
    name: '237-6 "Contractor", "contracting", "federal cost-plus'
weight: 68030
title: '"Contractor", "contracting", "federal cost-plus'
full_title: '237-6 "Contractor", "contracting", "federal cost-plus'
---
**§237-6 "Contractor", "contracting", "federal cost-plus contractor", defined.** "Contracting" means the business activities of a contractor.

"Contractor" includes, for purposes of this chapter:

(1) Every person engaging in the business of contracting to erect, construct, repair, or improve buildings or structures, of any kind or description, including any portion thereof, or to make any installation therein, or to make, construct, repair, or improve any highway, road, street, sidewalk, ditch, excavation, fill, bridge, shaft, well, culvert, sewer, water system, drainage system, dredging or harbor improvement project, electric or steam rail, lighting or power system, transmission line, tower, dock, wharf, or other improvements;

(2) Every person engaging in the practice of architecture, professional engineering, land surveying, and landscape architecture, as defined in section 464-1; and

(3) Every person engaged in the practice of pest control or fumigation as a pest control operator as defined in section 460J-1.

"Federal cost-plus contractor" means a contractor having a contract with the United States or an instrumentality thereof, excluding national banks, where, by the terms of the contract, the United States or such instrumentality, excluding national banks, agrees to reimburse the contractor for the cost of material, plant, or equipment used in the performance of the contract and for taxes which the contractor may be required to pay with respect to such material, plant, or equipment, whether the contractor's profit is computed in the form of a fixed fee or on a percentage basis; and also means a subcontractor under such a contract, who also operates on a cost-plus basis. [L 1935, c 141, pt of §1; am L 1941, c 265, §1(b); am L 1943, c 81, §1(a); RL 1945, §5448; RL 1955, §117-7; am L 1965, c 201, §36; [HRS §237-6](/title-14/chapter-237/section-237-6/); am L 1971, c 4, §1 and c 204, §3; am L 1984, c 60, §1; am L 2000, c 198, §2]

Case Notes

"Structures" does not include boats and vessels, and taxpayer engaged in repair of marine vessels is not a "contractor". 55 H. 572, 524 P.2d 890.

Cited: 44 H. 584, 587, 358 P.2d 539.

repository: SamMade/BlueAndKrabby

repo_name: SamMade/BlueAndKrabby


text:
# Reflection

## JS Refactor

- Refactored AJAX data loading using jQuery promises instead of the `setTimeout` functions. This allowed control flow to process synchronously, e.g., the rest of the script would continue to run once the AJAX call finished retrieving the JSON data.
- Composed `ProductView` and `ProductController` objects to handle DOM manipulation and `Product` models.
- Wrapped entire application code in an immediately invoked function expression (IIFE) to keep variables inside the IIFE's closure scope.

## Styling

- Used Bootstrap columns to responsively show different number of products per row depending on user's viewport and to have products "slide" into place when the product preceding it is deleted.
- Set font-sizes as requested.
- Used Bootstrap `cards` class to display products.
- Imported Bootstrap Glyphicons for "X" to remove products.
- Imported Google Fonts for unique typography.

## Overlay

- Used jQuery `.toggle` to add/remove `hidden` class from `overlay` div.

## Bonus
- Used jQuery `.animate` to fade out deleted product before removing it from the DOM.
- Stored the product template in a variable. This improved performance by allowing reuse without making an AJAX call for each subsequent product template being rendered.
- Included jQuery, Bootstrap and Bootstrap JS libraries locally to avoid using CDNs. *Note: In production I would use the minified verision of these files, but in development I prefer the non-minified version because they are easier to navigate when debugging*

repository: mtvillwock/front-end-challenge

repo_name: mtvillwock/front-end-challenge


text:
---
layout: post
title: GSoC Progress - Week 8
---

My first two months under `GSoC` have finally ended, and we are right on track towards the completion of the project. I finished up on my log of `SymPy`'s directories and have analysed everything that needs to be further implemented or improved upon.

## Report

### SymEngine
I pushed in [#1313](https://github.com/symengine/symengine.py/pull/1313), implementing `row_insert` and `column_insert` functions in `DenseMatrix` class and `row_del` and `col_del` functions in `C` wrappers, while making `row_join`, `col_join`, `row_del` and `col_del` in-place member functions.

### SymPy
After testing all the viable directories that could use `SymEngine` as a backend, only the `LieAlgebras` module worked completely out of the box, with no major issues. As such, we were able to achieve the same through [#13023](https://github.com/sympy/sympy/pull/13023), which now marks the beginning of Phase III of my proposal. I have also pushed the work done on other directories as separate branches on my local repository, to be finished upon gradually.

### SymEngine.py
I worked on implementing the `Singleton` pattern in the wrappers through [#178](https://github.com/symengine/symengine.py/pull/178), though the work is currently in progress. More on this next week.

That's all I have for now.

**Bidāẏa**

repository: ShikharJ/old-site

repo_name: ShikharJ/old-site


text:
app/controllers/*.rb
=================
This is your routing and logic folder. Basic routing requires a url address and a destination.
This framework provides full flexibility and room for
customization.

For example, a users controller file might look something like this:
```
# app/controllers/users.rb

get '/signup' do
	erb :'users/new'
end

post '/signup' do
	# Do something processing with user input
	redirect to '/user/dashboard'
end

get '/user/dashboard' do
	erb :dashboard
end
```
Remember to link/require the appropriate controller if you require access to their related objects.

You can create many controller files as long as there is no conflicted routes. Sinatra go through
each controller file and compile all available routes.

gha_language: Ruby


text:
# Getting Iffy - A Ruby Kata

## Josh thoughts

Hmm, the modules defining the methods was unfortunate.

## About

You must refactor the beast that lies beneath the authorization mechanism of an invoice system.  You are new to the project.  All you see is a sea of "if" statements.  Your task:  Make the if statements go away.

The code is real.  It was at the bottom of our construction management invoice system that has handled billions of dollars of construction.  I have graciously been given permission by my supervisor to use it for this lesson.  Enjoy!

## Run

The kata was written with Ruby 1.9.3 and expects Minitest and SimpleCov.  Use 'bundle' to get everything just so.
A default rake task will run the tests and create a coverage report.  No fair changing the tests or modifying the stubbed-out classes and methods.

## License

Under Apache 2.0 license.


text:
## About DSAIMS

This is a client project for the DePaul School of Jacksonville.

### Group Members

- [Kevin Bell](https://github.com/jawsofdoom)
- [Andrew Greer](https://github.com/Initech10)
- [Stephen Hartman](https://github.com/stephenhartman)
- [Lindsey Wanta](https://github.com/lindseywanta)

## Laravel Documentation

- [Simple, fast routing engine](https://laravel.com/docs/routing).
- [Powerful dependency injection container](https://laravel.com/docs/container).
- Multiple back-ends for [session](https://laravel.com/docs/session) and [cache](https://laravel.com/docs/cache) storage.
- Expressive, intuitive [database ORM](https://laravel.com/docs/eloquent).
- Database agnostic [schema migrations](https://laravel.com/docs/migrations).
- [Robust background job processing](https://laravel.com/docs/queues).
- [Real-time event broadcasting](https://laravel.com/docs/broadcasting).

## Installation

### Mac OSX

1. Clone [the repository](https://github.com/stephenhartman/ds_aims) into project folder of choice

`git clone https://github.com/stephenhartman/ds_aims.git`

2. Install [PHP](http://php.net/)

- Install [Homebrew](https://github.com/Homebrew/brew)
`brew tap homebrew/homebrew-php`

3. Install [Composer](https://getcomposer.org/download/) Dependency Manager

```
php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"
php -r "if (hash_file('SHA384', 'composer-setup.php') === '669656bab3166a7aff8a7506b8cb2d1c292f042046c5a994c43155c0be6190fa0355160742ab2e1c88d40d5be660b410') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"
php composer-setup.php
php -r "unlink('composer-setup.php');"
```

4. Download [Laravel](https://laravel.com/) using Composer

`composer global require "laravel/installer"`

- Add $HOME/.composer/vendor/bin to $PATH in terminal rc file (e.g. ~/.bashrc)

5. Install npm in project folder

```
brew install npm
brew install node
```

6. Install [Laravel Mix](https://laravel.com/docs/5.4/mix) in project folder

`npm install`

`npm run watch` will monitor all relevant files for changes to compile (css and js)

7. Setup Mysql database

- Download [mysql](https://www.mysql.com/downloads/) or use command line `brew install mysql`
- Start daemon `mysqld` or use GUI tool to start the server on localhost
- Log into mysql `mysql -u root`
- Create the database `mysql> create database vol_db;`
- Make sure you create the user, example `mysql> CREATE USER 'newuser'@'localhost' IDENTIFIED BY 'password';`
- Grant permissions for that user `mysql> GRANT ALL PRIVILEGES ON vol_db . * TO 'newuser'@'localhost';`
    - The first variable after `ON` is the database and the second variable after `.` is the table, * for all tables.
- Reset permissions `mysql> FLUSH PRIVILEGES;`

8. Migrate and seed database from shell
```
php artisan migrate
php artisan db:seed
```
flat Earth!

gha_language: PHP


text:
# Description

This is a PowerShell helper module that will aid in the creation and deletion of (single and batch) service principal and applications (enterprise and registered) when used with Microsoft Exchange application development with use with Basic Authentication deprecation. These can also be used with the use of regular 3rd party applications needing service principals and applications in Azure.

Version 1.0.1 - 1.0.8 (Beta test)
Version 1.0.9 - Stable release build

New functionality in version 1.0.9
The ability to create single self-signed certificates for applications to be used with Certificate Based Authenticaion (CBA). Certificated are stored in the users personal cert store.
The ability to create enterprise and registered Azure applications and service principals
The ability to remove applications and service principals in pairs

NOTE: When running New-ServicePrincipalObject -CreateSelfSignedCert you must be running PowerShell as an administrator to save certs to the local user cert store.

# Project Setup Instructions
## Working with the layout

 - Don't touch the psm1 file
 - Place functions you export in `functions/` (can have subfolders)
 - Place private/internal functions invisible to the user in `internal/functions` (can have subfolders)
 - Don't add code directly to the `postimport.ps1` or `preimport.ps1`.
   Those files are designed to import other files only.
 - When adding files you load during `preimport.ps1`, be sure to add corresponding entries to `filesBefore.txt`.
   The text files are used as reference when compiling the module during the build script.
 - When adding files you load during `postimport.ps1`, be sure to add corresponding entries to `filesAfter.txt`.
   The text files are used as reference when compiling the module during the build script.

## Setting up CI/CD

> To create a PR validation pipeline, set up tasks like this:

 - Install Prerequisites (PowerShell Task; VSTS-Prerequisites.ps1)
 - Validate (PowerShell Task; VSTS-Validate.ps1)
 - Publish Test Results (Publish Test Results; NUnit format; Run no matter what)

> To create a build/publish pipeline, set up tasks like this:

 - Install Prerequisites (PowerShell Task; VSTS-Prerequisites.ps1)
 - Validate (PowerShell Task; VSTS-Validate.ps1)
 - Build (PowerShell Task; VSTS-Build.ps1)
 - Publish Test Results (Publish Test Results; NUnit format; Run no matter what).

repository: FriedrichWeinmann/PSServicePrincipal

repo_name: FriedrichWeinmann/PSServicePrincipal


text:
# [Practice JavaScript and Learn: Create a Contact Form][published url]
## Instructor: [Jeremy McPeak][instructor url]

If you understand the basics of JavaScript and the key concepts we use to build web apps, the next step is to practice putting it all together in a practical project. In this course, use those fundamentals to build a working, functional, and engaging contact form.

Jeremy McPeak will show you how to build an AJAX contact form from scratch. You'll create a modern contact form you can be proud of with the latest features of JavaScript and web development best practices. Along the way you'll get to practice HTML5 validation, object-oriented programming, DOM manipulation, responding to event listeners, and using the Fetch API for AJAX form submission.

## Source Files Description

Each lesson's code is contained within a folder named with the corresponding lesson number.

------

These are source files for the Envato Tuts+ course: [Practice JavaScript and Learn: Create a Contact Form][published url]

Available on [Envato Tuts+](https://tutsplus.com). Teaching skills to millions worldwide.

[published url]: https://code.tutsplus.com/courses/practice-javascript-and-learn-create-a-contact-form
[instructor url]: https://tutsplus.com/authors/jeremy-mcpeak


text:
---
author: gep13
comments: true
date: 2011-12-13 12:59:53+00:00
layout: post
slug: just-updated-this-blog-to-wordpress-3-3
title: Just updated this blog to WordPress 3.3
wordpress_id: 513
categories:
- gep13 blog
tags:
- '3.3'
- Updates
- WordPress
---

Thanks to a tweet from Richard Hay ([@WinObs](https://twitter.com/#!/WinObs)), I have just updated this WordPress blog to WordPress 3.3.  As always the installation was painless, and the new look and feel is very nice!  Might take a bit of getting used to, but in a good way.

If you are interested in the new features that WordPress 3.3 has to offer, you can check them out in the video below.  I am particularly impressed with the new drag and drop features for adding media to your blog, and the changes to the menus make perfect sense and are a great addition!

You can also find more information on Richard's Blog [here](http://www.windowsobserver.com/2011/12/12/wordpress-3-3-released/).

branch_name: refs/heads/source

extension: markdown

gha_language: CSS


text:
# Changelog

All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.

## 1.0.0 (2021-02-14)

### Features

* add license ([e03bb18](https://github.com/masb0ymas/express-docs-functions/commit/e03bb18bd8e64d743f54d09284edbf43f0419f91))
* add readme ([86d7f99](https://github.com/masb0ymas/express-docs-functions/commit/86d7f994d73ecd27fd90f37121aa5ddfa977ec66))

### Bug Fixes

* bin/server ([cd6847e](https://github.com/masb0ymas/express-docs-functions/commit/cd6847edb1fdff3757c3386e844ea9b6ba99aed3))
* update package json ([5aa445b](https://github.com/masb0ymas/express-docs-functions/commit/5aa445bbb8e2f4a992f680c099bb4b62523798ba))
* update readme ([e512ded](https://github.com/masb0ymas/express-docs-functions/commit/e512ded0e2d7b731a98a741ea97036217377d15c))


text:
## "Refactoring F#"

Examples from my "Refactoring F#" talk.

Code available at https://github.com/swlaschin/RefactoringFSharp

## Key principles of functional programming

* Separate code from data
* Every function has an output -- this is important for composition
* Functions should not have hidden side-effects

## Functional Design Guidelines

* Composition everywhere
  * E.g. Convert everything to the same "level" using lifting - then composition is easier.
* Parameterize all the things
  * E.g. remove dependencies on global code by passing in functions
* There is no problem that cannot be solved by wrapping it in a type
* Model the system like a compiler:
  1. Parse the (untrusted) input into a trusted internal representation (use Option.ofObj, ofNullable, etc)
  2. Process and transform the data
  3. Emit data back to the untrusted world: transform domain types back to strings and ints.

## Tips for refactoring from imperative code

* Replace throwing exceptions with returning a Result. Chain results together using "bind". See http://fsharpforfunandprofit.com/rop/
* Change void-returning methods to return something.
* Use types to remove the need for validation. Obviously no nulls, but also e.g PositiveInteger
  * Pass the buck! It's the caller's responsibility to give you valid data
* Replace inheritance with discriminated unions where appropriate.
* Replace if/then/else tests with pattern matching -- it helps you detect edge cases
* Use Active patterns to make conditional logic clearer

## Tips for converting imperative loops

* If you are iterating over all the elements, use fold
* If you need to break early, use recursion, or fold with a flag.
* Take full advantage of the built-in collection functions -- see http://fsharpforfunandprofit.com/posts/list-module-functions/
* Don't forget `choose` and `pick`
* Don't treat lists like indexed collections

## General Tips

* Using Some/None matching with options can generally be replaced with Option.map or Option.bind.
* Use #IComparable, etc., instead of ugly type constraints
* Booleans
  * If you see boolean flags in a data structure, chances are it's a state machine. Use a DU instead.
  * If you see a function returning a boolean, replace the result with something useful.

## Code smells

* Ignoring the output of an expression
* Throwing exceptions rather than returning error types.
* Returning unit rather than something useful.
* Null checks in the core domain -- these should only be done at the boundary
* Wildcards in pattern matching
* Primitive obsession: Using strings and ints everywhere, rather than exploiting the type system.
* Accessing "global" functions and state rather than having them be passed in as parameters
* Treating lists like indexed collections
* Treating lists as appendable collections
* Over-reliance on "if" expressions and booleans rather than using pattern matching.
* Over-reliance on booleans (see tip above)
* Unwrapping and rewrapping options using "IsSome" rather than using staying in the world of options and using Option.map and Option.bind.
  * See http://fsharpforfunandprofit.com/series/map-and-bind-and-apply-oh-my.html
* Having deeply nested lambdas - I prefer the use of private helpers


text:
Calendar Demo
=============

This example shows how to use the calendar API to list calendars and events.
It also shows how to add an event and view it using the built-in calendar app.

repository: Appercode/monodroid-samples

branch_name: refs/heads/Appercode

gha_language: C#

repo_name: Appercode/monodroid-samples


text:
# ID Generator

Generates secure IDs for people. Built for [Something New](https://somethingnew.org.uk) financial open data publishing.

## Why?

As the treasurer of an political party, I want to [publish all our finances as open data](https://somethingnew.org.uk/about/finances/). In this data, it's useful to be able to see who is making donations, how often, and of what size.

We ask if we can make donor names public, but not everyone wishes to do so, as is their right. Therefore for users of the open data to be able to track donations over time, we need a stable identifier for individuals which is not relatable to their personal data.

We wish to avoid simply minting a random ID for each user, because in order to reuse those IDs, we will have to keep them in a database, which if leaked would allow donation details to be linked to real people.

Therefore we wish to generate IDs from the personal data using a fixed algorithm which does not rely on a data store, and which cannot be reversed to obtain the input data even if the algorithm and any keys used are known.

## ID format

### Anonymous IDs

Anonymous IDs consist of the first 10 characters of a salted SHA-512 hash of the name and email address.

We combine the data as "{name} <{email}> {salt}", generate a SHA-512 hex digest, and use the first 10 characters as the ID.

The salt is stored in a secure password database along with other party credentials, but even if the salt is leaked the hashes could not be reverse engineered to obtain input data, though if possible input data was known it would be possible to verify if a person was a donor.

### Public IDs

Public IDs consist of the given name, plus the anonymous ID above. These are used where donors have given permission for their name to be published.

## Usage:

Pass name, email, and a salt value to the `anon` or `public` generators, then use the result instead of the name.

```
$ bundle

$ bundle exec ./generate anon "James Smith"<EMAIL_ADDRESS>ChauJe6dee6foo3sheeXag6Uu
>> 8f6b0c9338

$ bundle exec ./generate public "James Smith"<EMAIL_ADDRESS>ChauJe6dee6foo3sheeXag6Uu
>> James Smith 8f6b0c9338
```

To avoid passing the salt every time, you can also put it in an a `ID_GENERATOR_SALT` environment variable:

```
$ export ID_GENERATOR_SALT=ChauJe6dee6foo3sheeXag6Uu

$ bundle exec ./generate public "James Smith"<EMAIL_ADDRESS>>> James Smith 8f6b0c9338
```


text:
We have some good reasons to completely
switch over to solar power.
It's cheaper in many cases,
and definitely more sustainable
than our dependance on traditional power plants
that use resources like coal,
which will eventually run out.
So why don't we replace these
traditional plants with solar energy?
Because there's one factor that makes

solar power very unpredictable:
cloud cover.
As the sun's rays move towards Earth,
some get absorbed by the Earth's atmosphere,
some are reflected back into outer space,
but the rest make it to the Earth's surface.
The ones that aren't deviated
are called direct irradiance.
The ones that are deflected by clouds
are called diffuse irradiance.
And those rays that first get reflected by a surface,
like a nearby building,
before reaching the solar energy system
are called reflected irradiance.
But before we can examine how clouds
affect the sun's rays and electricity production,
let's see how these solar energy systems work.
First up, we have solar towers.
These are made up of a central tower
surrounded by a huge field of mirrors
that track the sun's path and focus
only the direct rays onto a single point on the tower,
kind of like an eager beachgoer.
The heat generated by these rays
is so immense that it can be used to boil water
producing steam that drives a traditional turbine,
which makes electricity.
But when we say solar energy systems,
we're usually talking about photovoltaics,
or solar panels,
which are the systems most commonly used
to generate solar power.
In solar panels,
photons from the sun's rays hit the surface of a panel,
and electrons are released
to get an electric current going.
Solar panels can use all types of irradiance,
while solar towers can only use direct irradiance,
and this is where clouds become important
because depending on their type and location
relative to the sun,
they can either increase or decrease
the amount of electricity produced.
For instance, even a few cumulus clouds
in front of the sun can reduce
the electricity production in solar towers
to almost zero because of this dependence on direct rays.
In solar panels, those clouds would decrease
energy output as well,
though not as much
because solar panels can use all types of irradiance.
However, all this depends on the clouds exact positioning.
Due to reflection, or a particular phenomeon
called Mie scattering,
the sun's rays can actually be focused forward
by clouds to create a more than 50% increase
in the solar irradiance reaching a solar panel.
If this potential increase isn't accounted for,
it could damage the solar panel.
Why does this matter?
Well, you wouldn't want this lesson to stop
just because a cloud passed over the panel on your roof.
In solar towers, huge tanks of molten salt or oil
can be used to store any excess heat
and use it when needed,
so that's how they manage the problem
of fluctuating solar irradiance to smooth out
electricity production.
But in the case of solar panels,
there currently isn't any way to affordably
store extra energy.
That's where traditional power plants come in
because to correct for any fluctuations
in these solar powered plants,
extra electricity from traditional sources
always needs to be available.
But then why aren't these tradtional power plants
just used as a backup,
instead of us humans depending on them
as our main sources of energy?
Because it's impossible for an employee
at a coal fired or a nuclear plant
to turn a knob to produce
more or less electricity depending
on how many clouds there are in the sky.
The response time would simply be too slow.
Instead, to accommodate these fluctuations,
some extra electricity from traditional power plants
is always being produced.
On clear sky days,
that extra electricity might be wasted,
but when cloudy skies prevail,
it's what fills the gap.
This is what we currently depend on
for a constant supply of energy.
For this reason, a lot of researchers
are interested in forcasting the motion
and formation of clouds through satellite images
or cameras that look up at the sky
to maximize the energy from solar power plants
and minimize energy waste.
If we could accomplish that,
you'd be able to enjoy this video
powered solely by the sun's rays,
no matter what the weather,
although if the sun is shining,
you may be tempted to venture outside
to go and do a different kind of cloud gazing.

repository: prewittdavon/TEDVis

repo_name: prewittdavon/TEDVis


text:
$!The rate of vehicle tax for cars is based on engine size or on fuel type and carbon dioxide (CO2) emissions, depending on when the car was registered - other types of vehicles have their own rates.$!

If you know the vehicle details, you can [find out its vehicle tax rate online](/calculate-vehicle-tax-rates "find out its vehicle tax rate online").

Otherwise, you can check the vehicle tax rates in the tables below. They also show the tax class (TC) of the vehicle type they are for.

##Cars registered before 1 March 2001

^The rate of vehicle tax is based on engine size for cars registered before 1 March 2001.^

###Private/light goods (TC11)

Engine size (cc) | 12 months rate | 6 months rate
- | - | -
Not over 1549 | £130.00 | £71.50
Over 1549 | £215.00 | £118.25

##Cars registered on or after 1 March 2001

^The rate of vehicle tax is based on fuel type and CO2 emissions for cars registered on or after 1 March 2001.^

The rates are split into bands depending on CO2 emissions - the lower the emissions, the lower the vehicle tax.

^CO2 emission details are shown on the car’s V5C registration certificate, or you can [find emission details online.](http://carfueldata.direct.gov.uk/search-new-or-used-cars.aspx "find emission details online"){:rel="external"}

The following 2 tables contain the ‘standard’ rates of vehicle tax for cars that are already registered.

###Petrol car (TC48) and diesel car (TC49)

Band | CO2 emission (g/km) | 12 months rate | 6 months rate
- | - | - | -
A | Up to 100 | £0.00 | Not available
B | 101-110 | £20.00 | Not available
C | 111-120 | £30.00 | Not available
D | 121-130 | £95.00 | £52.25
E | 131-140 |£115.00 | £63.25
F | 141-150 | £130.00 | £71.50
G | 151-165 | £165.00 | £90.75
H | 166-175 | £190.00 | £104.50
I | 176-185 | £210.00 | £115.50
J | 186-200 | £245.00 | £134.75
K* | 201-225 | £260.00 | £143.00
L | 226-255 | £445.00 | £244.75
M | Over 255 | £460.00 | £253.00

*Includes cars with a CO2 figure over 225g/km but were registered before 23 March 2006.

###Alternative fuel car (TC59)

Band | CO2 emission (g/km) | 12 months rate | 6 months rate
- | - | -
A | Up to 100 | £0.00 | Not available
B | 101-110 | £10.00 | Not available
C | 111-120 | £20.00 | Not available
D | 121-130 | £85.00 | £46.75
E | 131-140 | £105.00 | £57.75
F | 141-150 | £120.00 | £66.00
G | 151-165 | £155.00 | £85.25
H | 166-175 | £180.00 | £99.00
I | 176-185 | £200.00 | £110.00
J | 186-200 | £235.00 | £129.25
K* | 201-225 | £250.00 | £137.50
L | 226-255 | £435.00 | £239.25
M | Over 255 | £450.00 | £247.50

*Includes cars with a CO2 figure over 225g/km but were registered before 23 March 2006.

##First year rates - cars registered on or after 1 April 2010

These rates are for a vehicle’s first tax disc when they're first registered.

All tax discs after that are charged at the rates shown in the ‘Cars registered on or after 1 March 2001’ table above.

###Petrol car (TC48) and diesel car (TC49)

Band | CO2 emission (g/km) | 12 months rate | 6 months rate
- | - | -
A | Up to 100 | £0.00 | Not available
B | 101-110 | £0.00 | Not available
C| 111-120 | £0.00 | Not available
D | 121-130 | £0.00 | Not available
E | 131-140 | £115.00 | £63.25
F | 141-150 | £130.00 | £71.50
G | 151-165 | £165.00 | £90.75
H | 166-175 | £265.00 | Not available
I | 176-185 | £315.00 | Not available
J | 186-200 | £445.00 | Not available
K | 201-225 | £580.00 | Not available
L | 226-255 | £790.00 | Not available
M | Over 255 | £1,000.00 | Not available

###Alternative fuel car (TC59)

Band | CO2 emission (g/km) | 12 months rate | 6 months rate
- | - | -
A | Up to 100 | £0.00 | Not available
B | 101-110 | £0.00 | Not available
C| 111-120 | £0.00 | Not available
D | 121-130 | £0.00 | Not available
E | 131-140 | £105.00 | £57.75
F | 141-150 | £120.00 | £66.00
G | 151-165 | £155.00 | £85.25
H | 166-175 | £255.00 | Not available
I | 176-185 | £305.00 | Not available
J | 186-200 | £435.00 | Not available
K | 201-225 | £570.00 | Not available
L | 226-255 | £780.00 | Not available
M | Over 255 | £990.00 | Not available

##Other vehicle tax rates

###Light goods vehicles (TC39)

Registered on or after 1 March 2001 and not over 3,500kg revenue weight.

Vehicle | 12 months rate | 6 months rate
- | - | -
Light goods vehicle | £210.00 | £115.50

###Euro 4 light goods vehicles (TC36)

Registered between 1 March 2003 and 31 December 2006 and not over 3,500kg revenue weight.

Vehicle | 12 months rate | 6 months
- | - | -
Euro 4 light goods vehicles | £130.00 | £71.50

###Euro 5 light goods vehicles (TC36)

Registered between 1 January 2009 and 31 December 2010 and not over 3,500kg revenue weight.

Vehicle | 12 months rate | 6 months rate
- | - | -
Euro 5 light goods vehicles | £130.00 | £71.50

###Motorcycle (with or without sidecar) (TC17)

Engine size (cc) | 12 months rate | 6 months rate
- | - | -
Not over 150 | £16.00 | Not available
151-400 | £35.00 | Not available
401-600 | £53.00 | £29.15
Over 600 | £74.00 | £40.70

###Tricycles (not over 450kg unladen) (TC50)

Engine size (cc) | 12 months rate | 6 months rate
- | - | -
Tricycle not over 150 | £16.00 | Not available
All other tricycles | £74.00 | £40.70

###Trade licences

Vehicle | 12 months rate | 6 months rate
- | - | -
All vehicles | £165.00 | £90.75
Bicycles (only) not over 450kg | £74.00 | £40.70
Tricycles (only) not over 450kg | £74.00 | £40.70

*[TC]: Tax Class
*[CO2]: Carbon Dioxide

repository: craigw/govuk-data

gha_license_id: NOASSERTION

repo_name: craigw/govuk-data


text:
# User Stories
1. As a user, I would like to pick my favorite product out of *three* different products shown.
2. As a user, I would like the app to display which product I liked most after the survey has ended.
3. As a user, I would like the app to look clean and presentable as well as being user friendly.
4. As a developer, I would like my app to never display *two* of the same products at the same time.
5. As a developer, I would like my app to cycle through every product at least once.
6. As a developer, I would like my app to keep track of the data input by the user.
7. As a developer, I would like my the survey to end after displaying *fifteen sets* of products.
8. As a developer, I would like my app to display that stored data after the survey is completed.
9. As a developer, I would like my app to have a "reset" button at the end of the survey to let the user take it again.
10. As a Bus Mall executive, I would like for the app to show the most liked product and use it as a baseline to conduct business
11. As a Bus Mall executive, I would also like for the app to be user friendly and incorporate nice colors to represent the business.

repository: peffles/bus-mall

repo_name: peffles/bus-mall