ለመላው የክርስትና እምነት ተከታዮች በሙሉ

መልካም የመስቀል በዓል

አዲስ አበባ ዩኒቨርስቲ

⚠️ Even if vibe coding isn’t recommended , Bookmark this before you start vibe coding.
You’ll need it !

@CTBEsoftwareengineers

Critical Database Checks Before You Build
Before writing your database schema, don't only think about the main tables. Check these too:

• Relationships — who belongs to what, and what happens when related data is deleted?

• Constraints — required fields, unique values, foreign keys, valid ranges, and enums.

• Indexes — which fields will be searched, filtered, sorted, or joined often?

• Data lifecycle — create, update, archive, restore, and permanent delete.

• Security — passwords, tokens, sensitive data, encryption, and access control.

• User states — active, inactive, suspended, verified, deleted, etc.

• Transactions — what operations must succeed or fail together?

• Concurrency — what happens when two users change the same data at the same time?

• Files & images — metadata, size, type, storage, ownership, and deletion.

• Soft delete & recovery — should data really be deleted or only archived?

• Versioning — do important records need history or previous versions?

• Performance — what happens when you have 1M+ records instead of 100?

• Retention & backup — how long is data kept, and how will it be restored?

• Future changes — can the schema evolve without breaking existing users or data?

Simple rule: Don't design a database only for how the app works today. Design it for how the data will behave throughout its entire lifecycle.

@CTBEsoftwareengineers

✨Database tip: sharding, and why you should delay it✨

Sharding means splitting one big database into smaller pieces (shards), each on its own server. Every shard holds only part of the data. Sounds great for scale, but it makes life harder: joins across shards get painful, transactions get tricky, and moving data later is a headache.

Try these first:
🔹Add indexes on slow queries
🔹Add read replicas for heavy read traffic
🔹Cache hot data (Redis)
🔹Archive old data

If you do shard, the shard key is everything.
Pick a key that: Spreads data evenly (like user_id) Matches how you query most often
A bad key, like country, creates "hot shards" where one server does all the work while others sit idle.

Rule of thumb: shard only when a single well-tuned server can no longer handle your data or writes.

This is only a heads-up. Do your own deep dive before you build on it. Hope this helps ☺️

@CTBEsoftwareengineers

Our Weekly Article is ready , It will posted soon
Who is Ready ?

Dear Past Me: Notes From the Developer Who Has to Fix Your Code

Last month I opened an old project and found a function called handleStuff. It was 140 lines long, had zero comments, and right in the middle sat a line that said // TODO: fix this later.
I did what any mature developer would do. I opened git blame, ready to find the guilty person and have a serious talk with them. ....

Read Here

@CTBEsoftwareengineers don't miss out - join now!

AI models are moving fast. Here are some of the notable releases from the past two weeks:

Gemini 4 Argon — Google
Released Sept. 30, Argon targets complex reasoning, coding, cybersecurity, and enterprise work, with a 1M-token context window.

Claude Sonnet 5.5 — Anthropic
Released Sept. 28, Sonnet 5.5 focuses on everyday knowledge work, coding, documents, and long-horizon tasks, while being faster and cheaper than its predecessor.

GPT-6.1 Sol — OpenAI
Released Sept. 29, GPT-6.1 Sol is designed for complex coding and professional work, with lower pricing than GPT-6 Astra and support for multi-agent workflows.

Claude Opus 5.5 — Anthropic
Released Sept. 22, Opus 5.5 targets demanding reasoning and professional tasks, with Anthropic reporting substantially lower operating costs than Opus 5.

Gemini 3.8 Live — Google
Released Sept. 15, the new Live models focus on real-time voice interaction, visual context, and more advanced multi-step reasoning.

#news
@CTBEsoftwareengineers

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

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

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

🔐 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

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

Our Weekly Article is ready , It will posted soon
Who is Ready ?

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

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.

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

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

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

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

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