AAU Software Engineering community

This is proof that you can make things happen when you fully commit to an idea, put in the work, and go all in.

Big things don't happen by just wishing for them.

We’re happy to announce that RAVN has successfully completed its Antler residency and secured its funding 🎉. This marks an important milestone for me and my cofounder. RAVN now has guaranteed funding, giving us the resources and support to move forward with our vision and focus on what comes next. We’re grateful to everyone who has been part of this journey. This is just the beginning.

10 Full-Stack Development Concepts Every Devekoper Must Master [Part 2 ] From Medium.

Everyone is renaming the same job this week, and the names actually matter. - Vibe coding: you describe what you want and accept what comes back. Fast for a prototype, dangerous for anything a client will pay for. - Agentic coding: you give the agent a goal, not a sentence. It plans, reads the code, runs tests, fixes its own mistakes, and comes back when it is done. You are the reviewer, not the typist. - Harness coding: the system around the agent. The permissions, the tests, the tools, the memory, and the rules for when it must stop and ask. You are not prompting better. You are building the rails that keep an agent honest. - Spec-driven development: you write the spec first and let the agent fill it in. - Context engineering: you decide what the model is allowed to see. - Copilot coding: still you driving, with autocomplete that got ambitious. The real difference is not the model. It is where control lives. - In vibe coding, control lives in the prompt. - In agentic coding, it lives in the task. - In harness coding, it lives in the system. I learned this building client sites in Addis. A vibe-coded demo impresses in a call. A client site needs tests, review, and a harness that catches the agent before the client does.

🚀 Upcoming Hackathons 1. Accessibility Hackathon 2026  Build tools that make learning and work more accessible for people with disabilities, refugees, and returnees. Choose from three tracks, with an optional Career Gateway challenge.  📅 November 14–15 | 📍 ALX Tech Hub, Lideta  🏆 Win 100,000 ETB  Register: LINK  2. Dev3Pack Hackathon 2026  Build AI and blockchain apps on Solana. Join online or at the Addis Ababa Build Station.  📅 November 27–29  🏆 $10,000+ top prize, local prizes, Seeker Phones, and student perks  Register: LINK 3. NASA Space Apps Challenge Addis Ababa 2026  Join developers, designers, and innovators for 48 hours of creative problem-solving.  📅 November 14–15 | 📍 Sheger Institute of Technology (SIT) LINK @CTBEsoftwareengineers

And here we go again... the cycle starts. You start learning one thing, then you hear React is trending, so you jump to React. Then someone tells you Go is the next big thing, so you move to Go. You hear Java is worth learning, so you start Java. And before you know it, you're jumping from one technology to another. Days turn into months, months into a year, and you've spent countless hours trying to learn different things, but somehow, you still feel like you haven't made much progress. Sometimes, it's not that you're not putting in the effort. It's that you're not giving one thing enough time before moving to the next. So, let's break that cycle. Pick one skill and stick with it for a while. Get comfortable using it. Build projects, make mistakes, get stuck, figure things out, and go beyond just learning the basic syntax. Actually understand how things work. You don't have to chase every trending technology. Give yourself time to become good at one thing first. And once you have a solid foundation, moving to another language or tech stack becomes much easier. Many concepts and problem-solving approaches carry over. The syntax and some underlying ideas might change, but you're not starting from zero. You don't need to learn everything at once. Just give yourself the time to master something first.

Fun Facts About Rust🌝 ▫️It started with a broken elevator. In 2006, Mozilla engineer Graydon Hoare walked up 21 flights of stairs because his building’s elevator software had crashed. He began working on a language that would make crashes like that much harder. ▫️It’s named after a fungus. Graydon has said the name comes from rust fungi, which are tough, spread widely, and are hard to kill. ▫️The first compiler wasn’t written in Rust. It was written in OCaml. Later Rust was rewritten to compile itself. ▫️The mascot is a crab named Ferris, and Rust developers call themselves Rustaceans. ▫️Developers love it. It has been voted the most loved (now “most admired”) language in the Stack Overflow survey every year since 2016. ▫️It’s younger than you might think. Rust 1.0 was released in May 2015. ▫️Its creator left before it got famous. Graydon stepped away in 2013, and the community took it from there. #Rust #FunFacts @CTBEsoftwareengineers

Episode one Rust🩵 ▫️Rust: Is It Worth Learning? Most languages make you choose. C and C++ give you speed and control, but managing memory is your job, and one mistake means crashes or security holes. Java, Python, and Go handle memory for you with a garbage collector, but you give up some performance and control. Rust’s approach is different: it checks memory safety at compile time through ownership. Every value has exactly one owner. You can either lend it out to many readers or to one writer, never both at once. When the owner goes out of scope, the memory is freed automatically. That gives you no garbage collector, no manual free(), and no data races. The trade-off is real. Rust has a steep learning curve, and the borrow checker will reject code that looks fine to you. Compile times are slower than Go’s, and for a quick script, Python is still the better choice. But the effort pays off. Ownership teaches you to think about memory, lifetimes, and concurrency, and those ideas carry over to every language you’ll write. The tooling (Cargo, rustfmt, clippy) is some of the best around, and the error messages actually explain what went wrong. As for why it matters now, Rust has moved into the Linux kernel, Android, Windows, and cloud infrastructure, and security agencies keep pushing the industry toward memory-safe languages. You don’t need Rust for your first job. Learning it does make you understand what your code is actually doing, and that makes you a stronger engineer whatever stack you end up in. Free start: doc.rust-lang.org/book #Rust #ProgrammingLanguages @CTBEsoftwareengineers

