₦airaland Forum

Hey Davisizu,

To be honest, there aren't many active cloud/DevOps threads here. Most older ones are abandoned questions or course/bootcamp ads. So you haven't really missed much.

If you want to explore what's there, you can try Google searches like:

Cloud site:nairaland.com

DevOps site:nairaland.com

Cybersecurity site:nairaland.com

This will bring up most threads related to cloud topics on Nairaland.

For active communities, you may want to look outside Nairaland: LinkedIn, Discord, WhatsApp, Telegram, and similar platforms.

Below are some channels you can explore
:
Discord -> Nextwork, Learn2Cloud.

LinkedIn -> Search for DevOps groups

WhatsApp / Telegram -> I know a few tech circles; if you are interested, you can use the "Send Email" option on my profile for details.

Davisizu:
Yes. Some challenges throughout the learning and quiz

Meaning to ask you some questions i don't know if its ok to ask

Please go ahead

Alright, Davisizu

I hope your learning resource includes hands-on exercises or challenges. That's what really makes concepts stick

Hi Davisizu, Glad you are pushing forward!

For most cloud providers, including GCP, these are the things you usually keep in mind when designing IAM in production:

Least privilege by default: ->applications and CI/CD pipelines run under service accounts with narrowly scoped roles. Full admin access is avoided outside of bootstrap or break-glass scenarios.

IAM is continuously refined –> Access isn't static. Users change roles, teams evolve, services gain new responsibilities, and people leave. Access needs regular review and cleanup.

Audit logs are part of the design –>GCP provides deep visibility via Cloud Audit Logs, but it’s up to the you the customer to monitor and alert on IAM changes.

Short-lived credentials over static keys –> even for service accounts, long-lived keys are discouraged. Workload Identity and ephemeral tokens are preferred.

shyboy187:
Ok.. I have been on a start and stop journey in devops. Probably because I have been going like a sheep without direction. I have completed Linux, shell scripting and Jenkins last year and left it for a long time. I have just started afresh again to study Linux, shell scripting. Then I left it again and started working on projects because its making more sense to me to see what I am learning in action. I have a certification in cloud practitioner and solutions architect in 2024, just yesterday I decided, I switched again and decided to work on cloud engineering projects just to get enough experience to get a cloud engineering job and continue my devops.

Aha, I see exactly what you mean now.
What you described is actually very common, especially for people learning DevOps.

Most start–stop cycles happen because of lack of a clear path, not lack of effort. When there is no structure, people end up learning tools in isolation, chasing hype, and collecting certificates without context.


From what you wrote, here is what I can already tell:

* You already have a solid foundation (Linux, CI/CD, cloud certs).

* Project-based learning works better for you than pure tutorials.

* You are willing to restart when things don’t make sense -> that's a strength.

* Switching between roles (cloud vs DevOps) has been confusing you.


If I were to simplify your path going forward, I would suggest this mindset:


1. Pick ONE role and stick to it for now: Based on what you have done so far, DevOps makes sense. Commit to it long enough to build depth and job readiness before thinking of switching.

2. Pick ONE cloud and go deep: Avoid jumping between AWS, Azure, and GCP. Pick one (AWS is fine). learn it well, build projects, and use it to get a role first.

3. Standardize your tools Don't try everything at once. For example:
Linux: Ubuntu
CI/CD: GitHub Actions or Jenkins
Monitoring/Logs: Grafana/Loki or ELK

*Depth beats variety at this stage.*

4. Lean fully into project-based learning: Since projects work for you, use them as your learning spine.

A simple but powerful project you can try:

* Take a basic Node.js app (no DB)

* Deploy it manually to a cloud VM

* Connect a real domain + SSL

* Push the code to GitHub

* Add CI/CD to redeploy automatically

* Sketch the architecture

* Document everything

One project like this ties together Linux, cloud, CI/CD, networking, and architecture.


5. Start applying for jobs now: Oh yes, You don't need to be perfect. Interviews themselves expose gaps and give direction.



For clarity: I am not available for full-time mentorship, but I can offer guidance here on Nairaland when I can, so others can also benefit. You can also send me a mail if needed.


*You are closer than you think. You just need structure, not a reset!*

shyboy187:
Ok
I am literally looking for a mentor to guide me. So I am confident I am not beating around the bush, just want to know what I need to know to get ahead if you know what I mean

Cool, I understand what you mean.

To give you useful guidance, it would help to know where you are on the journey right now.
Have you started learning already ? If yes , what topics are you currently on ?

shyboy187:
Please how do I contact you

