❕

Advice for entry-level software engineers: Focus on understanding how computers work. Learn how they transmit, process, and store data. Fundamentals are more important than the latest frameworks. Right now, AI can generate code, but it cannot solve the problem for you. To effectively instruct the tool, you must understand the building blocks. 1. Start with Networking. Don't just verify that an API works. Understand how the data gets there. - HTTP/HTTPS: Learn the request lifecycle. - DNS: How names become IP addresses. - TCP vs. UDP: Reliability vs. Speed. If you don't understand the transport, you can't debug the latency. 2. Master the Operating System, specifically Linux. Most of the cloud runs on Linux. You need to be comfortable in the terminal. - File Systems: Everything is a file. - Process Management: How programs start, run, and die. - Memory Management: Stack vs. Heap. All code needs an OS to run. 3. Understand Data Structures (and when to use them). This isn't about passing interview tests; it's about performance. - Know why a Hash Map is faster than an Array for lookups. - Understand Big O notation to predict how your code behaves as user traffic grows. Inefficient code costs money. 4. Deep dive into Databases. Storing data is easy; retrieving it quickly is the hard part. - Indexing: How to make queries fast. - ACID: Understanding transaction integrity. - Normalization: How to structure data to avoid redundancy. Bad schema design creates tech debt that is painful to fix later. The best engineers I know aren't the ones who know every syntax of a new language. They are the ones who can understand systems thinking & can visualize the path of a byte from the user's click to the hard drive and back. “Vision without systems thinking ends up painting lovely pictures of the future with no deep understanding of the forces that must be mastered to move from here to there. — Peter Senge, The Fifth Discipline (Currency)” Focus on the mechanics, and the tools will make sense. Happy New Year, May the force be with you!

Quick update on what I’ve built so far: Started with the app side first — I’ll move into the AI part after this. - Built out 6 main components, and added 4 stage types (you can see them in the video) - You can rearrange everything in the scene objects panel - Added 3 views: top, front, and a full walkthrough Still shaping up nicely.

Nigeria as a whole needs a lot more activity and interest based third spaces for children and adults. Our tendency to turn everything in into a mini Owambe is because we have nothing doing. Just hustling to death and then showing off.

Don’t be embarrassed to ask for help. We all need a helping hand sometimes

Stop drawing flat ❌

My church has been planning an event, and I was trying to mock up the sound setup. Then I realized… the media and lighting guys needed the same thing too. We were all basically trying to visualize the same setup, just from different angles. Somewhere between moving speakers around for the third time and guessing where lights should go, it hit me. Why not just type what you want and get a full event setup? So I started building a tool where you can prompt your event setup, adjust things, and even see it in 3D. Still early, but this might actually be useful. Why not just type what you want and get a full event setup? And yes, you can make changes by moving elements around. So I started building a tool where you can prompt your event setup, adjust things, and even see it in 3D. Still early, but this might actually be useful.