-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathindex.htm
258 lines (246 loc) · 22.2 KB
/
index.htm
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
<html>
<head>
<!--Import Google Icon Font-->
<link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet">
<!-- Compiled and minified CSS -->
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/materialize/0.97.1/css/materialize.min.css">
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.4.0/css/font-awesome.min.css">
<!--Import jQuery before materialize.js-->
<script type="text/javascript" src="https://code.jquery.com/jquery-2.1.1.min.js"></script>
<!-- Compiled and minified JavaScript -->
<script src="https://cdnjs.cloudflare.com/ajax/libs/materialize/0.97.1/js/materialize.min.js"></script>
<link href='https://fonts.googleapis.com/css?family=VT323' rel='stylesheet' type='text/css'>
<script>
$(document).ready(function(){
$('.scrollspy').scrollSpy();
});
</script>
<!-- This is our local style sheet. -->
<link rel="stylesheet" href="css/style.css">
<script src="js/scripts.js"></script>
<!--Let browser know website is optimized for mobile-->
<meta name="viewport" content="width=device-width, initial-scale=1.0"/>
<meta name="theme-color" content="#2196F3">
<!-- Windows Phone -->
<meta name="msapplication-navbutton-color" content="#2196F3">
<!-- iOS Safari -->
<meta name="apple-mobile-web-app-status-bar-style" content="#2196F3">
<title> Rainer Paskiewicz, Developer, Writer, and Occasional Blacksmith</title>
</head>
<nav class="blue hide-on-med-and-up fixed">
<h4 class="imaged">Rainer Paskiewicz </h4>
</nav>
<body>
<div id="credits" class="hidden">
<div class="content">
<span id="credits-message" class="message"></span><span class="typed-cursor">_</span>
</div>
</div>
<main>
<div class="waterfall blue white-text hide-on-med-and-up">
<h5>Writer</h5>
<h5>Developer</h5>
<h5>Occasional Blacksmith</h5>
<span class="contact-info"><a class="white-text" href="mailto:Email: [email protected]?subject=Job"> <i class="small material-icons">email</i>[email protected]</a></span>
<span class="contact-info"><i class="small material-icons">phone</i><a class="white-text" href="tel:12035339005"> (203)533-9005</a></span>
<p>Hi. Hello. Welcome. Greetings. Etc. You have landed on my little webpage. Here you'll get a glimpse of my past, my opinions on the languages and frameworks I've worked in, and find ways to contact me. </p>
</div>
<!-- Hey, you looked at my source code, good job you! First off, if you've noticed anything wrong with this site, please feel free to email me at [email protected]. I'll get right on fixing it and you'll get a heartfelt thankyou. This site is hosted by GitHubs amazing GitHub Pages feature. If you want to know more, you can find out at the link right here: https://pages.github.com/ The CSS/JS framework you see litterting the site with style is known as Materializecss. Its a great library that gives you Google's Material Design without a lot of overhead or having to use Polymer(Which isn't really done yet). You can find out more about them here: http://materializecss.com/ Finally, a BIG thank you to the guys and gals over at Atom.io. Not because they helped in any way, but because their editor helps me every day get my work done faster. -->
<div class="container">
<div class="row">
<div class="col hide-on-small-only m3 l2">
<div class="toc-wrapper pinned">
<img class="responsive-img circle" src="images/logo.svg">
<ul class="section table-of-contents card">
<li><a href="#introduction">Introduction</a></li>
<li><a href="#experience">Experience</a></li>
<li><a href="#languages">Languages</a></li>
<li><a href="#frameworks">Frameworks</a></li>
<li><a href="#education">Education </a></li>
<li><a href="#certificates">Certificates </a></li>
</ul>
</div>
</div>
<div class="col s12 offset-m3 m9 offset-l2 l10">
<div id="introduction" class="section scrollspy hide-on-small-only">
<!-- <div class="row "> -->
<!-- <div class="col s12 m1"> <img class="responsive-img" src="images/logo.svg"></div> -->
<!-- <div class="col s12 m10"> -->
<h1 class="imaged ">Rainer Paskiewicz </h1>
<!-- </div> -->
<!-- </div> -->
<h6> Or why I put this together in a few hours</h6>
<p>Hi. Hello. Welcome. Greetings. Etc, etc, etc, etc. Welcome to my little resume webpage. Its not super long, or overly technical. But it does give you a quick glimpse into who I am professionally, as well as the kind of work I do. </p>
</div>
<div id="experience" class="section scrollspy">
<h5 class="card-panel blue darken-1 white-text"> Employment History</h5>
<ul>
<li>
<h5>Technical Lead, Checkmate Creations</h5>
<div class="chip">
July 2016 -> Now
</div>
<p>Checkmate Creations. We solve problems with a mix of fire, magic, and good old fashioned code. This means we craft all manner of solutions. And who makes sure that all the cogs keep spinning harmonously? Well, part of that is me. Not all of it by any means, we're a team of dedicated developers, but my job is to make sure the team is kinda moving in the same direction in terms of technology. I also manage our servers. </p>
</li>
<li>
<h5>Developer, DCPHP L.L.C</h5>
<div class="chip">
2011 -> Dec. 2015
</div>
<p>While working at DCPHP I grew from a basic data entry and QA member to a Lead Developer with all the responsibilities and the skills the position entails. The challenge of meeting the needs of a diverse and multifaceted client base drove me to broaden not only my technical skills, but my understanding of client's needs and wants.</p>
<strong>Accomplishments</strong>
<ul class="collection">
<li class="collection-item">Shepherded the company's in house software through several major language and library updates.</li>
<li class="collection-item">Expanded company's development base from a purely LAMP structure to include more modern development languages and paradigms.</li>
<li class="collection-item">Introduced, developed, and deployed a client license control library for use in company projects.</li>
<li class="collection-item">Expanded my personal understanding of development languages to include those still under development(GO, etc) to keep the company aprised of upcoming trends in web development.</li>
</ul>
<strong>Responsibilities</strong>
<ul class="collection">
<li class="collection-item">Development and design of Applications to fit client's needs, using various combined development tools and enviroments.</li>
<li class="collection-item">Administration of Linux and Windows based servers.</li>
<li class="collection-item">Management of various code revision solutions(Git,Subversion) on multiple platforms.</li>
<li class="collection-item">Deploy and manage LAMP environments to both cloud based and local hardware.</li>
<li class="collection-item">Database Structure design, including embed business logic.</li>
<li class="collection-item">API design and management</li>
</ul>
</li>
</ul>
</div>
<div id="languages" class="section scrollspy betterCarded">
<h5 class="card-panel blue darken-1 white-text"> Languages </h5>
<p> In my time as a developer I've picked up a wide variety of languages. Sometimes it seems as if each new project requires learning a new language or design paradigm. Bellow is a short list of the languages I've come across, and what I think about them. </p>
<ul class="collapsible" data-collapsible="accordion">
<li>
<div class="collapsible-header">PHP</div>
<div class="collapsible-body"><p>PHP, some people love it. A lot of people hate it. My opinion falls someplace in between. PHP runs a lot of the net. You can't go very far without tripping over a site that has its backbone rooted in this wide spread language. But it's not without its faults. My experience allows me to easily anticipate these issues, and guide the project around them. </p></div>
</li>
<li>
<div class="collapsible-header">Python</div>
<div class="collapsible-body"><p>The other scripting languages turned multipurpose tool, Python is simple, easy to use, and extremely powerful. My go to for quick scripts that have to talk to hardware, its syntax takes some getting used to. </p></div>
</li>
<li>
<div class="collapsible-header">Node.JS</div>
<div class="collapsible-body"><p>Node.JS its a strange one. Its JavaScript, a languages normally reserved for front end web development, deployed for serverside processing. And it's almost completely asynchronous. Normally, these two things would not lead to success. But here were are, in a world were Node has successfully made the transition from neat new fringe language to a real contender in the world of web development. Personally, I love the different approach to the normally stagnant call/response web server.</p></div>
</li>
<li>
<div class="collapsible-header">HMTL</div>
<div class="collapsible-body"><p>What can I say about HTML that hasn't already been said. It's the markup that formats the net. But it's become so much more than that. With HTML5 we've finally got a language that starts to tie together all the other parts of front end web development. And those new input types are just so, so, helpful.</p></div>
</li>
<li>
<div class="collapsible-header">JavaScript</div>
<div class="collapsible-body"><p>JavaScript gets a bad wrap. Some of it deserved, most of it isn't. JavaScript lets you do amazing things, but it doesn't give you the safety net of strong types, or easy syntax that a compiled language would. But for modifying a DOM element there is still no better way to do it than with JavaScript. Or, if Plain Jane JavaScript isn't your thing, then there are some great libraries that make using the power of JavaScript very simple. <!-- NOTE: I'm not going into things like TypeScript or CoffeeScript. --></p></div>
</li>
<li>
<div class="collapsible-header">CSS</div>
<div class="collapsible-body"><p>Cascading Style Sheets are a lot like JavaScript in that they get a bad wrap. But in this case, its some what deserved. Support for features can be spotty, the syntax is unwieldy, and even when you get things right a small change can break your design. But in my time as a developer I've come to respect CSS. It make things look amazing, when user properly. And a finely tuned CSS theme can, and often is, the difference between a professional looking project and something you threw together in an afternoon.</p></div>
</li>
<li>
<div class="collapsible-header">SASS</div>
<div class="collapsible-body"><p>Writing CSS is a pain. Using CSS is not. So that's where SASS comes in. A pre-processor it allows a developer to write an amazing array of styles without having to repeat themselves over and over again. By abstracting the busy work of CSS to variables, functions, and included libraries, it takes the hassle out of creating beautiful CSS. And the hassle out of having to change it later. </p></div>
</li>
<li>
<div class="collapsible-header">SQL</div>
<div class="collapsible-body"><p>The great granddaddy of the relational database languages. Regardless of flavor(MySQL, MSSQL, or ProgresSQL), it has been the gold standard for relation databases since the 70s. And with good reason. It allows for data to be manipulated and standardized quickly, for deep queries to be syntactically plain, and its human readable to boot. However, it does fall victim to issues of complexity from time to time.</p></div>
</li>
<li>
<div class="collapsible-header">MongoDB</div>
<div class="collapsible-body"><p>MongoDB was the first none relational database I came across as a web developer. And you know what, I fell in love. The idea of handling data points as Documents made sense when a relational database seemed overkill. And the easy integration with Node.JS and Meteor didn't hurt things ether. </p></div>
</li>
<li>
<div class="collapsible-header">C++</div>
<div class="collapsible-body"><p>C++ wasn't the first languages I learned. Its wasn't even the second. It wasn't until well into my college career that I was introduce to C++. However, I still find myself going back to C++ to explain issues of Object Oriented Programing and class structure. Its one of the foundations, even more so than C, that I keep coming back to time and time again to explain certain aspects of development.</p></div>
</li>
</ul>
</div>
<div id="frameworks" class="section scrollspy betterCarded">
<h5 class="card-panel blue darken-1 white-text"> Frameworks</h5>
<p> Languages are great. However, you can only get so far on your own. Frameworks allow developers to share a common set of tools. They allow for us share the burden of common tasks that aren't covered by our languages. Sometimes they just make handling content easier. Sometimes they take care of almost all the heavy lifting, leaving you to implement the novel functionality that really matters. Below is a short list of those that I've worked with, and a short story about my time with them. </p>
<ul class="collapsible" data-collapsible="accordion">
<li>
<div class="collapsible-header">Symphony</div>
<div class="collapsible-body"><p>The biggest, and perhaps the most wide spread of the PHP frameworks. Its heavy, but it brings a lot to the table and gets the busy work of setting up site/api/app out of the way so that a developer can focus on functionality. There is a little bloat in the code, but that's not really so strange for a project of such a scope.</p></div>
</li>
<li>
<div class="collapsible-header">Silex</div>
<div class="collapsible-body"><p>Symphony's baby brother. If Symphony is too heavy, but I'm still working with Devs who are used to living in a Symphony world, Silex is my goto micro-framework. Same routing language, similar database management, but without the overhead that comes with a full fledged Symphony install. Also, you can move code up into a full Symphony project without to much refactoring.</p></div>
</li>
<li>
<div class="collapsible-header">Wordpress</div>
<div class="collapsible-body"><p>The most popular CMS out there at the moment. Countless blogs, brochure websites, and social groups run on Wordpress. This has lead the code to become a bit bloated, and made it a near constant target for attack. But, its easy to set up, quick to administer, and simple enough that most end users can handle running it. </p></div>
</li>
<li>
<div class="collapsible-header">Bootstrap</div>
<div class="collapsible-body"><p>Twitter's CSS/JS framework. Made popular as the first framework to really support modern responsive design. However, its rise to fame has caused sites and apps built using Bootstrap to have a very "Bootstrappy" feel to them. This can be overcome with careful design and modification of the underlying SASS/LESS, and you can't beat the speed for prototyping. It's a great framework, that has gained a well earned following from the web development community.</p></div>
</li>
<li>
<div class="collapsible-header">AngularJS</div>
<div class="collapsible-body"><p>Google's monolithic JavaScript library. Based off the idea of letting the data speak for itself, Angular runs a wide gambit of very powerful web apps. Personally I like the fact that data is not longer a second class citizen when it comes to design in Angular. Best suited for single page applications, it is currently my front end of choice.</p></div>
</li>
<li>
<div class="collapsible-header">React</div>
<div class="collapsible-body"><p>Say what you will about Facebook, but they have created one amazingly graceful front end framework. It's slowly becoming a toss up between React and Angular as to which framework is my favorite for front end only work. In the end, it comes down to what I'm doing. For more reactive datasources, I still prefer Angular. For my "statey" data, I like React. We'll have to see what Angular 2 brings to teh table before really deciding. </p></div>
</li>
<li>
<div class="collapsible-header">Meteor</div>
<div class="collapsible-body"><p>The new kid on the block, but rapidly gaining fans in the MEAN development world. The quick development lifecycle, combined with the "install and go" setup has made Meteor one of the fastest growing stacks in recent memory. While there are some questions about issues of scale, only time will tell if these are concerns are founded. In my opinion, still the best way to get an app up and running in an afternoon.</p></div>
</li>
<li>
<div class="collapsible-header">Django</div>
<div class="collapsible-body"><p>The more popular web framework for Python, I've built a few personal projects using Django. Its powerful, but also a little weighty. It brings a lot to the party, and it would still be my suggestion if you want a framework for a web project backed by Python.</p></div>
</li>
<li>
<div class="collapsible-header">Flask</div>
<div class="collapsible-body"><p>The best micro-framework for Python, hands down. If Django is Symphony, this is Silex. Small, light weight, and simple to use, Flask is a great framework for quick projects or those with a limited scope. Also, the easy to follow documentation is a real plus for people just getting started in the Python world of web development.</p></div>
</li>
</ul>
</div>
<div id="education" class="section scrollspy">
<h5 class="card-panel blue darken-1 white-text">Education</h5>
<div class="card">
<div class="card-image">
<img src="images/chopped-seal.png">
</div>
<div class="card-content">
<h5>University of Connecticut College of Liberal Arts</h5>
<p>Bachelor of Arts: English 2010</p>
</div>
</div>
</div>
<div id="certificates" class="section scrollspy">
<h5 class="card-panel blue darken-1 white-text">Certificates</h5>
<div class="card">
<div class="card-content">
<h5>A100</h5>
<p>Certified Developer, Winter 2016</p>
</div>
</div>
</div>
</div>
</div>
</main>
<footer class="page-footer blue">
<div class="container">
<div class="row">
<div class="col l6 s12 hide-on-small-only">
<h5 class="white-text">Thank you!</h5>
<p class="grey-text text-lighten-4">You scrolled all the way to the bottom of my page. That means you either really like what you saw, or accidentally held down the page down button. Either way, thank you.</p>
</div>
<div class="col l4 offset-l2 s12">
<h5 class="white-text">Contact Me</h5>
<ul>
<li><spanc class="grey-text text-lighten-3"> Email: </span><a class="grey-text text-lighten-3" href="mailto:[email protected]?subject=Job">[email protected]</a></li>
<li><spanc class="grey-text text-lighten-3">GitHub:</span> <a class="grey-text text-lighten-3" href="https://github.com/LibertyBeta"> LibertyBeta </a></li>
<li><spanc class="grey-text text-lighten-3">phone: <a class="grey-text text-lighten-3" href="tel:12035339005">(203)533-9005</a></span></li>
</ul>
</div>
</div>
</div>
<div class="footer-copyright">
<div class="container" onClick="playCredits()">
© 2015 Copyright Rainer Paskiewicz
</div>
</div>
</footer>
</body>
</html>