Matt Watson

Serial Entrepreneur, Startup CTO, Podcaster, Blogger @ VisionaryCTO.com

I’ve spent over 20 years as a founder and CTO, starting in 2003 when I co-founded one of the earliest SaaS companies. We bootstrapped VinSolutions to $35M ARR and sold it for $150M in 2011.

Since then, I’ve built and scaled multiple companies. I’ve led engineering teams through every phase of growth. I’ve also learned firsthand what breaks when leadership, product, and engineering aren’t aligned.

In 2018, I started Full Scale. It began as a way to help myself scale faster with top-tier engineering talent in the Philippines. Today, Full Scale has over 300 developers supporting fast-growing tech companies that need to move efficiently and with clarity.

I recently launched Full Scale Ventures, a venture studio focused on solving real problems for startup founders and engineering leaders. Our first product is EngagePath, a tool designed to help thought leaders identify warm leaders from their followers.

Most recently, I wrote Product Driven, a book for engineering leaders who want to stop playing whack-a-mole with tickets and start building real product momentum. The book is about aligning culture, leadership, and customer focus. Product thinking isn’t just for product managers anymore.

I also host a podcast and write a weekly newsletter focused on the gap between business and engineering and how to close it.

Read the book and subscribe here: https://productdriven.com/connect

Learn more about Full Scale: https://fullscale.io

Founder & CEO

We started Full Scale to do software development the right way from the Philippines. Our 300+ employees are helping dozens of companies build their software quickly and affordably.

* Philippines based, English fluency is superb!
* Staff augmentation model, our team works directly for you!
* Focused on senior level developers
* No middle man project managers in the way

Startups don’t need a CTO. They need a CPTO. That’s a hill I’m willing to die on.

For 20+ years, I’ve had the CTO title. The only reason I’ve been successful is because I never acted like just the head of engineering. I acted like the Chief Product AND Technology Officer.

Building software isn’t about code. It’s about outcomes.

It’s knowing what matters to the customer.
It’s tying what you build to real value.
It’s iterating based on impact, not ego.

In the age of AI, this is even more obvious.

AI can write the code. That’s not the bottleneck anymore.

Product thinking is.

What should we build?
Why does it matter?
How does it change the user’s life?

The worst setup in a startup is a Head of Product and a Head of Engineering negotiating priorities while momentum dies.

Engineering and product can’t be separate empires.

They have to be fused.

If you think you need to hire a CTO in 2026, they better be a CPTO.

5x Founder & CTO | Author of Product Driven | Bootstrapped to 9-Figure SaaS Exit | CEO of Full Scale | Teaching Product Thinking to Engineers

AI generated code is amazing until the shit hits the fan.
Production is down. Your best engineer is troubleshooting it.

There is one massive problem.

They have never debugged any of this code before. They didn't write the code, AI did.

They lack familiarity and muscle memory about how the code works.

It isn't much different than asking your engineer who started yesterday to go figure it out.

This is the ultimate problem with AI generated systems.

They work great until they don't. Then nobody knows how it actually works. There is no deep expertise.

How do we fix this?

Pray that AI can fix it when production is down?

undefined undefined

Author

Chief Executive Officer

Podcast Host

Founder, CEO, CTO

Scaling Tech Teams through Product Thinking & High-Performing Offshore Talent | CEO @ Full Scale | Author Product Driven | Podcast Host

Here are the 4 golden rules of software development: 
 
#1 If it can be null, it will be null 
 
#2 The answer to every question is "It depends" 
 
#3 Getting users to actually use software is 10x harder than building it 
 
#4 Great requirements are more important than great developers

Every new software project should start with the database, not the UI. 
 
The database is the foundation of most software applications. 
 
Bad database architecture can make it difficult to add new features later. 
 
The UI is simply the lipstick on the pig if the database is done incorrectly! 
 
Spending time understanding the UI and UX is really important. It helps shape the database architecture. 
 
But when it comes time to write code and build something, it always starts with the database.

Most “senior” engineers aren’t senior.
They’re just juniors who stayed at the same company for 5+ years.

They know every quirk of the legacy code.
They can tell you which bug comes back every quarter.
But ask them to design a brand new clean, simple service? Well...

