Please avoid sharing any personal content in this channel comment section !
This space is dedicated to sharing, learning, and growing as a community not for advertisements or self-promotion.
If you have something valuable for members (projects, tips, events, resources, or anything relevant to the tech community), kindly contact the admins.
Weโll be happy to review and share it.
Posts that donโt follow these guidelines may result in an automatic ban.
@CTBEsoftwareengineers
โค5๐2๐1
Here are some free AI resources from Top AI companies you can learn Fundamentals there
๐ญ - ๐๐ป๐๐ต๐ฟ๐ผ๐ฝ๐ถ๐ฐ:
anthropic.skilljar.com
๐ฎ - ๐๐ผ๐ผ๐ด๐น๐ฒ:
grow.google/ai
๐ฏ - ๐ ๐ฒ๐๐ฎ:
ai.meta.com/resources/
๐ฐ - ๐ก๐ฉ๐๐๐๐:
developer.nvidia.com/cuda
๐ฑ - ๐ ๐ถ๐ฐ๐ฟ๐ผ๐๐ผ๐ณ๐:
learn.microsoft.com/en-us/training/
๐ฒ - ๐ข๐ฝ๐ฒ๐ป๐๐:
academy.openai.com
๐ณ - ๐๐๐ :
skillsbuild.org
๐ด - ๐๐ช๐ฆ:
skillbuilder.aws
๐ต - ๐๐ฒ๐ฒ๐ฝ๐๐ฒ๐ฎ๐ฟ๐ป๐ถ๐ป๐ด๐๐:
deeplearning.ai
๐ญ๐ฌ - ๐๐๐ด๐ด๐ถ๐ป๐ด ๐๐ฎ๐ฐ๐ฒ:
huggingface.co/learn
hope it helps โบ๏ธ
@CTBEsoftwareengineers
๐ญ - ๐๐ป๐๐ต๐ฟ๐ผ๐ฝ๐ถ๐ฐ:
anthropic.skilljar.com
๐ฎ - ๐๐ผ๐ผ๐ด๐น๐ฒ:
grow.google/ai
๐ฏ - ๐ ๐ฒ๐๐ฎ:
ai.meta.com/resources/
๐ฐ - ๐ก๐ฉ๐๐๐๐:
developer.nvidia.com/cuda
๐ฑ - ๐ ๐ถ๐ฐ๐ฟ๐ผ๐๐ผ๐ณ๐:
learn.microsoft.com/en-us/training/
๐ฒ - ๐ข๐ฝ๐ฒ๐ป๐๐:
academy.openai.com
๐ณ - ๐๐๐ :
skillsbuild.org
๐ด - ๐๐ช๐ฆ:
skillbuilder.aws
๐ต - ๐๐ฒ๐ฒ๐ฝ๐๐ฒ๐ฎ๐ฟ๐ป๐ถ๐ป๐ด๐๐:
deeplearning.ai
๐ญ๐ฌ - ๐๐๐ด๐ด๐ถ๐ป๐ด ๐๐ฎ๐ฐ๐ฒ:
huggingface.co/learn
hope it helps โบ๏ธ
@CTBEsoftwareengineers
โค6๐2๐ฅ1
The AI Copy-Paste Trap: Are We Forgetting How to Code? ๐ง
Letโs be real, everyone is using AI to write code right now. Itโs fast, but blindly copy-pasting is the quickest way to lose our core skills. If we just paste and ship, we aren't software engineers ,we're just prompt typists.
To keep actually growing your skills this semester, build these habits:
Read Before You Run: Treat AI like a junior dev. Read every line. If you canโt explain why it works, don't use it.
Refactor & Structure: AI usually spits out isolated, brute-force solutions. Take time to fit it into your project's architecture and clean up the structure.
Test & Break It: Plausible-looking AI code hides the worst bugs. Don't assume it works just because it compiled. Write tests and find the edge cases yourself.
Own the Code: The real work starts after you paste. If the AI used a new method or design pattern, take 10 minutes to actually learn it.
AI should handle the heavy typing so you have time for the heavy thinking.
How do you verify AI code before submitting assignments? Drop your strategies below! ๐
@CTBEsoftwareengineers
Letโs be real, everyone is using AI to write code right now. Itโs fast, but blindly copy-pasting is the quickest way to lose our core skills. If we just paste and ship, we aren't software engineers ,we're just prompt typists.
To keep actually growing your skills this semester, build these habits:
Read Before You Run: Treat AI like a junior dev. Read every line. If you canโt explain why it works, don't use it.
Refactor & Structure: AI usually spits out isolated, brute-force solutions. Take time to fit it into your project's architecture and clean up the structure.
Test & Break It: Plausible-looking AI code hides the worst bugs. Don't assume it works just because it compiled. Write tests and find the edge cases yourself.
Own the Code: The real work starts after you paste. If the AI used a new method or design pattern, take 10 minutes to actually learn it.
AI should handle the heavy typing so you have time for the heavy thinking.
How do you verify AI code before submitting assignments? Drop your strategies below! ๐
@CTBEsoftwareengineers
โค8
Please open Telegram to view this post
VIEW IN TELEGRAM
โค3
๐ OWASP Top 10
The OWASP Top 10 is a must-know security checklist for web developers. It highlights the most critical web application security risks:
1๏ธโฃ Broken Access Control
2๏ธโฃ Security Misconfiguration
3๏ธโฃ Software Supply Chain Failures
4๏ธโฃ Cryptographic Failures
5๏ธโฃ Injection
6๏ธโฃ Insecure Design
7๏ธโฃ Authentication Failures
8๏ธโฃ Software/Data Integrity Failures
9๏ธโฃ Logging & Alerting Failures
๐ Mishandling of Exceptional Conditions
If you build web apps, APIs, or full-stack systems, understanding these risks can help you prevent vulnerabilities before they reach production.
๐ Learn the official OWASP Top 10:
OWASP Top 10:2025
@CTBEsoftwareengineers
The OWASP Top 10 is a must-know security checklist for web developers. It highlights the most critical web application security risks:
1๏ธโฃ Broken Access Control
2๏ธโฃ Security Misconfiguration
3๏ธโฃ Software Supply Chain Failures
4๏ธโฃ Cryptographic Failures
5๏ธโฃ Injection
6๏ธโฃ Insecure Design
7๏ธโฃ Authentication Failures
8๏ธโฃ Software/Data Integrity Failures
9๏ธโฃ Logging & Alerting Failures
๐ Mishandling of Exceptional Conditions
If you build web apps, APIs, or full-stack systems, understanding these risks can help you prevent vulnerabilities before they reach production.
๐ Learn the official OWASP Top 10:
OWASP Top 10:2025
@CTBEsoftwareengineers
โค3
Nobody wants to hire you.
Not because youโre worthless, but because you havenโt built enough value yet.
You donโt have many real-world skills, you still require significant investment in time and training before you can create serious value, and you may not know how to lead, delegate,communicate, or work independently.
Your college degree alone probably hasnโt turned you into an asset for a company.
So what now?
Understand the game. A company doesnโt hire you because you need a job. They hire you because they believe you can create more value than they pay you. Your salary is an investment, and companies expect that investment to eventually produce a return.
That means your responsibility is simple: become valuable.
Build skills that solve real problems.
Learn to ship.
Learn to communicate.
Learn to work independently.
Understand what businesses actually need and develop the ability to solve those problems.
Stop obsessing over how to look employable. Focus on becoming useful. Because the goal isnโt just to get someone to give you a job.
The goal is to become the kind of person a company canโt ignore.
@CTBEsoftwareengineers
๐6โค4โก1๐1๐1
Our Weekly Article is ready , It will posted soon
Who is Ready ?
Who is Ready ?
๐ฅ9โค3
The Illusion of Instant Transformation: Why You Must Build Slowly ?
@CTBEsoftwareengineers
Weโve been influenced by the idea that one decision can change everything That if you just decide hard enough, commit strongly enough, and push yourself enough, your life will instantly align with your goals. But real life doesnโt work like that read more ...
@CTBEsoftwareengineers
๐16๐ฅ8โ1โค1
DID YOU KNOW? YOUR CPU CAN LIE TO YOU.
Modern processors use speculative execution. they predict what your program will do next and execute instructions before knowing whether the prediction is correct.
Why? To save time.
The surprising part? Even when the CPU discards those results, traces can remain in the cache, potentially exposing sensitive data through attacks like Spectre.
One prediction. A hidden security risk.
@CTBEsoftwareengineers
Modern processors use speculative execution. they predict what your program will do next and execute instructions before knowing whether the prediction is correct.
Why? To save time.
The surprising part? Even when the CPU discards those results, traces can remain in the cache, potentially exposing sensitive data through attacks like Spectre.
One prediction. A hidden security risk.
@CTBEsoftwareengineers
โค4๐ฅ3
University students, listen up.
This isn't a motivational speech, believe me for real Just sit down and talk to 3 or 4 university graduates ...Ask them about their lives after graduation Then you'll understand what I'm talking about because Sometimes, you don't realize the value of a season of your life until you're no longer in it.
๏ปฟ
Right now, you have assignments, exams, deadlines, and all the usual university stress.
But alongside all that, you still have something valuable: the freedom to explore without having your entire life figured out.
Want to learn to code? Build something ๐ณ
Curious about AI? Experiment with it.
Have a business idea? Try it.
Want to create content, freelance, or learn a completely random skill? Go for it.
Build projects.
Meet people who challenge you.
Try things you're terrible at.
Start something that might fail.
Learn things that have absolutely nothing to do with your degree.
You don't need to have everything figured out. You just need to start exploring.
Because one day, you'll graduate. You'll have responsibilities, deadlines, bills, and a job that demands most of your time and energy and finding time to experiment with random interests might not be as easy as it is now.
Your degree may matters.
But there's so much more you can do with these years.
Use this time to discover who you are, what you can build, and what you're capable of becoming.
Don't just survive university. Make something out of it. ๐ช
@CTBEsoftwareengineers
This isn't a motivational speech, believe me for real Just sit down and talk to 3 or 4 university graduates ...Ask them about their lives after graduation Then you'll understand what I'm talking about because Sometimes, you don't realize the value of a season of your life until you're no longer in it.
You probably won't have this much freedom again.
๏ปฟ
Right now, you have assignments, exams, deadlines, and all the usual university stress.
But alongside all that, you still have something valuable: the freedom to explore without having your entire life figured out.
Want to learn to code? Build something ๐ณ
Curious about AI? Experiment with it.
Have a business idea? Try it.
Want to create content, freelance, or learn a completely random skill? Go for it.
Don't let your uni life become nothing more than attending lectures, passing exams, collecting grades, and waiting for graduation.
Build projects.
Meet people who challenge you.
Try things you're terrible at.
Start something that might fail.
Learn things that have absolutely nothing to do with your degree.
You don't need to have everything figured out. You just need to start exploring.
Because one day, you'll graduate. You'll have responsibilities, deadlines, bills, and a job that demands most of your time and energy and finding time to experiment with random interests might not be as easy as it is now.
So please, don't spend your entire university life preparing for a future while forgetting to build something for it.
Your degree may matters.
But there's so much more you can do with these years.
Use this time to discover who you are, what you can build, and what you're capable of becoming.
Don't just survive university. Make something out of it. ๐ช
@CTBEsoftwareengineers
โค25๐ซก7โ6๐4๐ฅ2
Error UX: Showing the Right Error
Don't show users only โSomething went wrong.โ Define each error and decide what the user should do next.
โ Network error: Check your internet and retry.
โ Timeout: The request took too long. Try again.
โ Validation error: Show what is wrong with the input.
โ Authentication error: Ask the user to log in again.
โ Permission error: Explain that they don't have access.
โ Server error: Show a simple message and offer support if needed.
โ Rate limit: Ask the user to wait before trying again.
โ Resource deleted: Explain that the item no longer exists and offer a way back.
โ Conflict: Explain that the data changed or the action cannot be completed as requested.
โ Upload failure: Explain the problem and offer retry or cancel.
For developers: Logs should include the error type, error code, request ID, time, affected operation, and useful technical details. Never log passwords, tokens, or other secrets.
Users need clear messages and next steps. Developers need enough detail to find and fix the problem.
@CTBEsoftwareengineers
Don't show users only โSomething went wrong.โ Define each error and decide what the user should do next.
โ Network error: Check your internet and retry.
โ Timeout: The request took too long. Try again.
โ Validation error: Show what is wrong with the input.
โ Authentication error: Ask the user to log in again.
โ Permission error: Explain that they don't have access.
โ Server error: Show a simple message and offer support if needed.
โ Rate limit: Ask the user to wait before trying again.
โ Resource deleted: Explain that the item no longer exists and offer a way back.
โ Conflict: Explain that the data changed or the action cannot be completed as requested.
โ Upload failure: Explain the problem and offer retry or cancel.
For developers: Logs should include the error type, error code, request ID, time, affected operation, and useful technical details. Never log passwords, tokens, or other secrets.
Users need clear messages and next steps. Developers need enough detail to find and fix the problem.
@CTBEsoftwareengineers
โค14
I just spent 30 minutes debugging. The bug was that I never saved the file. ๐คฆโโ๏ธ
Let me explain.
I changed my code. Ran it. Same error.
Changed it again. Same error.
Rewrote the whole function. Same error.
Googled. Read websites. Blamed the library. Blamed the framework. Blamed my laptop.
Then I noticed the white dot on the tab. The file was unsaved the whole time.
My code was probably fine for the 30 minutes๐ญ.
Every developer has a story like this, and nobody talks about it. We all act like we only fail at hard problems, but half of our bugs are typos, wrong branches, and the wrong .env file.
@CTBEsoftwareengineers
Let me explain.
I changed my code. Ran it. Same error.
Changed it again. Same error.
Rewrote the whole function. Same error.
Googled. Read websites. Blamed the library. Blamed the framework. Blamed my laptop.
Then I noticed the white dot on the tab. The file was unsaved the whole time.
My code was probably fine for the 30 minutes๐ญ.
Every developer has a story like this, and nobody talks about it. We all act like we only fail at hard problems, but half of our bugs are typos, wrong branches, and the wrong .env file.
@CTBEsoftwareengineers
๐14๐ญ11โค3๐ข1๐ซก1
A Team Can Have Genius People and Still Fail
Our Friday weekly article is here.
this one is about team work and how to make it efficient. Hope you enjoy reading it :)
@CTBEsoftwareengineers
Our Friday weekly article is here.
this one is about team work and how to make it efficient. Hope you enjoy reading it :)
@CTBEsoftwareengineers
โค6๐ฅ1๐1
Software engineering is dying?
No, it isnโt.
AI is reducing the barrier to producing code. It is not eliminating the need to understand what that code should do, why it should work, and what happens when it doesnโt.
The industry isnโt necessarily losing software engineers. Itโs changing what separates an engineer from someone who can simply produce software.
@CTBEsoftwareengineers
โค5๐ฅ5๐ญ2
Common Git and GitHub features besides git commit and git push:
โ git status shows which files are changed, new, or ready to save.
โ git log shows the history of past changes.
โ git diff shows exactly what changed in a file.
โ git branch creates or lists separate lines of work, so people can try ideas safely.
โ git switch or git checkout moves you to another branch.
โ git merge combines changes from one branch into another.
โ git clone copies a repository to your computer.
โ git pull gets the newest changes from a remote repository.
โ git stash saves work temporarily when you are not ready to commit.
โ On GitHub, pull requests let people review and discuss changes before merging.
โ GitHub issues help track bugs, tasks, and ideas.
โ GitHub Actions can run tests and builds automatically.
โ Forking copies someone elseโs GitHub repository to your own account.
โ Releases let you mark and share important versions of a project.
@CTBEsoftwareengineers
โ git status shows which files are changed, new, or ready to save.
โ git log shows the history of past changes.
โ git diff shows exactly what changed in a file.
โ git branch creates or lists separate lines of work, so people can try ideas safely.
โ git switch or git checkout moves you to another branch.
โ git merge combines changes from one branch into another.
โ git clone copies a repository to your computer.
โ git pull gets the newest changes from a remote repository.
โ git stash saves work temporarily when you are not ready to commit.
โ On GitHub, pull requests let people review and discuss changes before merging.
โ GitHub issues help track bugs, tasks, and ideas.
โ GitHub Actions can run tests and builds automatically.
โ Forking copies someone elseโs GitHub repository to your own account.
โ Releases let you mark and share important versions of a project.
@CTBEsoftwareengineers
โค6๐ฅ2
Hello AAU Coders!
I'm a new admin here, and I'm excited to get this community active . ๐
Starting *today*, expect a post every day:
๐ก Coding tips & concepts
๐งฉ Quizzes & challenges
๐ Project ideas
๐ผ Internships, jobs & scholarships
๐ Study & exam resources
๐ Dev humor & motivation
This is your community, so help shape it.๐
What do you want to see more of? React or comment:
I'm a new admin here, and I'm excited to get this community active . ๐
Starting *today*, expect a post every day:
๐ก Coding tips & concepts
๐งฉ Quizzes & challenges
๐ Project ideas
๐ผ Internships, jobs & scholarships
๐ Study & exam resources
๐ Dev humor & motivation
This is your community, so help shape it.๐
What do you want to see more of? React or comment:
โค18
If our code lives on GitHub, where does GitHub store its own code? ๐
Feel free to ask AI. We want you to know what happens behind the scenes.
Answer in the comment ๐
@CTBEsoftwareengineers
Feel free to ask AI. We want you to know what happens behind the scenes.
Answer in the comment ๐
@CTBEsoftwareengineers
โค3โก1
AAU Software Engineering community
If our code lives on GitHub, where does GitHub store its own code? ๐ Feel free to ask AI. We want you to know what happens behind the scenes. Answer in the comment ๐ @CTBEsoftwareengineers
Ever wondered where GitHub stores its own code? ๐
GitHub doesn't need some magical place outside the system.
Its engineers use private repositories on GitHub itself to build and maintain the platform.
Curious to see whatโs behind the scenes? Explore their public repositories here ๐
๐ https://github.com/github
GitHub doesn't need some magical place outside the system.
Its engineers use private repositories on GitHub itself to build and maintain the platform.
Yep, GitHub uses GitHub to build GitHub.
Curious to see whatโs behind the scenes? Explore their public repositories here ๐
๐ https://github.com/github
GitHub
How people build software. GitHub has 573 repositories available. Follow their code on GitHub.
๐คฉ3๐ฅ1
1. Coding is just the cover. Software Engineering is building the skyscraper
๐AI is getting incredibly good at coding (writing lines of syntax). But coding is not software engineering.
AI cannot talk to a frustrated client, understand their messy human emotions, figure out what they actually need (because clients never know what they want), and design a system to solve it. It doesn't understand business strategy, user empathy, or organizational politics. The syntax is automated; the problem-solving is yours.
2. If everyone can code, the "Ideas & Execution" person rules the world
Think about this as an entrepreneur: If AI makes coding "free," then code is no longer a moat. A billion-dollar company can't stop you just because they have 10,000 engineers. If you have a brilliant idea, a deep understanding of a specific industry's pain points, and the drive to execute, AI becomes your free, infinite workforce.
Instead of being a tiny cog in someone else's tech company, you are now the conductor of an AI orchestra. But to conduct the orchestra, you still need to know how music works. You need that engineering foundation to guide the AI effectively.
3. The "Last Mile" Problem (Why AI needs you)
Projects like ArtCraft prove exactly why humans are safe. An AI can generate 90% of a massive codebase in an hour. But that last 10%? Itโs filled with weird, hallucinated bugs, security vulnerabilities, and architectural nightmares.
AI cannot fix its own deep architectural flaws yet because it doesn't "think" it predicts the next token. The world is going to need a massive wave of AI-fluent human engineers to step in, debug, refine, and deploy this massive wave of AI-generated software.
4. You are entering at the absolute baseline
Imagine trying to learn software engineering in the 1970s, punching holes into physical cards and waiting days to see if your code worked. Every generation of tech gets higher-level abstractions.
You don't have to struggle through the old, tedious ways of learning. You get to learn with AI as your personal, 24/7 tutor. You can learn concepts 10x faster than engineers did five years ago. You aren't falling behind; you are being handed the most powerful educational tool in human history.
The Real Danger
The only way you get "cooked" is if you quit. If you quit, you miss the boat entirely. If you keep going, you become part of the top tier of builders who know how to command these models to build the future.
Take a deep breath. The tools are changing, but the world will always need builders !
@CTBEsoftwareengineers
๐8โค3๐ฅ1