Knowing that You're Bad!
I think that if you have never thought of yourself as a bad engineer before, then you are probably a Bad engineer!
Diverse Experiences in Tech as a programmer
Over my 10 last jobs, over the course of 14 years, no two of them were even remotely similar. The amount of variation in terms of field, company size, culture, personalities, skill sets, and process is really high. I think it made me a lot stronger in general. Nothing like going through a few rounds of lay-offs to understand why certain things happen in business.
The Unique Feeling of Visceral Mastery
Experiencing extreme effortless mastery in person doesn't compare to reading about it or watching an internet video. It can really change you forever.
PARTNERING UP: Always beneficial
I found that partnering up brings a lot of value, serving as a constant critical feedback loop and a cross-benefit relationship. If you can't get a real person, use a rubber duck. Its the "Dummy Developer" concept which can also bring you value by pulling value out of yourself. Just dont get caught talking to it out loud about systems design... 😂
THEORY OFF / ON: being Naive on demand!
This bit is about being able to be naive on demand for 30 minutes, and then being theoretical again for 30 minutes. The reason? Promote action and feedback ahead of over-analysis, for the sake of balance and speed. Let me know your thoughts in the comments below.
DEVELOPER TOOLBOX: Building generic components.
The reason humanity has reached such great levels of scientific advancement is because each person who contributes, does so based on years of proven discoveries made by people before them. So as a developer I'm trying to keep this in mind. In order to keep getting more productive, I want to build on top of previous discoveries that are tried and tested. Those can be others' or my own.
I think that if you have never thought of yourself as a bad engineer before, then you are probably a Bad engineer!
Diverse Experiences in Tech as a programmer
Over my 10 last jobs, over the course of 14 years, no two of them were even remotely similar. The amount of variation in terms of field, company size, culture, personalities, skill sets, and process is really high. I think it made me a lot stronger in general. Nothing like going through a few rounds of lay-offs to understand why certain things happen in business.
The Unique Feeling of Visceral Mastery
Experiencing extreme effortless mastery in person doesn't compare to reading about it or watching an internet video. It can really change you forever.
PARTNERING UP: Always beneficial
I found that partnering up brings a lot of value, serving as a constant critical feedback loop and a cross-benefit relationship. If you can't get a real person, use a rubber duck. Its the "Dummy Developer" concept which can also bring you value by pulling value out of yourself. Just dont get caught talking to it out loud about systems design... 😂
THEORY OFF / ON: being Naive on demand!
This bit is about being able to be naive on demand for 30 minutes, and then being theoretical again for 30 minutes. The reason? Promote action and feedback ahead of over-analysis, for the sake of balance and speed. Let me know your thoughts in the comments below.
DEVELOPER TOOLBOX: Building generic components.
The reason humanity has reached such great levels of scientific advancement is because each person who contributes, does so based on years of proven discoveries made by people before them. So as a developer I'm trying to keep this in mind. In order to keep getting more productive, I want to build on top of previous discoveries that are tried and tested. Those can be others' or my own.
No comments:
Post a Comment