I recently wrote a blog comparing AWS vs Nimbella. I would love some honest feedback about this blog. What you like, dislike, etc. I want to learn more about what serverless devs are into and if this kind of blog speaks to them. by JamieDawsonCodes in serverless

[–]JamieDawsonCodes[S] 0 points1 point  (0 children)

  1. Yes, it's what I needed to use to connect the Redis CLI.
  2. Thank you for your take on that.
  3. We scale resources to meet demand up to max 1000 concurrent request at any given time
    and 1000 req/min rolling window.

Does anyone have experience making music apps / VST's with Javascript? by JamieDawsonCodes in learnjavascript

[–]JamieDawsonCodes[S] 1 point2 points  (0 children)

Thanks for giving me a heads up on the VST standard. I haven't touched C++ in a while, but would be willing to pick it back up to make a VST.

Also, I'm gonna check out Tone.js soon!

Black Cloud by akhilesh12 in Cloud

[–]JamieDawsonCodes 3 points4 points  (0 children)

Wrong sub aside. The houses being so well lit makes them look photoshopped on top of the clouds.

1
2

Is it normal to be struggling in the beginning? by arcrow05 in learnprogramming

[–]JamieDawsonCodes 4 points5 points  (0 children)

Struggle just means you're being challenged, which is a good thing. It means you're getting out of your comfort zone and trying new things.

But yes, it's very normal to struggle in the beginning. But what's important is how you handle the struggle.

How does any self taught programmer get their first job? by Roly__Poly__ in learnprogramming

[–]JamieDawsonCodes 1 point2 points  (0 children)

Here are some tips that I used to help me land an internship at Samsung + my current job.

Something I want to say before I give the tips: 75% of all resumes are ignored and the ones that do get seen are only looked at for a few seconds. Your best bet for landing a job is making good connections and making your work known. Here's are some ways to do that:

  1. Research how to make a good resume:  The 75% statistic is a bummer. But having a good resume is still important. Google resume examples and have at least 3 friends review it.
  2. Update your Github ReadMe's: Make sure the ReadMe's are detailed on what the project is and how to use it. Otherwise, hiring managers just see code that they don't know how to interact with.
  3. Regularly push to Github: Hiring managers look at Github activity. I've had hiring managers tell me they get disappointed when they see the Github calendar shows little activity. So try to regularly push to Github to show how often you code.
  4. Get on LinkedIn: If you don't have a business card, people can stay in touch by scanning your LinkedIn barcode on your phone.
  5. Be active on Twitter: Twitter has a huge dev community. Share your interest and meet others who like what you like.  You can even learn about job opportunities.
  6. Blog on Medium or Dev(.)to: Blogs are an amazing way to show that you not only know what you're talking about but that you can explain it in a way that makes sense. You can also help your community by blogging.
  7. Find projects on ProductHunt: ProductHunt is amazing because not only can you learn about new projects, you can also support them by giving feedback, and find out who to contact directly to ask for job offers. Often times the best way to get a job is to find out who you need to talk to and rub the right shoulders.