What Makes a World Class Engineer

What makes a world class engineer?

Analytical problem solving with code
Technical communication--I can implement your approach just from your description.
Engineering best practices and approach--debugging, code structure, referring to documentation, patience, making code that others can "pick up", DRY code, Small Code, Single Responsibility Principal
Non-technical communication (empathetic and thoughtful communication)
Language and computer science experience

Our Principals

DRY (don't repeat yourself) - Every piece of knowledge must have a single, unambiguous, authoritative representation within the system. Practically speaking, if something does something, there should only be 1 place we're doing it.
KISS (Keep it Simple Stupid) & YAGNI (You aren't going to need it) - Don't overengineer components. What's the smallest, simplest version of this that we can write? The easiest code to maintain is the code we don't write. 80% of the time is invested in 20% of the functionality. Opt for removal and simplicity over complexity and clever.
Once and Only Once - You should only declare a behavior one time. There should be a single version of truth. When you have multiple versions of code, there often becomes subtle differences in code that causes things to behave unexpectedly (buggy). A Single Point of Truth keeps this from happening. Practically, opt for factories in your code.
Open-Closed Principal & Dependency Inversion - Your code should be open to extension, but closed to modification. If someone wants to extend your code, they should be able to do it easily. They should have a minimal interface, and no undeclared requirements.
Do One Thing & Separation of Concerns - Each class or module should only do 1 thing. Single Responsibility Principal. If things are mixed together, then they should be broken down into smaller items. If your class is greater than 100 lines, think about if it's breaking this rule. If a method or function is longer than 10 lines, is it doing too much?

PreviousCulture NextSituational Statuses

Last updated 7 years ago

What makes a world class engineer?

Analytical problem solving with code

Technical communication--I can implement your approach just from your description.

Engineering best practices and approach--debugging, code structure, referring to documentation, patience, making code that others can "pick up", DRY code, Small Code, Single Responsibility Principal

Non-technical communication (empathetic and thoughtful communication)

Language and computer science experience

Our Principals

DRY (don't repeat yourself) - Every piece of knowledge must have a single, unambiguous, authoritative representation within the system. Practically speaking, if something does something, there should only be 1 place we're doing it.

KISS (Keep it Simple Stupid) & YAGNI (You aren't going to need it) - Don't overengineer components. What's the smallest, simplest version of this that we can write? The easiest code to maintain is the code we don't write. 80% of the time is invested in 20% of the functionality. Opt for removal and simplicity over complexity and clever.

Once and Only Once - You should only declare a behavior one time. There should be a single version of truth. When you have multiple versions of code, there often becomes subtle differences in code that causes things to behave unexpectedly (buggy). A Single Point of Truth keeps this from happening. Practically, opt for factories in your code.

Open-Closed Principal & Dependency Inversion - Your code should be open to extension, but closed to modification. If someone wants to extend your code, they should be able to do it easily. They should have a minimal interface, and no undeclared requirements.

Do One Thing & Separation of Concerns - Each class or module should only do 1 thing. Single Responsibility Principal. If things are mixed together, then they should be broken down into smaller items. If your class is greater than 100 lines, think about if it's breaking this rule. If a method or function is longer than 10 lines, is it doing too much?