I am hiring an assistant officer

Gender - Female
Computer skill - intermediate

Quick to learn and please be active

You should live around Bethel, Ayer Tena, alembank

Appreciated if you could speak English.

DM on @HundaolFekadu

🚀 WORKSHOP: App Builder (No-Code / Low-Code Development)

📱Learn how to build real-world mobile applications without deep coding, using powerful app builder tools.

👤 Guest Speaker: Behailu Getachew aka Lij Baya
Software Developer | Sketchware Developer
Co-Founder at Taadhii E-ticketing General Trading PLC

🎤 Hosted by: Haymanot Gebeyehu

📅 Date: January 5, 2026
⏰ Time: 8:00 PM (Mata 2 LT)

What you’ll learn:
✅ Introduction to app builders & low-code platforms
✅ How Sketch-ware works in real projects
✅ Turning ideas into functional mobile apps
✅ Real-life experience from building production apps
✅ Tips for beginners and aspiring app developers

🏆Challenge Alert
At the end of the workshop, there will be a hands-on challenge prepared by Lij Baya.

🎯 Who should attend?
Students, beginners, non-coders, and anyone curious about building apps quickly and efficiently.

Follow Lij Baya's on Youtube and Telegram

Telegram|LinkedIn|YouTube|Tiktok|

#ISHubAAU #Workshop #AppBuilder #Workshop #LowCodePlatform #LijBaya

Happening now🔥🔥🔥

🚀 How Startups Benefit From ETHIOPIAN STARTUP PROCLAMATION

1️⃣ Business Support & Growth Help

Startups get structured support instead of guessing everything on their own. This includes:

a. Business guidance and mentorship

b. Help refining ideas into real products

c. Support for scaling operations

d. Better decision-making using proven frameworks

👉 This saves time, money, and costly mistakes.

https://justice.gov.et/en/law/%e1%8b%a8%e1%8a%a2%e1%89%b5%e1%8b%ae%e1%8c%b5%e1%8b%ab-%e1%88%b5%e1%89%b3%e1%88%ad%e1%89%b3%e1%8d%95-%e1%8a%a0%e1%8b%8b%e1%8c%85-%e1%89%81%e1%8c%a5%e1%88%ad-1396-2017-ethiopian-startup-procla/

𝗛𝗼𝘄 𝘁𝗼 𝗮𝗻𝘀𝘄𝗲𝗿 𝘀𝘆𝘀𝘁𝗲𝗺 𝗱𝗲𝘀𝗶𝗴𝗻 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝘂𝘀𝗶𝗻𝗴 𝘁𝗵𝗲 𝗦𝘆𝘀𝘁𝗲𝗺 𝗗𝗲𝘀𝗶𝗴𝗻 𝗠𝗮𝘀𝘁𝗲𝗿 𝗧𝗲𝗺𝗽𝗹𝗮𝘁𝗲?

Here is the System Design Master Template, which you can use as a basis for any system design problem you may encounter during an interview.

A list of topics that you should know:

𝟭. 𝗟𝗼𝗮𝗱 𝗕𝗮𝗹𝗮𝗻𝗰𝗲𝗿. Distributes inbound requests across healthy nodes using rules such as round-robin or least-connections. Keeps latency stable and enables rolling upgrades without downtime.

𝟮. 𝗔𝗣𝗜 𝗚𝗮𝘁𝗲𝘄𝗮𝘆. Single entry that authenticates callers, enforces quotas, and routes each call to the right microservice. Can also aggregate responses so that clients hit a single endpoint.

𝟯. 𝗖𝗼𝗻𝘁𝗲𝗻𝘁 𝗗𝗲𝗹𝗶𝘃𝗲𝗿𝘆 𝗡𝗲𝘁𝘄𝗼𝗿𝗸 (𝗖𝗗𝗡). An edge network that caches immutable assets near users, cutting round-trips and shielding origins from spikes. Often handles TLS and compression as well.

𝟰. 𝗠𝗲𝘁𝗮𝗱𝗮𝘁𝗮 𝗦𝗲𝗿𝘃𝗲𝗿. Stores pointers, permissions, and object properties in a small, fast store. Replicates data for reads and writes to block servers when files are changed.

𝟱. 𝗕𝗹𝗼𝗰𝗸 𝗦𝗲𝗿𝘃𝗲𝗿. Persists data chunks on commodity disks, replicates across racks, and self-heals after failures. Clients stream blocks in parallel for throughput.

𝟲. 𝗦𝗵𝗮𝗿𝗱 / 𝗣𝗮𝗿𝘁𝗶𝘁𝗶𝗼𝗻 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁. Splits a growing dataset by user ID, time, or hash so that each DB instance remains small. Rebalances shards when a node fills or a hot key appears.