if It's not something private, feel free to share it here so others can also benefit. Otherwise you can use the "Send Email to ..." on my profile to shoot me a mail

Laycon26:
My name is mufutau olamilekan .... I want to learn a skills in tech to improve myself and also be a professional tech individual (software or networking engineer) in the next two years. Please anyone with suggestions or advice thanks.

Hi Laycon26,

The poster above me has already done justice to some parts, so I would like to add a few things:

Whatever path you pick, here are some factors that will influence your outcome over the next two years:

1. Time investment
Two years is just the duration. What really matters is how much active time you put into learning ( Reading, practicing, documenting, making mistakes ). The more time you actively spend on these, the better you will become.

2. Your study route
There are three main approaches, each with advantages and drawbacks:

* Self-study: Cheap, flexible, and self-paced. Great if you already have a job ( which you already do). YouTube, Udemy, and CBT Nuggets are good resources. The key here is discipline . You must stay focused and not get lost in the sea of tutorials.

*Bootcamps: Structured, fast-paced, often with mentorship. Good for accountability and peer learning, but usually costlier.

* Institutions (e.g., New Horizon, ALT School, ALX): Offer certifications and structured curricula.
Advantage is formal recognition and support, but still require you to self-study to master the material

Protip: self-study is always a core skill for any engineer. Also, you can combine them if you can.

3. Practice
* You need to build more than you study.
* Track your progress -> even a simple Excel sheet reviewed weekly is enough.
* Work on real projects: apps, networks, scripts -> anything that makes the concepts concrete.

4. Collaboration and feedback
Work with people who can critique your work, pair with you on projects, or help you learn faster. There are many communities online: Nairaland, Quora, LinkedIn, and WhatsApp groups.

5. Exposure
Attend tech events like DevFest, Moonshot, etc. to meet people, see real-world practices, and stay motivated.

If you focus on these five areas consistently, becoming a professional in two years is entirely achievable.

Babalakin:
I'm starting on the 2nd of January. Wish me luck.

Great! Wishing you all the best as you start on January 2nd

Feel free to share your progress along the way. it helps keep the momentum and lets others learn from your journey too.

Davisizu:
Thank you, I really appreciate the guidance. I’m focusing on the fundamentals and taking things step by step, especially Linux, networking, and The platform I'm using to learn is GCP Google Cloud Platform. I’ll keep sharing my progress here

cool.

GCP is a solid choice. Looking forward to seeing your updates!

Well done OP, Kubernetes can feel overwhelming at first, but here's how I would tackle it if I were starting again:

* First, understand the concepts -> microservices, deployment strategies (blue/green, rolling updates, canary), scaling, metrics… these existed before Kubernetes. Knowing them makes K8s way easier to grasp.

* Take networking seriously -> DNS, routing, services, ingress. This is key for troubleshooting and designing clusters.

* Know Docker well -> features and its limits. K8s sits on Docker, so solid Docker knowledge helps a lot.

* Start with Minikube and deploy a real microservice -> Don’t just do HTML pages or basic 3-tier apps. You need a real reason to use K8s.

* After that, focus on managed Kubernetes in the cloud -> EKS (AWS), AKS (Azure), or CCE (Huawei Cloud). Most teams use these, and it’s more practical than spending too much time on the control plane early.

* Learn Serverless workloads -> your CEO/startup will want ways to cut cloud costs, and Serverless helps.

* Check out enterprise deployment strategies like GitOps with ArgoCD -> see how real teams deploy, manage, and roll back apps.

* Finally, once comfortable with managed K8s, come back and set up your own control plane manually. It will deepen your understanding and make you a stronger DevOps practitioner.

DevOpsnCloud:
It starts like any other day—power is doing hide and seek, the internet is deciding whether it wants to work, and someone, somewhere, is about to break production .....

Well done, OP. Very relatable post.

One subtle thing your post captures (that courses rarely teach) is context switching in DevOps -> jumping between infra, app behavior, databases, CI/CD, and people, all in one day. That mental load is one of the hardest parts of the job.

A few things that help manage it in real life:

* Keep issues in one central place instead of personal inboxes, so you can prioritize properly.

* Production issues first; everything else can wait.

* Any task that will take more than an hour goes into a tracker (Jira, etc).

* Over time, train other engineers to check logs or reproduce issues locally before escalating.

Akwamkpuruamu:
I wish to start afresh

Hi Akwamkpuruamu,

I hope you have started your tech journey.

How has it been so far?

dgee1:
Boss, please which platform are you using to learn?

Hi, dgee1 Which platform did you end up picking?

Here are some in case you still need some options:

