carlcrott

Carl Crott
Oakland CA
carlcrott@gmail.com
415.304.3670

                        recruiters: please no unsolicited phone calls, email is preferred.

Bio:

carlcrott

Carl Crott
Oakland CA
carlcrott@gmail.com
415.304.3670

                        recruiters: please no unsolicited phone calls, email is preferred.

Bio:

Capable and driven multi-systems engineer with a core focus on UI to DB development and automated infrastructure. Both a technical developer and conversational in research concepts. Experience in scaling, application testing/hardening, linux sysadmin, web scraping, biochem / bioinformatics and design and prototyping of scientific hardware.

carlcrott

Expect no privacy.

This is a place holder because Ebays auth is broken.

carlcrott

Carl Crott
Oakland CA
carlcrott@gmail.com
415.304.3670

                        recruiters: please no unsolicited phone calls, email is preferred.

Bio:

carlcrott

Code changes should only be pushed to github if all tests are passing.


Below is a common work-flow for a team working with a central repo. 
Variations are possible, but if unsure, please go by this:

1. Git pull (or, if this is your first time ever getting the code, do git clone git@github.com:our_repo/our_repo.git to get a local copy of the repo)
2. Run tests
3. If tests fail, stop here and investigate. Do not continue to develop until all tests are passing.
4. git checkout -b my_work (create and switch to a local branch where you'll do your work)

carlcrott

(btcdev) Armament:joinmarket carlcrott$ pip install -r requirements-dev.txt 
Collecting pexpect (from -r requirements-dev.txt (line 1))
  Using cached pexpect-4.2.1-py2.py3-none-any.whl
Collecting pytest==2.8.2 (from -r requirements-dev.txt (line 2))
  Using cached pytest-2.8.2-py2.py3-none-any.whl
Collecting pytest-cov==2.2.1 (from -r requirements-dev.txt (line 3))
  Using cached pytest_cov-2.2.1-py2.py3-none-any.whl
Collecting python-coveralls (from -r requirements-dev.txt (line 4))
  Using cached python_coveralls-2.9.1-py2.py3-none-any.whl
Collecting mock (from -r requirements-dev.txt (line 5))

carlcrott

#define TEMP_PIN_05 5
const int READING_COUNT = 5;
int val_05[READING_COUNT];

const int how_many = 5;
bool run_once = true;

int read_05 = 0;
//int val_06 = 0;
//int val_07 = 0;

carlcrott

/*
*		JoomSpirit CSS file for typo
*/
body {
color:#6e6e6e;
font: normal 0.8em/1.3 arial, sans-serif;
}

carlcrott

Valued client black glass,

I've recently worked with several of my customers to help drastically lower their EC2 costs by leveraging Reserved Instances. As I was looking at some of my other customers, your account came up as one that could potentially be saving a lot of money based on your current EC2 usage.

For your account, I analyzed your September EC2 usage. Based on that usage, I calculated the optimal number of Reserved Instances that would result in the most cost savings for you each month. If your usage remained the same but you purchased Reserved Instances, you could save approximately $27.90 per month. This would save you between 45% ($701.88) and 64% ($1,004.44) depending on if you went with 1 year or 3 year Reserved Instances.

I've attached a complete proposal that goes into details on this analysis showing you the exact number of Reserved Instances and the exact cost savings that you could immediately start to recognize by leveraging Reserved Instances.

As explained in the attached proposal, 

carlcrott

The x3 repo is the third incarnation of the Integrated Plasmonics experiment interface.

#### Installation:
<pre>
# get x3 
$ sudo apt-get -y install python-virtualenv
$ cd ~/django_projects/
$ git clone git@github.com:IntegratedPlasmonics/x3.git

# configure + install packages