Upgrade to Pro — share decks privately, control downloads, hide ads and more …

When Knowledge is not Enough

When Knowledge is not Enough

Conducted at the orientation program of batch 25 at Faculty of Information Technology, University of Moratuwa, Sri Lanka.

Avatar for Nishan Chathuranga

Nishan Chathuranga

January 21, 2026
Tweet

More Decks by Nishan Chathuranga

Other Decks in Education

Transcript

  1. NISHAN WICKRAMARATHNA Associate Tech Lead @ XEYNERGY B.Sc. in Information

    Technology Faculty of IT (University of Moratuwa) linkedin.com/in/nishancw
  2. TABLE OF CONTENTS What do you need to have Why

    we are here? What’s your purpose Career Paths What you can become Skills you need to develop 1 3 2
  3. Why Are We Here? “Because this was the best option

    in the application form.” “Because the cutoff marks were enough.” “Because my parents said this was a ‘safe’ choice.” “Because someone said IT has good salaries.” “Because I didn’t want to repeat A/Ls.” “Because my friends applied here.” “Because it sounded impressive at family gatherings.” “Because I like computers… and Wi-Fi.” “Because this degree has air-conditioning.” “Because I wasn’t sure what else to do.” Honestly… none of these answers are wrong. Most of us start exactly like this.
  4. Why Are We Here? For Real. To learn how to

    think, not just what to study. To build problem-solving ability. To gain access to people, ideas, and opportunities. To earn time — time to explore, fail, and grow. To prepare for paths we don’t fully understand yet. To build a foundation, not a final identity. To become ready for challenges beyond exams. If being here was only about collecting knowledge… You could do that anywhere today. So this session is about when knowledge isn’t enough.
  5. Imagine I give two people a recipe. Person A •

    Follows the recipe exactly • Doesn’t understand why steps exist • If one ingredient is missing → stuck Person B • Understands ingredients • Adjusts when something is missing • Can cook the same dish for 2 people or 200 people
  6. “A traffic light turns green, yellow, red.” That’s knowledge. What

    happens when: • The light breaks? • There’s an ambulance? • A road is closed? • Someone must design rules • Think about exceptions • Consider future problems Knowing the rules is not the same as managing the system.
  7. • Engineer A • Completes their part • Submits on

    time • Doesn’t care if others are stuck • Engineer B • Understands the full requirement • Helps unblock others • Adjusts when someone fails Who actually saves the business? Finishing your part is different from making the whole thing work. Client’s Project
  8. In technical fields, this same difference exists. At first, everyone

    learns steps. Over time, some people learn systems.
  9. Tomorrow, marketing adds: • Seasonal discounts • Loyalty points •

    Country-based tax rules • New customer types every month What happens to this function in 6 months?
  10. CAREER PATHS! 1 3 2 DevOps Engineers Network Engineers •Infrastructure

    is increasingly automated •But production failures are still human problems •Cloud abstracts much of this •Still critical for security, large-scale systems Software Engineers (SE) •Coding becomes faster •System design, integration, and ownership remain scarce
  11. CAREER PATHS! AI / ML Engineers Data Engineers / Scientists

    4 6 5 •Build, adapt, and govern intelligent systems •LLMs increase demand for people who understand them •AI is useless without clean, reliable data •LLMs don’t fix bad pipelines ML Ops Engineers •Models fail in production, drift, break, and cost money •Automation makes this role more critical, not less
  12. CAREER PATHS! QA (Traditional Manual QA) Business Analysts / UI/UX

    Engineers 7 9 8 Robotics Engineers •High impact, but limited number of positions •Strong in manufacturing, healthcare, defense •Automation + AI testing tools reduce need •QA does not disappear, but transforms •UX grounded in human behavior •BA roles that define problems, not write specs
  13. T-Shaped engineers became popular mostly due to agile principles (focus

    on self- organizing teams with cross-functional members) since a T-shaped engineer is an ideal candidate to be a cross-functional team member
  14. • English ◦ Native language hits a limit • Probability

    & Statistics ◦ Decision-making under uncertainty ◦ ML, data science, experimentation, analytics • Linear Algebra & Calculus ◦ Foundation of AI, ML, data science, graphics, robotics ◦ Vectors, matrices, transformations = how machines “think” ◦ Understanding change and gradients (optimizations) Skills to learn ASAP
  15. • Problem Solving & Algorithms ◦ This is where thinking

    is trained ◦ Breaking problems down ◦ Time & space trade-offs ◦ Algorithm & Data Structure Practice (LeetCode, HackerRank) • Data Structures ◦ Performance, scalability, efficiency • Databases & Data Modeling Skills to learn ASAP
  16. • Cloud Literacy ◦ Hands on experience in deploying and

    scaling software solutions / AI models • AI Literacy (Even If You Don’t Do AI) ◦ Prompt engineering ◦ Knowledge about tools / models ◦ AI will touch every role ◦ Integrate AI to existing applications ◦ Create solutions for Sri Lankan context • Communication & Writing (Underrated) ◦ Your ideas are useless if you can’t explain them Skills to learn ASAP
  17. Baseline Microsoft Foundry chat reference architecture to build and deploy

    enterprise chat applications by using Microsoft Foundry and Azure OpenAI in Foundry Models.
  18. Start doing freelancing work Fiverr / Upwork Whatever you build,

    think about how to monetize it Even a simple assignment can have potential to become next start-up Your goal : build a start-up at some point in life It can be within next 4 years / doesn’t have to be tech 1 3 2 Entrepreneur Mindset
  19. DEMO www.magicpatterns.com chatgpt.com github.com/features/copilot “Give me a polished prompt for

    an agent to build a web app for speakers to share slides, gather feedback and ratings, conduct anonymous live Q&A. These 4 features only”
  20. The value is not the app. The value is saved

    time and reduced frustration. People don’t pay for software. They pay for problems disappearing. If nobody would pay for it, it’s not a product — it’s practice
  21. But.. • Quality – features work as expected? • Security

    – Vulnerable to cyber attacks? • Observability – When something breaks do you know where and what was broken? • Scalability – Can it handle 5000 simultaneous users? What coding agents can't do!
  22. 90% reliability means: • 1 in 10 times, something goes

    wrong • You don’t know which time it will fail For safety-critical systems, even 99.9% may not be enough For elevators: Cost of failure = injury or death “In some systems, ‘mostly works’ is the same as ‘doesn’t work.’”
  23. • Spec-driven development with AI (Read more) • Workflow Automation

    (n8n) • AI first / AI native applications (Read more) • Large Language Models (LLMs) (The future) • Fast Language Models (Read more) • Small Language Models (SLMs) (Read more) • Explainable AI (XAI) (Read more) • Responsible AI (Read more) • Agentic AI (Read more) The Future of the Industry Just type it into the YouTube
  24. AI-native applications are built with AI as the core component

    that influences architecture, development, and deployment processes.
  25. The transition from AI- enabled to AI-native applications represents a

    paradigm shift in software development. AI-enabled applications integrate AI functionality into existing systems, typically through APIs or third-party services, to enhance specific features. In contrast, AI-native applications are fundamentally designed around AI capabilities. (Read more)
  26. What happens at the interviews? No basics / No fundamentals

    No hands-on experience Attitude problems
  27. “Have you ever taken plates from a stack in a

    cafeteria?” •Plates are added only on top •You don’t insert a plate in the middle •You place it on the top •Plates are removed only from the top •You never pull a plate from the bottom •You take the most recently placed one This Data Structure is called a “stack”
  28. Optimize for Skills Grades open doors once. Skills open doors

    forever. • Pass exams • But also learn how things work (debugging, system thinking, reading docs) Ask yourself: “Can I build this without a tutorial?” A 3.0 GPA + strong skills beats a 4.0 GPA with projects.
  29. Consistency Beats Talent You don’t need to be smart. You

    need to show up daily. • 45 minutes of coding every day > 6 hours once a week • Small effort, zero motivation required • Never miss twice Treat learning like brushing your teeth, not like motivation-driven gym visits.
  30. Google Is a Skill (Learn It Early) Good developers aren’t

    memorization machines. Learn to: • Read error messages fully • Search symptoms, not solutions • Scan Stack Overflow & docs fast If you can’t Google well, you’ll think you’re bad at coding (you’re not).
  31. Your Network Is a Hidden Curriculum Sit next to: •

    Curious people • Builders • Intern seekers • Hackathon nerds Avoid: • Chronic complainers • Negative thinkers Opportunities come through people, not notices.
  32. Learn How to Fail Publicly You’ll: • Push broken code

    • Ask “stupid” questions • Mess up presentations Good. Engineers who grow fast are not fearless—just less embarrassed.
  33. Don’t Worship Any One Technology Frameworks change. Fundamentals don’t. Focus

    on: • Data structures • Problem solving • Databases • Networking basics • System design thinking Tools are temporary. Thinking is permanent.
  34. Start now: • GitHub • Blog • LinkedIn posts Write

    about: • What you learned • What confused you • How you solved it Teaching clarifies thinking—and attracts opportunities. Document Your Journey
  35. • Started blogging (Medium / Blogger) • You have a

    portfolio website (github pages) • An ATS friendly CV • Good LinkedIn profile with frequent posts (online presence) • Keep up with evolving technologies • Subscribe to a news letter (javascriptweekly.com, tldr.tech) • Knows 1 Web Framework (React, .NET). • Knows how to integrate AI to web apps / mobile apps • Knows 1 Cloud Service (Azure, AWS) and knows how to deploy and maintain a web app
  36. THANK YOU! Does anyone have any questions? Send them to

    [email protected] linkedin.com/in/nishancw nishanc.com/contact ▲ Download slides from
  37. “Do what you can, with what you have, where you

    are…” - Theodore Roosevelt