* YouTube: Tons of DevOps videos here. Good for learning concepts, but it's mostly passive. To make it stick, you need to combine it with exercises. You can even use AI to generate exercises based on the videos you watch. You should also be able to find some exercises on Guthub

* Udemy: Paid courses are decent. Same issue.. many of the courses don't have enough hands-on practice, so you still need to experiment on your own.

KodeCloud: Works well if you can invest some $. You get structured courses plus practice. But still, it's best to supplement with other resources like YouTube or Udemy, because KodeCloud abstracts a lot. For example, it's important to know how to provision the infrastructure they automate for you.

shyboy187:
Hi all,

I just started studying Devops and i am looking for study buddies and experienced devops professionals. Please any assistance will be appreciated.

Hi shyboy187 ,

I hope you are still grinding on the DevOps path!

Do you still need some assistance? If yes, it would help to know which areas you need support in.

Welcome, Davisizu

Good to see you being intentional about cloud security and building your foundation step by step.

Cloud can feel overwhelming because there are many tools and many ways to approach the same problem.
Here are few things that can help as you continue:

Focus on the basics first (Linux, networking, how systems work): These existed before cloud and will save you a lot of frustration later.

Pick one cloud platform (AWS, Azure, or GCP) and learn it well.: You can’t secure what you don’t understand.

Practice actively: Don't just watch videos or read articles. Try small exercises/challanges/projects and document as you go

Keep sharing your progress and remember consistency matters more than speed !

danielclerkson:
I am mainly doing front-end for now and alot of python

Either of them is a fine option for your use case (frontend, Python).

Fedora is stable. Ubuntu just gets recommended more because it has a larger community and more beginner-focused guides. so it is often easier to find help when you are stuck.

Honestly, I would advise you not to overthink your choice. Whichever you choose, the Linux fundamentals you learn will transfer easily.

abuaasiyah1:
Pls,what is the specification of a system one can use to learn cybersecurity

Hi abuaasiyah1, I guess you probably already have a system by now, but I will still drop my recommendations since your question about system specs is still relevant and might help others.

Here’s a good starting point:

CPU: Any modern processor (Intel i5 /Ryzen 5+)

RAM: 8GB min, 16GB if running multiple VMs

Storage: 256GB SSD

OS: Linux (Ubuntu, Kali) is popular, Windows works too

Basically, if your system can run Linux VMs and security tools without lag, you are good to start.

You can always upgrade as you dive deeper.

Hi Profwriter, just catching your post.

Love seeing you share your journey !

From your post, it is clear you have been hands-on and that's exactly how you level up in DevOps. You have covered a solid mix of Cloud, Automation and infrastructure skills

Hope you have been holding fort!

Yes, Ubuntu is very beginner friendly.
There's plenty of support out there ..community, youtube tutorials, and more which makes learning easier.

It is also widely used on servers. so if you are aiming for roles like backend, DevOps, or cloud, starting with Ubuntu makes a lot of sense.

Starting with Ubuntu Desktop now makes moving to Ubuntu Server seamless ( same commands, package management (apt) and file structures). You just lose the GUI but your Linux knowledge transfers directly.

That said, Fedora is also a decent choice, so both are solid for getting started.

Well done !!

The key is CONSISTENCY, not waiting for the "right time". Every small step counts.

I like that your are already documenting your journey....that's a solid skill to have

My advice : focus on small apps first before diving into too many libraries.

Keep the momentum! Can't wait to see Day 30 and beyond

danielclerkson:
So please senior devs in the forum what version do you recommend between KDE Plasma and Fedora Workstation.

They are both great options.

KDE Plasma is very customizable and closer to Windows, but it can be overwhelming for beginners.

I would recommend Fedora Workstation (GNOME) to start with. It has fewer distractions and gives a better beginner experience. It also makes switching to Ubuntu Desktop later (if you ever want) much easier.

Hint : I personally use Ubuntu

Thank you, Stephen0mozzy and Personperson01, for sharing those real-world insights.

You can't just jump into tech. You have to plan carefully, stay consistent, and play the long game.

I hope beginners can learn from this.

TONYE001:
Hi, greetings.

I've always been interested in tech. Once started a free course online but medschool + other activities made it tough.

This past Saturday, I decided to revisit my tech journey, and I've started a free HTML + CSS tutorial online.

As a medical doctor, my schedules are quite unpredictable - mostly busy,

.....

Hi, Just checking in. Medical schedules can get crazy!

Did you continue your tech journey and just stop updating the thread, or did work get in the way?

Would be nice to hear how it is going.

