#KCAD

1 messages · Page 1 of 1 (latest)

pearl shuttle
#

CKAD? No, it's a deep dive course on educative. I wondering if $400 is worth it for the certification

pearl shuttle
#

Nice, I think I should be able to add it in my resume within this week then

#

But I don't have professional experience using k8s, so a certification might substitute for it in the meanwhile, atleast to pass resume screens. Once I get a job I don't think it matters too much, anything can be learnt on the job.

#

True, how about Terraform certification then. I might as well go for AWS certification.

#

I just want something to set my resume apart

#

I'm Java wizard 😎

#

True true, AWS makes most sense rn, I am pretty good with it already so it shouldn't take too long to study. Plus I'm weak in networking concepts so studying for cert should cover that as well.

#

Yeah, It's mostly Java + AWS or C# with Azure. Only random startups are using Python or Rust in production rn

#

Yeah, but if I'm optimizing for Java + AWS, python gets sidetracked for those kind of roles. It will mostly be some PySpark or Databricks notebook on Java + AWS infra.

#

But anyway, good discussion. You're right that I should get AWS certification first.

#

It's required for roles where you are building Platforms or Cloud Control Panes, which is pretty common these days

#

Usually a combinatioin of Terraform + K8s + Java + Multi Cloud

#

I mean I know Python, but mostly for Data Science stuff.. can't pivot into Python web development now!

#

I ran into quite a few jobs like that, even interviewed for one.. my previous job was along the same lines as well.

#

Nice

#

Do you have custom deployment or use a managed service?

#

Sounds true to most extent, exception might be cases like multi cloud deployments. For most small-med scale orgs, it's always better to use managed services than implement anything like this themselves.

#

At my last job, whenever someone pitched implementing something very complex my manager used to retort we are a Analytics company, not a cloud, networking, or hardward shop. Let's not solve solved problems!

#

I get your pain.
I think point is, just like most things, it's very use case, team and company dependent, might not be ideal to use it just because we can.

#

But good to know that I should avoid it if it's ever in my hand in the future craughing