Introductory Portrait
Good day, sir or madam:
My name is Evan William Gretok, and I am a student of computer engineering technology at the University of Pittsburgh at Johnstown. This digital portfolio is a collection of coursework for you to sample and peruse, primarily showcasing professional writing samples for various courses. My discipline requires highly refined skills in written and verbal communication, and I hope you will find my work from various courses in the past several years to be proof of my growing skill-set. From formal laboratory reports, to research papers, to design proposals, to thorough evaluations; the professional writing requirement for engineering is diverse and extensive.
I am deeply passionate about programming, electronics, and computer hardware. I have completed coursework in advanced mathematics, physics, and engineering principles, and programming. I have professional experience in information technology, user services, web application development, software testing, and databases. I am currently applying my knowledge and enthusiasm to data and information structures, digital electronics, advanced programming concepts, and embedded systems. I identify as a “maker,” and am deeply interested in the application of technology in solutions to everyday problems. I am detail-oriented, focusing not only on the solution, but on the presentation and refinement of that solution. I am an imaginative, hands-on forward thinker looking to continue learning and growing, wherever my career takes me.
I consider myself a student who is looking for not just a tested learning, but a knowledge and experience that is applied to reach a concrete goal and make a difference in people’s lives. I take my academic and professional pursuits very seriously, but I also acknowledge that my degree as well as any position I will serve in is not for me. I look not to boost my own prestige, but to contribute positively to a body of professionals who seek to do their best work for the sake of the customer, the public, and the world. I am committed to upholding the ethics, responsibilities, and integrity demanded by my field to the highest degree. I aim to act for the sake of others, using my experience and abilities to better my community and the lives of the people in it.
If you have any questions about myself or the material listed here, please do not hesitate to contact me using the information in my resume. Thank you for your time and consideration. Have a remarkably pleasant day.
Evan William Gretok
Student of Computer Engineering Technology
University of Pittsburgh at Johnstown
Sunday, December 13, 2015
A Presentation of Professional Writing
Tuesday, December 1, 2015
Building a Professional Portrait
Wednesday, November 18, 2015
Life Is Elsewhere: What I Am Really Doing Here
Wednesday, November 11, 2015
A Symbiotic Proposal
Wednesday, November 4, 2015
Being a Professional Dreamer
In our proposal, my group is assuming the role of a cross-department committee to propose a course of action for the yearly computer upgrades of a graphic design and video editing firm. In such a firm, the "upgrades" being considered are remarkably expensive. We are proposing the acquisition of over fifty thousand dollars of computer workstations and related equipment, not to mention the expenses of specialty software licensing. In a class setting, it is easy to stand in front of a group of disinterested students (at various levels between asleep and awake, no doubt) and make such requests. I could hardly imagine, however, being in the position to formally make this request from the financial department or CEO of a large and intimidating corporation. It would be hard enough to do in writing, let alone forcing oneself to make eye contact in a direct presentation.
We have discussed needs, values, and attitudes in class, important considerations for any proposal. It is immediately apparent to me that a core value of the financial department is money, and requesting so much may indeed put that value in jeopardy. Their needs and values, and their responsibilities to the company, are to maintain financial stability and adherence to budget. Their attitudes may reflect negatively to such an expensive project, not understanding the advantage over cheaper alternatives. I suppose this is the advantage we have allowed ourselves by considering an internal proposal on upgrades that are required either way. It is easier to consider the worth of an investment when money will be spent either way. We can then focus on how the expense will improve productivity, quality, and reliability, also highlighting ways we have been able to reduce costs.
In this manner, I can see how each and every proposal serves as a persuasive document. Every member of the groups both proposing and considering has something to contribute, but not everyone will maintain the same level of understanding toward all topics. The proposal must be an accessible document that forms a clear path from each member, through, in this case, more technical decisions, passing close to the company's overall mission, and concluding at a point where the goals of the whole party are met. This comes not without conflict and compromise, more considerations the proposal must work to meet. I suppose the beauty of a proposal may be the sense that it isn't set in stone. The bulk of the work is perhaps in the final tailoring to the organizations preferences and the follow through to accomplish the outlined goals.
Wednesday, October 28, 2015
Further Discussion and Elaboration of Press Release
I was initially at a loss for what direction to take on this assignment. I typically don't highly value the contributions of mobile devices. I have more of an interest in larger systems. Considering their current popularity and relevance however, I wanted to explore their future presence further. The irony is that devices like this may take a nearly unrecognizable form by the launch year of the Ouevre, 2026. Theories range from wearable technology to embedded physical or neural components: a fusion of man and machine. It seemed a bit overwhelming to try to determine success criteria for a venture like that, so I decided to stay reasonably close to the current format.
The press release is of surprising importance for someone in my field. In particular, working with the press kit in its entirety has made me see how much an engineer could contribute, including detailed diagrams, specification sheets, and functional documentation. It is the job of the marketing and communications team to build interest and capture media attention. However, when dealing with a highly technical product, an engineer may very well provide the translation from incomprehensible technology acronyms to exciting, press-worthy features. It is difficult to explain quantified benefits, how much of an upgrade something is, but once that big step is taken, it can become another lure to the public.
I wanted to add a bit more engineering flare to the press kit. I had begun working on scale perspective drawings, dimensioning the unit and documenting ports. Unfortunately, with other class obligations, the time I had to spend has been cut short. I would have loved to delve deeper into future technologies like neural linking or holographic projection, but the amount of fabrication that would have been necessary would have made the press release even less accessible to a public audience. To be honest, it is already a bit borderline in that regard. It would have been interesting to further explain my ideas on the heuristic awareness engine or embedded transparent solar panels. Given enough space, time, and incoherent jargon, I could have made it make sense. Brevity is essential, though; something I am still learning.
Tuesday, October 20, 2015
Orwellian Concision and Memes
Wednesday, October 14, 2015
Code <= Art != Professional Writing
void IFind(Myself, AllIHoldDear) {
int ErFacing = 2; //Man and Machine
float IngInACommonSpace = 3.1415926535897932384626433;
for( int erference = 0; erference <= will; erference++) {
printf("There is %s beyond this.", something);
scanf("Meaning to be found: %s", &somethingWorthFinding);
thereIs(Order); thereIs(Chaos);
theTruth = Order > Chaos;
thereIs(B3@uty); thereIs("p_u_r_p_o_s_e");
if( thereIsNothing > This ) whatMoreCanISeek--;
elseif( thereIsNoPurpose ) whyOrder = "at all?";
else //I
{
return home;
}
}
}
I have written thousands of words in the last several weeks that do not exist in prose. They cannot contribute to a technical report. They do not communicate heartfelt messages. Whether or not they qualify as professional writing is a dilemma. However, there is something about them: something I have always appreciated, but have barely come close to fully understanding.
In my Digital Humanities class, several days ago, Doctor Jeremy Justus was discussing the notion of code as language. Digital Humanities has been an eye-opening course in the exploration of an intersection between my disciple, sometimes a logically and mathematically constructed wasteland, and points of humanity and deeper meaning, constructed or not. We have explored numerous instances of media created by and through code, experienced only as digital artifacts, ultimately ones and zeros, that are still remarkably capable of leaving profound impressions on the psyche.
Something Doctor Justus said resonated with me. In the beginning, or so it is written, the world was spoken into existence. Meaning was understood to be intrinsic to language. Understanding has since shifted to an arguably more educated view that meaning is constructed from independent experience and is not necessarily universal. In the digital realm, however, these languages of programming are clearly defined. Code shapes the digital landscape, from human-readable high-level commands to binary and hex based machine code. Within a digital space, code is the language of God.
Is code language? It must be. Does that code hold the same meaning as the encrypted messages it carries? Only to those who dare to decipher it. To them, to us, it is a sort of artistic medium, a condensed representation of meaning lost in transmission. Proof of our existence beyond that of the machine. In my pursuit of the knowledge of computer engineering, perhaps I seek to emulate my Creator. At least I would like to think so.
/*
*The ultimate irony is that the function declared above is void. It can return nothing. There can be * no return home... I'm gonna go nerd out in the corner for a bit.
*/
Thursday, October 8, 2015
Accessibility by Design
Sunday, September 27, 2015
The Finer Aspects of Evaluation and Translating Technicality
Saturday, September 19, 2015
When? Just About All the Time.
Sunday, September 13, 2015
An Educator and an Engineer
If I had any doubts about the need for professional writing skills in my discipline, Professor Stan quickly expunged them. He thoroughly outlined his use of professional writing, providing a double perspective as both a professional and an educator. He noted that he typically expects to spend one to two hours a day on writing alone. Much of this is rooted in the need for documentation of nearly all work that is done. Professor Stan was very clear in his mindfulness that “communication in written form…is essential to work with others in the engineering field.”
I had written much previously for Professor Stan in terms of technical laboratory reports, so that was something I wanted to discuss more in depth with him. My concerns were in the satisfactory realization of both professional and public level writing, as well as the balance of technicality and “creativity” in these reports. Professor Stan was encouraging in his experience that, with time and practice, the ability to transition between writing for technical individuals and the general public will become seamless. He confirmed that one should develop the aptitude to write with both sides in mind. Professor Stan also commented that even fact-filled technical reports “can be made to be more enjoyable to read, without diluting the details, by adding some creative ideas or thoughts into the report. It is always good to show how the information in these types of technical reports [is] applicable to real world situations.”
I deeply enjoyed my exchange with Professor Stan and have taken much away from it. I have heard it said that an engineer is the bridge between theory and reality. Engineers must balance feasibility, practicality, and the latest in technology, while effectively communicating with teams of experts at the concept and execution ends of the spectrum, to bring about the new. This interview aided in my continued realization of how professional writing skills, whether for documentation or communication, are absolutely necessary for future success in this field.