Заглавная страница Избранные статьи Случайная статья Познавательные статьи Новые добавления Обратная связь FAQ Написать работу КАТЕГОРИИ: АрхеологияБиология Генетика География Информатика История Логика Маркетинг Математика Менеджмент Механика Педагогика Религия Социология Технологии Физика Философия Финансы Химия Экология ТОП 10 на сайте Приготовление дезинфицирующих растворов различной концентрацииТехника нижней прямой подачи мяча. Франко-прусская война (причины и последствия) Организация работы процедурного кабинета Смысловое и механическое запоминание, их место и роль в усвоении знаний Коммуникативные барьеры и пути их преодоления Обработка изделий медицинского назначения многократного применения Образцы текста публицистического стиля Четыре типа изменения баланса Задачи с ответами для Всероссийской олимпиады по праву Мы поможем в написании ваших работ! ЗНАЕТЕ ЛИ ВЫ?
Влияние общества на человека
Приготовление дезинфицирующих растворов различной концентрации Практические работы по географии для 6 класса Организация работы процедурного кабинета Изменения в неживой природе осенью Уборка процедурного кабинета Сольфеджио. Все правила по сольфеджио Балочные системы. Определение реакций опор и моментов защемления |
Exercises That Will Make You A Better EngineerСодержание книги
Поиск на нашем сайте
Posted on 23rd Jul 2013 by Bogdan Carstoiu in CEO's Blog
It is so easy to distinguish an engineer (or an engineer to be) from a non-engineer. When we interview people for a software engineering position, we want to determine how much of an engineer the candidate is. That’s why we ask a fair amount of questions apparently unrelated to software. Real engineers focus on the problem, break it into pieces, and analyze them. They translate the problem into their “own words”, making analogies with common, easy-to-understand processes. Once their solution is challenged, they are able to optimize and explain it. Non-engineers on the other hand tend to scratch the surface of the problem and come up with a quick solution. When challenged with questions, they get defensive saying that it’s not something they ever studied or ever did and that’s why they cannot propose a better solution. The truth is not everyone is born to be an engineer. And still, many schools pretend to be able to train people in becoming one. Jokes aside, engineering is not something you are born with, well … maybe exceptional capabilities. Anyone can train to become a decent engineer. Unfortunately, schools are not of great help. For example, software engineering schools train students in a lot of things, because knowing as much as possible about computers is definitely good. Certainly, it’s necessary, but not enough. Computing helps people and the final goal of a software engineer is to make things possible. Of course, the way things are built matters, but the final objective is to improve someone’s life. Many times, engineers forget about the final goal, usually because they are educated to focus on the inner layers. Fortunately, there are ways you can train yourself to become a better engineer. 1. Ask Yourself Questions. A Lot Of Them! I do not mean questions related to your work (I assume you are already doing this), but situational questions in general. In short, be inquisitive. I remember that, when I was about seven years old, I noticed that generally the braking distance does not depend on the car weight. For almost a month, I tried to find an explanation for it… It might seem pointless to ask yourself questions for which you can very easily find the answer on the Internet, but training your brain is really a good thing. Some people prefer to lift weights, you should lift problems. Validate Your Findings. Assuming you’ve already found some answers, do some research on the Internet. Understanding how far your approach was from ideal may be very rewarding. Put Yourself In Charge. There are many ways to do a specific thing, but some ways are better than others. Engineers are change agents. You can imagine what would have happened if Einstein had taken everything for granted. Yes, I think Einstein was a great engineer, as he was able to connect the dots. Learn How To Ask Questions. No matter who you ask questions – yourself or others, there has to be a process that starts with the overall picture and ends with the last detail. To me, the process of asking questions is very much like Google Maps. First, you get the picture of the entire region and afterwards you may zoom in. The basic set of questions imply at least a “what”, a “how”, a “when”, and a “where”. Sometimes, you may need to ask more, but always ask “what” and “how” (in this order). Having a strategy for asking questions is one of the most important things you can do – never break the rule and try to make other people follow the process. Otherwise, simple things like meetings, for instance, can turn into mess. 5. Don’t Be Afraid Of Making Mistake s. Great engineers make big mistakes. People who do not want to make mistakes live by the book. For example, in software engineering there is a solution for almost anything. All you need is a little bit of research. I like it when people still try to build greater things, even though they failed in the past. It’s really no shame to fail. With engineering in particular, lots of things can go wrong and many lands remain unexplored. Because most people choose to walk the line. I do not particularly like people who give up once they discover that other people tried the same thing and failed. Before anything else, it is important to understand why other attempts failed. Just because other people failed doesn’t mean you should abandon.
|
||||
Последнее изменение этой страницы: 2016-12-28; просмотров: 332; Нарушение авторского права страницы; Мы поможем в написании вашей работы! infopedia.su Все материалы представленные на сайте исключительно с целью ознакомления читателями и не преследуют коммерческих целей или нарушение авторских прав. Обратная связь - 3.147.64.68 (0.009 с.) |