Craig Macomber

Hi, I'm Craig Macomber, and this is my Advanced Technical Writing and Oral Presentation portfolio. It's just like my other portfolio except way less exciting. Perhaps this ones got a bit more style though. Enjoy!

Herein ye shall find proof of my wall of text generating capability, and how it transcends english to the realm of idea transcription and presentation. This portfolio consists of a collection of walls of text, and annotations about how they show I'm awesome. I'll walk you through it all, and make sure you understand; thats what the annotations and this introduction are for.

You see, I'm a software engineer, and software is made out of transcribed ideas. Said transcriptions need to be documented with walls of text, and are walls of text themselves, so this is all quite relevant. If you want to hire my skills though, you will have to wait. I'm booked through fall 2012 getting my official Bachelor of Science in Computer Engineering, and the summer is filled by my Google internship. So, if you want some of my (awesome) time, start bidding on times starting next spring, ok?

Artifacts: Walls of text, and how they make me awesome

This portfolio

This portfolio shows my ability to efficiently use recursive references, and even refer to those references recursively. Understanding recursive referencing is important, as some texts, such as this one, employ them, but thinking to use them, and doing so efficiently and effectively is the true talent on display here. You want a software engineer who thinks of and tries approaches other miss, and recursive patters often fall into this category. This sentence itself is proof I fall into that category.

Apparently this portfolio can't count as an artifact due a lack of popular understanding of the elegance of recursion, but don't worry; like any good engineer, I have a solution already prepared: four more artifacts.

That portfolio

I have another portfolio, and it contains some fantastic walls of text. Like here, it shows my ability to construct annotations, but its artifacts also show my ability to carry out many interesting tasks. There is some pretty sweet things there, so feel free to become rather distracted browsing it. It is a bit out of date though: it's lacking in recent awesomenesses.

My other portfolio shows my ability to do reflective thinking and documenting of my own work. This is an important skill for any engineer, because we need to continually refine our procedures and designs. And even if our work were perfect, whats the point of perfect work if you lack the ability to reflect on and enjoy (and gloat about) its perfection? But there is also an even more meta level here: this annotation shows my ability to reflect on my reflection. Perhaps this reflection does not cover too much of how my other portfolio could be improved, or what was done well, but at least this sentence does exactly that about my reflection on this reflection which now demos my ability to reflection on my reflection's reflection. Perhaps the original portfolio could be considered a reflection on its artifacts adding yet another layer.

I also have the ability to mix many different skills: just like the projects in my other portfolio show this, this annotation shows my ability to mix the previously mentioned recursion with reflection. With the ability to mix such complex skills, and transcribe it all to text, I clearly have the ability to produce excellent code, and my reflection skills referred to and demonstrated herein demonstrate my ability to document my works, such as code.

My Resume


Remember that Google internship I mentioned? I scored that with this resume. Well not quite: they had no interest in cover letters, or an objective statement, so those weren't in the version I gave them. This careful catering to two different groups shows my ability perform "hoop jumping": the completion of mostly meaningless and unnecessary tasks to achieve a goal. It also shows that I can write up quality and effective documents when it actually matters, since I wouldn't have gotten the job if my resume sucked. In-fact, it was as good as necessary: it got me my first choice job. Thus I can do sufficiently good work, and by definition, no one needs better than that right?

Project Proposal


I have the necessary skills to churn out massive amounts of documentation for things I don't care about. This is demonstrated by my production of the "Technical Information" section of this project proposal. It was my second project sustainability project proposal for a technical writing class on nuclear power in the last year. With the area of focus being outside my field, and the level of detail being less than my knowledge, combined with having written basically the same thing before, this was truly an excellent example of boring work I did not care about. Despite this, I was able to focus, and in and churn out this large volume of work in a single sitting. This is incredibly important skill for a software engineer. It's good to care about your work, but sometimes you won't, especially when documenting stuff. Someone who is not effective at producing documentation has no right to produce code, since undocumented code is an atrocity waiting to bring wrath, and often unemployment, upon the author. But since I have the ability to produce such walls of text, you have nothing to fear. Hire me and I'll bring the joy of comprehensible documented code to your code base for all future employees to enjoy. Hiring me is an investment in your future!

Lab Report

My Wire Finder Lab Report shows my ability to collaborate on project, and work on technical projects outside my core field. I did most of the writing and formatting for that report, as well as put together that great video. Working tightly with my partner on the project, I demonstrated my ability to combine and express collective ideas in the form of successful and entertaining devices, while extending my knowledge and skills. With the simple goal of locating outlets by their electric fields, we went above and beyond producing the longest ranged sensor in the class. If you want a member on your team to drive it toward unprecedented success, while developing the skills needed to accomplish such successes, you want me.

Collectively these artifacts show that I can work with others, and produce successful, well documented projects while employing a variety of complex reasoning and analysis skills, even if I don't care about the project. If you want experience, I have years of that too! Really, what more could you want in a software engineer?

Copyright © 2011-2013 Craig Macomber