Pinned Tweet
Hi , I'm Miracle Nnaji.
I'm a software Developer (specifically Full-stack web dev and blockchain but can learn any new technology).
Actively contributing to open source project, learning and connecting with people all over the world.
Happy to help you build with a fee
Learning Go?
Pick your path:
Go + Gin → Backend APIs
Go + gRPC → Distributed Systems
Go + Kafka → Event-Driven Systems
Go + Kubernetes → Cloud Native
Go + Docker → Containers
Go + Terraform → Infrastructure
Go + Prometheus → Observability
Go + Redis → High-Performance Caching
Go + WebSockets → Real-Time Apps
One language. Countless engineering careers.
I'm building a school ERP for a client, and I just rewired its results engine to grade by the school's real rules instead of a hardcoded pass mark.
So the engine now:
→ Reads CA and exam weights from the class's grading system
→ Looks up grade bands per class, not globally
→ Returns total and grade from the server, never the browser
→ Rolls term results into an annual result with an average
Teachers, managers, students, parents and platform staff each get a distinct permission set.
A Super Admin can open a term for mark entry and lock it again. A Manager can't reopen what Super Admin closed, even with the same permission verbs.
Permissions answer who. Sometimes you need to answer when, and mixing the two is how you get role escalation.
Model entry windows as exam state, enforce them server-side, and never let a role check stand in for a time check.
#Laravel #RBAC #AccessControl
The trickiest authorization problem in the school ERP I'm building for a client wasn't "can this user see students."
It was "can this user change a score right now." 🧵
Best warzone player teapawt.org/i/broadcasts/1wxWjlwYD…
Miracle Nnaji retweeted
I’m fully back on X family, and I’m fully back to Trading 🙂↔️
Get in jhoir 💪
Let’s get the bag 💼 💸
I'm building a school ERP for a client. Their instinct was microservices.
I talked them into a modular monolith, and that call saved months.
At this scale (two schools, ~1,000 students, ~500 users), microservices buy independent deploys you don't need, and charge you in distributed transactions and operational overhead.
Modular boundaries give you the discipline without the network.
Talking a client out of microservices wasn't about being anti-microservices. It was about matching the architecture to the problem.
Laravel 12, PostgreSQL, Redis.
#Laravel #SoftwareArchitecture #EdTech













