TripleA
@Triple123A
Followers
383
Following
325
Media
35
Statuses
817
Developer Advocate | Software Engineer | React JS | Next Js | JavaScript | Typescript | HTML | CSS | Tailwind CSS | Software development tips | HNGx Finalist
Joined February 2022
RT @dxmentorship: Excited to announce DxMentorship is giving away 5 FREE tickets to tomorrow’s DevRel Meetup + Unconference by @thedevrelca….
0
12
0
RT @kenny_io: We just wrapped up the 4th Cohort of the @dxmentorship program!! Super excited for everyone graduating today 🎉🔥 https://t.co/….
0
13
0
RT @osca_hq: Join the #OSCAFest25 team! 🚀.We’re looking for passionate frontend volunteers to help build for OSCA Festival 2025. Got skill….
docs.google.com
Would you like to contribute to Open Source Community Africa Festival 2025 as an engineer?
0
47
0
Here I am cooking with @dxmentorship co-members.
Meet the amazing people who have contributed to the Developer Relations Knowledge Base @dxmentorship . We appreciate everyone who has shared their expertise and insights!. Check the list :).
0
0
0
TL;DR:. env in frontend != secure.If it's used in the browser, it's exposed. 👉 Use .env correctly.👉 Don’t trust it blindly.👉 Backend is where secrets belong. Some developers still assume .env = secure. It's not unless you're using it correctly.
0
0
0
What should you do instead?. ✅ Keep sensitive keys on the backend.✅ Use API routes or serverless functions.✅ Only expose what's absolutely necessary to the browser. Frontend .env is not private it's public by design.
1
0
0
Why is this dangerous?. Because leaked frontend API keys can be:. – Abused to bypass usage limits.– Used to impersonate your app.– Exploited for billing abuse. And you'll be the one paying the price 💸.
1
0
0
Those "secret" keys?.They're public. ✅ Open DevTools.✅ Go to Network or Sources.✅ Boom your keys are there for everyone to see. Even if you didn't push your .env to GitHub,.your frontend is still exposing them.
1
0
0
"If I put my API keys in .env, I'm safe.". 🚨 Wrong at least on the frontend. In frameworks like React, Vue, or Vite, .env variables with VITE_ / NEXT_PUBLIC_ are bundled into the browser. Which means… 👇.
1
0
0
Been hearing this a lot:. "Don't push your .env to GitHub.".Cool. ��. But no one talks about the real problem:.Using .env in the frontend and thinking it's secure. Here's what devs get wrong 🧵👇.
1
1
0
Happy birthday to you @kenny_io, thanks for the support and training 💪 more years to come.
Happy Birthday to our amazing founder, @kenny_io. You’ve been the backboneof this entire journey — showing up, guiding us, and pushing the vision forward. We’re super grateful for all you do and can’t wait to see everything you’ll build next.
0
0
0
Proud to officially represent @torcdotdev as an ambassador! As a platform that merges innovation with community, Torc is redefining how top developers connect with global opportunities. Can’t wait to share some exciting updates with my network. #TorcAmbassador #TeamTorc
0
0
3
RT @torcdotdev: 🚀 Dev communities thrive on authenticity & engagement!. @TessaMero & @msbrianaholmes share key insights on building strong….
0
3
0
This blog post is a repurposed version of a video guide by @dennisivy11 on using Appwrite MCP with Claude. I added step-by-step breakdowns + practical examples using `cursor` to make it even more dev-friendly. Read here: .
0
0
0
I have applied for the Developer Relations internship at Appwrite, and I have included my article as a work sample in my resume. I am looking forward to a positive outcome! 😀.
2
0
1
If you’re hiring in DevRel especially at @Appwrite and looking for someone who codes, writes, edits, and cares deeply about developer education…. Let’s chat 🫱🏽🫲🏽.
2
0
0
Shoutout to:.💡 @TessaMero for the motivation during #DxMentorship.📢 @dennisivy11 for always sharing awesome dev opportunities. Y’all inspire the community more than you know 🙌.
1
0
1
Why go this far?. Because I genuinely believe in open-source education — and Appwrite makes backend dev easier for everyone. This is my way of showing value, not just saying it.
1
0
0