KELLY BIO: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
 
(74 intermediate revisions by the same user not shown)
Line 4: Line 4:


==2) COMMITMENT: Can you commit to 10 hours of volunteer time for 90 days?==
==2) COMMITMENT: Can you commit to 10 hours of volunteer time for 90 days?==
A serious time commitment is required.


All we can do is try...and keep trying.  I will try 2 hours per day during normal workdays, preferably in the mornings.
All we can do is try...and keep trying.  There is good probability.


==3) PURPOSE: What is the biggest value that you get out of volunteering with OSE?==
==3) PURPOSE: What is the biggest value that you get out of volunteering with OSE?==
Line 12: Line 11:
The biggest value volunteering with OSE provides is a team to work on engineering projects that are inline with my abilities and ambitions.
The biggest value volunteering with OSE provides is a team to work on engineering projects that are inline with my abilities and ambitions.


==4) OPEN SOURCE SOFTWARE AND COLLABORATION Are you willing to download a Ubuntu distribution of Linux that comes preloaded with all software that OSE uses - to facilitate any software issues?==
==4) OPEN SOURCE SOFTWARE AND COLLABORATION Are you willing to download an Ubuntu distribution of Linux that comes preloaded with all software that OSE uses - to facilitate any software issues?==


Already done.  That was easy!
Already done.  That was easy!
Windows supports the software I use most and that is my primary OS.
Windows supports the software I use most and that is my primary OS.


==5) We collaborate via work logs where we document our work and include links to all work product. Are you willing to do this on a continuing basis?==
==5) LOGGING.  We collaborate via work logs where we document our work and include links to all work product. Are you willing to do this on a continuing basis?==
I like this work log concept.  In the past I refused to update worklogs that were very tedious to update, did not provide good data to management, or was any help to me personally.  This work log concept is efficient and useful.
I like this work log concept.  I tend to log everything.  In the past I refused to update particular worklogs that were very tedious to update, did not provide good data to management, or were not helpful.  This work log concept is efficient and useful.


==6) FINANCES: Do you currently have a full time job?==
==6) FINANCES: Do you currently have a full time job?==
I have a steady income. I am a manager for the pre-schools my partner runs, and I contract my product design services to OEMs on an occasional basis.  My workload may not be consistent, so there are periods that duty calls elsewhere.
I can cover expenses. I work full time.


==7) VIDEO INSTRUCTIONALS: A big part of our work is documentation and instructionals- Are you willing to learn Kdenlive, collaborative video editing and screencasting?==
==7) VIDEO INSTRUCTIONALS: A big part of our work is documentation and instructionals- Are you willing to learn Kdenlive, collaborative video editing and screencasting?==
Line 35: Line 34:


==10) HARD SKILLS: What hard skills do you have such as IT, CAD, Graphics, Publishing, manufacturing, design, etc.==
==10) HARD SKILLS: What hard skills do you have such as IT, CAD, Graphics, Publishing, manufacturing, design, etc.==
The skill I do not have that I want is creating design calculations in Smath, or equivalent.  I was trained in Matlab, and it hasn't been helpful nor do I feel it is appropriate until at least the third major generation of design.
The skill I do not have that I want are creating design calculations in Smath, or equivalent.  I have created design calculations in Matlab, but design calculations should be sensical and on a WYSIWIG program.


The skills floating around my head somewhere include:
Skills on the list include:


IT: TCP/IP, CANbus, Modbus.
IT: TCP/IP, CANbus, Modbus.
Line 54: Line 53:


==11) SOFT SKILLS: Do you have experience in management+ conflict resolution? Teaching? Managing/starting a community or group?==
==11) SOFT SKILLS: Do you have experience in management+ conflict resolution? Teaching? Managing/starting a community or group?==
===Executive Summary===
===SHORT AND SWEET===
The Golden Rule
Managers lead and workers manage.


The Buddy System
If workers cannot manage, then they need a manager to lead them in management.


The Scientific Method
A manager must recognize limitations in workers' management.


===Management Philosophy===
The job of a manager is to remove the limitations in workers' management.  
I like a functional leadership model, and try to fulfill the roles I can.  I am better situated on the "other side of the wall", and feel that the traditional management that maintains the wall should be replaced by servers, for the most part.  


For the management tasks that servers cannot replace, I have been most interested in adapting the communication paradigms that IT has created, adapting software management strategies, and using the team-based approaches that manufacturing has developed. I believe that documents ultimately rule the show, and ultimately dictate the managers tasks. 
Managers enable workers to manage.


