AAU Software Engineering community

✨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

🎒 THE SOFTWARE ENGINEERING STARTER PACK Imagine a first-year student just joined our community. You can recommend ONLY ONE resource that genuinely helped you become a better developer. It can be: 📚 A book 🎥 A YouTube channel 💻 A website 🛠️ A tool 🧠 A course 📖 A documentation page Comment with: Resource: Best for: Why you'd recommend it: No recommending something just because it's popular. Tell us what actually helped YOU. Let's build a resource list worth saving. 🔖 Don't be shy...

It was not that long ago that we were saying, "AI is just a tool"😭😂 I dont think we're too far from a future where AI starts using us as the tool

Your past is not your future. Past: I wasted months learning without building anything. Future: What if I spend another year and still fail? Present: You become overwhelmed and avoid the very work that could help you improve. Your mind gets trapped between two things you cannot change directly: yesterday and tomorrow. Use the past to learn. Use the future to set direction. Then bring your attention back to what you can do today. Ask yourself: What did the past teach me? What am I working toward? What is the next action I can take right now?

Your future is shaped by what you repeatedly do in the present, not by how vividly you imagine tomorrow.

@CTBEsoftwareengineers

CI/CD is a set of automated practices that help teams build, test, and release software safely and quickly. CI (Continuous Integration) means every time a developer pushes code or opens a pull request, an automated system checks that the code builds and passes tests. CD (Continuous Delivery/Deployment) means code that passes those checks can be automatically prepared for release or deployed to an environment like staging or production. Here is how it works in practice: you create a small config file, usually a .yml file (for example, .github/workflows/ci.yml for GitHub Actions), and inside it you define when the pipeline should run and which commands it should execute, such as npm ci, npm run lint, npm test, and npm run build. You can set it to run on pull requests, for example with on: pull_request, so when a developer creates or updates a PR, the CI system automatically starts a machine, installs dependencies, and runs those lint/test/build commands. The PR then shows a green check if everything passes or a red X if something fails. This helps because problems are caught early before merging, every PR gets the same checks instead of relying on people to remember, reviewers save time, and the main branch stays safer and more stable. After merge, CD can continue the same idea by automatically deploying the app to staging or production. @CTBEsoftwareengineers

What is an API, really? Think about sending money using a banking app. You open the app, enter someone’s account number, and send 500 birr. But your phone doesn’t have direct access to the bank’s database. It can’t just reach in and change your balance. Instead, your app sends a request to the bank’s system through an API. The bank checks the request, processes the transfer, and sends a response back to your app. Request: “Send 500 birr to this account.” Endpoint: The specific address your app sends that request to. Response: “Transfer successful” — or “Insufficient balance.” That’s an API. It lets two different software systems communicate without either one needing direct access to the other’s internal workings. And this happens every time you log in with Google, check the weather, or pay online. An API is how software asks other software to do something. Follow for more explanations of the technology you use every day.

⚖️ THE DEVELOPER'S COURT IS NOW IN SESSION. Today's defendant: "If it works, don't touch it." The prosecution argues that this mindset creates technical debt. The defense argues that nobody has time to rewrite working code just because the developer had a sudden spiritual awakening. 😭 👨‍⚖️ JURY, WHAT'S YOUR VERDICT? 🟢 INNOCENT — ship it. 🔴 GUILTY — clean up your code. 🟡 IT DEPENDS — context is king. Drop your verdict and defend your position in the comments. Objection? Make it technical. 👨‍💻

HTTP status codes in plain English 🌐 Every time your browser or app talks to a server, the server answers with a 3-digit code. Read it before you blame your code. 200 - OK, it worked 201 - Created, your POST made something new 400 - Bad request, your request was malformed 401 - Unauthorized, you need to log in 403 - Forbidden, logged in but not allowed 404 - Not found, that page or resource doesn't exist 500 - Server error, the backend broke Next time a page fails, check the code first. It tells you where to look. 👇

