TMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ

1.6K posts

TMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ banner
TMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ

TMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ

@0xtmb

Christ first โœ๏ธ โ€ข Full Stack Web developer ๐Ÿ’ป โ€ข AI fan ๐Ÿค– โ€ข Exploring Web3 ๐ŸŒ #DawgsOnCaffeine

Web 3 ๊ฐ€์ž…์ผ Nisan 2024
259 ํŒ”๋กœ์ž‰415 ํŒ”๋กœ์›Œ
๊ณ ์ •๋œ ํŠธ์œ—
TMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ
My Cavista Hackathon Experience Part 1: How it all started Cavista Hackathon has always been on our radar. The interesting thing is that a team from our school actually won the previous edition. So when we heard about it again, we felt the pressure in a good way. The goal was simple. Represent our school again and see if we could bring the win home once more. But our team did not start at Cavista. It actually started earlier at the Lagos Impact Hackathon. Three of my teammates attended that one while I could not make it because of some unforeseen circumstances. That was where the foundation of the team was built. At that time, the team name was Centenize. However, when it was time to register for the Cavista Hackathon, we looked at the name again and realized it did not really represent what we wanted. So we decided to rethink it and come up with something better. After some thinking, we chose the name #Nibble. In computing, four bits make one nibble. The idea behind the name was simple. Individually we may just be bits, but when we come together we form something complete and more powerful. That name stuck. Before the hackathon started, we also spent time studying previous Cavista winners and the kind of solutions they built. We wanted to understand the level of the competition before stepping in. Luckily, everyone who registered from our side was available, and we were also able to add one more teammate to strengthen the squad. With the team set and the mission clear, we were ready to represent our school. Part 2 will be about how we came up with the project idea and how the project itself got its name.
TMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ tweet mediaTMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ tweet media
English
7
6
24
441
TMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ ๋ฆฌํŠธ์œ—ํ•จ
Marvelg | UI/UX Designer in Training
Marvelg | UI/UX Designer in Training@designbymarvelgยท
Small progress here... tried to recreate Facebook. Looking back now, the alignment is 'doing me somehow,' but we move! ๐Ÿ“ˆ #DesignInspiration #figma #uiux
Marvelg | UI/UX Designer in Training tweet mediaMarvelg | UI/UX Designer in Training tweet media
English
0
1
9
31
TMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ ๋ฆฌํŠธ์œ—ํ•จ
Marvelg | UI/UX Designer in Training
Marvelg | UI/UX Designer in Training@designbymarvelgยท
Day 1: Learning what a 'Frame' is. Everything was a bit chunky, but the excitement was real! ๐Ÿš€
Marvelg | UI/UX Designer in Training tweet mediaMarvelg | UI/UX Designer in Training tweet media
English
2
2
8
44
Technical Ben
Technical Ben@TechnicalBbenยท
Last man standing ๐Ÿค—๐Ÿค—
English
47
2
102
2.2K
TMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ ๋ฆฌํŠธ์œ—ํ•จ
IBMSSP
IBMSSP@ibmssp_ngยท
Eid Mubarak. As we celebrate Eid al-fitr, may this season inspire discipline, purpose, and renewed commitment to excellence in all we do. Strong values build strong systems. #EidMubarak #Leadership #BusinessStandards #ProfessionalExcellence
IBMSSP tweet media
English
0
3
5
26
Casper
Casper@CasperOnChainยท
@0xtmb Rise and grind โ˜•๏ธ
English
1
0
1
12
TMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ ๋ฆฌํŠธ์œ—ํ•จ
IBMSSP
IBMSSP@ibmssp_ngยท
Daily Insight Professional excellence does not happen by accident. It is built through discipline, standards, and continuous improvement. #ManagementSystems #ProfessionalDevelopment
IBMSSP tweet media
English
0
3
6
30
TMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ
TMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ@0xtmb

My Cavista Hackathon Experience Part 1: How it all started Cavista Hackathon has always been on our radar. The interesting thing is that a team from our school actually won the previous edition. So when we heard about it again, we felt the pressure in a good way. The goal was simple. Represent our school again and see if we could bring the win home once more. But our team did not start at Cavista. It actually started earlier at the Lagos Impact Hackathon. Three of my teammates attended that one while I could not make it because of some unforeseen circumstances. That was where the foundation of the team was built. At that time, the team name was Centenize. However, when it was time to register for the Cavista Hackathon, we looked at the name again and realized it did not really represent what we wanted. So we decided to rethink it and come up with something better. After some thinking, we chose the name #Nibble. In computing, four bits make one nibble. The idea behind the name was simple. Individually we may just be bits, but when we come together we form something complete and more powerful. That name stuck. Before the hackathon started, we also spent time studying previous Cavista winners and the kind of solutions they built. We wanted to understand the level of the competition before stepping in. Luckily, everyone who registered from our side was available, and we were also able to add one more teammate to strengthen the squad. With the team set and the mission clear, we were ready to represent our school. Part 2 will be about how we came up with the project idea and how the project itself got its name.

ZXX
0
0
2
15
TMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ
My Cavista Hackathon Experience Part 3: The build, the bugs, and the breakthrough Once the idea was clear, it was time to build. We had 24 hours. I worked on the front end with @muq_techh, while @olamzyweb and @1212Damilare handled the back end. Maxwell also prepared the slide deck in case we made the Top 10. The front end came together quickly. In about four hours we had the onboarding, language selection, and core interface ready with the help of AI tools. While I was building the interface, the backend was also coming together smoothly. Then the real problems started. First, translation. Text translation worked, but speech translation had issues. Most AI models pronounced Nigerian languages with English intonation, like someone trying to speak Yoruba with an American accent. That clearly would not work for what we wanted. Then around 2 a.m., a bigger problem hit. Our backend server went down. At first we thought it was a front end issue because we kept seeing timeout errors. But after checking everything, we realized the backend server itself was the problem. So we had to quickly redeploy everything to another server. That process alone took about 45 minutes, but once it came back up, everything started working again. For the voice system, we remembered YarnGPT.ai, an AI model built by a student of Unilag that handles Nigerian languages with proper Nigerian intonation. We connected the API and it worked, but the responses were slow. The text would appear before the audio finished loading. So we kept adjusting, fixing delays, debugging APIs, and solving small issues one after another. Luckily, because we built most of the core system early, we still had time to fix bugs. By 4 p.m., most things were stable. The slides were ready, the system was deployed, and the project was ready to be submitted We eventually submitted everything about 2hrs before the deadline and even after submitting, we were still fixing small bugs here and there. Then came the judging. When they started announcing the Top 10, our team #Nibble was called towards the end of the top ten teams. We actually had the confidence that if only we could get to the stage, we would kill it. And in the end, we finished 3rd place - second runner up, representing @realLasustech. Even more interesting, about three LASUSTECH teams made the Top 10. For us, that moment made the entire sleepless build worth it. Next: what the experience really taught me.
TMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ tweet mediaTMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ tweet mediaTMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ tweet mediaTMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ tweet media
English
1
1
9
50
TMB ๐Ÿ™‚โ€โ†”๏ธ๐ŸŸฆโœ๏ธ ๋ฆฌํŠธ์œ—ํ•จ
Zinny ๐ŸŽ€
Zinny ๐ŸŽ€@Zinny_Edmundยท
This never found or solved any problems.
Zinny ๐ŸŽ€ tweet media
Enugu, Nigeria ๐Ÿ‡ณ๐Ÿ‡ฌ English
7
3
17
256