<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jeff Benning on Medium]]></title>
        <description><![CDATA[Stories by Jeff Benning on Medium]]></description>
        <link>https://medium.com/@jeffbenning?source=rss-84f47a6786f1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*PLL59xcgXOq1PiHo.</url>
            <title>Stories by Jeff Benning on Medium</title>
            <link>https://medium.com/@jeffbenning?source=rss-84f47a6786f1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:29:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jeffbenning/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Cool Stuff In Engineering No. 9]]></title>
            <link>https://medium.com/first-engineering-job/cool-stuff-in-engineering-no-9-8aecade3e3a1?source=rss-84f47a6786f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/8aecade3e3a1</guid>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Jeff Benning]]></dc:creator>
            <pubDate>Sun, 26 Feb 2017 00:58:43 GMT</pubDate>
            <atom:updated>2017-02-26T00:58:43.887Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J0fmU7sXz71YLESevRl_bQ.png" /></figure><p>Every day we store information, pictures, videos, music and other digital media on a computer in the form of data. Have you ever stopped to think how this works? Maybe you have and you might not have liked what you found. It’s incredibly complex and often the explanations are no better. I’m going to try and break it down as simply as possible right here.</p><p>There are actually three parts to storing data on a computer, all of which you are probably aware of but may not know how they work. The three parts are</p><ol><li>Hard Drive</li><li>Ram</li><li>Cache</li><li>BIOS</li></ol><h3>How Do They Work?</h3><p>Let’s break it down</p><h3>The Hard Drive</h3><p>I’m going to steal Wikipedia’s explanation because it is just so darn good.</p><p>“A [<strong>…]hard drive […]</strong> is a data storage device that uses magnetic storage to store and retrieve digital information using one or more rigid rapidly rotating disks (platters) coated with magnetic material.”</p><p>Well that’s what it physically is. Now here’s how it works.</p><p>When you store data in a hard drive, binary bits are set by a read and write head that magnetize specific parts of the disks. This represents a series of bits (1’s and 0’s) so the data can be interpreted later.</p><p>The advantages of a hard drive are its capacity and ability to store data without power. Its disadvantage are its read and write times, mostly because it requires the print head to physically move and the disk to actually spin in order to write data. These mechanical operations take time.</p><h3>Random Access Memory (RAM)</h3><p>RAM is installed in a computer in the form of sticks which are fairly easily replaceable and upgradeable. Modern RAM takes the form of integrated circuits, which is basically a tiny chip that contains a whole bunch of tinier electric circuits.</p><p>It works by storing frequently used programs from the hard drive onto it to reduce read times. Since the RAM has no moving parts, it doesn’t have the same physical limitations as the hard drive does. It doesn’t store data for long time use, however. As you open and close programs, older programs are cleared from the RAM in order to store the new ones. If you have too many programs open at once, you run out of RAM and you’re computer runs very slow, or even crashes.</p><p>Its advantages are its quicker read/write times. Its disadvantages are its size limit and the fact that when power is removed from it, the data is lost.</p><h3>Cache</h3><p>Cache is memory that is physically included on the processor. It can have several levels referred to as L1, L2, etc. and is the fastest memory on the computer. The programs that are used even more commonly than what’s on the RAM are stored here. This is why if you open a program right after you close it, it opens faster than if you close it and open it tomorrow.</p><p>The biggest advantage is how fast it is to read/write speed while the disadvantage is it’s small size.</p><h3>BIOS</h3><p>I need to throw this in here for completeness. The BIOS, or Basic Input/Output System, is the firmware for how the computer will identify and test its hardware and for how it will load the operating system. Firmware means that is was built in with the motherboard, where the BIOS is stored, and cannot be changed. At least not easily.</p><h3>How They Work Together</h3><p>The purpose of all computer memory is to store data for future use. The only way this can be done is within the hard drive because that is the only memory that can store data in the power-off state. So when you hit that power button for the first time, the first thing that happens is that the BIOS turns on and performs hardware checks. It then loads the operating system from the hard drive.</p><p>The information for the operating system is stored in the RAM and any startup programs are read into the RAM and then the cache. This is why disabling startup programs can make your computer start faster.</p><p>Now when you start a program, the computer first looks to see if it is in the cache. If it is, it load it super-fast! If not, is looks at the RAM. If it is still not there, it gets it from the hard drive. So it looks in the fastest but smallest memory and moves down to the slowest but largest memory.</p><p>This is also why a solid state drive is so much faster than a hard drive. Since most of the programs are stored on this drive, the computer doesn’t have to worry about the physical movement of the hard drive in order to find the information it wants. It’s like reading a giant stick of RAM (kind of but not exactly).</p><p>So that’s a quick rundown of what your computer is really doing behind the scenes. Hopefully this was simple but accurate. You could read pages and pages on this but if you really want to learn more, read the Wikipedia’s!</p><p><a href="https://en.wikipedia.org/wiki/BIOS">BIOS</a></p><p><a href="https://en.wikipedia.org/wiki/Cache_memory">Cache</a></p><p><a href="https://en.wikipedia.org/wiki/Random-access_memory">RAM</a></p><p><a href="https://en.wikipedia.org/wiki/Hard_disk_drive">Hard Drive</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8aecade3e3a1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/first-engineering-job/cool-stuff-in-engineering-no-9-8aecade3e3a1">Cool Stuff In Engineering No. 9</a> was originally published in <a href="https://medium.com/first-engineering-job">First Engineering Job</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interview — Circuit Scribe]]></title>
            <link>https://medium.com/first-engineering-job/interview-circuit-scribe-c4e66ae427b?source=rss-84f47a6786f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4e66ae427b</guid>
            <category><![CDATA[education]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Jeff Benning]]></dc:creator>
            <pubDate>Thu, 23 Feb 2017 01:07:13 GMT</pubDate>
            <atom:updated>2017-02-23T01:07:13.376Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Nr-VX6oFo6xl3-dauigWw.png" /></figure><p>Electricity seems to be the magic of engineering. You know it works. You use it every day. But when you run into a problem that you don’t know how to solve, and it seems to be electrical, you run to the nearest EE to see if they can work their magic once again.</p><p>Circuit Scribe is aiming to change this, and they are doing it in a very creative way. They have developed a unique product that will teach you the fundamentals of electric circuits. Before it was Circuit Scribe, Ph.D. students Analisa and Brett developed a conductive ink at the University of Illinois Urbana-Champaign that could carry electricity. They incorporated this technology into a pen that essentially lets you <em>draw</em> wires. You can now connect various electrical devices like fans, motors, and switches to make real, working circuits just by drawing lines on regular paper.</p><p>After an insanely successful <a href="https://www.kickstarter.com/projects/electroninks/circuit-scribe-draw-circuits-instantly">Kickstarter campaign</a> that got funded almost 8 times over, they have released several kits that make learning electronics fun.</p><p>I got the pleasure of interviewing Valerie Nogueira, the Director of Product Planning at Circuit Scribe and an electrical engineer. Check out our interview!</p><p><strong>Can you give a brief description of what it is your company does so my readers can hear it firsthand?</strong></p><p>Electroninks Writables developed the Circuit Scribe pen. Circuit Scribe is a conductive ink pen which allows users to draw circuits on paper. Since the ink is conductive, you can build prototype circuits on paper with standard surface mount components. However, our company also developed an extremely tactile module library to go along with the pen as a way to lower the barrier of entry into electronics and allow users 8 and up to start exploring circuits no matter what their level of previous knowledge is.</p><p><strong>What is your role in the company and what does a general day entail for you?</strong></p><p>I am the Director of Product Planning. I work on getting products from ideas on a whiteboard to final shelf ready goods. Right now we are working on creating some project-based DIY kits. We are in the final stages of prototyping before we send the product off to get a sample from our manufacturer. So right now my days are filled with doing all the final tests on our new product. I take a look at what we have so far, test ways in which it could fail and then make it better. I also look at how to simplify the product for manufacturability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/969/1*NtLJ2J2B8W2FH0HFwtJe0A.jpeg" /></figure><p>Photo Credit: Circuit Scribe</p><p><a href="https://www.circuitscribe.com/product/maker-kit/">The Circuit Scribe Maker Kit</a></p><p><strong>I read through your “Meet the Team” page and I love that you have some young engineers on board. What are some of your team member’s backgrounds and how did they find their way to Circuit Scribe?</strong></p><p>Valerie and Gunnar were both students at Wentworth Institute of Technology when they applied for co-op positions at Electroninks. Valerie, Electrical Engineering student, worked full-time for Electroninks during the fall of her senior year and continued part-time until she graduated in August 2015. Gunnar, an Electromechanical Engineering student, worked full time during the summer before his junior year and has continued to work part-time while still in school.</p><p><strong>Were there any classes in particular that really help you with the work you do? What kind of knowledge did you walk out of college with that really applies to developing your products?</strong></p><p>I attended Wentworth Institute of Technology which focuses on a very hands-on learning approach. The majority of my electrical engineering classes were lab based and that’s where I really found I was able to take the things I learned in school and apply them to my job. I think the two classes which helped me the most in the role I am in now were my Digital Logic class and my Microcontroller applications class.</p><p><strong>What software do you use for your designs?</strong></p><p>We use EAGLE for our schematic capture and board layout needs.</p><p><strong>What kind of failures have you come across that you had to work through to get a project up and running? I tend to see students get discouraged when they fail but I try to enforce that failure is a part of learning. What was something that happened during a project that maybe set you back or something you did not expect to get in the way?</strong></p><p>Sometimes I feel like I spend a whole day or even a week failing. That’s what prototyping is about, you try something and if it doesn’t work, you figure out why and try again. Even when I finally have the “ah-ha” moment and it works, my next question is how can I make it work better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JJ0z9ztc-ZudyRVHUSfczg.jpeg" /></figure><p>Photo Credit: Circuit Scribe</p><p><a href="https://www.circuitscribe.com/product/basic-kit/">A simple setup showing how to draw a circuit</a></p><p><strong>What is an important lesson you learned during the development process? Or what is something you wish you had known when you started?</strong></p><p>I think the most important thing I learned when I started developing products was to give myself a realistic timeline. A lot of times I have to solve problems I don’t know a lot about and that can mean I need to spend some time researching a topic I’m not familiar with before brainstorming a solution. If you let yourself get behind then you can become stressed and discouraged very quickly. So now before I commit to a date to have something done by I make sure to write down everything I need to do and identify how long each process should take and build in some extra time in case I run into an issue.</p><p><strong>As a recent graduate yourself, what advice would you give to a young engineer that is about to finish college and get their start in the field?</strong></p><p>In my opinion engineering school isn’t about how many equations you can memorize or how many problem sets you burn the midnight oil finishing. Engineering school is about learning how to identify a problem and build a solution. It’s about learning to work with a team and gaining the confidence to try a new idea. When you get into the field your ability to work with a team, own your decisions, and think on your feet are going to make you the most valuable. So apply for any job you want and trust that when they hire you, it’s because they know you are capable of learning not because they already think you’re an expert.</p><p><strong>Thanks for your answers!</strong></p><p>Thank you</p><h3>Takeaways</h3><p>Circuit Scribe is a great example of the engineering process at its finest. Identify a problem. Brainstorm a solution. Test until it’s fixed. Circuit Scribe does this so well every day and it shows through their work.</p><p>Their success also stresses the importance of planning in order to get something done which applies to so many areas in engineering, college, and life in general.</p><p><em>“A lot of times I have to solve problems I don’t know a lot about, and that can mean I need to spend some time researching a topic I’m not familiar with before brainstorming a solution.”</em></p><p>This is one of the extra lessons you learn from school. The professor is only there to show you what you need to learn. You need to rely on your own resources and deep-thinking to figure out how to solve the problem. This is as true in college as it is the real world.</p><p>Here is another great piece of advice I got from Valerie:</p><p><em>“So apply for any job you want and trust that when they hire you, it’s because they know you are capable of learning not because they already think you’re an expert.”</em></p><p>I hear from a lot of students that think they are underqualified for every job out there. They look at the criteria for the required candidate, and if they don’t meet every qualification, they don’t apply.</p><p>It’s okay if you’re not perfect!</p><p>The great thing about being engineers is that we have been taught how to learn. We don’t need to know everything before we dive in to a project. We are natural learners and researchers. I think by the time an engineer hits their junior year, they have been given at least one project with little instruction and somehow pulled it off.</p><p>This is engineering.</p><p>Make the best you can with what you have and figure out the rest. Circuit Scribe has made great waves in the engineering industry by doing just that and it shows through their work.</p><p>If you’d like to learn more about Circuit Scribe, check out their website at <a href="https://www.circuitscribe.com/">https://www.circuitscribe.com/</a> and learn electrical magic!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4e66ae427b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/first-engineering-job/interview-circuit-scribe-c4e66ae427b">Interview — Circuit Scribe</a> was originally published in <a href="https://medium.com/first-engineering-job">First Engineering Job</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[There Is No Such Think As Multitasking]]></title>
            <link>https://medium.com/first-engineering-job/there-is-no-such-think-as-multitasking-443b36e6db12?source=rss-84f47a6786f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/443b36e6db12</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[education-reform]]></category>
            <dc:creator><![CDATA[Jeff Benning]]></dc:creator>
            <pubDate>Mon, 20 Feb 2017 01:30:34 GMT</pubDate>
            <atom:updated>2017-02-20T01:30:34.460Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HV1xmVtUGOnIiFChpYu3ig.png" /></figure><p>Like many students, you probably take pride in getting a lot of things done at once. You want to study for exams, get your homework done, work on projects, and check your phone all at the same time. Multitasking isn’t what you think and I’ve gotten to understand this pretty well. There is no such thing as multitasking.</p><h3>Here’s Why</h3><p>It isn’t a real thing.</p><p>As much as we might like to think that our brain is like a computer, it really isn’t. We have one brain. One processor. We can actively think about one thing at a time. We do not have the ability of parallel processing and multithreading that computers do to accomplish several things at once.</p><p>It might seem like you can multitask because you’re trying to do several things at once but really you are just rapidly switching back and forth between tasks very quickly. You never give one task your complete attention and because of that, that task suffers, as do every other task you try and do during that time.</p><p>What you understand is multi-tasking is actually a myth broadcast by the technology world to make excessively scheduled and stressed-out people feel productive and efficient. People think that it’s something to brag about. “I got so much done today!” And maybe you did but it wasn’t because you multitasked.</p><h3>What about Actually Doing More Than One Thing?</h3><p>Our brains can only delegate out a certain amount of attention and productivity at once. So what about when we actually do two things at once? Like walking and eating. Anybody can walk and eat at the same time. These are things that are so ingrained on our brain that we don’t think twice about them.</p><p>Multitasking is when you engage in two or more tasks simultaneously but only if two conditions are met. First, one of the tasks must be so well learned as to be automatic such that no focus or thought is necessary to engage in the task.</p><p>Second, the tasks must involve different types of brain processing. For example, it is easy is read effectively while listening to classical music because different parts of the brain are engaged in reading comprehension and music processing. However, it is difficult to retain information and listen to music with lyrics because both tasks activate the language section of the brain.</p><p>What you’re doing by reading different engineering books or enrolling for multiple courses at the same time is not multitasking but serial tasking. Instead of engaging in multiple tasks simultaneously, you are in fact shifting from one task to another in rapid succession.</p><h3>Why you Shouldn’t Multitask in your Studies</h3><p>The truth is that multitasking is actually holding you back. It has been proven to be less effective and efficient. A number of studies have demonstrated that if you shift focus from one task to another, that transition is neither fast nor smooth. In fact, there is a lag time during which your brain must wrench itself from the initial task and then switch onto the new task.</p><p>When you multitask, you’re at high risk of making mistakes and remembering items. Multitasking makes you take a longer time completing a task that requires complete focusing like studying.</p><p>The benefits of not multitasking are quite spread out and laid out. Focusing on one task at a time increases your productivity and performance. As a student, it is important to complete one class or activity first before diving into another. The best way to be efficient and get the most out of your studies is to follow through on one thing until it is done. Only then should you move on to the next thing.</p><h3>F.O.C.U.S.</h3><p>The key word is FOCUS — Follow One Course Until Success.</p><p>This can have a lot of different meanings depending on how you apply it, but it holds true to all of them. Don’t start studying for your statics exam until you have finished studying for thermodynamics. Maybe not completely, but don’t do one question here, one question there, one question back here, and so on. Set dedicated time to one subject before you move on.</p><p>This can be hard to do, especially if you have both exams in the same day. So even during study sessions, focus on just one course. When you feel you have gotten sufficient value from studying, take a break, and move on to the next subject. For engineering, this means that you fully understand one concept first before moving on to another.</p><h3>The Pareto Principle</h3><p>If you have not heard of the Pareto Principle or the 80/20 rule, I’m about to blow your mind. The Pareto Principle states that 80% of your output comes from 20% of your input. So 80% of how you do on exam came from 20% of your studying.</p><p>Don’t believe it? Think if during those several hours you studies, you only worked on the most important problems. The ones you knew would be on the test. Think if you didn’t check your phone all the time, get distracted by Facebook, or try to snack while you studied. Instead, just hit the top 20% of topics you know you need to do and you will get better results.</p><p>It can be a difficult concept to truly grasp but in the couple years I’ve started applying it to my life, productivity has went way up. Combine this with our FOCUS acronym, and you can do some pretty impressive things.</p><h3>Conclusion</h3><p>Multitasking gives the illusion of productivity but in reality, it is a detriment to productivity. When you multitask, you perform multiple duties at the same time but fully focusing on none of them. The only sure way to productivity and efficiency is to focus on one project at a time while avoiding distractions until it is completely done before moving on to another. As an engineering student, designate a significant effort and time to complete one course or class or project first then move on to the next one.</p><p>There’s no such thing as multitasking. Like Steve Jobs said, “Be like a postage stamp…stick to one thing until you get there”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=443b36e6db12" width="1" height="1" alt=""><hr><p><a href="https://medium.com/first-engineering-job/there-is-no-such-think-as-multitasking-443b36e6db12">There Is No Such Think As Multitasking</a> was originally published in <a href="https://medium.com/first-engineering-job">First Engineering Job</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interview with mcThings and the Internet of Things]]></title>
            <link>https://medium.com/first-engineering-job/interview-with-mcthings-and-the-internet-of-things-89e330fc6fd7?source=rss-84f47a6786f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/89e330fc6fd7</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[internet]]></category>
            <category><![CDATA[diy]]></category>
            <category><![CDATA[iot]]></category>
            <dc:creator><![CDATA[Jeff Benning]]></dc:creator>
            <pubDate>Thu, 16 Feb 2017 02:33:53 GMT</pubDate>
            <atom:updated>2017-02-16T02:33:53.549Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BvwQVWNHq_oiHu3zeAJ0LA.png" /></figure><p>In the realm of the Internet of Things, companies like the one I had the pleasure of interviewing today are making major waves. mcThings (pronounced emm-see things) is a small company that makes it easy for people like you and me to bring the Internet of Things to our house. <a href="https://app.losant.com/#/dashboards/575f90f3e7a2700100d1ddb0">Literally</a>.</p><p>Using the software and circuitry they’ve developed at their facility in Cochrane, Alberta, Canada, they managed to wire up an entire house with a smart monitoring system. They keep track of everything from how warm the living room is to whether the plants have been watered or not.</p><p>They can even see how many times the fridge has been opened.</p><p>All of mcThings boards communicate wirelessly using their very own communication protocol. I spoke with Thomas Edworthy, a sales specialist at mcThings, and asked him a little about his company. Check out our awesome interview here.</p><h3>The Interview</h3><p><strong>Can you give a brief description of what mcThings does so my readers can hear it firsthand?</strong></p><p>mcThings develops electronics and the firmware platforms to help companies to create and maintain IoT solutions. Our platform is a powerful measurement and control platform allowing users to develop and deploy large scale Internet-of-Things solutions rapidly and cost effectively. Essentially, we connect ‘things’ to the internet that don’t have a plug! Using our platform, you can connect almost anything to the internet to be able to control or measure different variables. Our platform can be used in practically any industry for almost any purpose. We work with our own communication protocol (mcAir) and also work with SIGFOX which is an up and coming IoT communication network (LPWAN).</p><p>Some examples of using our platform:</p><ul><li>Smart cities — example — measure the weight or load of a garbage bin and then report its status. Now, instead of picking up every bin every day, only those bins that are full can be picked up and emptied saving time, gas, congestion, etc.</li><li>Smart agriculture — Easily measure critical variables (such as temperature, humidity, light levels, soil moisture, etc.) and relay that information back for analysis and alerts. Start to be very efficient with resources and possibly increase yields by having increased real-time information</li><li>Industrial IoT — measure variables and control equipment in industrial settings</li><li>Inexpensive asset tracking — using SIGFOX, asset tracking is now feasible enough to track almost any asset. (IE — City construction signs, waste bins, beehives (yes, beehives) livestock tracking, etc.</li></ul><p>Some really cool examples that people are exploring:</p><ul><li>mcThings modules into the base of beer pint glasses — With a sensor, you could alert the wait staff when that beer is getting empty and also temperature.</li><li>Embedding mcThings modules into seats at an arena which could then relay how many ‘butts’ are in the seats at any given moment, are there any trends that can be identified, can advertising be billed differently in certain sections during different periods/quarters in a sports game based on trend data, etc.</li><li>– There are many more (I could go on for hours) as the hardware and the platform is so versatile, you can practically turn anything into an IoT device!</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/363/0*i6xsTC8cM9P8l4Jq." /></figure><p>Photo credit: <a href="http://www.mcthings.com/">www.mcThings.com</a></p><p><a href="https://www.mcthings.com/products/mc-combo-pack-a">This kit</a> is everything you need to get started with the Internet of Things</p><p><strong>What are the backgrounds of some of the engineers you have on board that help to design your products?</strong></p><p>We have multiple engineers working in different areas within our company. We have a couple of Software engineers which includes our CTO. Combined, they have over 35 years of software experience and have created our IDE (mcStudio). We also have two senior firmware engineers who have spent countless hours writing and testing the mcOS operating system as well as the specific firmware that each device/module requires. This is also an advantage to our platform as we have written the firmware already for our devices so those who are working with our platform don’t need to write the firmware, they just need to program the devices to whatever their use-case is.</p><p>We also employ a full-time hardware engineer who’s main focus is to design and modify all existing and new modules/devices that we are working on. All of our engineers have come from backgrounds doing similar things but never with creating brand-new technology like we have done here at mcThings.</p><p><strong>Can you describe what a general day looks like for an engineer at mcThings?</strong></p><p>Every day is different! We have multiple projects that are ongoing and new ones all the time. Our engineers spend their days writing programming, firmware and hardware design. Some days we are designing custom devices for clients, some are fixing bugs that have been identified within our system and testing. Some days are doing client meetings and working out requirements and others are prototyping and testing different sensors and working closely with our cloud partners to test capabilities. It’s a great work environment and everyone works together as one team — Everyone has the chance/ability to give input on all projects and other happenings at the office and we encourage that! The more views on what we do and suggestions just help us to make our platform better! The only thing that is the same every day is our required minimum of 1 foosball game per engineer/day! J</p><p><strong>What software do you use for your designs?</strong></p><p>Hardware — Altium designer</p><p>Software and firmware — Visual studio, Eclipse, GCC compiler, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/0*u--oWwEPqOdjYrY7." /></figure><p><a href="https://app.losant.com/#/dashboards/575f90f3e7a2700100d1ddb0">Check out this LIVE data of a smart house</a>!</p><p><strong>Can you tell me about a failure you encountered that you had to work through to get a project up and running? I tend to see students get discouraged when they fail but I try to enforce that failure is an important part of learning. How did a failure wind up teaching you a valuable lesson or work to your benefit in the long run?</strong></p><p>We’ve had our fair share of failures and road blocks during the creation of our platform. This was not unexpected and some were worse than others! When creating new technology you can do your best to work out the issues that you will need to deal with but there will always be things that come up that you don’t expect! Some examples would be designed hardware that does not work the first time and needed to be redesigned. This can be discouraging as you work really hard to design everything to suit your needs (cost, design and functionality considerations) and when you run into issues, it’s not fun! However, taking the time to figure out where we went wrong, fixing that and learning from those mistakes make the next design that much easier. Finding/designing solutions to problems is the core of our business and we reflect that in our work ethic. Some of the greatest days we’ve had at the office are when you finally track that one bug down in software or realize that a small change on a PCB design will solve our problems! Finding the solution to a problem and fixing it is quite gratifying and it allows us to face the next challenge knowing that there is a solution to every problem, you just have to find it!</p><p><strong>Your team has accomplished some amazing things, from completely wireless communication to your own scripting language. What advice would you give to a young engineer that is about to graduate college and is looking to accomplish such ambitious goals in engineering?</strong></p><p>Believe in yourself and don’t give up! Some of the greatest inventions and innovations in human history were marred with unbelievable roadblocks yet, with some gumption and hard-work, those inventions and innovations still came to life! Yes, you will face problems and issues, but part of being an engineer is solving those issues and designing/implementing the solution.</p><p><strong>I try to enforce how important it is to self-educate and learn things that are not just for a grade but because you genuinely want to know them. What kind of things do you do outside of work that contribute to your engineering knowledge?</strong></p><p>All of our team (engineers and other departments) spend considerable time learning outside of the office. For example, our senior hardware engineer is currently enrolled in programming language courses as is our sales and marketing team. We all keep an eye out on emerging technology to be informed and to see if there is anything that we can incorporate into our platform. While this is a daunting task to continue to learn outside of our workplace, we genuinely enjoy learning about new technology and other disciplines as we have seen these learnings help us in the past and they will no doubt help us in the future</p><p><strong>Thanks for your answers!</strong></p><p>Thanks again and talk to you soon!</p><h3>Takeaways</h3><p>If there’s one thing you walk away from reading this interview with, I hope it’s that you don’t ever think something is too big to accomplish again. Not only does mcThings provide the circuitry to develop smart technology, they developed their own communication protocol, development environment, and operating system!</p><p>If this isn’t an inspiration, I don’t know what is.</p><p>I also love what Tom said about learning outside of work.</p><p><em>“All of our team (engineers and other departments) spend considerable time learning outside of the office.”</em></p><p>If you’ve been around this blog for any length of time, you’ll know I’m a huge fan of self-education and learning outside of the classroom. Even with a homemade operating system under their belt, engineers at mcThings are still spending their free time improving their skills.</p><p>This little quote about not giving up was another great piece of advice to take away from this interview.</p><p><em>“Yes, you will face problems and issues, but part of being an engineer is solving those issues and designing/implementing the solution.”</em></p><p>I believe failure is such an amazing teaching tool and should be used as such. A lot of people give up when things don’t go as planned but that is the exact point that you need to keep carrying on. You come out of every experience, good or bad, a little wiser and more experienced than you entered it with.</p><p>If you’d like to learn more about mcThings, check out <a href="https://www.mcthings.com/">https://www.mcthings.com/</a> and get working on the Internet of Things!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89e330fc6fd7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/first-engineering-job/interview-with-mcthings-and-the-internet-of-things-89e330fc6fd7">Interview with mcThings and the Internet of Things</a> was originally published in <a href="https://medium.com/first-engineering-job">First Engineering Job</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Attention CS Majors]]></title>
            <link>https://medium.com/first-engineering-job/attention-cs-majors-6dd6b5b8c55d?source=rss-84f47a6786f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/6dd6b5b8c55d</guid>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Jeff Benning]]></dc:creator>
            <pubDate>Mon, 13 Feb 2017 12:52:33 GMT</pubDate>
            <atom:updated>2017-02-13T12:52:33.756Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*miKuJEavrJjYoBPEromSjg.png" /></figure><p>I get a lot of emails from Computer Science majors that say they are not confident in their programming ability. They can usually do the coursework and labs but still aren’t sure if they can make it as a programmer in the real world. CS majors probably have the most work intensive major of all of the engineering disciplines.</p><p>If all you are doing is the coursework, then I have some bad news for you.</p><p>That is not enough.</p><p>To make it as a programmer means you have to really know what you’re doing. College does a good job at teaching you these skills but there simply isn’t enough time to teach you everything. You’re going to have to go out on your own to learn how to learn the ins and outs of computer science.</p><h3>The Class Projects Should Be Easy</h3><p>You should be able to do your class projects with ease. If you can’t, then you need to spend more time out of the classroom learning how to code. I’m not going to lie, programmers have it tough. I only have a minor in computer science but I worked my butt off for it.</p><p>Lucky for me, I picked it up pretty quickly. I really enjoyed an introductory programming class I took as an M.E. and started learning to program games after that. They were nothing special and I spent hours upon hours just to get a ball to move on screen, but it taught me a ton. If nothing else, it taught me that hard work will lead to results.</p><p>This is exactly how great programmers are born. They put time into it. A lot of time. This really annoys me about programmers in TV shows. They are rarely shown actually programming and appear to be living these extravagant, overly social lives. Maybe when you’re older but when you’re a student, you’ve got a lot of learning to do. Just remember, if you don’t know it now, it’s not because you can’t. It’s just that you haven’t spent enough time yet.</p><p>So like I was saying, stay ahead of your assignments. Do the extra credit if it’s available. I had a couple of professors that offered the option of implementing extra features in our programs for extra points.</p><p>If that’s an option, do it.</p><p>You should also try to help others. There are students in every class that have a hard time learning programming. Maybe they saw Swordfish, or some other hacking movie, and decided they wanted to be the next great hacker so they signed up for computer science.</p><p>Help these kids. They don’t know anything. You don’t understand something well enough until you can teach it. And programming is such a teachable thing once you really understand it so make it happen. As Einstein said, “If you can’t explain it to a six-year-old, you don’t understand it yourself.”</p><h3>Find an Extra Project</h3><p>Ever looked into the world of open source code? I’m sure you have but if not, let me tell you a little bit about it.</p><p>In general, open source software refers to any software whose code is made available for anyone to see, use, and adapt as they see fit. This allows security in software as anybody can see if a piece of code is malicious or not. It offers adaptability for anyone who wants to expand on a project and improve it or implement new features.</p><p>Linux, for example, is an open source operating system. Have you ever wondered how an operating system works? You can see the source code for Ubuntu <a href="https://launchpad.net/ubuntu/+source/curl/7.21.2-4ubuntu1">here</a>.</p><p>GitHub is an online repository of code often used to host open source projects. There are over 35 million code repositories on GitHub so if you can’t find something there that interests you, you must not really like programming.</p><h3>Freelance</h3><p>The best way to learn coding is to simply sit down and do it. It’s great to build your own projects but if you can do it for someone else, you’ll learn what programming is like in the real world. You’ll learn about usability and the sometimes (often) unrealistic expectations of customers. You might even be able to make a few bucks doing it.</p><p>When you’re starting out, don’t expect to make money doing it. It’s great if you can but nobody is going to pay someone who’s never developed an app before. Find friends or family that have ideas and try to create something for them. It doesn’t matter if it’s been done before and it certainly doesn’t have to be the next big thing. The point is that you’re doing something outside of the classroom to advance your knowledge of programming. At the start of your career, that is invaluable.</p><p>Just get your stuff out there! Don’t start the second project until you finish the first.</p><p>Get it done.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6dd6b5b8c55d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/first-engineering-job/attention-cs-majors-6dd6b5b8c55d">Attention CS Majors</a> was originally published in <a href="https://medium.com/first-engineering-job">First Engineering Job</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cool Stuff in Engineering No.7 — Machine Vision]]></title>
            <link>https://medium.com/first-engineering-job/cool-stuff-in-engineering-no-7-machine-vision-5cfc218438e6?source=rss-84f47a6786f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5cfc218438e6</guid>
            <category><![CDATA[education-technology]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Jeff Benning]]></dc:creator>
            <pubDate>Tue, 07 Feb 2017 01:56:22 GMT</pubDate>
            <atom:updated>2017-02-07T01:56:22.818Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YqJEGmGDtheQJEmzZl44ow.png" /></figure><p>I recently went to a seminar hosted by Cognex, a leading manufacturer in machine vision applications. In the realm of automated control systems, machine vision has to be one of the coolest technologies you can implement.</p><p>A computer with a camera can analyze up to hundreds of parts a minute and decide if they pass quality checks or not. This is commonly used to check parts coming off of an assembly line. Check out <a href="https://www.youtube.com/watch?v=ZG9GIQgmisY">this video</a> to see a bottle checking machine making sure each bottle has a cap and that the fill level is right, among other things and to get an idea of what machine vision is.</p><h3>Why Bother?</h3><p>It’s easy for us, as humans with eyes and a brain, to look at something and tell if it’s right or not. Think about it this way. Take a look at a bottle or can that is near you. Is it suitable for sale as it sits right now? What makes it that way?</p><p>The bottle should be clean, with no dents or gouges in it.</p><p>It should have a label appropriately oriented and readable.</p><p>It should have liquid filled to the top and it should be the correct liquid.</p><p>It should have a seal on it, securing the cap to the bottle and indicating the bottle has not been tampered with.</p><p>It might even need to be oriented properly to make sure the next step in the process is performed correctly.</p><p>Now, you can perform all of these checks in a few seconds without much thought power. But imagine looking at hundreds of these a day. You might miss just one. Then you ship a poor-quality product to a customer who will not be very happy when they open their bottle of water and find it half full.</p><p>This is the power of machine vision. It can take images and determine if the part is good or bad in the range of milliseconds. And assuming you programmed it correctly, it will give an accurate outcome every time. The programming is the difficult part to get right, however. How do you teach a machine to think like you do?</p><h3>Here’s how it Works</h3><p>Most simply, machine vision works by taking an image of a product at a precise time and interpreting what it reads. If it does not detect any problems, it lets the part through. If something is not correct, it sends out a signal which can then be handled in a number of ways. The engineer might decide to stop the line, sound an alarm, remove the defective part from production, or any number of different things.</p><p>Utilizing machine vision is much more difficult than this. There are a number of feats to accomplish after the image has been taking, all which must be done in as little time as possible. After all, time is money.</p><p>The trick is in the image processing. The computer reads in pixel data from an image. It then locates what it is looking at by searching for a unique identifier. This can be something like the edge of a cap, or the rectangular box around a barcode.</p><p>Now that it knows where it’s at, it can search for the detail it is analyzing. Maybe the fill level should be exactly four inches above the barcode. If it doesn’t see a change in pixel color at 4” above the barcode, something must be wrong.</p><p>Then maybe five inches above the barcode, the computer should see a rectangular blog, indicating the cap. If this blob isn’t there, then there must not be a cap.</p><h3>Get the idea?</h3><p>The computer goes through very logical steps to make sure everything that needs to be there, is there. While machine vision is commonly used to look at assembly line parts, barcodes, inspection, and several other applications, there is much more to it than that.</p><p>Tesla uses an <a href="https://www.technologyreview.com/s/602048/tesla-might-replace-autopilots-eyes-with-something-far-more-advanced/">advanced form</a> of machine vision to guide its automated cars. Machine vision is commonly used in <a href="http://www.vision-systems.com/articles/print/volume-19/issue-11/features/choosing-a-3d-vision-system-for-automated-robotics-applications.html">robotics applications</a> as well.</p><h3>Engineers for Machine Vision</h3><p>Machine vision development is commonly carried out by electrical and software engineers. Robots that can see is a perfect combination of the two. You need the hardware to make sure you’re getting the most detailed picture you can, and software to analyze the image as accurately as possible.</p><p>I’ve done a quick job search to see what companies that hire engineers for machine vision like to see (pun intended) in a candidate and it’s not too strict. The general experience tends to be 3–5 years so it might not be your first job, but it could certainly be your second. They like to see work with robotics, data collection, and java and C++ programming languages. Any experience with lighting is also preferred as this is such an integral part of taking good pictures.</p><p>If machine vision floats your boat, it is certainly a field you can work up to fairly quickly. And you know I love everything robotic and with artificial intelligence and machine vision fits perfectly in there.</p><p>Find more great articles like this at <a href="http://www.firstengineeringjob.com/">www.FirstEngineeringJob.com!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5cfc218438e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/first-engineering-job/cool-stuff-in-engineering-no-7-machine-vision-5cfc218438e6">Cool Stuff in Engineering No.7 — Machine Vision</a> was originally published in <a href="https://medium.com/first-engineering-job">First Engineering Job</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Every Engineer Should Know How To Turn A Wrench]]></title>
            <link>https://medium.com/first-engineering-job/every-engineer-should-know-how-to-turn-a-wrench-7db9613006c6?source=rss-84f47a6786f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/7db9613006c6</guid>
            <category><![CDATA[mechanical-engineering]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[students]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Jeff Benning]]></dc:creator>
            <pubDate>Wed, 25 Jan 2017 13:10:53 GMT</pubDate>
            <atom:updated>2017-01-25T13:10:53.126Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hNZDRFXE2Dn-E8RrOzsNIQ.png" /></figure><p>A lot of engineers have never worked on a car before. Or as mechanics say, they’ve never turned a wrench. I’ve graduated with some bright engineers that didn’t know the difference between a socket wrench and a torque wrench. That has always surprised me. My father was a mechanic and he taught me to fix cars before I could even drive. These skills have helped me tremendously as an engineer not only on the job but in getting jobs as well.</p><h3>Mechanics vs. Engineers</h3><p>Before I was an engineer, I was an auto mechanic. I remember lying under a car on the cold ground trying to avoid oil drips, thinking “Who in their right mind designed this crap?!”</p><p>Well, engineers did. This is the perpetual fight between mechanics and engineers. Engineers design it so mechanics can’t fix it and mechanics despise engineers because they have to fix it. I’m exaggerating a little bit here but there is some truth to it. If you’ve ever had to change a part on your engine that didn’t exactly have a lot of room to get it out, it does make you wonder.</p><p>Once you get into engineering, you start to realize that there are a lot more important factors that go into design than ease of access. I’ve dealt with engine design only a little but I know that it’s one of the biggest challenges automotive engineers face. Think of everything you are packing into that tiny space under your hood. Not only do you have the whole mechanical powertrain, you need to include a smart braking system, a power generation system, a cooling system, and an emissions system that monitors itself constantly.</p><p>Not only is this difficult enough already, but it needs to be as light as possible, as cheap as possible, and as reliant as possible. There are emissions and safety standards to meet as well. Not only is there an onboard diagnostics system built into every car, there is a wide array of sensors to detect failures and leaks.</p><p>So ease of access doesn’t rank too highly on the list of priorities for automotive engineers. Although it certainly does rank on there somewhere and that’s why engineers should have an idea of what the next guy to work on it is in for when they design something.</p><h3>Learn How Its Built In Order To Design It Better</h3><p>The thing about all of this progress we’re making is that so much stuff has been done before. Think about it this way. Newton spent his whole life inventing calculus. He did a lot of other things as well but calculus was one of the big ones. It’s what he’s known for and calculus was his life’s work.</p><p>Now think back to modern times. Students start being taught calculus as young as 14 years old! If you’re an engineer, you’ll mostly likely learn calculus by your sophomore year at the latest. And guess what? Nobody is going to praise your name because you learned calculus. It’s expected of you. This means that you need to work harder in order to even get to the point where you get a chance to invent something new.</p><p>You need to learn calculus before you can expand on calculus. As an engineer, you need to learn how existing things work, so you can invent better ways to make them work. Or you need to learn how things work in order to find out what nobody has thought of yet. What can you invent that has yet to be discovered? What is something you always wished existed? Maybe you don’t know yet. That’s why you need to get your hands dirty in order to really see what is out there.</p><p>Not only this but sometimes other designs give you good ideas. Use other people designs for inspiration. You could spend a week thinking of the best way to make the front wheels of a vehicle drive AND turn. Try it out if you don’t already know. Then compare it to how an actual steering system on a car works and see how you did. Odds are that the existing ones are far better. They’ve had almost 200 years of testing to get right.</p><p>This is just an example to show you that before you start designing, it’s wise to do a little research. I still make this mistake all of the time at work, but when a machine breaks, I rarely think to ask someone else if they have seen that problem before. Instead, I go about diagnosing the problem myself. Sometimes I figure it out. Sometimes I have to ask for help. In any case, it usually turns out that another engineer has seen a similar problem before and can guide me in the right direction.</p><p>Now if that problem ever arises again, I’ll know what to do about it. Just like how my knowledge of fixing cars applies to problems on the job.</p><h3>Can Help You Out At Home</h3><p>Working on things lets you know how things work on other things. Most parts like gears, fittings, and enclosures don’t vary that much from an industrial setting to a home setting except in durability. A bearing is a bearing. Yes, bearing design is a science in itself but operationally they don’t change very much. Your car has bearings and so does your skateboard. If you know how one works, you know how the other works.</p><p>Same with fittings and hoses. If you can change a radiator hose on your car, you can install a toilet. You should also have a general understanding of fluid mechanics from college so you should know how to diagnose leaks, and how a fluid system acts if there is air trapped inside of it.</p><p>You become more self-reliant. You won’t have to call a plumber to fix a leak, an electrician to install an outlet, or a cable guy to setup a TV. Learn how to fix a seemingly simple thing, and you’ll learn how to fix the more complex things.</p><p>Many of you probably played with Lego’s as a kid, or took apart a broken toaster when you were younger to see how it works. Well, if you’ve never turned a wrench, do something similar now. Learn how the little things work. Next time something breaks on your car, do a little research online to see if other people with a similar make and model of car have had similar issues. You may find that the fix is doable yourself. Save a few bucks and learn something new by doing it yourself.</p><h3>Conclusion</h3><p>There is a lot to gain by doing the hands-on work yourself. After all, how can you design something new if you don’t know how the old stuff works? Try getting your hands dirty once in a while and you’ll be surprised at what you learn.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7db9613006c6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/first-engineering-job/every-engineer-should-know-how-to-turn-a-wrench-7db9613006c6">Every Engineer Should Know How To Turn A Wrench</a> was originally published in <a href="https://medium.com/first-engineering-job">First Engineering Job</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[9 Ways To Rock Your First Engineering Job]]></title>
            <link>https://medium.com/first-engineering-job/9-ways-to-rock-your-first-engineering-job-8d6d7edeb5fb?source=rss-84f47a6786f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d6d7edeb5fb</guid>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[what-a-world]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[college]]></category>
            <dc:creator><![CDATA[Jeff Benning]]></dc:creator>
            <pubDate>Tue, 24 Jan 2017 12:51:36 GMT</pubDate>
            <atom:updated>2017-01-24T12:51:36.499Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o2KNkjI-CpRH4AdmnkoSEA.png" /></figure><p>The first day at your first job is weird. You don’t know what to expect. Did school prepare you well enough? Do you remember the things you’re supposed to know? It’s tough at first, but here are nine things you can keep in the back of your mind for your first job so you’ll feel a little more confident.</p><h3>1. Ask for help when you need it</h3><p>One of the benefits of being new on any job is that you’re given that grace period of not knowing what the other engineers know and that’s okay. You’re given a little time to get acclimated to your new environment. It’s okay to forget someone’s name here and there or not know your way around the building.</p><p>This is an important grace period. Use this time to your advantage to learn as much as you can about the workplace you’re in. Make that extra effort to remember everyone’s name and remember the new things you’re taught. Write them down if necessary.</p><p>This period wears off quickly but you still won’t be expected to know everything. You’re new to the workplace, fresh out of college, and your employer knows that. They know you’ll have questions and will need help, so don’t be ashamed of it. Asking for help shows you’re not afraid to seek other people’s opinions when needed. Ask for help for more than just your way around the office, though.</p><p>If you’re stuck on a <a href="http://www.firstengineeringjob.com/interesting-projects-as-an-engineer/">project </a>you’re working on, ask another engineer for advice. If nothing else, you may have a good brainstorming session about it. Another amazing source of information is machine operators. They work on their machine all day every day and know more about how it works than the guys that built it.</p><p>If you’re in most plants, your work revolves around making sure the machine operators are consistently making quality products in as least amount of time as possible. This manifests itself in several ways from designing parts to creating time studies. The point is that when you need help, these are the people you need to be talking to.</p><h3>2. Learn by Doing</h3><p>The cool thing about working with seasoned engineers is that they know A LOT. Some went to college and some didn’t but the things they’ve spent their time doing, they’re pros at. I’ve been blown away sometimes at things I never knew I could do that these guys did so easily. And then taught me. I was wiring up control panels for a robot after about a year at my first job. Never thought I’d be able to do that. But it all started because I asked for help.</p><p>I showed interest in wiring up a data acquisition system to a machine we had. I asked if I could help the engineer install it because I wanted to learn. As it turned out, I wound up becoming my project. Apparently, I showed enough interest that they just let me take charge. It was a neat project that I learned a lot from. I made a lot of stupid mistakes that the other engineer was able to quickly diagnose so I could fix them. That’s how I learn best.</p><p>I tend not to learn by observation alone. I like seeing something done once and then trying to repeat it. If I do it wrong, I want to figure out what I need to change before I ask for more help. I need to do it myself in order for the information to stick. This is how I teach too. I’ll explain it to whoever I’m teaching, do it once, and then have them show me how to do it. Try this approach when learning a new skill if you don’t do this already. You may find it helps.</p><h3>3. Learn the Things You Don’t Know Off the Clock</h3><p>I’d like to add a disclaimer before I start this section. I don’t mean that you should clock out whenever your shift is over and then continue working. Your work off the clock should be for your benefit which will, in turn, benefit the company. Self-knowledge goes a long way and that’s what I’m talking about.</p><p>CAD is a perfect example. You probably used Inventor or SolidWorks during college. How much did you use it? If you’ve still got some skills but find that you should know more to do your job, take the time to learn it when you get home. CAD skills will be useful for your entire engineering career so it’s worth taking extra time to become proficient with a software. Most CAD software has trial versions of it so download the trial and watch some YouTube tutorials. It’ll help you so much down the road.</p><p>The same holds true for any software. For one of my internships, I needed to learn scripting language in AutoCAD. I spent a few nights doing some fairly basic tutorials and learned what I needed to know. A week later at work, I was able to write a pretty impressive script that saved a ton of time for me and a few coworkers. Now every time I need an AutoCAD script, I have a basis to go off of.</p><p>If you’re working on a project where some of your old classwork might come into play, browse through your old textbooks. On an oven I designed, I needed a quick recap about thermal expansion so I could calculate how to build the walls. I went back to my thermodynamics book and found the formulas I needed for thermal expansion. Obviously, this isn’t terribly difficult. I mean, it wasn’t like I was doing differential equations or anything, but I found the stuff I needed to know so when I went to work the next day, I had an idea of where to go.</p><p>The thing about classwork is that there is no way you could possibly remember four or five years worth of information every day of your life. This is why I disagree with the grading system so much but that’s an article for a different day. The more important thing is that you know the information exists and where to find it. Those two things will get you very far.</p><h3>4. Ask for more work when you need it</h3><p>Sometimes the employer doesn’t know how much you can handle. During my first six months or so at my job, I got fewer projects than everyone else, and for good reason. It took time for me to get used to the flow of things. But as I got better at my job, the days took a little longer to finish. I didn’t have enough to do but I didn’t say anything. I kind of just waited around for someone to give me work and when they did, I did it quickly.</p><p>If you’re bored, say something. Don’t expect anyone else to do it for you. It isn’t like college where you didn’t have to do anything if the professor didn’t give you homework. You have to find your own homework. As it was explained to me, “If you don’t like being told what to do, do it before you’re told.” This holds true and I try to remember it when I find myself with extra time on my hands. If you take charge of your job, you’ll have a lot more control over what you do. If you wait for others to tell you what to do, well, you’ll do what others want of you. Not what you want. You can change that if you want.</p><h3>5. Be honest</h3><p>You’re going to break something. I can tell you right now. Because you are new and have never done this before, you’re going to break something or screw something up. You’re going to cost the company money. You’re going to go into a situation feeling confident, do something wrong, and have no idea what to do. It’s happened to me more times in my life than I can count. There were definitely a couple during my first, and current, engineering job.</p><p>Listen carefully.</p><p>Don’t worry.</p><p>We have all been there. We have all screwed up and if we’re extremely lucky, it’s a minor mistake. Far more commonly the mistake costs $1000 or more, at least in my experience. This comes from destroying load cells, breaking motors, ordering the wrong material, using the wrong dimension on a drawing, and all sorts of annoying inconveniences.</p><p>But it’s okay. The best thing you can do is be honest about what happened and learn from it. Don’t try to hide your mistake. That just gets everyone in trouble. After all, look what happened to <a href="http://blog.caranddriver.com/everything-you-need-to-know-about-the-vw-diesel-emissions-scandal/">Volkswagen</a>.</p><p>So be honest!</p><h3>6. Be On Time</h3><p>Maybe it’s the way I was raised (actually it’s definitely the way I was raised) but I can’t stand when people are late. I’m the type of person who is always 5 minutes early and if I’m going to be even a minute late, I call to let the person know.</p><p>Being on time in the business world seems very much related to your position. For instance, the president of my company hasn’t been on time to a single engineering meeting since I got hired. They’re the same time and day every week but we inevitably wait up to 20 minutes for him to get there.</p><p>But it’s his company. He’s the president. He can do what he wants. If I’m late, it gets noticed. So until you’re running your own company, be on time. It’s just the right thing to do.</p><p>This seems to be especially true of the old timers. When they say show up at 7:30, they mean show up at 7:30. They don’t have time to wait around for you. I don’t know, I guess it’s a generational thing.</p><p>It’s good for vendors, customers, bosses, and even the employees you may have someday. Being on time is professional and shows you care. If you can’t be on time, call. I’m probably more impatient than most people but when someone says they’ll meet me at 2 o’clock and they don’t show up, every minute I’m standing there waiting is a minute wasted. I probably need to lighten up, but then again, maybe not.</p><h3>7. Don’t Be Afraid To Pick Up the Phone</h3><p>So this was something I felt so awkward doing when I started my internships. I would have to call these part vendors and ask questions about how their product worked, or how to trouble shoot really expensive equipment over the phone. I always had to check with my boss to make sure I was saying the right things.</p><p>Sooner or later, you’re going to have to talk with tech support, customers, suppliers, people you don’t know. It’s awkward at first but so important. Plus you’ll quickly learn that it may save you a lot of headaches in the future. Yeah, you can fiddle around with whatever it is you’re working on until you get it to work, or you can call someone who knows and have them help you. This goes back to before. Don’t be afraid to ask for help.</p><h3>8. Be Open to Learning</h3><p>I’ve said it before and I’ll say it again. The coolest thing about engineering is that we are doing things no one has ever done before. You’ll be inventing new products, new processes, new tests and the things you do will affect the world. Maybe not the whole world, but some of it.</p><p>Therefore there’s going to be things you don’t know yet and you can’t find anywhere. Be open to learning new things, even though they may or may not help you in the future. I once read up on laser ablation for a whole week to try a new process of stripping parts at work only to wind up going a completely different direction a couple weeks later.</p><p>I was frustrated but I learned what didn’t work. As Edison said “I have not failed. I’ve just found 10000 ways that won’t work.”</p><h3>9. Get Creative</h3><p>I’ve said it before and I’ll say it again. Seriously, though, be open to anything. Brainstorm on crazy ideas. Get creative. We’re engineers and we invent the world. Be creative about it.</p><p>I really hope this helps. Maybe I should have titled it 9 things I learned in my first year and a half as an engineer but I’ll leave it here for now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d6d7edeb5fb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/first-engineering-job/9-ways-to-rock-your-first-engineering-job-8d6d7edeb5fb">9 Ways To Rock Your First Engineering Job</a> was originally published in <a href="https://medium.com/first-engineering-job">First Engineering Job</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cool Stuff In Engineering No 6 — Do You Know How Many Vehicles Are On Mars?]]></title>
            <link>https://medium.com/first-engineering-job/cool-stuff-in-engineering-no-6-do-you-know-how-many-vehicles-are-on-mars-671ac5d5e709?source=rss-84f47a6786f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/671ac5d5e709</guid>
            <category><![CDATA[mars]]></category>
            <category><![CDATA[space]]></category>
            <category><![CDATA[autonomous-vehicles]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[students]]></category>
            <dc:creator><![CDATA[Jeff Benning]]></dc:creator>
            <pubDate>Fri, 20 Jan 2017 02:11:50 GMT</pubDate>
            <atom:updated>2017-01-20T02:11:50.480Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PJBgm0Q5DFNfyzBtUPjeng.png" /></figure><p>Believe it or not, there’s more than just a few vehicles that made the trip from <a href="https://en.wikipedia.org/wiki/List_of_artificial_objects_on_Mars">Earth to Mars</a>. Even more surprising is that humans first made it to mars in 1971. Well, more like something we made ran into Mars. But the important thing is that we got there. Space is one of the most fascinating things to me and I love learning about it. So here’s some research I’ve been doing the last couple weeks about our history with visiting Mars.</p><p>First of all, I’ve learned a lot in this research and here are some things that would have helped me if I’d known them before I started this. Most of the trips to Mars, regardless of which country went there, consist of an orbiter and a lander. They both launch together and arrive in the Mars atmosphere at the same time. The orbiter hangs out in in space while the lander makes the trip down to the surface. The lander usually has a rover which can explore the planet once it lands.</p><p>One of the biggest engineering challenges seems to be getting the lander safely on the surface. A lot of the failures happen during this descent. Anyway, on with the vehicles.</p><h3>USSR</h3><p>The first vehicle to touch mars was called the Mars 2 and it was developed by the USSR. It was an unmanned vehicle which reached Mars orbit in March of 1971. The orbiter was able to gather data on the Marian atmosphere, landscape, temperature, gravity, and magnetic field.</p><p>The lander had a different story. It ultimately wound up crashing on the Mars surface due to a failure with the <a href="http://history.nasa.gov/monograph15.pdf">landing trajectory</a>. Due to an improper approach angle, its parachute did not deploy as it was supposed to. Pretty cool to think this all happened in 1971 though.</p><h3>Vikings</h3><p>Only five years later, the first rover landed successfully on Mars. The NASA Viking program started in 1976 and was the United States first attempt at landing on Mars. The orbiter operated until 1980 and NASA believes it’s still in Mars orbit.</p><p>The Viking 1 lander reached the surface in July of 1976 and operated for an amazing 2245 sols. A sol is one day on Mars which is 39.58 minutes longer than an Earth day making it just short of 6 years of activity, a record until it was <a href="http://mars.nasa.gov/mer/newsroom/pressreleases/20100519a.html">beaten</a> by the Opportunity rover. Viking 1’s objective was to look for evidence of past life. It had an impressive array of recording equipment. One of Viking 1’s objectives was to analyze the composition of the Martian soil in hopes of finding organic material. Its findings have been questionable.</p><h3>21 Years Later</h3><p>It was another 21 years before another vehicle would make it to Mars. The United States Mars Pathfinder launched on December 4th, 1996 and landed on July 4th the following year. The Pathfinder actually just the lander. It was launched along with Sojourner, the first rover to operate on Mars.</p><p>Both Pathfinder and Sojourner outlasted their expected lives and provided a wealth of information. Together, they sent back over <a href="https://www.nasa.gov/mission_pages/mars-pathfinder/">17,000 images</a> and conducted experiments providing evidence that Mars was once warm and wet.</p><h3>A Grave Miscalculation</h3><p>After Pathfinder and Sojourner, the next three attempts to learn more about Mars didn’t go that well. The U.S. launched the Mars Climate Orbiter in December of 1998. Its job was to look for water on mars, monitor the Martian atmosphere, and try to understand the history of the planet based on climate change. The Mars Climate Orbiter was also intended to be a communications relay for the next vehicle to land on Mars.</p><p>The problem happened once the spacecraft tried to enter the atmosphere of Mars. Calculations were carried out to bring the craft at an altitude of 110 kilometers of Mars while it performed an orbital insertion maneuver. If it descended any less than 80 kilometers in altitude, the conditions would be too harsh for the craft to survive.</p><p>Communication was lost with The Mars Climate Orbiter at 9:06 on September 23rd, 1999. The craft was determined to have reached 57 kilometers from Mars and disintegrated due to the atmospheric stresses. The problem was chased down to a <a href="http://www.washingtonpost.com/wp-srv/national/longterm/space/stories/orbiter100199.htm">simple miscommunication</a>. Lockheed Martin developed software that calculated the impulse produced by firing the thrusters. NASA used this software to update the position of the Mars Orbiter. The problem was that the software was written using U.S. standard units whereas NASA specified it to use metric units. Because Lockheed had the units wrong, the wrong number was given to the spacecraft which ultimately led to its destruction.</p><h3>Opportunity and Spirit!</h3><p>In this writer’s opinion, Spirit and Opportunity more than made up for the failure of the Mars Climate Orbiter and the two that followed it. These amazing machines were launched in 2004 and the Opportunity rover is STILL going. My car is a 2004 and I can’t tell you how many times I’ve had to fix that thing. Opportunity is doing better and it’s on Mars.</p><p>It turns out I couldn’t quite find a straight answer as to why the mission was only planned for 90 days when the rovers were built so robustly. The best reason I can find is that NASA seemed to think the dust storms on Mars would diminish the rover’s ability for the solar panels to produce power. Thanks to some wind and a lot of luck, that seemed to not be the case.</p><h3>Construction</h3><p>Spirit and Opportunity aren’t your ordinary Mars rover. These rovers were built out of aluminum and titanium to withstand the 180-degree temperature swings the Martian atmosphere experiences every day. Each rover has its weight split up across six wheels designed to overcome rocky surfaces and steep hills. Even though Mars gets down to -157 degrees Fahrenheit at night, the rovers have heaters built in to keep cold-sensitive equipment operational.</p><h3>Spirit</h3><p>The Spirit rover, despite a weird <a href="http://www.itworld.com/article/2832818/it-management/the-day-a-software-bug-almost-killed-the-spirit-rover.html">programming anomaly</a> that gave NASA a good scare, far exceeded its expected 90-day lifespan. It took the world’s first high-resolution image on another planet’s surface and carried out the first intentional grinding of a Martian rock. Spirit braved many close encounters, mostly due to power scares, but ultimately wound up getting stuck in some Martian soil. NASA’s Jet Propulsion Laboratory tried finding ways to get Spirit out by means of computer simulations and even a sandbox mockup of the situation but were unsuccessful. The rover was used in its stationary state for several more months until its last communication in March of 2010.</p><h3>Opportunity</h3><p>This rover is still going today. It had a <a href="http://www.space.com/18289-opportunity-rover.html">couple close calls</a> including being stuck in Martian sand for five weeks, a bum front wheel, and a close call with some dust covered solar panels. Opportunity has made a number of accomplishments on the surface of Mars including finding evidence of water by observing the minerals in rocks. It has made important astronomical findings and collected invaluable atmospheric information on Mars.</p><p>Space is something that has always intrigued me more than anything else. I can’t wait to see where we get with Mars during my lifetime.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=671ac5d5e709" width="1" height="1" alt=""><hr><p><a href="https://medium.com/first-engineering-job/cool-stuff-in-engineering-no-6-do-you-know-how-many-vehicles-are-on-mars-671ac5d5e709">Cool Stuff In Engineering No 6 — Do You Know How Many Vehicles Are On Mars?</a> was originally published in <a href="https://medium.com/first-engineering-job">First Engineering Job</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One Year Left To Make The Most Of College]]></title>
            <link>https://medium.com/first-engineering-job/one-year-left-to-make-the-most-of-college-b60e7ae4fea0?source=rss-84f47a6786f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b60e7ae4fea0</guid>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[college]]></category>
            <category><![CDATA[mechanical-engineering]]></category>
            <dc:creator><![CDATA[Jeff Benning]]></dc:creator>
            <pubDate>Wed, 18 Jan 2017 02:16:05 GMT</pubDate>
            <atom:updated>2017-01-18T02:16:05.551Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*21ra6LmFzSdIZnvBnT3pRg.png" /></figure><p>Many of you reading this blog may not have the luxury of time that others have. Maybe you are in your last year of college and want to do whatever you can to help get yourself ready for a job. The reality of graduation is sinking in and you need to get as much experience as possible. Fast. Here’s a quick list of things you should focus on. Odds are you can only do one so start at the top.</p><h3>Get an Internship</h3><p>If you have time to get a summer internship, do everything you can to <a href="http://www.firstengineeringjob.com/first-engineering-internship/">get one</a>. If it will be your first internship, apply literally everywhere that you think have the slightest chance of getting a job at. It is so important to have an internship on your resume when you start applying to jobs. Regardless of what you actually do there, just being able to list employment for a real company is an immediate confidence boost in your abilities.</p><p>If it’s too late for the summer, you might still be able to get a co-op, a part-time internship. Even if you’re in your last semester, this may still be possible. It certainly can’t hurt to try. The nice thing about this is that a lot of employers hire students in their last year as sort of a trial period for full-time employment. If they like you, they may ask you to stay. I know quite a few people that have gotten jobs like this.</p><h3>Join a Club</h3><p>If you can’t get an internship, a club is the next best thing and if you haven’t been a part of an engineering club yet, it’s <a href="http://www.firstengineeringjob.com/importance-joining-engineering-club/">more important</a> than you probably think. Engineering clubs provide a lot of real life experience you can’t find in the classroom. They are also much more accessible than an internship. There is no application process or interviews. You just show up and get to work.</p><p>Now, there can be that period of acclimating to the people in the club. If you’re not comfortable around a lot of new people, it can be tough. That’s absolutely how I was. After I joined my college’s SAE club, I was pretty quiet the first few weeks. But eventually, I found the best friends I made in college. You make friends quickly when you have to work so closely together towards a common goal.</p><p>You’ll get some real life experience as well. Engineering clubs aren’t just goofing around and playing games. Join a club that builds a tangible product and you can learn a ton of useful information in your last year. Some clubs build robots, some planes, some cars, and some is purely theoretical. Whatever it is you want to learn, you can find a club that deals with it.</p><p>It may also be a wise idea to join the society for your respective engineering branch. Mechanical engineers have <a href="https://www.asme.org/">ASME</a>. Civil Engineers have <a href="http://www.asce.org/">ASCE</a>. Electrical engineers have <a href="https://www.ieee.org/index.html">IEEE</a>. Find the society for your major and join up. Student membership is often free or cheap and it is an excellent place to make connections if you’re willing to put in the work.</p><h3>Get Your GPA Up</h3><p>If you can’t get experience outside of the classroom, do the best you can <a href="http://www.firstengineeringjob.com/8-tips-to-improve-your-study-habits-for-2017/">inside it</a>. Get straight A’s. Do extra work. Talk to your professor and your TA’s. If you aren’t working another job and school is your only obligation, you have no excuse to not get the best grades you can get. If you’ve got some club experience or an internship under your belt and aren’t currently participating in either one, keep your grades up as well.</p><p>Senioritis is a very real thing, as much as I tried to think that it wasn’t. I certainly got a little lazy during my last semester in college but I finished pretty strong. Keep up your grades as well as you can.</p><h3>Talk to Everybody</h3><p>Let people know you’re graduating, whoever you may be talking to. You’d be surprised at the connections you might make. Like they say, “People don’t get jobs. People that know people get jobs.” A recommendation from another person about you goes a lot further than a little experience you might have. Talk to neighbors, family friends, even random people you meet throughout the day.</p><p>This includes talking to professors as well. Let them know what kind of work interests you and that you’re starting to apply for jobs. Ask where they think might be a good fit for a new engineer. Professors are often very well connected in the industry since a lot of them were engineers before they became professors.</p><p>Keep in touch with friends that have already graduated as well. Quite a few of the engineers I graduated with wound up at the same job because they kept recommending their friends for new positions. Pay it forward, too. When you’ve been working for a little while and hear of someone looking for a job, think about if they might fit in at your company.</p><p>Talk to your college advisors as well. They’re used to helping students in your position. See if they have advice for you on what to do, where to apply, or anything else you can do right now to help you get hired.</p><p>Lastly, take advantage of any resume reviews or mock <a href="http://www.firstengineeringjob.com/the-key-to-a-successful-engineering-interview/">interviews </a>that your college’s career center might offer. These are great opportunities to make sure you’re ready for the job hunt once you graduate. This is especially necessary if you don’t have a lot of experience. If you’re not getting a lot of calls back about your resume, it is especially important that you nail every one you get. Practice makes perfect.</p><h3>Do Your Own Work</h3><p>If you can’t find experience elsewhere, get it yourself. Would your grandma like a porch in the back of her house? Do you need new cabinets for your kitchen? Design it. Draw them up in CAD software, make the bill of materials, quote the whole job, including labor, and package it up in a binder. You now have a portfolio.</p><p>This is experience. This is something tangible you can describe on a resume, show during an interview, and use for future projects. You’d be surprised how much you can learn when you stop waiting for someone else to provide you the opportunity and go after it yourself.</p><p>Maybe you have an idea for something you’ve always wanted to design. You’re an engineer. You’ve probably got tons of ideas stewing around in your head. Bring one of them to life. Or get as close to it as you can. Draw the plans. Figure out what you’d need to get it going. This is along the lines of your grandma’s porch except that hopefully, it is something that doesn’t exist yet. A brand new technology. After all, this is the basis of Kickstarter. Find something that you want to see invented and invent it.</p><h3>Takeaways</h3><p>Your last year can be a huge eye opener. Graduation always comes up faster than you think it will so you need to be prepared. But in the case that you weren’t as prepared as you meant to be, do these things I’ve listed here. And when all else fails, get the experience yourself. You don’t have to rely on anyone else to be the best engineer you can be.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b60e7ae4fea0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/first-engineering-job/one-year-left-to-make-the-most-of-college-b60e7ae4fea0">One Year Left To Make The Most Of College</a> was originally published in <a href="https://medium.com/first-engineering-job">First Engineering Job</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>