Oct 8, 2023
Edabit
seen from Australia
seen from Canada
seen from United States
seen from Israel
seen from China
seen from China
seen from Hong Kong SAR China
seen from Belarus
seen from Italy
seen from United States
seen from Vietnam
seen from Italy
seen from United States
seen from T1
seen from Brazil
seen from T1
seen from United States
seen from United States
seen from United States
seen from South Korea
Edabit
Coding learning hub with several languages and an active userbase
Designer Stefano Peschiera shares his tried-and-true tips and workflow for choosing effective and beautiful UI color schemes.
Here's how you memorize things:
Tell yourself you will do it. Don't try to find tricks or easy ways out of it, just sit down and do it
Write what you want to memorize on some index cards. Put one half of what you need to learn on one side, then another half on the other side
Every day for about 15-30 minutes, drill yourself on the index cards, trying to recall each one. Put any cards you don't get right into a different pile, just drill those cards until you get bored, then try the whole deck and see if you improve
Before you go to bed, drill just the cards you got wrong for about 5 minutes, then go to sleep.
If you do this every day, you should be able to memorize most things I tell you to memorize in about a week to a month. Once you do, nearly everything else becomes easier and intuitive, which is the purpose of memorization. It's not to teach you abstract concepts, but rather to ingrain the basics so that they are intuitive and you don't have to think about them. Once you've memorized these basics they stop being speed bumps preventing you from learning more advanced abstract concepts.
There is no genius. No one works alone in a cave, and if they are they’re probably not working on the right thing or making something useful. Learn to lose the ego: be able to work and communicate with other people. Criticism is not evil; invite it early and often, especially from people more senior than you
Embrace failure: fail fast, fail often, and change your approach. Don’t fail at the same thing repeatedly. Don’t hide the history. Document what happened and learn from it.
Be a small fish: aim to learn from more senior developers and people more experienced than you. Be open to influence from others.
Pay attention to timing: involve collaborators early, but not too (at the 'sweet spot'). You don’t want design by committee. Have a mission statement and a mockup.
A complete computer science study plan to become a software engineer. - jwasham/coding-interview-university