Captain-EO 👨🏾‍💻

16.9K posts

Captain-EO 👨🏾‍💻 banner
Captain-EO 👨🏾‍💻

Captain-EO 👨🏾‍💻

@EOEboh

SWE (JS & Go) • Software & AI systems • Sports fan • https://t.co/iWA1BA95MC

Katılım Mart 2020
1.1K Takip Edilen18K Takipçiler
Shams Charania
Shams Charania@ShamsCharania·
Just in: Detroit Pistons star Cade Cunningham has been diagnosed with a collapsed lung and is expected to miss an extended period of time, sources tell ESPN.
Shams Charania tweet media
English
5.5K
7.7K
91.2K
11.9M
Captain-EO 👨🏾‍💻
As a developer, have you ever wondered: Google Maps tells you there's traffic ahead in real time There are no sensors on the road So how does it know?
English
268
42
2.3K
1.1M
Camila
Camila@AiCamila_·
@EOEboh You don’t notice bad security… until attackers do 💀🔥
English
1
0
2
353
Captain-EO 👨🏾‍💻
API security checklist most devs skip in production: - HTTPS enforced on all endpoints - JWT expiry set appropriately - Rate limiting on auth endpoints - Passwords hashed with bcrypt/argon2 - 401 vs 403 used correctly - Input validated and sanitized - Refresh tokens rotated on use Save this 🔖
English
4
17
189
7K
Cool Fellow
Cool Fellow@SuDevelopers·
@EOEboh And there's me who dey paste 403 for everything, just like I paste 200 for all success. 🤣
English
1
0
0
1.7K
Captain-EO 👨🏾‍💻
Most devs return a 403 when a user isn't logged in. Do you know the difference between 401 and 403?
English
23
2
116
28.2K
Sid
Sid@SidJain_80·
@EOEboh 401 Unauthorized “I don’t know who you are.” 403 Forbidden “I know who you are, but you can’t do this.”
English
4
3
44
3.1K
Vance The Conqueror 🌎
Vance The Conqueror 🌎@VanceBillions·
@EOEboh Which is bad practice. 403 simply means, “we know who you are but you can’t enter here” while a 401 is “we don’t know you from Adam” 😅
English
1
0
4
2.5K
Benita Mbulu
Benita Mbulu@benitambulu_·
Is consistency really enough to succeed in tech, or is there more to it?
English
70
2
68
3.6K
Captain-EO 👨🏾‍💻 retweetledi
Akintola Steve
Akintola Steve@Akintola_steve·
My uncle used to say, “Money has a spirit. If you don’t respect it, it will embarrass you.” I didn’t understand what he meant… until I watched a Lagos founder almost lose his entire business over payments. This story will change how you see “Pay Now” forever. Bookmark this. Retweet it. You’ll come back to it.
English
13
22
95
4.7K
Akintola Steve
Akintola Steve@Akintola_steve·
@EOEboh Exactly 👍🏾 I’m dropping a detailed thread by 11:45AM on payment systems please I’ll really appreciate it if you can engage with it via a retweet too
English
1
0
1
144
Captain-EO 👨🏾‍💻
You're redesigning a public API that 10,000 developers already use. You need to make breaking changes. How do you do it without destroying everyone's integration?
English
19
5
78
19.2K
Synaptica
Synaptica@SynapticaTech·
Version the API properly — that's the only safe way. Keep v1 running indefinitely (or long sunset period: 12–24 months) Launch v2 at /v2/... with breaking changes Update docs clearly: "v1 deprecated — migrate to v2 by [date]" Add deprecation headers (Deprecation: true, Sunset: 2027-06-01) Use feature flags for soft transitions We did this for agent APIs — zero integrations broke. You ever had to break an API with users? How did you handle it?
English
2
0
3
1.6K
Akintola Steve
Akintola Steve@Akintola_steve·
@EOEboh Implement Semantic Versioning (SemVer) and side-by-side deployments. I’d keep V1 active while launching V2, then use 'Deprecation' headers in V1 responses to warn developers to migrate before the eventual sunset.
English
1
0
22
1.5K
Captain-EO 👨🏾‍💻 retweetledi
Akintola Steve
Akintola Steve@Akintola_steve·
Posting between 11:45 AM and 3:00 PM (WAT) allows your post to reach both Nigerian and US audiences. While it’s around 3:00 AM to 6:00 AM in the US, early risers and global teams will catch it. However, if you are aiming specifically for a Nigerian audience, 11:45 AM is a 'sweet spot' because people at work are preparing for their lunch break and will almost certainly be checking their phones
Captain-EO 👨🏾‍💻@EOEboh

9 am on a Tuesday morning

English
3
3
51
2K