yassinerajallah

I guess he meant it in a broad term and it's up to you to get creative. Now that I think about it, you can start by complimenting the resume for the employee you are interested in, and ask how he/she got there. Generally, if they are open to helping they’ll drive the discussion forward. Needless to say, if your first message/email is "please recommend me" it won't work. Personally, I always get back to first principles: Provide value first before asking something back.

Yeah, never dared personally, but guess was just overthinking. Are you fine if I add your point to the article?

Hey! Author here, this article was inspired by my 3 years journey in coding. I didn't know what to start with so ended up jumping from a stack to another. The journey of finding the 'right' stack is not so obvious to begin with, unless someone learns the lesson the hard way and shares it. So I did. Hope you find it helpful

Valid point you got there, I'll take it into consideration in my next articles. I just started blogging 3 days ago and never expected this would blow up. Thanks for the advice again !

If you can bootstrap this, then you are fine, but it's hard to tell from just the "services pov" It's much more complex: How many active daily users are there?, can the free tier for AWS handle that?, until when your AWS credits will expire? etc... Generally, you wanna keep monitoring AWS expenses the first 3 months to be sure you aren't up-sold on some service you aren't using. Also you can make use of the SUS $5k AWS credits if you aren't already. For more info you can check this paragraph "Your servers will make you pay for what you don’t know (Literally)" of my blog article: https://yassine.substack.com/p/the-gap-between-learning-code...

Good luck!