Skills pay your bills, designing APIs, 6 years for GKE, and Cloud Security remediation guides

Hello šš½
Welcome to my weekly tech musings. Do reply to me on what you liked this week and what you want to see more. In addition, you could access old issuesĀ here!
This week, Vivek and I launched a Cloud Skilling challenge for learning Elastic on Azure. It reminded me of my time learning Hadoop in 2013, which helped me foray into Open source, big data, NoSQL, and eventually DevRel. It all started with that one skill.
At that time, Iām neither actively working on Hadoop nor anticipate it, but did a paid course to learn it š Continuous learning helps in many ways. Sometimes to improve your knowledge, or get a new job, or even make new friends!
In recent times, Iāve learned NextJS, TailwindCSS, Javalin, Github Actions, OpenTelemetry, and more. All of them helped in some way to improve my knowledge.
Many over-index on doing tech certifications. Even if you donāt get certified, it is ok, but gaining knowledge continuously by attending meetups, developer events, and participating in one community benefits you in the long run.
Most importantly, learning is democratized today than in 2013, with many folks creating excellent content. You can sit in Imphal, MN, and learn from the instructor in Austin, TX.
Overall, I believe skills do help in paying your bills.
What I read this week?
Illustrations, comics, explain-like-iam-five
blogs have become a big part of learning. For example, see this DNS works illustration.
A comic that explains what happens when you browse on the internet
Iāve designed, coded, and used several APIs so far. Frankly, designing APIs is an art š especially, if you reach a point where there are many users affected by an even small change in API. Iāve read this advisory piece from Slack Engg
on how they design APIs.
Not all might be possible to follow, but some are a must for a great developer experience.
How We Design Our APIs at Slack - Slack Engineering
More than five years ago, we launched the Slack Platform. Today, millions of users bring their work into Slack, and those apps are built by over 885,000 active developers.
You might not believe it. Iāve first heard about Kubernetes in 2015 at a GDG meetup. It is hard to believe it is a big thing today š while I felt confused with all the pods and selectors terminology. That being said, listen to this beautiful podcast celebrating GKE - 6th anniversary š„³
Kaslin Fields and Mark Mirchandani host this weekās episode of the podcast as we celebrate one of our favorite Google products, Google Kubernetes Engine!
Open source projects
It is a no-brainer that the cloud is becoming an integral part of a developerās workflow. Gone are the days, where your deploy team deploys to your data center in Dallas, TX. In turn, the security of those resources is too important as the attacks increase. So I found these friendly remediation guides from Aquasec, which give detailed steps on remediation common security issues in some cloud services. For example, Open Elasticsearch instance on EC2.
cloud-security-remediation-guides
Security Remediation Guides.
Upcoming Developer Conferences
Join Nafiul and me this Friday on PyCharm TV by Jetbrains to learn about āBuilding Search for a Python Flask using Elasticsearchā. Donāt forget to set a reminder.
Building Search Functionality With Python, Flask, and Elasticsearch
Building a web application to solve a business problem is relatively easy, but how do you create a compelling experience that draws your users.
If you like this weekās newsletter, rate it with āthumbs up/down.ā
If youāre finding this newsletter valuable, considerĀ sharing it with friends or subscribing if you havenāt already.
Sincerely,
Aravind Putrevu šš½
In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Created with Revue by Twitter.
Bengaluru 560102