Edtech Empowering Africa's Tech future | 75,000+ learners, 100+ countries | Upskill, transition into tech & earn online | #DEXA #DigitalSkills #Tech #Africa
Nigeria
Joined February 2021
- Tweets2K
- Following65
- Followers16.3K
- Likes1.8K
Pinned Tweet
Free courses To Take on DEXA this January.
- Cyber Security
- Product Management
- Virtual & Executive Assistance
- Human Resource Management
- Project Management.
If you intend to join any of these courses this January, please join our newly created WhatsApp Channel where all important information will be published.
As soon as you join, please click on the cancelled bell icon 🔕 on the top right side of the page to turn on notification so you don't miss any updates. 🔔
whatsapp.com/channel/0029VaI…
Don't ask whether AI will replace a career.
Ask how AI will change the tasks inside that career.
Take marketing.
AI can assist with:
Research.
Ideation.
Drafting.
Analysis.
Personalisation.
Reporting.
But marketers still need to understand:
Customers.
Positioning.
Brand.
Business goals.
Distribution.
Measurement.
Take software development.
AI can assist with:
Code generation.
Debugging.
Documentation.
Testing.
But developers still need to understand:
Architecture.
Requirements.
Security.
Performance.
Trade-offs.
The future isn't simply:
Human vs AI.
For many careers, it will increasingly be:
Human + AI vs human without AI.
The exact balance will vary by profession.
The most valuable human skill in an AI-heavy workplace may be knowing when the AI is wrong.
AI can produce convincing answers.
That creates a dangerous failure mode.
A confident wrong answer can be more harmful than an obviously incomplete answer.
So learn to verify.
Check sources.
Test calculations.
Challenge assumptions.
Compare outputs.
Understand the domain.
Look for contradictions.
Ask what evidence supports the conclusion.
This is why domain expertise is becoming more important, not less.
If you don't understand the subject, you may not recognise an impressive-looking mistake.
AI makes generating answers cheaper.
It makes judgement more important.
Putting “AI expert” on your CV because you use ChatGPT is like putting “Excel specialist” because you can open a spreadsheet.
AI literacy is becoming useful.
But there are levels to it.
Level 1:
You know how to ask an AI tool questions.
Useful, but basic.
Level 2:
You understand prompting, context, verification and structured workflows.
Better.
Level 3:
You can integrate AI into an existing professional workflow.
Now you're getting interesting.
Level 4:
You can design systems, automations or products that use AI to solve a business problem.
That is a different category of value.
So don't ask:
“Do I know AI?”
Ask:
“What can I accomplish with AI that creates measurable value?”
That is a much stronger career question.
There is a skill that makes almost every other skill more valuable: being able to communicate what you know.
You can be an excellent analyst and still struggle to explain your findings.
You can be a good designer and fail to explain your decisions.
You can write excellent code and struggle to communicate what the code does.
You can build a powerful automation and fail to convince a business to use it.
Technical ability creates value.
Communication helps other people recognise and trust that value.
Learn to write clearly.
Explain your thinking.
Present evidence.
Ask precise questions.
Document your work.
Tell people what changed because of your contribution.
The person who can do the work and explain the work is often much more useful than the person who can only do one of those things.
“Degree or skills?” is the wrong question.
For many careers, the strongest position is:
Degree + skills + proof + experience.
A degree can provide foundational knowledge, credibility and access to certain opportunities.
Practical skills show that you can apply knowledge.
Projects provide evidence.
Experience gives you exposure to real constraints.
None automatically replaces the others.
And AI doesn't suddenly make formal education worthless.
The better question is:
What combination of education, practical ability and evidence gives me the strongest position for the career I want?
Don't throw away a useful asset because the internet has turned “degree vs skills” into a content category.
Build a stronger stack instead.
A certificate can prove that you completed something.
It cannot prove that you can do the job.
This distinction matters.
Imagine two candidates.
Candidate A has seven certificates but cannot show a single project.
Candidate B has two certificates and three strong projects with clear explanations of the problems solved.
Who would you rather interview?
The answer depends on the role, but the second candidate has something extremely valuable:
evidence.
Certificates can help establish that you completed structured learning.
They can help with signalling.
They can sometimes satisfy a screening requirement.
But competence needs stronger evidence.
Build projects.
Document your process.
Show your decisions.
Explain what went wrong.
Show what you improved.
Get someone competent to critique your work.
The goal isn't to eliminate certificates.
The goal is to stop treating certificates as the final destination.
Learn.
Practise.
Prove.
Then certify if certification is useful for your situation.
If you want to learn without paying tuition upfront, explore DEXA's tuition-free learning model. Link in bio.
Motivation is a terrible long-term learning strategy.
You feel motivated.
You study for four hours.
You feel productive.
Three days later, life gets busy.
The solution isn't waiting for motivation to return.
Build a system.
Choose a realistic schedule.
Define what you will study.
Decide what you will produce.
Track your progress.
Create accountability.
Reduce friction.
Make the next action obvious.
A learner who studies 45 minutes consistently can outperform someone who studies eight hours once every three weeks.
The goal is not heroic effort.
The goal is repeatable effort.
Finishing a course is one of the least interesting achievements in a career.
It tells you that you reached the end of the material.
It does not tell you whether you can perform the work.
After finishing a course, force yourself through four stages:
Reproduce
Can you do the exercises without following the instructor?
Apply
Can you use the concept on a different problem?
Explain
Can you teach the concept to another person?
Produce
Can you create something useful with it?
If you can do all four, you are moving beyond passive learning.
This is why DEXA's goal should never be simply:
“How many people completed a course?”
The more meaningful question is:
“What can they do now that they couldn't do before?”
You can spend two years “learning tech” and still have nothing to show for it.
The problem is usually not lack of information.
There is too much information.
100-hour courses.
YouTube playlists.
PDFs.
Bootcamps.
Newsletters.
AI tutorials.
LinkedIn posts.
The learner keeps consuming because consumption feels like progress.
But careers are built through capability.
Try this instead.
For every major concept you learn, ask:
What can I build, solve or explain now that I couldn't before?
Learn Excel?
Analyse a real dataset.
Learn SQL?
Answer real business questions with data.
Learn UI/UX?
Redesign a real product experience and explain your decisions.
Learn automation?
Automate a repetitive process.
Learn copywriting?
Write something designed to produce a measurable business outcome.
Learning becomes powerful when it leaves evidence behind.
Don't collect courses.
Collect proof of capability.
Save this before starting your next course.
If you are starting a tech career from zero, don't make your first goal “get a job.”
Make your first 90 days about becoming demonstrably useful.
Days 1–30
Understand the field.
Learn the vocabulary.
Study the tools.
Watch professionals work.
Complete foundational exercises.
Days 31–60
Start producing.
Build small projects.
Solve realistic problems.
Get feedback.
Document your work.
Days 61–90
Start testing yourself against the market.
Apply.
Freelance.
Ask for reviews.
Enter communities.
Talk to practitioners.
Look for internships and junior opportunities.
Your first 90 days should move you from:
“I am interested in this.”
to:
“Here is what I can actually do.”
Don't measure the first three months by how many courses you completed.
Measure them by how much capability you can demonstrate.
“How do I get experience if every job requires experience?”
Create smaller versions of the work.
Want to become a data analyst?
Analyse public data.
Want to become a UX designer?
Solve a real interface problem.
Want to become a copywriter?
Rewrite an existing landing page and explain your decisions.
Want to become a project manager?
Plan and execute a small project.
Want to become an automation specialist?
Automate a repetitive process.
Want to become a developer?
Build a useful application.
This isn't the same as pretending you have professional experience.
It is creating evidence of capability before someone gives you professional responsibility.
Be honest about what you did.
But don't wait for permission to start practising.
Open your portfolio and remove anything that exists only because you thought it would look impressive.
Then ask of every project:
What problem does this solve?
Who is it for?
What did I personally do?
What decisions did I make?
What tools did I use?
What went wrong?
What would I improve?
What result did it produce?
If the project cannot answer those questions, it may be decoration rather than evidence.
A portfolio should help a recruiter, client or collaborator understand your ability quickly.
Don't make people admire your screenshots.
Make them understand your thinking.
Your portfolio is not supposed to say, “Look what I made.”
It should say, “Here is how I solve problems.”
Two people can have the same skill.
One gets interviews.
The other gets ignored.
Sometimes the difference is evidence.
Imagine two junior analysts.
Candidate A:
“Completed a Data Analytics course.”
Candidate B:
“Analysed a retail dataset, identified three major revenue patterns, built an interactive dashboard and wrote a five-page recommendation.”
Candidate B has given the employer something to inspect.
The employer doesn't have to take the candidate's word for it.
They can see the thinking.
That is what proof of work does.
It reduces uncertainty.
And hiring is full of uncertainty.
A recruiter doesn't know you.
A client doesn't know you.
A portfolio gives them evidence before they take the risk of saying yes.
Don't just tell the market what you can do.
Show it.
Your first portfolio project should not be designed to impress everyone.
It should prove one thing clearly.
Suppose you want to become a data analyst.
Don't build a dashboard with 47 charts because you think more charts look impressive.
Choose one question.
For example:
“What factors appear to influence sales performance?”
Then:
Find data.
Clean it.
Analyse it.
Identify patterns.
Build only the visualisations necessary.
Write your conclusion.
Explain what you would investigate next.
Now someone looking at the project can see your thinking.
That's far stronger than:
“Here is a dashboard I made.”
Your portfolio is not an art gallery.
It is evidence of how you solve problems.
Save this if you're building your first portfolio project.
You don't need 50 completely different CVs.
You do need to stop sending the exact same CV to every role.
Start with a strong master CV.
Then adapt the relevant parts.
If the role emphasises analytics, make your analytical experience easy to find.
If it emphasises project coordination, bring those examples forward.
If it requires stakeholder management, show evidence of it.
If it requires a specific tool you genuinely know, make that visible.
This isn't about lying or stuffing keywords into your CV.
It is about making relevant evidence easier to find.
Think of your CV as an interface.
The recruiter has limited time.
Your job is to reduce the effort required to understand why you are relevant.
Your CV does not need to sound impressive.
It needs to make your relevance obvious.
Compare:
“Responsible for social media management.”
with:
“Managed weekly content across three social platforms and improved average post engagement by 31% over four months.”
The second statement gives the reader something to evaluate.
Good CV writing is not about stuffing every achievement into two pages.
It is about reducing the distance between:
What the employer needs
and
Evidence that you can provide it.
For every major bullet, ask:
What did I actually do?
What changed because I did it?
Can I quantify the result?
If I cannot quantify it, can I describe the scope clearly?
Your CV is not your biography.
It is a relevance document.
Use AI to improve your job search.
Don't let AI turn your application into something that sounds like everyone else's.
AI can help you:
Identify recurring requirements.
Compare your CV with a job description.
Find gaps.
Generate interview questions.
Practise answers.
Improve clarity.
Organise applications.
But there is a trap.
If 500 candidates use the same AI tool to generate:
“passionate, results-driven, innovative professional”
their applications start sounding identical.
Use AI for analysis and assistance.
Keep your actual experience, evidence and voice.
The goal is not to make your application sound like AI.
The goal is to make your application clearer and more relevant.
Before applying for a remote job, spend five minutes trying to disqualify yourself.
It sounds backwards.
It isn't.
Check:
Location: Can they legally hire someone where I live?
Work authorization: Do they require existing authorization?
Time zone: Do they require fixed overlap?
Experience: Do I actually meet the minimum requirements?
Work arrangement: Employee, contractor, freelancer or EOR?
Language: Is a specific language required?
Application status: Is the vacancy actually open?
If you pass those checks, then invest the time in tailoring your application.
Job searching becomes much more efficient when you stop treating every job posting as an opportunity.
Some are simply not your opportunity.
Your time is a resource too.
