Bits and Pieces Part 5: Not Like Us

I stared blankly at my screen in utter disbelief for 5 minutes, like I just heard I broke a bottle of champagne at Quillox. The jokes write themselves in indignation, It's a sore for eyes. These Bits and Pieces can’t be coupled by the far-sighted. Of course they can’t. These stories of code, told in the form of epic rants, are someone’s travail. But that doesn’t compute for most.Of course its 12:29AM, and It struck me that I'm not being heard.For the record there are no rules, only a room of cluttered ideas but perfect lighting to say it in. False advertising I need to distract myself, easy enough except I need an idea.…I'm little intoxicated, I'm not gonna lie. So, what? It's not even 4am and its a Friday night.TwoCents is open. Black background, white text. Looks like a platform for thinkers. Feels like a graveyard for approval-seekers.Microsoft Word? Closed. I don’t need formatting. I need momentum. This is shipping, not literature.something has kicked in.. Last i stopped in bits and pieces we were able to build an middle man that tells the database to basically add a new classroom that our users will create. What gives this middle man power, I wonder... From my observation, It's obvious the user fills a form to create a classroom, that form is coming from the frontend (the nice little input form you fill while applying for project fame). JavaScript. The backend (the judges) can’t understand it natively; it’s not psychic. So when you fill a form, we call that the body (… still your form, but in backend language its called body). And what do we do with a body? We break it down. Dissect it. Map it. That body (remember still your form) could have three fields. Or two. Depends on how many questions you force your users to answer before they can do anything useful.For me? Just one.Name.Straight to the point. Saves everybody time. While we’re waiting for that request, we run a parallel function, that function tells our database to do what databases do: create and store. But not blindly. We run checks.We verify the data.We ask: is the user even allowed to create a classroom? Like... you’re not logged in. You’re not a user. Why the hell are you trying to create a classroom?Imagine no auth. Chaos. Now we’ve got a middleman — an API endpoint — that links the frontend to the backend and creates a classroom. Basically, you’re putting a letter in a DHL box, and the backend knows exactly where to send it. Cool.Now I’ve got an idea. See, it’s not the classroom that should populate the explore page where users would like to see me post a tutorial video of how to make methIt’s the content! The person who creates the classroom should be able to post videos or writeups, that’s what we use to populate the rest of the explore page. Not empty shells. So now the real question:Should content be its own table in the database?Or should it belong to the classroom?Or to the user? I’ll sleep on that. But for now, I’m obsessing over this one thing: True mastery is being able to explain even the most grotesque and mighty detail to the simplest mind.If I can do that, I win. Not the trending tab.Not the applause.Not the monthly writing prize. I win the game.

Other insights from Matthew Okadinya

Referral Earning

Points-to-Coupons