Linus Kipkemoi Langat

I'm an apprentice software engineer building applications that turn pain points into memorable experiences—secure and scalable by design.

[Linus Kipkemoi Langat @Developer_Linus]

@8Nehe Mindset. I believe it's the source of what we do. Without the right mindset, you cannot discern what you should focus on depending on the paradigm shift.

[Nehemiah Kamolu @8Nehe]

What matters most today?

• AI Tools
• Mindset
• Network

Or something else ?

[Linus Kipkemoi Langat @Developer_Linus]

@8Nehe React.

[Linus Kipkemoi Langat @Developer_Linus]

@8Nehe Go for it. Fundamentals!

[Nehemiah Kamolu @8Nehe]

A beginner wants to learn HTML. What is your advice?

[Nehemiah Kamolu @8Nehe]

🔵 24. Consistency patterns In System Design 🔵

Three patterns you need to understand to ensure your system behaves as expected under load.

➤ Weak Consistency
In this pattern, a system adopts a "best-effort" approach.

After a write operation, subsequent reads may or may not return the most recent data.

This model is ideal for real-time systems such as VoIP calls or online multiplayer games where maintaining a continuous, fluid connection is more important than ensuring every single data packet arrives perfectly in order.

➤ Eventual Consistency
Eventual consistency is a common choice for high-traffic social platforms.

Here, data is replicated asynchronously, meaning while a write might not be reflected for all users instantly, the system guarantees that all reads will eventually converge on the correct value, usually within milliseconds.

A perfect example is the "like" count on a viral video; while the number might fluctuate or lag slightly for some users, it will normalize shortly.

➤ Strong Consistency
For applications where accuracy is non-negotiable such as banking system, strong consistency is the gold standard .

This pattern ensures that every read operation returns the absolute most recent write.

To achieve this, the system often uses synchronous replication and locks data resources (like account balances) during transactions to prevent any discrepancies.

This overview is part of a broader series on system design fundamentals. Choosing the right consistency model is essential for balancing system performance, availability, and reliability.

[Nehemiah Kamolu @8Nehe]

Scaling is the new frontier.

The demand for engineers who can integrate AI models into scalable, reliable backends is exploding. You are the builder of this new world.

[Linus Kipkemoi Langat @Developer_Linus]

@8Nehe Happy new month too. May you win big too.

[Eric @amerix]

Sebastian Sawe,

Congratulations!

What a record.

[Miu @Miu42121]

⚠️ ALERT❗️❗️

MISSING CHILD!!!!

Name:Luther GICHERU

Age:5yrs

last seen in Dandora phase 4 near baptist church on Wednesday 15/04/2026 wearing a yellow tshirt and a black trouser.(( He Can't clearly communicate))

If seen kindly get to us through 0799542472

RT WIDELY❗️❗️

[Linus Kipkemoi Langat @Developer_Linus]

@Jaseci_Org ProtoMCP is a useful product as we use AI assistants with MCP servers to provide context. With the tool, we get an understanding of our favorite MCP server(s) concerning their tools.

[Jaseci Labs @Jaseci_Org]

Developing MCP servers is 90% "Why didn't that tool call work?" and 10% actual coding.

Is it a schema hallucination? A bad param? Or did I just break the server?

We built ProtoMCP, so we can see exactly what the model is sending vs. what your server is doing.

[Linus Kipkemoi Langat @Developer_Linus]

@Jaseci_Org ProtoMCP is a great open-source MCP connection tool to discover its tools with ease accompanied by their schema. No more guessing of how tools work. I now have clear mental picture of tools in my favorite MCPs!

[Linus Kipkemoi Langat @Developer_Linus]

@devXritesh How did you know I'm learning Rust? This will be useful. Thank you.

[Nehemiah Kamolu @8Nehe]

I can't count the number of times `git stash` has been of help. One of my favorite git commands.

- One common case for me is when I forget to pull changes from remote when I have unstaged changes.

[Linus Kipkemoi Langat @Developer_Linus]

@8Nehe I agree.

[avrl ☘ @avrldotdev]

The best guide for anyone to start learning networking with programming.
This article will help you learn:

0. Networking protocols (TCP/UDP)
1. HTTP under the hood
2. Chunked encoding
3. Building state machines
4. Writing your own parser
5. Concurrency basics (multithreading)

[Nehemiah Kamolu @8Nehe]

3. The client-server Model

The internet is full of billions of activities, which can be summarized into two.
1. Making requests.
2. Returning responses.

In a basic way, devices responsible for making requests are called clients. The ones that return responses are called servers.

They use protocols to communicate. A protocol is a set of rules and principles to be followed by clients and servers when communicating e.g HTTP & SMTP. I'll touch on this in detail soon in a post.

Sometimes a client sends a request and waits for the server's response before continuing. This is called synchronous communication. When the client sends a request but does not wait for the server's response before proceeding, this is called asynchronous communication.

Frequent request responses can be stored temporarily so that the load on the server is reduced. This is called caching.

Some servers store and maintain session information for a client. They're called stateful servers. Others do not retain client session data between requests. They're called stateless servers.

There's more to the above in a video I created , here's the link: https://t.co/z8pPnTs46B.

[Nehemiah Kamolu @8Nehe]

You were scammed by vibe coding. Now it’s time to learn and grow.