This AI skill explains code by building it as a machine. 🔧 Meet Anatomy, a free, open-source skill for Claude Code, also compatible with OpenCode, Codex, and Antigravity. Ask it to explain a hard concept, and instead of a wall of text, it builds an interactive illustration of a machine that works like the concept. A rate limiter becomes a token bucket machine. A cache becomes a lock that only opens when every pin matches. You can hover to take it apart and watch the numbers change live. It already passed 19,000 stars on GitHub in about two weeks. Source: github.com/wheresryan22/anatomy

Hungry enough to build ➡️ Here is our Friday's weekly article. If you want to build a startup as a software engineer and student, you should read this. @CTBEsoftwareengineers

▎Dev3Pack Hackathon 2026 Build on Solana with students around the world, 27–29 November 2026. Join online or at the Addis Ababa Build Station to collaborate, get support, and bring your ideas to life. Learn Solana and Rust through the bootcamp starting 2 November. Top teams can continue with the Bridge Accelerator from 7 December. Compete for prizes including $10,000+ for the best Solana app, $500 local-track prizes, Seeker Phones, and $2,500+ in student perks. register here and Participate! @CTBEsoftwareengineers

Developing a Local Wispr Flow Alternative Using a 16.9 MB Model For individuals seeking immediate desktop voice-to-text conversion with no API expenses and complete offline privacy, Whistle by Cactus Compute facilitates execution on pure CPU architecture: • Minimal Resource Footprint: 16.9 MB model size • High Performance: Approximately 11 ms time-to-first-token • Multilingual Support: Seven languages supported • GPU Independence: Operates directly on the CPU 🛠 Implementation in three steps: Global Hotkey and Microphone: Assign a push-to-talk key (for example, holding Ctrl + Space) to record audio via a lightweight background script utilizing pynput and sounddevice. Immediate Local Speech-to-Text: Transmit the audio segment to the local Whistle engine immediately upon releasing the key. Active Window Input: Insert the resulting text directly into the currently focused text field using OS-level keystroke emulation methods such as xdotool, ydotool, or Windows SendInput APIs. This solution ensures complete privacy, eliminates network latency, and requires minimal RAM. It serves as an efficient project for enhancing daily typing productivity. 🚀

A real example of this that hit me recently: I was building a voice feature using Expo Audio, and no matter what I did, the recorded audio sounded terrible. Muffled, quiet, unusable. Instead of stepping back to understand how the audio pipeline actually worked, I started treating symptoms: • Tweaked random recording presets and audio modes • Added aggressive volume boosts • Built an entire backend server dedicated to noise suppression and audio cleanup Hours of work. Still sounded awful. The root cause? I had let AI scaffold the initial audio config, and it silently added unnecessary low-level flags that throttled sample rates and audio modes that were completely fine by default. I finally stopped patching over the mess, closed the extra backend, and actually read the core Expo Audio docs. I stripped out the clutter and implemented the native config myself from first principles. The result: Crystal-clear audio, zero external processing servers needed, and 70% less code. When you don’t fully grasp the underlying tool, you fix bad assumptions by adding more complexity. Master the fundamentals, understand what each line actually does, and the simplest solution usually wins.

Programming is clear thinking, not memorizing syntax or chasing trends. Avoid the classic beginner trap of obsessing over boilerplate and language quirks. Instead, focus on what actually lasts: • Breaking complex problems into simple, atomic steps • Designing clean, predictable data flow • Catching edge cases before they catch you Frameworks come and go, but core logic and algorithms never change. Once your mental blueprint is clear, the implementation is the easiest part. Master the fundamentalsthe code will follow effortlessly.

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

As an aspiring software engineer and entrepreneur, watching someone cloned billion-dollar software companies in a weekend makes us question... whether learning to code is even worth it anymore ? Read below for answer👇👇

Evening all, I'm SOphonyas, your new Administrator. I'm truly excited to join and contribute to this vibrant community.

AND I expect a lot of welcomes, seriously don't be shy! 😭😂

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.

Yep, GitHub uses GitHub to build GitHub.

Curious to see what’s behind the scenes? Explore their public repositories here 👇 🔗 https://github.com/github

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 👇