Because memorizing a codebase isn’t the same as mastering fundamentals.
Surviving time-in-seat isn’t the same as developing judgment.

At Full Scale, we don’t leave seniority up to tenure.
We provide ongoing training so our engineers develop the skills that actually make them seniors:

⚡ Architecture thinking. How to design systems that scale and stay simple.

⚡ Problem-solving. Approaching new challenges instead of defaulting to old hacks.

⚡ Communication. Explaining tradeoffs clearly to teammates and stakeholders.

⚡ Product context. Understanding why the code matters, not just how it works.


Real senior engineers aren’t defined by years in the seat.
They’re defined by how they grow and how they make the team better.

With 300+ engineers, career growth isn’t optional.
It is critical to our success and to the success of the 85 clients we serve at Full Scale.

Claude Code now commits 4% of all GitHub public commits. 

That is insane!

Every week I keep telling all of our team members and clients how important it is for them to learn to use these tools.

If you don't adapt to them, you are going to be left behind.

If you use it for a day and don't see the immense value in it, you are already left behind.

But is still like herding cats to get 300 people to use them and nearly 100 of our clients on board as well.

There will always be early adopters and late adopters.

The AI hype isn't hype for us. Claude Code and agentic engineering has permanently changed how we work.

4% of all commits is wild.

The real number of commits that used AI in some way is substantially higher.

Software engineering is fun... again.

When I started my career, I could prototype stuff in VB6 really rapidly. 

Talk to customers, hack some code together, deliver the solution, and have a beer to celebrate.

For the last 15 years, something else happened.

Mobile, cloud, SPAs, and a million new frameworks made our lives really complicated.

We spent more time learning tools and building tooling than actually solving real customer problems.

AI has changed that... for the good.

So much of the code writing can happen more quickly now.
Less tedious code.
Less need to be an expert in so many frameworks and tools.

How do you do X in JavaScript?
Who cares. Claude knows.

I'm writing React code and I've never done React in my life. (p.s. JavaScript sucks)

Now we can focus on the fun part!!!

Talking to customers and users, understanding their problems, and seeing the smile on their face when you make a difference in their lives.

Software engineering is back and it has never been more fun!!! 🎉

This weekend we had "Wellness Day" for all of our employees.
A day dedicated to them and their families to relax.

Swimming, yoga, food, music, and lots of other activities for kids of all ages.

No laptops or Slack notifications. Just family fun!

At Full Scale, we believe that team work is more than sprints. We also need to slow down once in a while, and when we do, something special happens.

I learned a long time ago that without your team, you don't have a business. We have to make time to recharge, reconnect, and remember why we do this in the first place.

Thanks to all the Full Scale team members who made it out this year. Next up is the summer party in May!

Full Scale

Software engineering has a K-shaped skill gap right now.

The engineers embracing agentic AI are on the top curve. 

The ones who aren't are on the bottom, and the distance between them is growing fast.

We talk to leaders at tech companies every day. The things I'm hearing:
"I haven't written code since November."
"I'm getting 5x more work done."

Six months ago, a lot of us thought this was hype. 

Nobody thinks that anymore.

You're either figuring it out, or you're in denial. 

There's not much middle ground left.

Do you pay software engineers more because they have a master’s degree?

What about certifications?

I don’t.

Credentials don’t move compensation for me.

They tell me you studied, memorized material, and passed a test. That’s fine. It just isn’t the thing customers pay us for.

What matters is what you can do with what you know.

Can you apply that knowledge to solve messy, ambiguous problems?
Can you make good decisions when the requirements are incomplete?
Can you take ownership of outcomes, not just tasks?
Can you raise the bar for the people around you?

That’s what increases your value. That’s what increases your pay.

Which leads to the real question we should be debating:

What do you think a software engineer actually needs to do to make more money?

They were right about software engineering being dead.
Just not in the way people think.

Software isn’t code.

It’s architecture, tradeoffs, and understanding the customer well enough to know what not to build, and connecting technical decisions to real business outcomes.

That isn't dead and it isn't going anywhere.

That has always been the job. Most people just forgot.

If you think software engineering is just about code, your career is dying.

Don’t tell me you’re using AI for software engineering if all you’re doing is opening ChatGPT.

That was impressive in 2024.

