“Take advantage of learning everything that comes your way because eventually it all connects. Even things that might seem left field like laser beams - we use lasers to make servers talk to each other - it all ends up being applicable.“- @lhi, mission critical engineering, SF 
“Don’t doubt yourself so much. The whole imposter syndrome thing is real, and it’s hard to get past. But everyone is faking it to an extent. And don’t be afraid to ask what you might think are stupid tech questions.” -@lee_eisenhardt, site ops technician, Atlanta data centre
“Keep things simple. There’s often a real fancy way to do something that you might think is better, but usually the simple thing is better and is more maintainable.” - @maxmichaels, staff reliability engineer, SF
“Care less about the specific language you use and more about the shared patterns between languages in software engineering, like data structures, making your code reusable and extensible and how to write tests.” -@cindyfightingl, software engineer, SF
“Stop being in your head and actually take action and make something happen.
Just kick the ball, and don’t be afraid to get things wrong.” - @jadeloyzaga, software engineer, SF
Just kick the ball, and don’t be afraid to get things wrong.” - @jadeloyzaga, software engineer, SF
“Slow down. In every engineering org there is a a bias towards urgency, but slowing down usually yields a better result for everyone. You can gain more perspective, and slowing down in the beginning allows you to speed up towards the end.” - @brianmichel, engineering manager, NY
“I would focus more on testing because it allows a lot more experimentation. If I have better tests I can be freer in some of the things I work on. It means the solutions can be a lot more creative and I’ll still get to the right answer because of the tests.” - @jack, CEO, SF
“Make it really clear what you’re trying to accomplish and why, define a clear success criteria, and reiterate on the core goal or customer problem that you’re trying to achieve. If the goal keeps moving you end up never achieving anything.” - @misse_michelle, product manager, SF
“Ask for opinions on your work as much as you can and take the average opinion. Ask people with different backgrounds and get different perspectives on what you’re working on. Don’t follow just one opinion.” - @josecabjim, computer vision research engineer, London
“Instead of waiting until you’ve hit perfection, try something out, see what the response is and then change it from there.” - @kauriemac, quality assurance engineer, Cambridge MA
“It took me a while to get comfortable asking questions. After a while I realised nobody has any idea what they’re doing, but the people that do have a better idea are the ones who did the question asking earlier on.” - @toddmaegerle, software engineer, Seattle
“Read more architectural papers, explore and have fun. Play around with all the new technologies out there and just learn. See what’s out there and then bring those ideas back to your work.” - @tang_htht, senior engineer, anti-spam, SF
“Don’t be afraid of JavaScript. If I had thrown away all my preconceived notions of what a good language is and a bad language is earlier, I would have been more open and willing to learn about different languages, expanding my world.” - @itsdavidamh, software engineer, Seattle
“When I first started engineering I was overwhelmed by how much I didn’t know. When I accepted that I was never going to know everything it became a hell of a lot easier. Take it easy, take your time to learn things and learn them well.” - @mattjbones, software engineer, London
“Once you understand a concept, take a blank piece of paper and teach it to yourself without looking at any materials, as if you are trying to teach it to someone else. Whatever gaps you have, go back to the concept and re-learn them.” - @roycehaynes, software engineer, Boulder
“Don’t focus on different languages and syntax, focus on different ways of thinking and different programming paradigms.” - @yukifartlek, software engineer, London
“Make fewer assumptions and don’t wait until you fully implemented something before testing or getting feedback. Start with MVP, get early feedback, learn, iterate, do better, repeat. This also applies to organisational process.” - @asulkina, engineering manager core services, SF
“You have moments when you think ‘I’m not made for this’, but don’t stop believing in yourself. Keep iterating, keep trying, keep breaking things, do things again, push through, and eventually you’ll be doing them 10 times better.” @mirelaiclodean, software engineer, London
“Ask questions. One of the biggest mistakes I made early at Twitter was being shy and worried that I didn’t meet the bar, and that if I was asking questions people would figure that out. Once I overcame that it helped me move and grow faster.” - @michaelmontano, engineering lead
“Sometimes you have a unique perspective that leads to a different design concept or solution and that’s actually a good thing. So trust your own perspective.” - @jenniferfraser, senior director engineering, SF
