Skip to main content

Laravel has soared in popularity in the last few years. The Laravel community even says that Laravel has made writing PHP enjoyable than a pain. Laravel 6 has some interesting new features. Getting a super scaleable working URL for your application take hours if not days. Setting up something like Kubernetes is a huge task. This is where Google Cloud Run shines, you can get a working HTTPs URL for any of your containerized app in minutes.

Google Cloud Run is serverless and fully managed by Google, you get super scale, billing by the second, HTTPs URL and your own domain mapping. If you want to run stateless containers Cloud run is hands down the easiest way to do it. In this post, I will detail how to get your Laravel 6 app working on Google cloud run with Continous Integration (CI).

Get Laravel 6 running on Google cloud run in minutes with CI

Podcasts are a great way to learn new things even for the lazy reader. If you are not fast at reading or don’t like it very much podcasts can be your way to get the information with less effort. It is easier than reading. This is a part 4 in the series (do check part 1 and 2 and 3) of podcasts you must subscribe to and listen to as a software engineer. Same as the last 3 times the 3 podcasts listed below have great content and considerably good sound quality too. Below is the list:

3 podcasts every software engineer should subscribe to - part 4

Logs from the application level are the only way your application talks back to you. Having proper logs with commendable search capabilities is like having a torch in a dark room.

Fully exploiting logs in case of any issues is very underrated. We as software engineers can utilize logs from the application to resolve issues as well as know the general health of the application.

Logs can be instrumental to profile application performance too.

I had written about logging some years back too. This post is focused on best practices you can follow when logging from the application level and how it can help you as a software engineer.

what recruiters look for

Have you ever applied to many tech jobs that suit your experience and skill but never heard back? Does it feel like you are sending your resume to a black hole? Then this is something you absolutely must read. In this post, 3 tech recruiters in Sydney, Australia answer what they look for in a resume/candidate profile. They also open up about top 3 things they evaluate while conducting the first interview.

After you know what the tech recruiters are looking for you can tailor your resume that lands you an interview.

what recruiters look for

NodeJs was released almost 9 years ago. The default debugging process of NodeJs (read Node.js) is quite clumsy. You are already aware of the need to add --inspect to the node script with node inspector. It is also dependent on chrome. Then look at the proper web socket connection which is hard and debug using chrome node debugger. To be honest, it is a pain in the neck.

Finally, Google chrome labs has released ndb, which they say is “An improved debugging experience for Node.js, enabled by Chrome DevTools”. It is a boon to debug a nodejs app.

I am going to show a step by step process of debugging nodejs application with ndb. In other words, you will learn how to debug a nodejs application using ndb. Below you can see it in action, let’s roll up your sleeves and get started:

debugging nodeJs applications