It felt like a superpowered Google search. You could research faster. Draft cleaner code. Spin up a small function without digging through Stack Overflow.

But that’s the old baseline.

If you’re an engineer in 2026 and you say you’re “using AI,” the question isn’t whether you’re chatting with a model. It’s whether you’re running an agent with real context.

We’re not asking AI how to do something anymore.

We’re telling it what to build.

There’s a difference.

A quick prompt has no idea how your system is architected. It doesn’t know your naming conventions, your constraints, your edge cases, your tech debt, or the trade-offs you’ve already made. It’s guessing from the outside.

An agent operating inside your environment is different. It understands your repo. It sees your patterns. It knows the rules you’ve defined. Tools like Claude Code or agent-based Codex setups can take detailed instructions, apply them across a codebase, and execute within the context of your actual system.

That’s not a better Google search.

It’s a hundred times more powerful.

If your team says they’re “using AI” and all they’re doing is pasting snippets into ChatGPT, that’s like saying you’ve modernized because you use Stack Overflow.

Helpful? Sure.

Transformational? Not even close.

The shift is from Q&A to delegation.

From isolated prompts to persistent context.

From “how do I write this function?” to “here’s the objective, here’s the codebase, here are the constraints, go execute.”

That requires more from you, not less.

You have to define standards. Provide context. Be explicit about architecture and intent. AI is only as good as the environment you plug it into.

The teams that win over the next few years won’t be the ones casually dabbling with prompts.

They’ll be the ones who build systems around agents. Be that Claude Code, Cursor, ChatGPT Code, etc.

Are we sure this isn't a software engineer running Claude Code?

BBC news showed this 15 screen setup.

“Monitoring the situation”
“Matrix”
“Where is my mouse?”

No matter what your thoughts on this. I genuinely impressed and feel ashamed of my four monitor setup now.


I’m off to buy more monitors 🤣

Shouldn't a "public benefit corporation" be against mass domestic surveillance and autonomous weapons?

I'm proud of Dario Amodei for holding his ground.

I wouldn't want my technology used for those things either.

CEO and Co-Founder at Anthropic

AI is making software engineering easier AND much harder.

Yes, writing code is easier than ever.

But the day-to-day life of software engineers, and the leaders responsible for them, has gotten more complex.

Here’s why.

Everyone is suddenly expected to be an AI expert.
Output expectations are rising. Timelines are shrinking. The baseline quietly moved.

Some of us love this. We’re early adopters. We’re experimenting constantly. It feels like being a kid in a candy store.

For everyone else?

Their job changed overnight.

They’re being told to stop writing as much code.
To stop doing the part of the job they’re best at... and often why they became engineers in the first place.

Instead, they’re expected to “work with agents.”
Systems that move fast, sound confident, and require constant supervision to keep from going off the rails.

At the same time, engineers are being asked to do more of everything else.

More product thinking.
More context switching.
More code review.
More responsibility for code spewed out by AI that they aren't experts at.

They’re not just learning AI.
They’re absorbing the parts of the job that used to sit around them.

Product. Planning. Testing. Deployments. Risk.

The scope of what it means to be a “software engineer” just expanded... without a pause to catch up.

AI didn’t just change how code gets written.
It changed the what's expected of engineers.

So what do we do?

Give your team empathy. The career they signed up for changed... fast.

Give them training. Give them space. Keep challenging them.

I've never met a good engineer who didn't love a good challenge.

Just make sure they're set up to meet it.

You don't need rockstar developers. You need rockstar requirements.

That was true in 2025. It's even more true now.

AI can write the code. It can't write the requirements.

Most of us are building really simple software. Display some data,
save it to a database, call an API. AI handles that now. A junior dev
with good prompts ships features in hours.

AI can't figure out what the customer actually meant.
It can't tell you which features matter and which are distractions.
It can't make the call when scope gets messy and someone has to say no.

The requirements, the clarity, the "why this and not that": that's
still a human job. Now it's the only job that matters.

AI made average developers rockstars.
It made bad requirements catastrophic.

"I used to think the code was the thing."

The most code-obsessed architect I know told me that yesterday.

Now he's watching four Claude Code agents churn out features while he figures out what to actually build next.