𝟳. 𝗖𝗮𝗰𝗵𝗲 (𝗥𝗲𝗱𝗶𝘀/𝗠𝗲𝗺𝗰𝗮𝗰𝗵𝗲𝗱). Holds hot keys in RAM with TTL, counters, and locks. Reduces read latency from milliseconds to microseconds and offloads the primary store.

𝟴. 𝗗𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗲𝗱 𝗠𝗲𝘀𝘀𝗮𝗴𝗶𝗻𝗴 (𝗞𝗮𝗳𝗸𝗮/𝗥𝗮𝗯𝗯𝗶𝘁𝗠𝗤). Durable log that decouples producers from consumers, provides replay, back-pressure, and at-least-once delivery. Enables event-driven designs.

𝟵. 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗦𝗲𝗿𝘃𝗶𝗰𝗲. Pulls events from the queue, batches them, and pushes email, SMS, or mobile alerts. Retries with exponential back-off and user-level throttling.

𝟭𝟬. 𝗝𝗼𝗯 𝗪𝗼𝗿𝗸𝗲𝗿𝘀. Stateless containers that pick tasks such as video encoding or thumbnail generation from a queue. Scale horizontally by adding replicas.

𝟭𝟭. 𝗗𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗲𝗱 𝗟𝗼𝗴𝗴𝗶𝗻𝗴 𝗮𝗻𝗱 𝗧𝗿𝗮𝗰𝗶𝗻𝗴. Ships structured logs and distributed spans to a central store, then indexes by request ID. Let's you trace a single user action across dozens of services.

𝟭𝟮. 𝗕𝗮𝘁𝗰𝗵 / 𝗦𝘁𝗿𝗲𝗮𝗺 𝗣𝗿𝗼𝗰𝗲𝘀𝘀𝗶𝗻𝗴 (𝗦𝗽𝗮𝗿𝗸, 𝗛𝗮𝗱𝗼𝗼𝗽). Transforms raw events into aggregates, ML features, and reports. Supports windowed joins for near-real-time dashboards.

𝟭𝟮. 𝗠𝗲𝘁𝗿𝗶𝗰𝘀 𝗮𝗻𝗱 𝗔𝗹𝗲𝗿𝘁𝗶𝗻𝗴. Scrapes time-series data, stores it efficiently, and renders dashboards. The Alert Rules page alerts you when latency, error rate, or saturation crosses SLOs.

How to use the template:

🔹 𝗖𝗹𝗮𝗿𝗶𝗳𝘆 𝗻𝗲𝗲𝗱𝘀. What’s the core read/write path? Which NFRs bite first?
🔹 𝗗𝗿𝗮𝘄 𝘁𝗵𝗲 𝗯𝗹𝗼𝗰𝗸𝘀 𝗮𝗯𝗼𝘃𝗲. Drop the ones you don’t need yet; add only the few missing pieces.
🔹 𝗗𝗶𝘃𝗲 𝗱𝗲𝗲𝗽. Select one risky block and explain the data model, failure modes, and scale limits.
🔹 𝗦𝘁𝗿𝗲𝘀𝘀 𝘁𝗲𝘀𝘁. Walk through spikes, region loss, and schema changes.

Hit every interview like this, and you’ll give a structured, high-signal answer in minutes.

Save for later and share with your team.
@et_open_source

Job Title: System Administrator
Company: Hagere Technology
Location: Addis Ababa, Ethiopia
Type: Full-time

Role Overview
Hagere Technology is seeking a skilled System Administrator to manage and maintain our clients’ servers, systems, and network infrastructure, ensuring security, stability, and high performance.

Key Responsibilities
• Install, configure, and maintain Linux/Windows servers
• Monitor systems, troubleshoot issues, and minimize downtime
• Manage security, backups, and disaster recovery
• Administer user accounts and access rights
• Maintain web and database servers (Apache/Nginx, MySQL/MariaDB)
• Provide technical support to teams and clients

Requirements
• Degree in IT, Computer Science, or equivalent experience
• Strong Linux knowledge
• Experience with web servers and databases
• Familiarity with cloud/virtualization (AWS, DigitalOcean, etc.)
• Basic noscripting skills are a plus

Apply:
Send your CV to career@hageretechnology.com

@et_open_source

🍎 iOS widgets are about meeting users where they already are and making your app more sticky. When your app has a real reason to live on the lock screen or home screen, it stays top of mind every time someone checks their phone.

This tutorial breaks down why this matters and how to add iOS widgets to your Expo apps with native Swift widgets and :
expo.dev/blog/how-to-im…

@et_open_source

