- Treat interviews as practice sessions
- Have fun!
- (I wanna be stupid – want to work with libraries instead of comming up with solutions which others already had before)
- Ask stupid questions! Swallow the ego! Don’t try to impress people by not asking questions! No one cares and no one remembers stupidity, but they’ll remember that you asked
- It saves lot’s of time and resources (for a company)
- Encourage others to ask you questions!
- 30 minutes rule
- Don’t waste more than 30 minutes (may be adjusted) on an issues without asking questions
- use Docstrings to document code
- use typehinits to reduce the docstrings needed
- use markdown (easy and portable)
- when following a tutorial or a talk: write down everything
- inhences your learning – many people learn better by taking notes
- documentation makes you look good
- gives you an advantage compared to people who didn’t take notes
- you may help others by publishing your notes
- notes may be used in other projects later
- notes may be a great basis to write books
- docs can look great (look at docs.python-requests.org & fastapi.tiangolo.com)
- not a guarantee for a successful project – but makes it more likely to be successful
- don’t repeat yourself
- use typehints
- put functions on GitHub
- you don’t want to debug code which worked before
- manual tests are boring and error-prone
- write tests!
- document how to use the tests (in the README)
- running the code
- testing the code
You may use readthedocs or GitHub pages.
- If you wanna become good at something: practice!!
Use Tools, which you use at work to build your own projects.
Explore the tools deeply.
Try new things.
Always be typing!
- Do it!
One types, the other watches and maybe comments
- Always be the person typing! Even if you don’t understand what you are typing!
If you are taking a class: Always be typing!
- Do expercises
- Don’t just be a spectator! Do it yourself!
- „You can’t become a tech CEO by watching the social network“
- First apply (the basics)
- Then learn
- build muscle memory in your fingers!
- take an active role in pair programming!
Own thoughts and statements from conversations after talk
Daniel Roy Greenfield:
- emojis are important in non-verbal communication
- If you work in a company which doesn’t accept/encourage asking questions: switch to another company!
- may make sense to find out how bosses want you to behave!