Code was never the thing.
What the code does is the thing.

Tech founders figured this out the hard way.
You can't sell code. You sell what the code makes possible.

Our client just fired two local software engineers.

Not because they were bad engineers.

Because they refused to use AI.

This isn’t the first time a profession has faced a shift like this.

Travel agents who ignored online booking tools disappeared.
Stockbrokers who ignored electronic trading platforms disappeared.
Accountants who ignored spreadsheet software disappeared.
Journalists who ignored the shift to digital media disappeared.

Technology doesn’t wait for people to get comfortable.

AI won’t replace engineers.

But engineers who use AI will replace engineers who don’t.

I need to hire offshore software engineers for my startup. 
 
Where should I hire them? 
 
How do I trust them? 
 
How do I make this work?

Building software is about 20% a technical problem and 80% a people problem.

Building software is hard.
Getting people to agree on what to build is harder.

Most of the real work is not writing code.

It is talking to people. 

Helping them understand what their problems actually are. Turning vague ideas and half-formed complaints into something concrete.

Getting your company or your boss to agree to your “crazy idea” can feel impossible. Not because it is wrong, but because alignment is harder than execution.

Writing the code has always been the easiest part.

Now with AI, that is even more obvious.

I personally need to build a new internal utility right now. Claude could probably write most of it in a day. That part is not hard.

The hard part is stopping long enough to think clearly about what needs to be built. Articulating the requirements. Deciding if it is even worth building in the first place.

I have ideas bouncing around in my head, but no clean answers. And even if I build it, I am not sure I will actually use it. It might be a waste of time. It might solve the wrong problem. Buying a third-party tool might be the better move.

That uncertainty is the real 80%.

Heck, it might be 95% at most big companies.

And that is what people miss.

The 80% is the meetings.
The conversations.
The back-and-forth to make sure we are building the right thing and that we actually get value out of it.

As engineers, we like to treat that part as overhead. Something in the way of the real work.

It is not.

That is the work.

Because if you skip the 80%, the 20% will not matter, no matter how good the code is.

🤖Data Scientist | Turning Raw Data into Money Generating Insights | Data-led Growth for Your Business 🚀

Freelance Data Scientist | ML Engineer | SQL | Python | Power BI | MLOps

Data analytics and Machine learning models built 5X faster - no quality compromise. Worked with 14 clients in 7 different industries in the last 3 years. Helped current company scale to $5M+ ARR. Featured TOP RATED PLUS talent on Upwork in 2025 with 100% job completion and satisfaction.

My Toolkit:
- Data analytics: Python, SQL, Excel
- ML Engineering: FastAPI, AWS, Streamlit, great_expectations
- Data visualization: PowerPoint, PowerBI, Plotly, Matplotlib
- Data modeling: Scikit-learn, TensorFlow, Keras
- MLOPs: CI/CD (GitHub Actions), Docker
- Additional tools: Notion, n8n, Canva, Git/GitHub

My Stats:
- 5-stars reviews on 99% of projects delivered.
- 100% Job Success Score for on-time, budget delivery.
- Helped scale currently business to $5M ARR with ATS analysis & Reporting.
- 1.5 years TOP RATER PLUS on Upwork.
- 1800 hours billed.
- $60k+ earned.

What You’ll Get Working With Me:
- A data analyst who is a real problem solver.
- Quick responses (within the hour on working hours)
- Clean, maintainable code and detailed documentation
- A clear “NO” if something isn’t feasible; no wasted time
- A well-crafted report or dashboard as per the requirements

My clients think:
- "Anas is great and highly knowledgeable. He is passionate about solving data science challenges and has helped me significantly streamline some of my processes, enabling better scalability.
- "Anas, was prompt and thorough and I would def use him again in the future."
- "Anas is great to work with. He made the job so fluid and his knowledge of data science makes him someone worth listening to. I’m glad I chose him for my small business. I’m looking forward to what’s coming next, and I would definitely hire him again."

Popular Clients & Products:
- Uhubs: Financial company based in London
- AllAboutGroup: Law recruitment firm based in London
- Growth Dynamics: Marketing and data strategist based in London.
- Adway: Tech and recruitment company based in Gotheborg, Sweden

