B E N retweeted
Till today there hasn't been any dancehall feature out of africa bigger than this collabo..
Stonebwoy=African Dancehall🐐
DULEGBA✊🏿
Light Conquereth Over Darkness Every time
Destiny shall Forever be Fulfilled
History was Made! 🇬🇧🔥
LONDON, GHANA, BHIM NATION.
Thank You. ❤️ I love y’all. I can’t wait to be back!
@BHIMFESTIVAL #THETORCHER
20
B E N retweeted
API Design Playbook (Giveaway Alert)
• Core API fundamentals.
• Clean & scalable design principles.
• Popular patterns used in real-world systems.
• Practical concepts for interviews & building projects.
24 HOURS ONLY!
To get it for free:
1 Follow @systemdesignone [MUST]
2 Like & Retweet to get DM
3 Reply "Playbook"
Then I'll DM you the details.
B E N retweeted
Throwback to 2018 when Stonebwoy and Samini delivered an electrifying live band performance, with Kelvynboy providing backing vocals. Stonebwoy paused the performance and invited Kelvynboy to step forward and take the spotlight.
A heart of Gold — 24 karat
#TheTorcherEP
B E N retweeted
Time spent because it was necessary.
Just like farmers used hoes and cutlasses
The definition of farmer hasn't changed. Neither has that of a software engineer.
The tools simply evolved.
Serious question.
For 20 years, a "Software Engineer" was someone who spent thousands of hours mastering complex syntax, logic, and architecture.
Now, a 19-year-old can vibe-code a production-ready SaaS in a weekend using plain English and a $20 Claude subscription.
What does the title "Software Engineer" even mean right now?
Strings look simple, but in Java interviews they’re one of the most discussed topics.
Let's cover these topics :
1. Strings are Immutable
Once created, a String cannot be changed.
Any operation like concat(), substring(), or replace() creates a new object.
Why?
Security (e.g. URLs, passwords)
Thread-safety
Allows reusability in the String Pool
2. String Pool (Interning)
A special memory region for string literals.
If two literals are the same, they share one reference from the pool.
String s1 = "Java";
String s2 = "Java";
System.out.println(s1 == s2); // true (same pool reference)
3. String Pool area in JVM
Java 6 and before: Pool was in PermGen (fixed, small size -> often OOM).
Java 7+: Pool moved to the heap.
Pool is now garbage-collectible.
Much larger, can grow dynamically.
4. new String() vs Literal
String s1 = "Java"; // goes into pool
String s2 = new String("Java"); // new object on heap
System.out.println(s1 == s2); // false
System.out.println(s1.equals(s2)); // true
== -> compares references
.equals() -> compares values
5. intern() Method
Ensures the string is in the pool.
If it already exists, returns pooled reference.
If not, adds it to the pool.
String s1 = new String("Hello");
String s2 = s1.intern();
String s3 = "Hello";
System.out.println(s1 == s2); // false
System.out.println(s2 == s3); // true
B E N retweeted
In summary, in sessions, combine sessions correctly:
1. Detect the guest-to-auth transition at login
2. Define a merge strategy per field, never one global rule
3. Always regenerate the session ID post-merge
4. Link sessions to user IDs for multi-device access
5. Extend TTL on activity and checkpoint critical intent to Postgres
6. Use Redis with replication in production
B E N retweeted
Why Fintech Apps Care About “What Happened,” Not Just “What Is”
CQRS + Event Sourcing. Powerful, But Don’t Use It Everywhere
B E N retweeted
Idempotency is one of those things you don’t think about until the same request runs twice.
A request fails, times out, or the client just retries. From the client side, it feels normal. But on the server, that same action might run again. If it’s something like placing an order or making a payment, running it twice can cause real problems.
That’s where idempotency comes in.
An operation is idempotent if running it multiple times gives the same result as running it once. Whether the request comes once or multiple times, the end result should not change.
A simple way to handle this is using something called an idempotency key. The client sends a unique key with the request. The server stores that key along with the result. The first time it sees the key, it processes the request. If the same key comes again, it doesn’t run the logic again. It just returns the previous result.
This is especially useful because retries are very common. Networks fail, services slow down, and clients retry automatically.
You don’t want to stop retries.
You just want to make sure retries don’t do the same work again.
Software Development using AI doesn't have to be generating AI slop.
You can apply all the engineering principles and leverage AI for faster development.
Agent Skills for Spec Driven Development
github.com/sivaprasadreddy/s…
No more AI slop ⛔️
#AI #SpecDrivenDevelopment #AgentSkills
B E N retweeted
Optimistic locking = trust first, verify later Pessimistic locking = block first, proceed carefully
Also important: locking is not just a database theory topic. It directly affects latency, throughput, user experience, and even revenue.
Imagine 10 people trying to buy the last product: optimistic locking may let many attempt, but only one succeeds and others retry or fail gracefully pessimistic locking may serialize access early, which is safer, but can slow the whole flow
In interviews explain this very clearly: Use optimistic locking when contention is low and retries are acceptable. Use pessimistic locking when contention is high and correctness of a critical section matters more than concurrency.
B E N retweeted
I have been doing software development for nearly forty years and there is one common pattern I have seen on all successful software projects.
You get to a point near the end of the project where the number of files that need to be modified for a given change get smaller and smaller.
If your AI is modifying large number of files for small changes near the end of a project, you have a serious problem.
As the cool kids say, you are NGMI.
B E N retweeted
1GAD Go Make U Feel Alive When Listening To His Lyrics 🤍🙏
#BhimFestAtOvoArena
#BhimVibez































