I am one of those people who function better by writing things down. One day, I realized that most of my notes don’t have to be private, so here they are - my second brain. Be warned that, if you stumble upon something here that doesn’t make sense to you, it isn’t meant to!
Brainstation.io talk
Ask from the coordinator: To break it down further, a potential format for the 1-hour session could be something like: - Introduction to yourself, your career journey, and your role at AWS - A potential case study or work example, exemplifying how you utilize your skills at work - Job search tips for when they eventually begin applying - Q&A Portion Flow: Intro: Major stages of my career and some of my mistakes along the way so that you can avoid those in your career. Adobe and Snapdeal: Adobe Story and e-commerce website: distributed systems and some frontend work. Excited about technology but didn’t know expectations in a corporate environment. They don’t teach you this in college. Tip 1: Ask for feedback from well-intentioned peers. Amazon: 10+ years now. Won’t bore you with all the teams I’ve been part of, so just the interesting ones. Lambda: I joined because I was excited about the potential of serverless. However, a very new field for me and I struggled. VM ballooning. Tip 2: How to make learning durable? Code yourself. Even if you are following a tutorial, rewrite on your own. Anki. Lookout for Metrics: Intentionality == “know what you’ll get out of a certain project”. I work in SageMaker. About SageMaker. I-ML org: we provide cloud based IDEs - JupyterLab or VS Code - for ML. Example of my work: Cosmos. Tip 3: Work backwards from customers, not a solution == solution should follow the problem, not the other way around.