Idea management is a core concept to my personal approach, and I believe that data will ultimately provide me the best tools.  I don't suppose to know everything, but want to make sure people who do know tell people that need to know.  I adapt my language to suite each party for a better take-a-way and reception.  Frequently, ego is a stumbling block for people that harbor a mono-view of the dual-nature existence, and I tend to hack away at that to maintain an objective view.  I would like to also personally learn what people know, but that is secondary.  In the past I have tried to know everything and spread people's ideas.  I know this function is better suited for a server, and a wiki provides a good way to keep the tedium out of my head.
Ultimately, the greatest limitation in workers' management will be the manager.


The elephant in the room is I do come up with half-brained ideas quite readily that seem to discredit me. If I am ever mistaken, then I greatly want to learn the truth.  I followup statements I make to check their accuracy and will state my corrected view if I find disconnect. I will also trust but verify, to remedy my short-sightedness.  I'm always hoping someone out there will have a matching half-brained idea. In Belbin's team role theory, this function is referred to as a Shaper.  And the process of creating chaos to recognize patterns is vital to strong team development, but a good Coordinator is required to maintain the stability of the team.  Teams are built on trust after all.  I hope to not to create too much chaos and focus on developing Coordinator skills to maintain trust among the team. 
Managers lead to become workers who can manage.


People can agree to about anything, and conflicts frequently result from a communication breakdown that is easily corrected.  If emotions become involved in a conflict, then dealing with issues discretely is important.  The blame for issues is typically 50/50, and both parties have to work towards a solution.  Usually, people just want the truth. 
===General Principles===


A lot of miss-communication is rooted in a lack of standards.  A motto I have is "If you're not using a standard, then you should be creating one."  There is a logical approach to every micro-decision, and standards should efficiently organize most of this logic.  Standards become the language that enables multiple people to operate together.  Greater productivity requires multiple people to make the same decision given the same information.  This convergence requires an elimination of tribal knowledge.  It has been hard for me to let go of my ego that gives me a sense of value.  Through gameification, I have found purpose in devolving tribal knowledge instead of harboring it. 
The Golden Rule


Everything is a game; a very serious game.  I play the game by asking good questions, finding out the answers for myself if they are not readily available, and creating reference material to direct people to if they ask me the same question. And, I tell people to relax because it's just a game.
The Buddy System


The goal of engineering, design, and management is linearization.  Linearization requires restricting certain degrees of freedom (DOF) and enabling other DOF so that all forces have acceptable reactions and useful work may be extracted.  Additional points are awarded for efficiency, predictability, elegance, and aesthetics.  Typically, enabling (1) DOF results in the best working efficiency.  And, controlling restricted DOF when reactions are not acceptable avoids catastrophic failures.  Positive engagement and controlled friction are good tools to use for these goals. To increase rigidity: "box it up."  To absorb energy, "let it go."
The Scientific Method
 
===Guidelines for Human Relations===
* Be helpful to your listener.
** Always explain the Why, How, When, Where, Who as best as possible when telling people to do something, or don't do something, or what's right, or what's wrong. 
** Explaining the conditions and assumptions allows the listener to adapt the concept to their frame of reference.  Also, short-sightedness is revealed before developing a concept too far.
** Communication should be precise, concise, comprehensible, and revealing.
 
* Be a good listener.
** Try to understand people and the essence of their comments and questions.
** People like being understood and frequently don't give enough information to be understood.
** Read between the lines.
 
* Repeat concepts in different ways.
** Learning new concepts usually requires three attempts.
** The goal is to find the simplest most logical truths.
 
* Develop a technical and prose understanding of concepts.
** Short familiar phrases are easier to understand and transmit.
** Long winded technical explanations are required to fully understand.
 
* Ask good questions.
** There are such things as bad questions; and it's better to discover the good questions than seeking an answer to an ill-formed question.
** Answers to good questions are usually much simpler and comprehensive than answers to bad questions.
** Break a problem down into its components.
 
* Try to answer your own questions.
** There should be resources to answer questions.
** Ask how to find an answer.
 
* Don't hypothesize too much or create what-if scenarios.
** Get actual feedback.
** Stay to the tasks that matter.
** It is better to interpolate than extrapolate.
 
* Propose a solution if you bring up a problem.
** There are far too many problems and what we really need are solutions.
 
* Be realistic.
** There will be a test.
** A person will complete a task regardless if they have the resources they need, and the results are predictably not ideal.
** Complexity breeds more complexity.
 
* Say your thoughts to a buddy.
** Helping people typically only requires listening to them so they have a chance to formulate their ideas into words.
** Don't bring ideas up the chain that didn't sound good out loud or you are hesitant to repeat to other people.


