Update: I actually finished it. 🚀 No more scrolling through hundreds of pages of this semester's GST test compilation just to practice. I turned it into a simple practice app with explanations, so I can revise a lot faster. It's based on this semester's GST test compilation, so if that's what you're already using to prepare, this should make your life much easier. It's currently available for 200-level students. If you want one for your level, just send me a DM. 🔗 gstpractice-xi.vercel.app/

Who remembers the time we used classes for components in Reactjs rather than functional components? Good old days😔

Slop?? What if he wants to make I general icon revamp through out his application , so you want him to start editing those classes throughout his application. With this approach he only needs to edit it once here and that’s all. Calling someone’s code slop without thinking deeply about the reason behind that decision. What he demonstrated here is code reusability , it makes his frontend uniform and makes life easy for anyone that would be working on that codebase later in the future.

What I did today as a software engineer: Implemented Google OAuth on EvexAI Pushed it to deployment and got it live Continued building my Dart CLI application and worked more on OOP. Also spent some time on NeetCode learning Dynamic Arrays and Prefix Sums. And outside of coding, I read another chapter of No Excuses Nothing crazy. Just trying to get a little better every day.

We started Qademy to solve problems we had as students. But the more we build, the more we realize it can be much bigger than that. I’ve been working with my partner to take Qademy beyond just an information and resource management tool for departments. We’re making studying with AI more accessible to students — inclusion is a big part of this. Your course materials are understood by our system. No more “you are out of uploads.” Large materials can be broken down into chapters, with brief and detailed summaries. You can test yourself based on any material uploaded to your department. We’re also introducing Theory Practice — where you’re tested and scored based on the actual material you’re studying. Your lecturer’s keywords. Your course material. What you’re actually expected to know. Not some generic AI-generated curriculum. We’re building this from our experience as students and trying to solve problems we actually face. Still a lot more to build, but Qademy is becoming much more than what we initially imagined. 🚀

Someone’s about to get laid off 😭

I’ve completed my 200 Level, and I’m currently seeking an internship placement as part of my Computer Science degree. I’d love the opportunity to intern with @BluechipTechNG or @dsn_ai_network , contribute to your teams, and gain practical industry experience. I had the opportunity to participate in the DSN AI Summit Hackathon, where my team, PulseAgent, placed 3rd🥉🏆 If there’s an internship opportunity available, I’d be grateful to be considered. And if anyone else has an internship opportunity for a Computer Science student, I’d really appreciate a referral or introduction. 🙏🏽

$0

😂 New quest: Get all 4/4 Currently at 1.5/4 Mental stability + a partially functioning social life. 2.5 more levels to unlock 💀

Once I’m done with these exams, I’m planning to use the holiday to go deeper into backend engineering. I already have experience building backend systems, but there’s still so much more to learn when it comes to building systems that are scalable, performant, secure, and reliable. I’m also thinking about picking up another backend language alongside the stack I already use. I currently have Go and Java in mind, but I’m open to suggestions. I also have an exciting project I’ve been thinking about lately, and I’m hoping to use what I learn to build it. I’ll share more about it on X when the time is right. For the backend engineers here, what concepts or technologies do you think I should explore?

A little ask to founders, CTOs, and hiring managers. I'm currently looking for a 3-month SIWES internship (a requirement for my Computer Science degree). I work primarily with TypeScript, Python , Node.js/NestJS, React/Next.js, React Native, PostgreSQL, AWS, and AI If your team is taking interns , or you know one that is , I’d really appreciate a referral or introduction. My DMs are open. Reposts are appreciated. 🙏

This week has been one of the craziest I've had in a while. While building the GST Practice app, I also had to take a Java test, I'm writing a Concurrent Programming test on Thursday, and I have a GST exam on Friday. Balancing development with university hasn't been easy, but one thing has surprised me: the app has actually become one of my best study tools. I find myself practicing GST questions on the road, while waiting for classes, or whenever I have a few free minutes. Instead of carrying around bulky test compilations or trying to remember where I stopped, I just open the app and keep practicing. It's funny how building a solution for other students ended up solving my own problem too. Back to studying... and back to shipping. 🚀

I have my GST exams coming up in less than a week.. The funny part? I haven’t even read the materials once. 💀 There are about 15 long PDFs filled with philosophy and a lot of text waiting for me. Instead of panicking and trying to brute-force everything, I started thinking: "Can I build something that helps me understand and study this faster?" So that’s what I’m working on now. Turning my exam problem into a project. Hopefully I finish it before tomorrow… because I still have an exam to prepare for. 😂

One thing about applying for software engineering jobs... The silence is brutal. At first I used to wonder, "How hard is it to send a rejection email?" Then I thought about it. Imagine you're hiring one engineer and 1,000 people apply. You shortlist 20. Would you actually send 980 rejection emails? Probably not. As an applicant, it still hurts because you're left refreshing your inbox, hoping for a response. But seeing it from both sides made me realize the problem isn't always a lack of courtesy , sometimes it's just the scale of hiring. What's your take? Should companies always send rejection emails?

One mistake can undo hours of good work. We had just released what we thought was a small update and told people to start downloading it. The new features worked perfectly... But we forgot to test the onboarding flow. New users couldn't register. The panic was real. 😅 My cofounder and I dropped everything, found the issue, and pushed another update as quickly as we could. That experience changed how we ship software. No matter how small an update is, we never skip testing the core user journeys. Sometimes the biggest bugs aren't in the new feature, they're in the parts you assumed would keep working.