B E N (@youngbernard283) header
B E N (@youngbernard283) profile picture

The quest to make life a place full of comfort ✌️

Joined May 2023
Photo by B E N (@youngbernard283)Photo by B E N (@youngbernard283)Photo by B E N (@youngbernard283)Photo by B E N (@youngbernard283)
Till today there hasn't been any dancehall feature out of africa bigger than this collabo.. Stonebwoy=African Dancehall🐐
4
53
3
492
4,492
Java 99.8%🖤🖤
Quote this tweet with the most popular language that makes up your backend tech stack. Mine: Rust 91.1%
1
1
3
88
Torcher iii 🔋 Loading….
719
1,775
229
10,654
335,043
Do you know Dangme was being written 400+ years ago?
5
43
3
150
4,231
B E N retweeted
HE IS WITH US 🌋☝🏾
49
476
25
3,084
27,722
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
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.
318
282
5
679
51,475
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
14
223
6
2,000
52,477
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?
1
11
48
3,726
B E N retweeted
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
3
6
46
3,170
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
1
4
181
Why Fintech Apps Care About “What Happened,” Not Just “What Is” CQRS + Event Sourcing. Powerful, But Don’t Use It Everywhere
18
56
6
532
14,171
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.
1
4
1
35
3,175
B E N retweeted
CHELSEA HAVE FINALLY SCORED AGAINST A TOP LEAGUE SIDE 🤯 They are flying over Leeds in the FA Cup semifinals 🔥
261
1,124
77
23,522
865,469
B E N retweeted
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
6
16
1
94
5,420
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.
As a backend developer , do you know the difference between Optimistic and Pessimistic Locking ?
3
7
106
6,154
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.
54
88
11
1,380
103,332
B E N retweeted
He thought stonebwoy how to freestyle. Nyame b3tua Alidu ka😂
24
98
5
1,102
11,066
1GAD Go Make U Feel Alive When Listening To His Lyrics 🤍🙏 #BhimFestAtOvoArena #BhimVibez
5
80
2
573
4,592