It's Monday🔥 so from now on we will review programming languages deeply every Monday. @CTBEsoftwareengineering

Beyond CRUD: Build Projects That Actually Make You Think

We’re tired of seeing developers build the same generic projects over and over again. Another management system. Another inventory app. Another CRUD application. Another to-do list. And honestly, there’s nothing inherently wrong with read more....

🥁🥁

Who is Ready for Our Weekly Article ?

🔧 Browser DevTools Ever wonder what those tabs in your browser’s DevTools do? Here is a simple guide to the main ones: ➔ Elements – Shows the page’s HTML and CSS. You can change them and see the result live. If you want to fix a layout or style problem - that's your tab to go. ➔ Console – Shows messages and errors. You can also type simple JavaScript here and run it. Use it if you want to test a small code idea or read an error. ➔ Network – Shows the files and requests the page loads, like images, scripts, and API calls. Used when a page loads slowly or a request fails. ➔ Sources – Shows the page’s code files. You can use it to debug JavaScript. When to use? - If you need to pause code and find where something goes wrong. ➔ Application – Shows stored data, like cookies, local storage, and session storage. Use it if you need to check login data or clear site data. ➔ Performance – Shows page speed, CPU, and memory use. Use it when a page feels slow, freezes, or uses too much power. Tip: Open DevTools with F12 or right-click and choose Inspect. @CTBEsoftwareengineers

To understand recursion, you must first understand recursion. 😂 ...and to understand that joke, you must first understand recursion. Happy Tuesday. Now go write a function that calls itself (with a base case, please).

Dear Gen Z Maybe the biggest thing holding you back is YOU.

You spend too much time: Worrying about what people think of you. Measuring your progress against someone else's timeline. Being afraid to fail where everyone can see. Chasing society's definition of success instead of defining your own. Giving attention to everything except what actually matters. Blaming your circumstances instead of taking responsibility for changing them. At some point, you have to stop watching everyone else's life and start taking ownership of yours.

Your life is yours. Act like it.

Tech newses this week🔥 1. AI agents are now real contributors to codebases GitHub reports that AI agents now start more than 40% of pull requests. For engineers, this means the job is shifting from writing every line to reviewing, testing, and guiding AI-generated code. Strong code review and system design skills are becoming more valuable, not less. 2. Big Tech is cutting staff while spending on AI Microsoft has been pushing to reduce headcount, raising concerns that critical systems become risky when departing employees take specialized, undocumented knowledge with them. Lesson for engineers: document your work, and become the person who understands systems end to end. 3. Markets want results, not hype The Nasdaq 100 was on track to lose over $1 trillion on Friday after weak results from Amazon and Intel, with Intel dropping about 30% on a poor outlook. Meanwhile, Meta plans to raise up to $95B to fund AI. Money is still flowing into AI, but companies must now show real value, so engineers who can ship practical, cost-efficient solutions stand out. 4. Security is a top priority Researchers confirmed attackers can execute commands on vulnerable PHP servers after two critical flaws were disclosed, and new cyber campaigns are targeting AI agents themselves. If you build with PHP or AI agents, patch quickly and learn secure coding basics. 5. Standards for AI agents are emerging Sierra and Meta published the Personal Agent Protocol, an open OAuth-based standard that lets a user’s AI agent authenticate with businesses. Worth reading if you want to build agent-based products. Hot take 🌩: Learn the fundamentals deeply (data structures, systems, networking, security), use AI tools daily but understand what they produce, and build real projects you can show. AI is changing how code gets written, but engineers who can think, verify, and design will stay in demand. #SoftwareEngineering #AI #Tech @CTBEsoftwareengineers

What do you think the cause is for this? 😅 @CTBEsoftwareengineers

Why do agent skills matter so much when using coding agents? Left unconstrained, coding agents act like over-eager interns. You ask for a simple feature. They generate three unnecessary wrapper files. They install redundant npm packages. They overcomplicate your entire codebase. Skills fix this by injecting plug-and-play discipline directly into the agent's workflow. My favorite skill right now is Ponytail. It stops the agent from jumping straight into writing custom code. Instead, it forces the AI through a strict decision ladder first. It checks if the feature is actually needed. It reuses existing repository components. It leverages standard libraries and native browser APIs before adding anything new. It is ridiculously powerful, and that saved me a lot of wasted tokens, bloated git diffs, and hours spent unwinding bad abstractions. Don't run your coding agents raw. Give them the discipline of a veteran senior dev. Check out the GitHub repo here:https://github.com/DietrichGebert/ponytail

✨Our Weekly Article is Ready. Read, Learn, Relate✨ The Best Code I Ever Wrote Was the Code I Deleted

Last week I opened a pull request with 1,900 lines removed and 40 lines added. My reviewer left one comment: “Are you sure?” I wasn’t. I clicked merge anyway. Nothing broke. The app got faster, the build time dropped, and I felt better than I had after any feature I shipped this year. That’s when I understood something that no tutorial says out loud ....

Read Here @CTBEsoftwareengineers