UK

Infra roles are going to be very hot; there will be a huge uptick. It’s worthwhile to learn skills around: - Kubernetes - networking - Linux - data resiliency/lifecycling Data sovereignty and residency, and AI governance is going to drive this.

Reactionary thinking.

Ever since I relocated to the intellectual side of Twitter, this app no too dey stress me again. Try it today. Engage only with intellectual content and watch your feed change. You won’t be online getting triggered by idiots and idiots won’t be many in mentions because they lack the intellectual capacity to understand your tweet, talkless of engage with it.

LAST CALL: SeGoM 2026 is TOMORROW. Join Akinlua Bolamigbe (Careem/Uber), Tejiri Odiase (CargoAI), Princewill Chiaka (NowPost), and other senior engineers for a deep dive into Go system design, AI integration, and real-world scalability. 📍 CivicHive, Yaba
📅 Tomorrow | 11 AM – 3 PM If you build Go at scale, this is your room.
Register now before seats run out — tr.ee/hZJwBL

Introducing Claude Code Security, now in limited research preview. It scans codebases for vulnerabilities and suggests targeted software patches for human review, allowing teams to find and fix issues that traditional tools often miss. Learn more: anthropic.com/news/claude-co…

A device that visualizes how a computer performs calculations

@sleekdesigner1 @Joe_brendan_ @_fbrz

Screen recording from a validation form task I worked on today by @Joe_brendan_ The goal wasn’t just to collect input, but to control how the form behaves at every step. Each field has its own validation rules, with error messages appearing only when the state changes, not all at once. I paid attention to how validation feedback shows up without shifting the layout, how errors clear as inputs become valid, and how the form maintains structure even when multiple states are triggered. I used the Coolors sign in and sign up layout as the design reference since I’m already cloning the site, which helped keep the UI grounded in a real product context. This kind of form work looks simple on the surface, but most of the effort is in managing states and edge cases cleanly. I will write about the palette animations later #day3 of #BuildInPublic #Frontend #coolors

@AbaPowerOnline @AbapowerOnline is forcing all customers under the Ọmụma 11kva to clear their arrears before they can generate new tokens. This information was not communicated to customers, customers had to find out in their office @myabiadaily @NG_AbiaState @alexottiofr

Dear Valued Customer, We are pleased to inform you that the gas facility maintenance has been successfully completed, and Geometric Power Aba Limited (GPAL) has resumed power generation. Feeder loading is currently ongoing, and regular power distribution will be restored

This repository has many Go challenges to help you write idiomatic Go. It looks very promising: github.com/MedUnes/go-kata

@0xlelouch_ Suggest project based resource(s) that teaches any or all of these please.

As a Go engineer, learning syntax + goroutines is just the start. To be effective in real systems, you need to go deeper (no pun intended) into how Go is used at scale. Essentials to master as a Go engineer: 1. Go concurrency primitives (goroutines, channels, select) 2. Context propagation (context.Context) 3. Memory model & escape analysis 4. Garbage collection behavior & tuning 5. Interfaces & idiomatic API design 6. Error handling patterns 7. Standard library mastery (net/http, sync, time, io) 8. Profiling & benchmarking (pprof, bench) 9. Building high-throughput servers 10. Networking & TCP fundamentals 11. Database access patterns (database/sql, pooling) 12. Distributed systems basics (timeouts, retries, idempotency) 13. Observability (metrics, tracing, logging) 14. Testing strategies (unit, integration, race detection) 15. Deployment & runtime behavior (containers, signals, shutdown) Try to understand systems, not just language features.

odin: overall a language with ability to write c bindings easily and a lot of very useful features, but also suffers a lot from golang brainrot zig: good ideas with comptime, overall weird but interesting syntax, very good for performance-first stuff, but the standard is more fragile than a block of thin ice, so you'll spend 80% of your time trying to update other peoples libraries because they decided to remove like 20 functions and nothing works anymore i'd go (haha) with odin, since the other option... well... i doubt even andrew knows what to do with it anymore

Plot twist from the DDoS incident. After we got hit with a targeted attack on Dodo Payments, I posted a sincere note basically saying: if you did this, let’s talk. Not to fight, but to learn and make the system stronger. I didn’t expect anything. A few hours later, the attacker actually reached out. No threats, no ransom, no grand agenda. Just a human on the other side saying it was done for fun and curiosity, and that they wanted to see how far they could push modern infra. We had a real conversation. A strange one, but real. About what broke, what held, and what we can still improve. Sharing only this half for now, still comprehending the details. The other half has lessons every startup shipping on the internet should hear. More soon.

shettima watching all of you urging tinubu to resign

I have lost faith in captcha or bot protection after this attack.

The easiest way to quit tiktok/instagram reels is to realize you are most likely consuming information from people who haven't read a book in years

i want my apartment to be my friends’ third place where they come to after long days, or for no reason at all. meals with mismatched plates that somehow make sense together. background music humming under layers of laughter and overlapping stories. a little sanctuary.

Quit brain rot. Read books. Watch classics. Keep a to-do list. Turn off notifications. Eat without screens. Train your body. Clean your space. Take your work seriously. Eat real food. Help others. Walk more. Create » consume. Spend time with loved ones. Travel to new places.

God pleaseee 😭😭😭😂

Redis started timing out randomly. 1-2 times per hour. Operation that should take 2ms was taking 5+ seconds. What we checked: - Memory: 40% used (plenty available) - CPU: 12% average - Network: normal - No slow queries in logs - Replication lag: 0ms Enabled Redis slow log (>10ms operations): - Found KEYS * commands - Running during the timeouts - From monitoring script - Script checked key count every 30 seconds The problem: - KEYS * is O(N) operation - Blocks Redis (single-threaded) - 2.4 million keys in database - Took 5-8 seconds to scan all keys - All other operations blocked during scan The monitoring script: - Written 3 years ago - Redis had 10k keys then (sub-second) - Nobody updated it as data grew - Now blocking production queries The fix: - Replaced KEYS * with DBSIZE (O(1)) - DBSIZE returns key count instantly - No more blocking operations - Timeouts disappeared The lesson: Commands that were fast at 10k keys become disasters at 1M keys. Always check algorithm complexity. Redis operations aren't all equal.