About me:
- Football fan since I can remember (Real Madrid fan)
- Tennis lover and practitioner (one-handed backhand style)
- Mangas fan (One Piece, Naruto, Bleach)
- Travel addict (South Asia, Europe, Africa, America (soon))
- Reading is something I enjoy as much as coffee (oat latte fan recently)

-----

YouTube Channel
→ GO HERE: https://www.youtube.com/anas_riad

Request services via LinkedIn or Email below:
r.riadanas@gmail.com

Hire on Upwork:
https://www.upwork.com/freelancers/~0163377bf3029c7553

Anas Riad

Dear recruiters,

If you expect a Data Scientist to be an expert in:

→ Python for large-scale data analysis
→ Excel with complex financial-style reports
→ Pandas and NumPy on real, broken datasets
→ Heavy data cleaning and feature engineering
→ Git workflows, CI/CD, and automated testing
→ LLMs, prompt design, and applied AI use cases
→ Business KPIs, north-star metrics, and trade-offs
→ Clear storytelling with non-technical stakeholders
→ Dockerized environments and reproducible pipelines
→ Experiment tracking, model versioning, and rollbacks
→ Data pipelines touching cloud storage and warehouses
→ Regression, classification, and model selection at scale
→ Advanced SQL with messy joins and window functions
→ Exploratory analysis with Matplotlib, Plotly, and Seaborn
→ Probability theory, hypothesis testing, and A/B experiments
→ Bias–variance trade-offs and model performance monitoring

… you’re not hiring one 𝗗𝗮𝘁𝗮 𝗦𝗰𝗶𝗲𝗻𝘁𝗶𝘀𝘁.
You’re describing an 𝗲𝗻𝘁𝗶𝗿𝗲 𝗱𝗮𝘁𝗮 𝗱𝗲𝗽𝗮𝗿𝘁𝗺𝗲𝗻𝘁.

PS: Post inspired by José Siles

📌 Follow Anas Riad for more content around data science

Data Scientist & BI Consultant @Adway • ML Engineer • YouTube @ Anas Riad

YouTube is still the BEST place to learn ML.

Most people still watch the wrong videos.

Here are 𝟭𝟮 𝗬𝗼𝘂𝗧𝘂𝗯𝗲 𝘃𝗶𝗱𝗲𝗼𝘀 𝘁𝗼 𝗺𝗮𝘀𝘁𝗲𝗿 ML ⤵️ 

---

𝗦𝘁𝗮𝗻𝗳𝗼𝗿𝗱 𝗖𝗦𝟮𝟮𝟵: 𝗠𝗮𝗰𝗵𝗶𝗻𝗲 𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴
 
The legendary starting point for ML.
Covers core theory, intuition, and key algorithms.

Video: https://lnkd.in/e-aJRQun
 
---

𝗔𝗹𝗹 𝗠𝗮𝗰𝗵𝗶𝗻𝗲 𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝗖𝗼𝗻𝗰𝗲𝗽𝘁𝘀 𝗘𝘅𝗽𝗹𝗮𝗶𝗻𝗲𝗱 𝗶𝗻 𝟮𝟮 𝗠𝗶𝗻𝘂𝘁𝗲𝘀

A fast, structured overview of all major ML concepts.
Great for building a mental map before going deeper.
 
Video: https://lnkd.in/exCP58F6
 
---

𝗠𝗟𝗢𝗽𝘀 𝗖𝗼𝘂𝗿𝘀𝗲 𝗳𝗼𝗿 𝗕𝗲𝗴𝗶𝗻𝗻𝗲𝗿𝘀
 
Shows how ML actually works in real products.
Pipelines, deployment, monitoring, and production mindset.
 
Video: https://lnkd.in/erzM3b4F

---

𝗛𝗼𝘄 𝘁𝗼 𝗗𝗲𝗽𝗹𝗼𝘆 𝗠𝗟 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻𝘀 (𝗙𝗮𝘀𝘁𝗔𝗣𝗜, 𝗗𝗼𝗰𝗸𝗲𝗿, 𝗔𝗪𝗦)
 
From trained model to live service.
A practical deployment walkthrough with modern tools.
 
Video: https://lnkd.in/e3JtcAZk

---