* Don't throw people under the bus.
Hustle
** You are probably wrong and the problem is much closer to home.
** People make mistakes, and that is okay.
** Bring people up instead of putting them down.


* Tame that superiority complex and don't get stuck in a rut; stay even keeled and peachy keen.
Lean
** Accomplishing a goal is great, but you're stuff will likely break or it contains a logical flaw that existed from conception.  Keep your head in the game.  Your actions speak more than your words.
** Nothing is really that bad or buggered up.  Solutions are typically very simple and elegant, and it is important to seek the answers with a positive attitude.


* Give credit where credit is due.
Agile
** The more the merrier.


* Admit when you are wrong.
Luck
** People like it when you tell them they were right and you were wrong.


* [https://www.psychologytoday.com/articles/201005/make-your-own-luck Be Lucky] (below statements developed from linked article.)
===Conflict Resolution===
** See serendipity everywhere. Every moment is rich with lessons. Everything you learn is useful somehow. 
Teams require trust.
** Prime yourself for chance.  Look to your network and keep expanding it.  Keep an open mind.  Don't judge too soon or too concretely.  Avoid neuroticism; the tendency to experience negative emotional states like anxiety, anger, guilt, and depression. 
** Relax a bit.  Provide a comfortable environment to share ideas.  There are hidden opportunities everywhere.
** Say yes.  Try new things.  Supporting another person creates a team, which is more valuable than creating a negative persona.
** Embrace failure.  The greatest learning opportunities are born from failure.


* Plan for failure and forgetting everything.
The best conflict resolution is to avoid conflict. I try to avoid conflict by following some [[KELLY BIO/GUIDELINES OF HUMAN REATIONS|guidelines of human relations]].
** Get your ducks in a row so when failure happens you have resources to remedy the problem and remember why things were done a certain way in the past to correct them in the future.


* Stay the course.
I also realize how silly everything has become and let things go. It's silly [[BEING HUMAN BEING|being human being]].
** This one is tricky, but stay the course under normal conditions.
** Implement improvements incrementally.  


* Avoid discussing conspiracy theories, making judgments with limited information, and discussing things that are outside your domain.
Conflicts require solutions. People can agree to about anything, and conflicts frequently result from a communication breakdown that is easily corrected. If emotions become involved in a conflict, then dealing with issues discretely is important. The blame for issues is typically 50/50, and both parties have to work towards a solution.
** There are a lot of cool ideas out there and ways to view events, but they are distracting and trivial to the tasks at hand.
** This isn't a spin room.
** A tool that is chattering isn't cutting well.


* Start resolving issues ASAP.
===Teaching===
** Sorting out bugs is a long process and time is valuable.   
  I have a large frame of reference and have good luck assimilating ideas into other peoples frame of reference.  I ultimately recognize that I have to assimilate others frame of reference to my own frame of reference to have good luck assimilating ideas.
** There will frequently be roadblocks that require additional information, that requires more waiting.
** Morale is improved when issues are dealt in a timely manner.


* Don't ask someone for a resource.
===Learning===
** Explain your situation, and your proposed solution, and how the resource seems like the best option.
Learning: I believe there are lessons in every moment in life and every lesson will be useful later in life. Teaching, documenting, and kinetic activities are useful methods of learning.  Learning is an important function of group development.  I like learning and teaching using dualisms.


==12) Which would you prefer to do - this Video Cover Letter or an online interview with OSE staff?==
==12) Which would you prefer to do - this Video Cover Letter or an online interview with OSE staff?==
Video cover letter.
Video cover letter.  Although interviews provide better raw feedback, I think the video cover letter is better in an online environment.


==13) Do you have any questions about OSE or how the Development Team works? Or final comments that you would like to make that we should have asked you but didn't?==
==13) Do you have any questions about OSE or how the Development Team works? Or final comments that you would like to make that we should have asked you but didn't?==
I can show you what projects I have been working on.
I can show you what projects I have been working on.

Latest revision as of 00:49, 23 March 2018

1) What is the link to your Video Cover Letter video upload?

You will do this after you have uploaded your Video Cover Letter. You don't need to answer this question in your video. Please make your video public, and leave it on YouTube or another video sharing site at least until the end of your involvement with the OSE Development Team so that we may share it with other team members as needed.


2) COMMITMENT: Can you commit to 10 hours of volunteer time for 90 days?

All we can do is try...and keep trying. There is good probability.

3) PURPOSE: What is the biggest value that you get out of volunteering with OSE?

