Abayomi Sunday Gabriel (@DynamoIntel) header
Abayomi Sunday Gabriel (@DynamoIntel) profile picture

Software Engineer building adaptive web and AI systems | On the road to XR | Building in Public

Minna, Niger state Nigeria
Joined February 2022
Photo by Abayomi Sunday Gabriel (@DynamoIntel)Photo by Abayomi Sunday Gabriel (@DynamoIntel)Photo by Abayomi Sunday Gabriel (@DynamoIntel)Photo by Abayomi Sunday Gabriel (@DynamoIntel)Photo by Abayomi Sunday Gabriel (@DynamoIntel)Photo by Abayomi Sunday Gabriel (@DynamoIntel)Photo by Abayomi Sunday Gabriel (@DynamoIntel)Photo by Abayomi Sunday Gabriel (@DynamoIntel)Photo by Abayomi Sunday Gabriel (@DynamoIntel)Photo by Abayomi Sunday Gabriel (@DynamoIntel)
I'm on a 90-day journey into C++ and spatial audio. I'll be sharing what I learn along the way. Let's see where this takes me. @X
2
1
3
46
10 songs. 2 pipelines. 1 week of melody extraction. The biggest discovery? basic-pitch transcribes the entire mix, not the melody. Spike done. Lesson learned. Time to build. 馃幎 @X @NoDAW_Studio #devcenterhacktobersprint
1
1
64
Finished my initial spike test, where I got audio source separation working. This shows that the core concept of my project is viable and doable Curious about the project? Ask in the comment section 馃憞 #BuildInPublic #hackathon @X
2
1
98
AI can 10x your development speed, no doubt, but only if you actually know how to use it. Using AI tools with shaky coding fundamentals is like putting a Nitro on a tricycle. You'll move faster, but you're probably going to crash somewhere 馃憞
1
44
The problem is not really about crashing or not, because everyone will eventually crash down the road. When you deeply understand the fundamentals, you aren't just helping yourself debug. You're giving the AI the exact context it needs to 10x.
1
34
Change a single button, break the entire application. That's what happens when you skip the architectural phase to chase visible progress on day one.
1
1
31
I learned this while building the frontend for a CEX platform. I spent time mapping flows, locking down the design system, and analyzing edge cases before they became bugs. It felt like no progress. It was the most important work I did on that project.
1
22
If skipped, small changes stop being small. A simple update turns into touching multiple unrelated parts of the codebase because the system was never properly thought through from the start. Slow down at the start. The rest moves faster because of it.
10
What if the problem with AI proctoring isn't the tech but the question it starts with? Most systems ask: "How do we catch cheaters?" What if we instead asked: "How do we design assessments where real understanding can't hide?"
1
22
Most AI proctoring systems treat students like suspects. A trust-first system treats them like participants responsible for proving their own understanding.
1
9
This is the question I'm asking while building my own AI proctoring system. The real question is: can we build assessments where cheating becomes pointless? Where would you start? #EdTech #AIProctoring #RemoteLearning #SoftwareEngineering #BuildingInPublic
13
Your code starts feeling like someone else is doing the thinking. You're no longer the pilot, you're just the person watching the flight recorder.
1
21
Software is an act of intention, not a series of lucky prompts. It's time to put the engineer back in software engineering. #SoftwareEngineering #BuildingInPublic #AITools #WebDevelopment #DevLife
2
18
Are you still the architect of your own codebase or just its editor?
13