- Hello, this is Renad Khawatreh, I'm a Computer System Engineer. I love tackling new challenges and collaborating with all kinds of interesting people along the way. I am a strong communicator, i work very well both on my own and as part of a team I am a positive forward-thinking person
- We learned about how we get a good developer mindset using key points when somebody proposes them, often they sound harmless such as:
- Conceiving The Purpose of Software
- The Goals of Software Design
- (Mis)understanding
- Simplicity
- Complexity
- Maintenance
- Consistency
- Prioritizing
-
The desirability of any change is directly proportional to the value of the change and inversely proportional to the effort involved in making the change.
- Solving Problems
- Good enough is fine
- Predictions
- Assumptions
- Stop Reinventing
The only times it’s okay to reinvent the wheel is when any of the following are true:
- You need something that doesn’t exist yet
- All of the existing “wheels” are bad technologies or incapable of handling your needs
- The existing “wheels” aren’t being properly maintained
- Resistance
- Automation
- Code measurement
- Productivity
- Testing
- (Under)Estimation
- Running Away From Rewriting
- Documentation and Commenting
- Picking Technologies
- Self-Development
- Don’t be a hero
- Don’t Ask Questions… Ask For Help
- Huseyin Polat Yuruk who wrote the article said that when you have tried everything, and preferably after you have a working solution, now is the best time to seek advice. Look to peers and senior developers to review your code. He strongly recommends we read Code Simplicity from
Max Kanat-Alexander
- The main goal of this Article is that to get a better understanding of the principles of a good developer, the article reviews the most sentences we had in our minds. Then, to gain a better understanding of the problem and the most common questions, the article suggested key points to share with a developer to be more efficiency.