𝗦𝘁𝗲𝗮𝗹 𝗠𝘆 𝗠𝗮𝗰𝗵𝗶𝗻𝗲 𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝗣𝗿𝗼𝗷𝗲𝗰𝘁 𝗧𝗲𝗺𝗽𝗹𝗮𝘁𝗲

Learn how to structure ML projects properly.
Clean folders, reproducibility, and real-world practices.
 
Video: https://lnkd.in/eds2Buq8

---

𝗘𝗻𝗱-𝘁𝗼-𝗘𝗻𝗱 𝗠𝗟 𝗣𝗿𝗼𝗷𝗲𝗰𝘁𝘀 𝗜𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻
 
A full ML project from start to finish.
Data prep, modeling, evaluation, and delivery.
 
Video: https://lnkd.in/ebx_dvtn

---

𝗠𝗟𝗢𝗽𝘀 𝗣𝗶𝗽𝗲𝗹𝗶𝗻𝗲 𝗧𝘂𝘁𝗼𝗿𝗶𝗮𝗹 (𝗬𝗼𝘂𝗧𝘂𝗯𝗲 𝗩𝗶𝗲𝘄𝗲𝗿 𝗦𝗲𝗻𝘁𝗶𝗺𝗲𝗻𝘁)
 
Build a real ML pipeline using real data.
Feature engineering, modeling, and orchestration.
 
Video: https://lnkd.in/e9_xVb-Z

---

𝗬𝗼𝘂 𝗪𝗶𝗹𝗹 𝗡𝗢𝗧 𝗟𝗲𝗮𝗿𝗻 𝗠𝗟 𝗶𝗻 𝟯 𝗠𝗼𝗻𝘁𝗵𝘀
 
A reality check on learning machine learning.
Focuses on process, depth, and consistency.
 
Video: https://lnkd.in/eRqYhJWK

---

𝗘𝗻𝗱-𝘁𝗼-𝗘𝗻𝗱 𝗥𝗲𝗴𝗿𝗲𝘀𝘀𝗶𝗼𝗻 𝗠𝗟 𝗣𝗿𝗼𝗷𝗲𝗰𝘁
 
A practical regression project walkthrough.
Covers evaluation, assumptions, trade-offs.
 
Video: https://lnkd.in/e2GEnb4N

---

𝗘𝘃𝗲𝗿𝘆 𝗠𝗮𝗰𝗵𝗶𝗻𝗲 𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝗠𝗼𝗱𝗲𝗹 𝗘𝘅𝗽𝗹𝗮𝗶𝗻𝗲𝗱
 
A clear overview of common ML models.
 
Video: https://lnkd.in/eMW3YNKq

---

𝗣𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻-𝗚𝗿𝗮𝗱𝗲 𝗠𝗟 𝗣𝗿𝗼𝗷𝗲𝗰𝘁 𝗧𝘂𝘁𝗼𝗿𝗶𝗮𝗹
 
Focus on building ML systems that last.
Code quality, deployment, and maintainability.
 
Video: https://lnkd.in/eXYhdxgt

---

𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻 𝘁𝗼 𝗠𝗮𝗰𝗵𝗶𝗻𝗲 𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴 (𝗙𝗼𝘂𝗻𝗱𝗮𝘁𝗶𝗼𝗻𝘀)
 
A simple introduction to ML definitions and concepts.
 
Video: https://lnkd.in/eT3qrGBt
 
---

📌 Save this for your next project.
♻️ Repost this to help your network in data.

90% of analysts use only 10% of Pandas.

Master these 10 operations. Level up instantly.

When I started learning data analysis,
I thought Pandas was “too big” to master.

Turns out… you only need the core.

Here are the operations I use almost daily:

