In September I read some articles with great tips on clean code, interviews, and more.
There are also articles on the benefits of personal projects and an example when serverless wasn't better.
As for any project, I started with one task and kept repeating it everyday. With time, this became familiar, almost automatic. I then combined new practices and consolidated them into the following points:
- Answer at least one question on Stack Overflow per day
- Don't skip a task on the Todo board
- Be always curious and eager to learn
- Always write down your ideas
But I believe the personal projects I’ve made have helped me become a better, creative, and more resourceful engineer.
Personal projects give the power back to the individual. The goals that you have for your ever-changing masterpiece can take as long as you like and can cost as little as you like.
Includes a list of helpful resources
- Check out company's social media
- Look at Glassdoor reviews, but look for trends not individual opinions
- Think of questions to ask during the interview based on your research
- Meditate before going to an interview
- Don't pretend to be someone you're not
- Show your nerves a bit; you're a person, not an act
- Interviews are a good place to find out if the company will be a good fit for you!
- Be excited and interested!
Choose questions to ask your interviewer that will help you determine if the company, manager, and group will be a good fit for you. Here are some examples:
What do you expect me to accomplish in the first 90 days?
- What does a typical day in this position look like?
- Do you have any reservations about hiring me for this position at this point? If so, what are they?
- What could I learn now that would best prepare me to get started right away if I were hired?2
- What do you like most and you dislike most about what you do?1
- Send a thank-you email within 24 hours of your interview
- Reference something you talked about in your interview to make it more personal
- Learn efficiently
- Don't try to learn all (really)
- Avoid boring stuff
- Refactoring - Unit-test - Debug
- Learn security
- Be open-minded
Tips to become a more product-minded engineer
- Understand how and why your company is successful
- Build a strong relationship with your product manager
- Engage in user research, customer support
- Bring well-backed product suggestions to the table
- Offer product/engineering tradeoffs
- Ask for frequent feedback from your product manager
- Avoid dependency clutter
- Commented-out code rarely has value
- Less is more: Don’t write code “just in case”
- Challenge your ideas
- Take advantage of what you already have
- Avoid "shiny object" syndrome
But even if we were just paying for Lambda, at 10$ a day we would be paying 300$ a month instead of 164$. We have a lot of requests, but each request does very little, it's basically one database call per request. Maybe heavier requests that use more compute time would be better served with Lambda, where you pay per 100ms of compute time