Skip to content

Commit 24b1540

Browse files
benjaminwsbenjaminws
authored
Work content. (#4)
1 parent 413ca32 commit 24b1540

File tree

4 files changed

+87
-7
lines changed

4 files changed

+87
-7
lines changed

‎src/App.css

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -62,6 +62,10 @@ a {
6262
text-shadow: 0 1px 1px rgba(0, 0, 0, 0.9);
6363
}
6464

65+
.callout-sub p {
66+
margin: 1em;
67+
}
68+
6569
.callout a {
6670
color: #DD0B1E;
6771
}

‎src/components/Footer.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ import {Link} from 'preact-router';
44
export const Footer = () => (
55
<footer class="footer">
66
<div class="container">
7-
<p class="text-center"><Link href="/about">About</Link> - <Link href="/contact">Contact</Link> - &copy; {new Date().getFullYear()} Benjamin Warfield Smith</p>
7+
<p class="text-center"><a href="https://twitter.com/benjaminws"><i class="fa fa-twitter fa-lg" aria-hidden="true"></i> Twitter</a> - <Link href="/about">About</Link> - <Link href="/contact">Contact</Link> - &copy; {new Date().getFullYear()} Benjamin Warfield Smith</p>
88
</div>
99
</footer>
1010
);

‎src/components/Navigation.js

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,10 +22,9 @@ export const Navigation = () => (
2222
<li><a href="/work" data-toggle="collapse" data-target=".navbar-collapse.in">Work</a></li>
2323
</ul>
2424
<ul class="nav navbar-nav navbar-right">
25-
<li><a href="https://twitter.com/benjaminws" data-toggle="collapse" data-target=".navbar-collapse.in"><i class="fa fa-twitter fa-lg" aria-hidden="true"></i></a></li>
26-
<li><a href="https://github.com/benjaminws" data-toggle="collapse" data-target=".navbar-collapse.in"><i class="fa fa-github fa-lg" aria-hidden="true"></i></a></li>
27-
<li><a href="https://linkedin.com/in/benjaminwarfield" data-toggle="collapse" data-target=".navbar-collapse.in"><i class="fa fa-linkedin fa-lg" aria-hidden="true"></i></a></li>
28-
<li><a href="https://facebook.com/benjaminws" data-toggle="collapse" data-target=".navbar-collapse.in"><i class="fa fa-facebook fa-lg" aria-hidden="true"></i></a></li>
25+
<li><a href="https://github.com/benjaminws" data-toggle="collapse" data-target=".navbar-collapse.in"><i class="fa fa-github fa-lg" aria-hidden="true"></i> GitHub</a></li>
26+
<li><a href="https://linkedin.com/in/benjaminwarfield" data-toggle="collapse" data-target=".navbar-collapse.in"><i class="fa fa-linkedin fa-lg" aria-hidden="true"></i> LinkedIn</a></li>
27+
<li><a href="https://facebook.com/benjaminws" data-toggle="collapse" data-target=".navbar-collapse.in"><i class="fa fa-facebook fa-lg" aria-hidden="true"></i> Facebook</a></li>
2928
</ul>
3029
</div>
3130
</div>

‎src/components/Work.js

Lines changed: 79 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,85 @@ export const Work = () => (
44
<div>
55
<h1>About My Work</h1>
66
<div class='content'>
7-
<div class='callout'>Let&#39;s talk about work. I&#39;ve been part of some special teams, that have build some amazing things.</div>
8-
<div class='callout-sub'>That doesn&#39;t mean I can&#39;t help you.</div>
7+
<div class='callout'>
8+
Introduction
9+
</div>
10+
<div class='callout-sub'>
11+
<p>I am an experienced Software Engineer and Technical Lead, with a focus on Systems Architecture and Software Delivery of web applications.</p>
12+
</div>
13+
<div class='callout'>
14+
Toolbox
15+
</div>
16+
<div class='callout-sub'>
17+
<p>I&#39;m very much a "right tool for the job" kind of person, but here are a few things I like to work with.</p>
18+
</div>
19+
<div class='callout'>
20+
Languages I reach to
21+
</div>
22+
<div class='callout-sub'>
23+
<p>I&#39;ll almost always go to <a href="https://www.python.org/">Python</a> (2 & 3) or <a href="https://golang.org/">Golang</a> for serious backend work, and <a href="https://www.javascript.com/">JavaScript</a> (<a href='https://nodejs.org/'>node.js</a>, <a href='https://en.wikipedia.org/wiki/ECMAScript'>ES5 & ES6</a>) for most front-end applications. I&#39;ll write languages targeting the <a href='http://java.net'>JVM</a> where appropriate as well, having written and maintained applications using <a href='http://java.net'>Java</a>, <a href='http://www.groovy-lang.org/'>Groovy</a>, <a href='http://jruby.org/'>JRuby</a>, and <a href='http://clojure.org/'>Clojure</a> for instance. I&#39;m also deeply familiar with <a href='https://www.ruby-lang.org/'>Ruby</a>.</p>
24+
</div>
25+
<div class='callout'>
26+
Tools I reach to
27+
</div>
28+
<div class='callout-sub'>
29+
<p>I prefer to use <a href='http://boto.cloudhackers.com/en/latest/'>Boto</a> (2 & 3), <a href='https://aws.amazon.com/sdk-for-go/'>AWS SDK for Go</a>, <a href='https://aws.amazon.com/sdk-for-java/'>AWS SDK for Java</a> when doing cloudy things. I like <a href='http://flask.pocoo.org/docs/0.10/'>Flask</a> (python), <a href='https://golang.org/pkg/net/http/'>"net/http"</a> (go) and <a href='https://ratpack.io/'>ratpack</a> (java) for building APIs. You can do so much with data using <a href='https://www.postgresql.org/'>PostgreSQL</a> and <a href='https://aws.amazon.com/redshift/'>Redshift</a>. <a href='https://www.ansible.com/'>Ansible</a> is my goto for configuration management, but I’m also very familiar with <a href='https://www.chef.io/chef/'>chef</a> & <a href='https://puppet.com/'>puppet</a>. I love <a href='https://www.hashicorp.com/'>Hashicorp</a> Tooling for a number of infrastructure needs. <a href='https://facebook.github.io/react/'>React</a> or <a href='https://github.com/developit/preact'>Preact</a> are my favorite for rich for front-end applications. I usually use <a href='http://www.vim.org/'>VIM</a>, <a href='https://atom.io/'>Atom</a>, or <a href='https://www.jetbrains.com/idea/'>IntelliJ IDEA</a> CE for text and code editing.</p>
30+
</div>
31+
<div class='callout'>
32+
Sr. Software Engineer @ <a href="https://www.timshel.com/">Timshel</a>
33+
</div>
34+
<div class='callout-sub'>
35+
<p>
36+
I was part of the initial team hired to greenfield a new platform to support the needs of a presidential campaign. I helped build and lead our DevOps team. I was a key engineer in the launch of the campaign website for Hillary Clinton. Our team built and managed a highly scalable infrastructure on Amazon Web Services using modern tools and principles.
37+
</p>
38+
<p>
39+
Being one of the first onboard, I was tasked with designing and building initial iterations of the infrastructure, including our deployment pipeline, configuration management, as well as tooling to support immutable deployments of microservices & front-end web applications. Most of our tooling is built in Python, Golang, Java/Groovy, and React.
40+
</p>
41+
<p>
42+
As a group we are driven to empower developers to be responsible for all aspects of their application, from code on their machine, to deployments, metrics, and dashboards. The tooling we provide allows developers to bootstrap an application and deploy it within minutes, with minimal effort or configuration. Applications are scalable, monitorable, and deployed redundantly by default.
43+
</p>
44+
<p>
45+
Throughout the campaign I was key in supporting the engineering team for Hillary Clinton, who used our tooling extensively. As we grew I assisted in mentoring other engineers on good practices and helped guide them on technology decisions.
46+
</p>
47+
</div>
48+
<div class='callout'>
49+
Systems Administrator @ <a href="https://www.python.org/psf/">The PSF</a>
50+
</div>
51+
<div class='callout-sub'>
52+
<p>I worked closely with other PSF team members to stabilize the PSF infrastructure, largely focused on the infrastructure around the PyPI software repository services.</p>
53+
</div>
54+
<div class='callout'>
55+
Sr. Systems Engineer @ <a href="https://www.dreamhost.com/">DreamHost</a>
56+
</div>
57+
<div class='callout-sub'>
58+
<p>As lead infrastructure engineer for the dreamhost.com website I implemented a new deployment strategy utilizing system packages, and source control tagging. I worked to implement a CDN to scale static assets. Subsequently I built tooling to manage the assets, as well as interactions with the CDN APIs.</p>
59+
<p>I was also responsible for DreamHosts large scale logging infrastructure, implementing ELK (ElasticSearch Logstash Kibana) before ELK was a thing. This included designing and implementing a new deployment strategy for the cluster.</p>
60+
<p>While here I implemented testing and continuous integration of configuration management code, written in Chef, using Test Kitchen and ServerSpec. </p>
61+
</div>
62+
<div class='callout'>
63+
Software & DevOps Consultant @ <a href="http://the-refinery.io/">Designing Interactive</a>
64+
</div>
65+
<div class='callout-sub'>
66+
<p>As one of the first hires at this successful design firm, I wrote a lot of web applications, helped to establish standards, and had a lot of face-time with our clients. Our backend applications were largely developed in Ruby on Rails or Sinatra, while our front-end mostly utilized Backbone and Ember. I was a key engineer in making design decisions to best meet client needs.</p>
67+
<p>As an early adopter of DevOps principles, I pushed them pretty hard internally and where applicable to client needs. The merits of this approach were recognized and adopted by several of our large clients, and worked well with Designing Interactives design first principles.</p>
68+
</div>
69+
<div class='callout'>
70+
DevOps Lead @ <a href="https://web.shootq.com/">Pictage</a>
71+
</div>
72+
<div class='callout-sub'>
73+
<p>As DevOps lead I was responsible for infrastructure and operations for a newly acquired product, <a href="https://web.shootq.com/">ShootQ</a>.</p>
74+
<p>I led a team to coordinate and execute moving the entire infrastructure for the product from a virtualization host, to a company owned data center. I led this same team to execute infrastructure, application, and data work to move all applications from MySQL to PostgreSQL.</p>
75+
<p>I designed and implemented configuration management of infrastructure using Chef, and also built an improved deployment pipeline for application code.</p>
76+
<p>I worked to integrate with existing Web Operations team tooling and processes, while introducing new tooling and processes to them.</p>
77+
</div>
78+
<div class='callout'>
79+
Systems Administrator @ <a href="http://www.americangreetings.com/">American Greetings</a>
80+
</div>
81+
<div class='callout-sub'>
82+
<p>As System Administrator I was responsible for a number of services, including management of NetApp filers and Falconstor appliances. I was responsible for build, configuration, and maintenance of Linux web servers, application servers, and payment processing nodes. I also worked closely with our cluster of F5 BigIP load balancers, and Content Delivery Networks on Akamai and Level 3.</p>
83+
<p>In working tightly with our development teams, I was able to help improve our development environment stability and lower deployment times, assisting with implementing and developing new technology solutions in a more timely manner.</p>
84+
<p>I was key in development of new configuration management scripts in Perl/Python/Shell, further scaling and automating the management of our large installation. I also assisted in on-call, networking issues, and hardware installation at remote data centers.</p>
85+
</div>
986
</div>
1087
</div>
1188
);

0 commit comments

Comments
 (0)