Gilbert Morris

Identity & Access Management @EquityGroupPLC

Msc. InfoSec @Experienceusiu

[Moe @moneyacademyKE]

Many Kenyans travelling abroad usually have to sort out internet after landing, either by buying a local SIM card or using international roaming.

Here is how to set up your mobile data before you travel using an eSIM.

[Nandkishor @devops_nk]

Interviewer:

Your EC2 in Private Subnet Needs Access to S3 what will you do ?

[محمد سالم @M10M199]

التعاون قوة 👍

[Farmer Akin Alabi® @akinwale_cfi]

After watching this short story to the end you will understand how Blockchain Technology can help solve problems within the Agricultural sector using EGGS 🥚 as a case study but unfortunately the Nigeria Agricultural sector is not fully organized to help us implement our full potentials in the sector..

Reason why I will always respect Oga @BolajiAkinboro one of Dr @akin_adesina right hand men for building Nigeria agriculture Blockchain technology that works when he co-founded #cellulant

[Adnan @Adnan_Ai2]

DURING A JOB INTERVIEW, IF THEY ASK: "HOW DO YOU HANDLE IT WHEN EVERYTHING IS A PRIORITY?"

USE THE GOLDEN RESPONSE:

[Moe @moneyacademyKE]

An investigation by Gamers Nexus found that some LG smart TVs can scan devices connected to your Wi-Fi and capture audio even when the screen is off.

The TVs can also collect information about nearby Wi-Fi networks and what users watch for targeted advertising.

[Umoja @W_Asherah]

Hivi exactly. This exactly. Hivi ndio tunafikiria 😂

[Gilbert Morris @G_MOH_]

@melshakzedeck @EngJohnMachari1 How was he there?

[Suraj Sharma @suraj_sharma14]

If you want to go GOD LEVEL in SYSTEM DESIGN, learn these concepts NOW:

1.) Load balancing ⇒ L4 vs L7, health checks, sticky sessions
2.) Horizontal vs vertical scaling ⇒ add machines not muscle
3.) Caching strategies ⇒ cache-aside, write-through, write-behind and when each breaks
4.) Cache invalidation ⇒ one of the two hardest problems in computer science
5.) Database replication ⇒ leader-follower, sync vs async tradeoffs
6.) Sharding ⇒ consistent hashing, hot spots, rebalancing without downtime
7.) CAP and PACELC ⇒ what you give up the moment the network partitions
8.) ACID vs BASE ⇒ transactions vs availability, and who actually needs what
9.) Message queues ⇒ Kafka, backpressure, consumer lag, dead-letter handling
10.) Idempotency ⇒ keys and dedup so retries never double-charge
11.) Event-driven architecture ⇒ pub/sub, saga pattern, eventual consistency
12.) Circuit breakers ⇒ fail fast before one slow service kills everything
13.) Rate limiting ⇒ token bucket, sliding window, per-tenant quotas
14.) Retries with backoff + jitter ⇒ how you prevent thundering herds
15.) Connection pooling ⇒ never open 10k live DB connections
16.) CDN and edge caching ⇒ serve from near, not far
17. Indexing ⇒ B-trees, LSM-trees, covering indexes, query plans
18.) Consensus ⇒ Raft, leader election, quorum reads and writes
19.) Observability ⇒ distributed tracing, SLOs, error budgets
20.) Vector search ⇒ HNSW, ANN tradeoffs, recall vs latency
21.) Inference serving ⇒ KV cache, continuous batching, speculative decoding

Bookmark and keep building.

[Amukelani Moyani @AmukelaniMoyani]

Who can be a gentleman and buy me this?

[Nandkishor @devops_nk]

Knowing APIs won’t make you a good DevOps engineer. Knowing how they work in production will.

Early in my career, I mostly thought about APIs as:

GET → POST → PUT → DELETE

But working on real systems changes the questions:

→ Should this API be public or internal?
→ REST, GraphQL, or SOAP?
→ Should services communicate synchronously or asynchronously?
→ Is this a partner integration or internal service?
→ How do we secure, monitor, and rate-limit it?
→ Should this traffic go through an API Gateway?
→ How do we handle authentication, TLS, retries, and failures?

That's when you realise there isn't just one type of API.

Different API patterns solve different problems:

🔹 REST → Application & service communication
🔹 GraphQL → Flexible data fetching
🔹 SOAP → Enterprise integrations
🔹 Internal APIs → Service-to-service communication
🔹 Partner APIs → External integrations
🔹 B2B APIs → Business system connectivity

The syntax is the easy part.

The real skill is understanding how the API fits into the overall architecture and behaves in production.

That's what separates someone who knows the tools from someone who understands the system.

[BlueEaglePatriots @BlueEagleP1ntg]

How to install tile floor in the shower

[Park G.M™️ @temitoayoo]

Different ideas for your plain walls.

[Moe @moneyacademyKE]

Veteran NSE investor Paul Wanderi Ndungu has made a massive gain from Car & General.

The stock has gone up 885% in a year, from Sh26.40 to Sh285 per share.

His stake is now worth Sh1.8 billion, up from Sh170 million — a gain of Sh1.7 billion

[Mustafa. @oprydai]

how to study and learn really difficult subjects:

1. don’t panic. hard just means dense. it’s not impossible, it’s just packed. unwrap it slowly.
2. get a map before diving in. watch an overview video, read the table of contents, or skim the wikipedia page. you need context first.
3. use multiple sources. one book will confuse you, two will clarify, three will enlighten.
4. build intuition, not memory. visualize it. simulate it. code it. teach it to a friend or a wall.
5. tolerate confusion. you’ll feel dumb 90% of the time; that’s the price of learning something that rewires your brain.
6. connect it to reality. every abstract thing has a real-world analog. find it. relate it. ground it.
7. revisit the same topic after a week. mastery is not about reading once; it’s about returning after your brain has “chewed” on it.
8. don’t romanticize genius. smart people aren’t born knowing it. they just survived longer in the confusion phase.

the truth is; learning hard stuff isn’t about intelligence.
it’s about endurance, humility, and curiosity.

you stay long enough in the fog until it clears.

[Pauline Njoroge @paulinenjoroge]

This was so sweet of Michelle

[Jaydeep @_jaydeepkarale]

Kubernetes was hard until I watched these videos

[Jaydeep @_jaydeepkarale]

System Design was hard until I watched these videos

[𝐇𝐚𝐦𝐳𝐚 | Networking Guy @Hamzaonchain]

SSH (Secure Shell) is the protocol that lets you securely access and manage a remote system over a network.

Here's the basic SSH workflow:

1. The SSH client initiates a connection to the SSH server (usually on TCP port 22).
2. The server presents its public key, allowing the client to verify the server's identity.
3. Both sides perform a key exchange to create an encrypted session.
4. The user authenticates using a password, public/private key pair, or another supported method.
5. Once authenticated, a secure encrypted tunnel is established.
6. Commands, files, and data can now be transmitted securely between the client and server.

Without SSH, remote administration would expose credentials and sensitive data to anyone intercepting the traffic. SSH solves this by providing encryption, authentication, and integrity protection for the entire session.

If you've ever managed a Linux server, network device, cloud instance, or Raspberry Pi remotely, chances are you've used SSH.

[Chandana 🌻✨ @CuriousOnTech]

I don't care what you do this weekend.
Just watch these 5 videos. That's it.