Everyone thinks tech is quick and easy. The truth? Most newbies struggle, burn out, or give up. Don't let that be you.
Here are 5 hard truths every beginner must know before starting. Please read carefully, or you might regret it later.

1. Don't learn Tech without a source of income

I cannot stress this enough. You need money to buy data, eat, maintain your laptop, and survive. If you don’t, you will end up rushing your learning just to "catch up" and trust me you will forget most of what you try to learn. Tech is a marathon, not a sprint. It might sound discouraging, but this is the reality from my experience. Start smart, start safe.

What you can do ? :
* If you already have a job but want to transition to tech: I recommend that you keep your job if you don't have another source of income and learn alongside it. That job feeds you while you grow your skills. Yes, it won't be easy, but it's the safest path. Set your study time and stick to it.


* If you don't have a job: you need to find one, unless someone can provide for you while you learn. Without this, motivation will fade fast.

Know this: Tech is easy online, but hunger, stress, and bills don't wait. Start safe, or you will burn out before your first project.


2. Learning Tech takes time: I know you’ve seen bootcamp ads: "Become a DevOps/AI engineer in 3 months" or "Master Python in 2 weeks." Sorry to disappoint, Chief, you can't really learn that fast. You can memorize terms and definitions, but being comfortable with a skill takes time. You need to practice, make mistakes, and let new knowledge mix with what you already know. That's how learning sticks.
Know this: Tech isn't a sprint. Quick courses give you knowledge, but time and practice give you skill.

3. Some roles are not entry-level This isn't to discourage you, but it's true. For example, DevOps is not entry-level. You need to know a little of many things to be job-ready. The knowledge spans multiple areas, so it's heavy. Some beginners can still make it, but only if you’re tough, committed, and have time to learn and practice. For most beginners, starting with Frontend, Backend, or QA is safer.
This isn't about devaluing roles. It's about being realistic, so you don’t burn out or get frustrated.

4. ALX, AtlSchool, Bootcamps? Don't fall for the hype Please, don’t just jump on the latest hype. Every program has strengths and weaknesses. Research their programs, fees, duration, and see if it fits your schedule and style. I know people who started ALX and dropped off after a short while. Is ALX bad? No, the people just didn't do their homework. Personally, I wouldn't recommend these programs if you already have a tight schedule because they can be tough to keep up with. But if you have time to commit, it can be a good option.
Also, be careful with the bootcamp hype. Most exist to cash out. Some are good, but do your research before committing.


5. Going the Self-Study route? : Believe me, this is the cheapest and most flexible option, but it has downsides.
It's easy to get lost in the web of information online. You can find tons of free YouTube tutorials, but you need discipline to follow through. Many courses are full of fillers, though there are still some good ones. Since there is no structure, it is easy to get distracted.
If you decide to go this route, here are some tips for you: you may want to walk the path with a study partner and follow a public roadmap or structured guide

Know this: Self-study works best if you are disciplined and consistent. Otherwise, you can spend months learning little and achieving less.


Happy tech journey!

Have you tried learning tech without a safety net, underestimated the time, or picked a role too advanced? Come share your testimonies.

# this line is the cause of the error.

return np.square(test.area())

I assume you are trying to call the area method from area_2 method.

Fix:
use the keyword self instead of the class name :

return np.square(self.area())

cliqtips:
Please, I sent you a mail.

Kindly check your mail

cliqtips:
I studied computer science

I could get you started for FREE

DM me your contact details.

cliqtips:
Trust me, I've watched some of those videos but I couldn't find one helpful.
But if you can help with materials or in any way possible, I would be glad.

Thank you in advance.

What is your background in IT?

cliqtips:
How can one become Dev Ops ?

Please, can anyone mentor or guide someone on how to be Dev Ops .

Do you have any tutorial you can recommend ?

I have searched Youtube (Maybe, I didn't search well) but I couldn't see any tutorial on it.

It just those videos like tech talks I've been coming across.

I look forward to your responses/assistance.

#Blessed

There are more than enough DevOps resources on youtube.
You can start by typing "how to become a DevOps engineer" on the Youtube search

clockwisereport:
Good morning gurus in the house

please, what are inline functions in c++ and when do we use them?
Thank you.

here are good reads on the above topic
What is C++ inline functions
Inline functions

There is no age limit for studying computer science. if you are determined, age can't stop you.
Please computer science is not all about codes.
Now to your questions

Do you think I can cope mathematically?
Yes, if you really want to. you do not need to become a professor in mathematics to study computer science

Is computer science a difficult course?

it is just like any other course you know

What can I do to get a good grade?
You need to do a lot of self study. The internet is full of resources. Try to brush up on your mathematics knowledge