Collins Kariuki (@collo_karis) header
Collins Kariuki (@collo_karis) profile picture

A little bit of everything

Nairobi, Kenya
Joined January 2021
Photo by Collins Kariuki (@collo_karis)Photo by Collins Kariuki (@collo_karis)Photo by Collins Kariuki (@collo_karis)Photo by Collins Kariuki (@collo_karis)Photo by Collins Kariuki (@collo_karis)Photo by Collins Kariuki (@collo_karis)Photo by Collins Kariuki (@collo_karis)Photo by Collins Kariuki (@collo_karis)
Collins Kariuki retweeted
Electrical engineer explains why keeping your laptop plugged in is actually better for the battery than constantly charging it. But I always thought it was the other way around.🤔
781
13,451
555
89,361
7,250,809
Collins Kariuki retweeted
we all know that AWS went down for some time. let’s look at what actually happened: The US-EAST-1 region is one of AWS’s largest and most critical data centers, hosting infrastructure for thousands of major websites and applications. When DynamoDB, a key database service, began experiencing high error rates, it created a ripple effect across AWS’s interconnected systems. This caused widespread disruptions because many applications rely on DynamoDB for data storage and retrieval operations. You see, DynamoDB is deeply embedded in AWS’s control plane architecture. Many AWS services use it internally for storing metadata, state information, and service configurations. So, when the DynamoDB API endpoint became unreachable via DNS, these dependent services couldn’t access critical operational data. The failure affected over 36 AWS services simultaneously. When DNS resolution failed, client services couldn’t locate the DynamoDB endpoints. This triggered a feedback loop similar to the September 2015 DynamoDB outage. Each retry consumed more resources, causing more timeouts, which in turn triggered further retries, creating a vicious cycle. AWS responded by pursuing multiple parallel recovery paths simultaneously, rather than waiting to identify and fix a single root cause. The primary fix involved stabilizing the DNS resolution infrastructure for the DynamoDB endpoint. AWS’s engineering teams likely: -Reconfigured or restarted DNS resolvers handling DynamoDB. -Potentially rerouted DNS queries through alternative resolution paths. -Implemented emergency DNS caching adjustments. This incident reflects the interdependence and fragility of large-scale cloud ecosystems, where even a single point of failure in a core service can cascade across dozens of systems within minutes.
64
619
57
4,441
469,180
Collins Kariuki retweeted
We had microservices calling microservices calling microservices. One API request triggered 12 internal calls. Believe me, Tracing was a nightmare. Debugging took hours and hours. Adding a new service meant updating 5 other services. The problem isn't microservices. It's what we're missing The orchestration layer that actually works.
At a past company, the head of engineering and the principal engineers decided to break our Ruby on Rails application into a Go microservices mesh. They created very detailed design documents and architecture diagrams. They went all out and used Kubernetes, gRPC, service templates, the whole shebang. The whole senior engineering leadership came from Amazon, where they were used to each team owning a distinct service. They tried to apply that model directly. But our issues were with code ownership and poor domain modeling. The entire application could have run on just a handful of EC2 instances. What was the result? Five years later, 70% of the application is still running on the Ruby on Rails monolith. Never completed the migration. But now they have to maintain two systems. None of the original leadership works there anymore.
48
53
15
1,041
160,167
4
84
4
1,164
43,012
Collins Kariuki retweeted
I strongly recommend this book: BREAKNECK by Dan Wang. It was published this year. It ,somehow , argues that China is led by Engineers while USA is led largely by Lawyers and this difference in type of leaderships has its consequences. Creating things while the other regulates etc. Read it if you want to understand some strategies of accelerating economic growth. And let me know what you think.
22
176
8
591
42,656
Collins Kariuki retweeted
PRO TIP: Never use indexes on your database. They slow down writes by 50%. It's a scam by cloud providers to make you pay for more IOPS.
263
57
47
2,444
267,349
Collins Kariuki retweeted
Major cheat code for life: Learn to delay your reaction. Anger, fear, and impulse will try to make you move fast. There's power in pausing. In the pause, you see clearly, you respond wisely, and you avoid decisions you’ll regret. Slow down to speed up.
102
1,274
47
6,839
247,579
Game theory teaches: the less invested player holds the power; if your happiness is tied to any specific outcome, you’ve already surrendered leverage. Indifference isn’t weakness, it’s insulation. And insulation creates advantage.
37
1,093
17
8,169
324,667
Collins Kariuki retweeted
There is some work I do at night for @Essentiall_Ke See that 3rd order from the top, it's from ChatGPT. If you do manage a website ujue SEO is on it's way out. Try your best and optimise for AI(ChatGPT and Gemini/Bard), this is callled Generative Engine Optimization aka GEO and it will be one of the most powerful tools for discovery. I hope eventually I will get better at this 👊
11
32
3
108
15,718
Collins Kariuki retweeted
I love how God is always protecting us! Guess who were looting supermarkets at night? Yep, the police!
343
7,520
179
14,962
493,849
Collins Kariuki retweeted
This country needs the Punguza Mzigo bill back. From 2027, no MP or politician should earn anything above 200K. They also have no business having special insurance, mortgage, cars etc. I don't understand why this isn't out focus.
53
848
62
1,216
120,853
If you're in danger during a protest, run into a bar, not a church. Some of these churches will shut the gates and leave you to the bullets. At least the bar won’t judge you or lock you out. Let that sink in. Shame on CITAM church #SiriNiNumbers
557
9,078
118
23,677
452,769
Hata huwezi sema nimenunua uoga niko karibu kulia😭😭🤣 #June25th
I’ve never been this afraid for my life. I just want to go home man😭😭😭
51
854
9
4,548
71,566
Collins Kariuki retweeted
Ive just seen another photo of Dedan Kimathi that we should be using from now on...
107
4,574
46
17,517
477,725
Collins Kariuki retweeted
“Mlikuwa wapi Uhuru na matiang’i wakiua watu” to gen z’s is crazy. Most of them were in school bro. Are you mad that the new adults don’t wanna be governed poorly by the leaders they chose? That we are asking for our basic human right? Not to be shot & killed? Are you guys okay?
36
2,247
18
5,685
103,687
Collins Kariuki retweeted
Thika Road is a sea of people.
221
6,562
428
13,640
666,728
Collins Kariuki retweeted
If you can make it to State House Road, just come... we are camping here until he goes #SiriNiNumbers
102
3,580
56
5,766
173,552
Collins Kariuki retweeted
How ever 'small' you think your platform is, USE IT TO AMPLIFY !!🫵🏾🫵🏾🫵🏾🫵🏾this tyranny has to end!! #SiriNiNumbers #RutoMustGo #June25th #Tumechoka
62
5,034
56
4,687
91,232