Everything I know about great Software Developers.
π§΅π
1. Great Software Developers are humble.
They never put themselves above anyone else. They are willing to leverage existing solutions and listen to others.
(1 of 15)
2. Great Software Developers are self-motivated to learn.
They never stop improving and never get complacent. They understand the importance of growing their skills.
(2 of 15)
3. Great Software Developers know when to write code and when to avoid it.
They understand the trade-offs involved in writing code. They understand that the best code is the one that was never written.
(3 of 15)
4. Great Software Developers are willing to challenge the status quo.
They understand that innovation happens when we are willing to challenge assumptions and think out of the box.
(4 of 15)
5. Great Software Developers think before they write.
They never jump to conclusions. They are methodical and take the time to explore before exploiting.
(5 of 15)
6. Great Software Developers never stop sharing.
They constantly look for ways to make the team around them look better. They understand this is the way they can multiply their value.
(6 of 15)
7. Great Software Developers support everyone around them.
They find areas where others struggle and lend a hand. They are constantly lifting others.
(7 of 15)
8. Great Software Developers have an insatiable curiosity.
They never settle before reaching the bottom of things. Every question is a new opportunity to learn.
(8 of 15)
9. Great Software Developers run towards problems, not away from them.
They arenβt afraid of failure. They look forward to solving difficult challenges as soon as they arise. They find ways to put themselves right at the front line.
(9 of 15)
10. Great Software Developers have a strong commitment to meet deadlines.
They make sure deadlines are both achievable and understood by them and their teams. They help those around them get across the finish line if necessary.
(10 of 15)
11. Great Software Developers take a lot of pride in their work quality.
They relentlessly focus on the internal and external quality of everything they build. They understand the importance of standing up for what they believe.
(11 of 15)
12. Great Software Developers understand trade-offs and know how to manage competing priorities.
They have a holistic view of the environment. They consider available constraints before recommending a solution.
(12 of 15)
13. Great Software Developers use Software as a vehicle to change lives.
They understand the impact of their work. They use their skills for good, to make the world a better place.
(13 of 15)
14. Great Software Developers have a "get stuff done" mentality.
They are eager to build things, and they donβt stop until they finish them. They understand the importance of results over the process to achieve them.
(14 of 15)
15. Great Software Developers criticize ideas and never the people who hold them.
They believe that ideas should stand or fall on their own merits. They never engage in personal attacks.
(15 of 15)
16 (bonus). Great Software Developers are proactive.
They take initiative to improve their team's developer experience.
20 (bonus). Great Software Developers understand the power of documentation.
They understand that others come after them. They strive to document their findings and every important detail to pave the way for others.
(20 of 15)
21 (bonus). Great Software Developers aren't limited by particular tools.
They understand that different problems require different approaches. They strive to learn the fundamentals and pick the best tool for every situation.
Here are 7 ways you can deal with overfitting in Deep Learning neural networks.
π§΅π
A quick reminder:
When your model makes good predictions on the same data that was used to train it but shows poor results with data that hasn't seen before, we say that the model is overfitting.
The model in the picture is overfitting.
π
1β£ Train your model on more data
The more data you feed the model, the more likely it will start generalizing (instead of memorizing the training set.)
Look at the relationship between dataset size and error.