Stephen Okon

Software Engineer @iklassafrica | Researcher | Gospel_Pianist

[Stephen Okon @stevestack_]

@benhenry01 It’s quite sad it has fallen to this level.

[Stephen Okon @stevestack_]

@WhatsApp @WhatsApp What is the issue with this incessant banning of my account?? I haven’t spammed on your app! There should be a better way for you to fix this mess, other than your automated system giving your users a very poor experience. Pls fix this, I need my account back.

[Stephen Okon @stevestack_]

@MugabeAugust1ne @WhatsApp @FCHWPO @BukayoSaka87 This is absolutely shameful from WhatsApp

[Dr. Gbenga Olowoye @GOlowoye]

Welcome to IKLASS AFRICA Virtual School! https://t.co/m9lcg4tCBk via @YouTube

[Salesforce Developers @SalesforceDevs]

Any frontend. Any experience. Powered by MCP. ⚡

Join @PhilippeOzil for the @Salesforce Headless 360 workshop and get hands-on as you build headless, agent-ready experiences using APIs and MCP tools.

🗓️ August 5 at 10:00 a.m. EDT
🔗 Save your spot today: https://t.co/OV5cJ9K8Db

[Salesforce @salesforce]

Most AI agents: great at finishing tasks, terrible at telling you if any of it matters.

“Loop engineering” gives an agent a goal and a way to measure progress, so it can plan, evaluate its work, learn, and adjust. When it works, an agent can complete more tasks on its own.

But a task isn’t a business outcome. More closed tickets won’t tell you whether you built a better product or sold more of it. The metrics can look great while the result that matters goes unmeasured.

The next frontier is aiming those loops at shared business outcomes—with sales, service, and marketing working toward the same goal instead of optimizing in separate corners.

That only works if you can measure the outcome. And most companies already can. Years of pipeline stages, service levels, and lead definitions are sitting in their systems.

You don’t need a new scoreboard. The business already is one. Your agents just need to learn against it.

[Stephen Okon @stevestack_]

@godofproducts Those guys are balling well

[Stephen Okon @stevestack_]

@PrevitOne @TheHindsightPod You said it quite well 💯

[DogeDesigner @cb_doge]

Elon Musk’s message to young entrepreneurs:

"Try to be as useful as possible. I think if you aspire to do true work, your probability of success is much higher. Do whatever it takes to succeed. Smash your ego, be humble. It's a super big deal."

[The General @1776General_]

@elonmusk Then we have to send all the INVADERS home to build up their own countries.

[Khairallah AL-Awady @eng_khairallah1]

🚨 Anthropic's own team just showed how to actually prompt Claude.

24 minutes. free. from the people who built it.

watch the workshop. bookmark it.

worth more than every $300 course you almost bought.

you've been using Claude without knowing 40 of its prompts.

Then read the guide below.

[Stephen Okon @stevestack_]

Tools can speed you up, but never gonna replace execution.
One week from idea to live usage is wild. @FOjebiyi 👏

[FO @FOjebiyi]

Hi guys, I built an open-source alternative to @pewbeam_ai in one week.

https://t.co/WwyVRtv8H3
Started coding during a Sunday church service. By the following Sunday, we were using it live during our church service. Wild.
Here's what Rhema does: it listens to your pastor's sermon in real-time, detects Bible verse references as they're mentioned, and displays them on screen instantly. No manual clicking, no dedicated slide operator needed.
The tech stack:
- Tauri 2.0 with a Rust backend handling all the heavy lifting: audio capture, transcription pipeline, verse detection logic, and system tray integration
- Local AI embeddings using Qwen3-0.6B so everything runs on-device with zero cloud dependency. Your sermons never leave your machine
- Real-time audio transcription paired with semantic search against a full Bible verse database

The Rust backend was a deliberate choice. We needed low latency audio processing and efficient memory usage for running an embedding model locally, and Rust delivers on both.

Is it perfect? Probably not. But the core functionality works and we're already using it in a real church environment

This is where you come in. Rhema is fully open source and we need contributors to help take it to the next level. Whether it's improving the verse detection accuracy, adding multi-language support, building a better overlay UI, adding support for more Bible translations, or optimizing the transcription pipeline, there's real work to be done and real impact to be made.
If you're a Rust developer, a frontend engineer, an ML enthusiast, or just someone who loves building tools for the church, come build with us.
Star the repo. Fork it. Open a PR. Let's make this the go-to open-source solution for live Bible verse display in churches worldwide.
https://t.co/WwyVRtv8H3

[Mari @Tech_girl]

Dear recruiters, if your requirements include:
Java, Python, PHP, JavaScript
React, Angular, Next, Node js
PostgreSQL, Redis, MongoDB
AWS (S3, EC2, ECS, EKS)
Linux system administration
Git, CI/CD, and TDD
Docker and Kubernetes

You’re not hiring a Full Stack Developer.
You’re hiring an entire IT department.

[Stephen Okon @stevestack_]

@ejirocodes Miracles happen…wdym??😏

[SumitM @SumitM_X]

As a frontend engineer.

Please learn:

- JavaScript/TypeScript

- Responsive Design (CSS, Flexbox, Grid)

- Performance Optimization (lazy loading, code splitting, tree shaking, memoization)

- Web Security (CORS, XSS, CSRF,Content Security Policy, Secure Cookies)

- Testing (Jest, Cypress, Enzyme)

- Build Tools (Webpack, Vite, Babel)

- Version Control (Git)

- Browser DevTools & Debugging

- Accessibility (WCAG standards)

- Progressive Web Apps (PWA)

- Component Architecture (Atomic Design, Higher-Order Components)

- Micro Frontends

- API Integration (REST, GraphQL, WebSockets)

- Testing Strategies (Unit, Integration, End-to-End)

- CI/CD for Frontend (automated builds, deployments)

- Browser Rendering & DOM Optimization

- WebAssembly (Wasm)

- UX/UI Design Collaboration

- Accessibility Audits (ARIA, screen readers)

- State Management (Redux, MobX)

- Frontend Framework Internals (eg: React Fiber for React, Angular Ivy for Angular)

Pick up a framework/library..

Stop jumping from one framework to the other

[Pelumi Isola | Software Engineer @softwareengng]

@mrchidipascal 😂😂😂 and for those assigning task don’t assign tasks in such a way 4 developers will edit a function

[The Tech Prophet (Amospikins) @Amospikins]

How Developers Fix CORS Error With Vibes… And Open Their Backend to the World

[Stephen Okon @stevestack_]

@ejirocodes Hacker harvester

[Stephen Okon @stevestack_]

@Cloudflare Thought as much after some troubleshooting 🤦‍♂️

[Stephen Okon @stevestack_]

@ejirocodes Very insightful as always! 💡