• 𝗟𝗼𝗮𝗱 𝗱𝗮𝘁𝗮 → pd.read_csv()
• 𝗜𝗻𝘀𝗽𝗲𝗰𝘁 𝗾𝘂𝗶𝗰𝗸𝗹𝘆 → .head(), .info(), .describe()
• 𝗦𝗲𝗹𝗲𝗰𝘁 𝗰𝗼𝗹𝘂𝗺𝗻𝘀 → df[["col1","col2"]]
• 𝗙𝗶𝗹𝘁𝗲𝗿 𝗿𝗼𝘄𝘀 → df[df["col"] > value]
• 𝗚𝗿𝗼𝘂𝗽 & 𝗮𝗴𝗴𝗿𝗲𝗴𝗮𝘁𝗲 → .groupby().agg()
• 𝗖𝗿𝗲𝗮𝘁𝗲 𝗳𝗲𝗮𝘁𝘂𝗿𝗲𝘀 → df["new"] = expression
• 𝗠𝗲𝗿𝗴𝗲 𝗱𝗮𝘁𝗮𝘀𝗲𝘁𝘀 → pd.merge()
• 𝗛𝗮𝗻𝗱𝗹𝗲 𝗺𝗶𝘀𝘀𝗶𝗻𝗴 𝘃𝗮𝗹𝘂𝗲𝘀 → .isna(), .fillna()
• 𝗦𝗼𝗿𝘁 𝗿𝗲𝘀𝘂𝗹𝘁𝘀 → .sort_values()
• 𝗘𝘅𝗽𝗼𝗿𝘁 𝗰𝗹𝗲𝗮𝗻 𝗱𝗮𝘁𝗮 → .to_csv() or .to_excel()

That’s it.

If you can combine these properly, you can solve 80% of real-world problems.

The rest is practice and business thinking.

PS: Is Pandas your go-to library for data analytics?

📌 Follow Anas Riad for more content around data science

I was never supposed to become a Data Scientist.

Nothing about my path pointed there.

I tried medicine.
Then architecture.
Spent 5 years on a Master’s in industrial engineering.
Worked as a professional DJ at the same time.

Then I found data science.
Late. Unexpectedly.
And honestly… it made no sense.

I changed countries.
I doubted myself constantly.
I had to spend one full year just learning how to speak better.
Five years ago, I couldn’t even express myself properly in this language.

Now I work in data science.
And create content in that same language.

It wasn’t linear.
It wasn’t clean.
And the odds were clearly against me.

What made the difference wasn’t just Python or maths.

Being a good data scientist is not only technical.

It’s also:

→ Being reliable when things break
→ Understanding the business, not just the model
→ Thinking clearly when data is messy
→ Explaining results so people actually act
→ Saying “this approach failed” and learning fast

Yes, you still need:

→ Coding
→ Statistics
→ Probability
→ Solid fundamentals

But that’s only part of the picture.

What really helped me:

→ Perseverance
→ Belief (especially when confidence was low)
→ Hard work
→ Learning from the right people

Data scientists don’t all look the same.
And they don’t come from the same background.

If your path feels messy, slow, or “wrong”,
you might actually be building something stronger.

PS: Did you find your path on the 1st try?

80% of analyst tasks will automate.

Will you still be relevant in 2026?

⭐ Venkata Naga Sai Kumar Bysani and I broke this down simply  ⤵️ 

1️⃣ Work with AI, not against it
Copilot, Claude, automation tools. Use them well. Guide them. Validate outputs.

2️⃣ SQL alone won’t cut it anymore
Add Python. Learn ML basics. Understand how data pipelines work.

3️⃣ Understand the business deeply
Dashboards are easy. Translating numbers into revenue, risk, and strategy is rare.

4️⃣ Solve problems, not tickets
No one cares about the tool. They care about impact.

5️⃣ Build systems that run without you
Automate reports. Schedule pipelines. Create alerts. Sleep while your work runs.

6️⃣ Explain insights clearly
If leadership can’t understand it, it won’t matter.

7️⃣ Share your work publicly
Document what you’re learning. Visibility creates leverage.

-- -- -- 

The analyst role isn’t disappearing.
It’s evolving.

And the ones who adapt will win big in 2026.

💬 What’s your take?
Is the Data Analyst role shrinking or just becoming more strategic?

📌 Follow Venkata Naga Sai Kumar Bysani & Anas Riad for top-tier data content
♻️ Repost this post with your network to benefit

taplio

The Battle

Matt Watson

Anas Riad

Followers

Posts

Engagements

Likes

Performance ScoreMatt Watson's LinkedIn Performance

Performance ScoreAnas Riad's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Matt Watson

Anas Riad

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Matt Watson's LinkedIn Performance

Performance ScoreAnas Riad's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreMatt Watson's LinkedIn Performance