The biggest value volunteering with OSE provides is a team to work on engineering projects that are inline with my abilities and ambitions.

4) OPEN SOURCE SOFTWARE AND COLLABORATION Are you willing to download an Ubuntu distribution of Linux that comes preloaded with all software that OSE uses - to facilitate any software issues?

Already done. That was easy! Windows supports the software I use most and that is my primary OS.

5) LOGGING. We collaborate via work logs where we document our work and include links to all work product. Are you willing to do this on a continuing basis?

I like this work log concept. I tend to log everything. In the past I refused to update particular worklogs that were very tedious to update, did not provide good data to management, or were not helpful. This work log concept is efficient and useful.

6) FINANCES: Do you currently have a full time job?

I can cover expenses. I work full time.

7) VIDEO INSTRUCTIONALS: A big part of our work is documentation and instructionals- Are you willing to learn Kdenlive, collaborative video editing and screencasting?

I am very willing to develop video editing services. Showing people the ropes is an asynchronous process these days.

8) EXECUTION AND INITIATIVE: What is the biggest task that you are proudest of yourself most that you accomplished? Please give an example of an audacious goal that you have set for yourself?

One of the biggest tasks that I have completed is getting a job as a machinist making production parts. Assuming this role was critical if I ever wanted to create an OEM.

An audacious goal I have set for myself is creating an OEM.

9) LEARNING: Show an example of something you learned that revolutionized your life?

As a child, I always wondered what the spinning shaft under trucks did. I have learned quite a bit about those spinning shafts; and everything connected to them, and how great they are, and ways to eliminate them, and how to improve them.

10) HARD SKILLS: What hard skills do you have such as IT, CAD, Graphics, Publishing, manufacturing, design, etc.

The skill I do not have that I want are creating design calculations in Smath, or equivalent. I have created design calculations in Matlab, but design calculations should be sensical and on a WYSIWIG program.

Skills on the list include:

IT: TCP/IP, CANbus, Modbus.

CAD: AutoCAD, AutoCAD Electrical, Inventor.

Graphics: Illustrator, Corel Draw

Publishing: Microsoft Word using Headings

Manufacturing: hand tools, power tools, lathe, mill, CNC, electrical assembly, mechanical assembly, mechanics, hydraulics, welding, testing.

Design: piece part drawings, weldment drawings, machining drawings, assembly drawings, wire harness drawings, installation drawings, service kit drawings, exploded parts diagrams, simple hydraulic systems, human-machine interface (discrete controls, overlays, and graphic displays), off-highway electrical & control systems, marine crane electrical & control systems, hydraulic dam sizing, wind turbine sizing, PV sizing, budgeting, instructional guides.

etc: cooking, organizing.

11) SOFT SKILLS: Do you have experience in management+ conflict resolution? Teaching? Managing/starting a community or group?

SHORT AND SWEET

Managers lead and workers manage.

If workers cannot manage, then they need a manager to lead them in management.

A manager must recognize limitations in workers' management.

The job of a manager is to remove the limitations in workers' management.

Managers enable workers to manage.

Ultimately, the greatest limitation in workers' management will be the manager.

Managers lead to become workers who can manage.

General Principles

The Golden Rule

The Buddy System

The Scientific Method

Hustle

Lean

Agile

Luck

Conflict Resolution

Teams require trust.

The best conflict resolution is to avoid conflict. I try to avoid conflict by following some guidelines of human relations.

I also realize how silly everything has become and let things go. It's silly being human being.

Conflicts require solutions. People can agree to about anything, and conflicts frequently result from a communication breakdown that is easily corrected. If emotions become involved in a conflict, then dealing with issues discretely is important. The blame for issues is typically 50/50, and both parties have to work towards a solution.

Teaching

 I have a large frame of reference and have good luck assimilating ideas into other peoples frame of reference.  I ultimately recognize that I have to assimilate others frame of reference to my own frame of reference to have good luck assimilating ideas.

Learning

Learning: I believe there are lessons in every moment in life and every lesson will be useful later in life. Teaching, documenting, and kinetic activities are useful methods of learning. Learning is an important function of group development. I like learning and teaching using dualisms.

12) Which would you prefer to do - this Video Cover Letter or an online interview with OSE staff?

Video cover letter. Although interviews provide better raw feedback, I think the video cover letter is better in an online environment.

13) Do you have any questions about OSE or how the Development Team works? Or final comments that you would like to make that we should have asked you but didn't?

I can show you what projects I have been working on.

Retrieved from "https://wiki.opensourceecology.org/index.php?title=KELLY_BIO&oldid=168584"