𝐀𝐟𝐫𝐢𝐪𝐮𝐞𝐋𝐋𝐌 — a suite of open Large Language Models (LLMs) adapted to 𝟮𝟬 𝗔𝗳𝗿𝗶𝗰𝗮𝗻 𝗹𝗮𝗻𝗴𝘂𝗮𝗴𝗲𝘀 through Continue pre-training (CPT) on 26B tokens.

It have 3 🇪🇹 langauges: Amharic, Tigrinya, and Afaan Oromoo

https://huggingface.co/collections/McGill-NLP/afriquellm

Go.sum is not a lockfile (Score: 150+ in 15 hours)

Link: https://readhacker.news/s/6JZDz
Comments: https://readhacker.news/c/6JZDz

List of websites to practice your frontend dev skills ;
1. frontendmentor.io

2. devchallenges.io

3. codepen.io

4. webdevdaily.io

5. frontendpractice.com

6. greatfrontend.com


@et_open_source

Dear Codenight members,

Dossie Solutions is looking for a new Backend Developer with Node.js and Express.js experience.

Here is the link for the job posting: https://akilconnect.org/en/talent/opportunities/696119007440b6cb768e5f5c

I treat system design like a checklist.

Here’s my go-to mental TODO list when building systems:

Fundamentals
- What are the read patterns?
- What are the write patterns?
- Who owns the source of truth?
- Is consistency or availability more critical?
- Single writer or multiple writers?

Architecture
- Synchronous or async?
- Do I need a queue, or is a cron job enough?
- Can I separate the compute from storage?
- Stateless or stateful services?
- Contracts versioned?

Reliability
- What happens when this fails?
- Where’s the retry logic, and is it idempotent?
- Are we alerting to symptoms or root causes?
- Timeouts configured?

Scaling
- How do reads scale?
- How do writes scale?
- Will this design hold up at 10x traffic?
- What’s the hot path, and how do we optimize it?

Observability
- Do we log what we need to debug in production?
- Can we trace a request across services?
- What metrics define “healthy”?
- Debuggable without redeploy?

I don’t always follow it linearly, but if something breaks or feels off, this list helps me pinpoint what I may have overlooked.


@et_open_source

Top 37 Git Commands Every DevOps Engineer Must Know

🔹 Daily Workflow (Basics)
1.git clone – Copy repo locally
2.git status – Check repo state
3.git pull – Fetch & merge changes
4.git push – Push commits to remote
5.git add – Stage changes
6.git commit – Save changes

🔹 Branching & Collaboration
7.git branch – List branches
8.git branch <name> – Create branch
9.git checkout <branch> – Switch branch
10.git checkout -b <branch> – Create & switch
11.git switch – Switch branches (modern)
12.git merge – Merge branches
13.git rebase – Reapply commits cleanly

🔹 History & Inspection
14.git log – Commit history
15.git log --oneline --graph – Visual history
16.git diff – Show changes
17.git show – Inspect commit
18.git blame – Who changed what

🔹 Undo & Recovery (Very Important)
19.git reset – Undo commits (local)
20.git reset --hard – Force reset
21.git revert – Safe undo (prod-friendly)
22.git stash – Save uncommitted work
23.git stash pop – Restore stashed work
24.git reflog – Recover lost commits

🔹 Remote & Repo Management
25.git remote -v – View remotes
26.git fetch – Fetch without merge
27.git tag – Create version tag
28.git describe – Version info from tags

🔹 DevOps Power Commands
29.git cherry-pick – Pick specific commit
30.git clean -fd – Remove untracked files
31.git config – Git configuration
32.git shortlog – Commit summary
33.git archive – Create source archive

🔹 CI/CD & Ops Friendly
34.git diff HEAD~1 – Compare last commit
35.git rev-parse HEAD – Get commit hash
36.git show-ref – List refs
37.git worktree – Multiple working trees

Knowing Git deeply = fewer CI/CD failures & faster production fixes.

👉 For more insights, tools, and open-source updates, join our channel here:
🔗 open_source

Do you know? 🐳

Docker → Go

☸️ Kubernetes → Go
🧰 Terraform → Go
📊 Prometheus → Go
📈 Grafana → TypeScript

⚙️ Jenkins → Java
🐍 Ansible → Python
🍳 Chef → Ruby
🎭 Puppet → Ruby

🔍 ELK Stack → Java & Ruby
🧠 Nagios → C
💾 Splunk → C++
☁️ AWS CLI → Python

🔵 Azure CLI → Python
🦊 GitLab → Ruby & Go
🔁 CircleCI → Clojure
🔐 HashiCorp Vault → Go
🚀 ArgoCD → Go
🛡️ Istio → Go

The backbone of DevOps tools is built with Go, Python, Ruby, and Java.
Isn't it time you mastered them? 🚀

👉 For more DevOps insights, tools, and open-source updates, join our channel here:
🔗 open_source