God's Grace | React, Next JS, React Native | Frontend Developer(learning never ends🫨) | Tech Enthusiast | Student
Ibadan, Nigeria
Joined September 2013
- Tweets223
- Following351
- Followers99
- Likes7.2K
Ọrẹolúwa retweeted
I promise …. once you realize you’re the one who can help you and it starts with you … life gets good 👍🏼 … pass this on to 3 people who need it or tag @ them in the comments
Ọrẹolúwa retweeted
Meet my 6th @framer Template: Aster Bloom
Aster Bloom is a minimal, editorial portfolio template for art directors and visual artists. Built around bold imagery, refined typography, immersive project pages, and an image-focused archive that lets the work take center stage.
Ọrẹolúwa retweeted
Learning Is Dead, and AI Killed It!
I want you to actually read this. Not skim it, not scroll fast to pick up something to comment onto can move on to the next tweet, actually read it.
I want to talk about the generation effect. Now, I could hand you a definition right now and you'd read through, file it away, and forget it by dinner. Instead I'm going to make you sit with some stories. Because that's the whole point of what I'm about to tell you: the struggle of getting there is the thing that makes it stick.
Ọrẹolúwa retweeted
I'm obsessed with cognitive biases.
A "cognitive bias" is a systematic error in thinking that destroys decision-making.
11 most powerful (and dangerous) cognitive biases I've found: 🧵
1. Survivorship Bias:
Ọrẹolúwa retweeted
Software Engineering 101:
I shared a tweet yesterday as regards how Software engineering isn't Frontend and Backend.
I was surprised at how some people were surprised or saw the tweet as a hot take instead of taking it for the fact that it is.
I later realised that it was just a "curse of knowledge" that made me assume everyone knew this already.
I feel like a lot of boot camps aren't doing enough justice because this is meant to be foundational knowledge and not something you find out after years of being in the tech space!
I spent 1hr trying to come up with the best way to explain this and the best approach is using an analogy to break down what Software Engineering really is and what Frontend and Backend are.
One of the ways I learn to understand and explain anything tech is by using analogies, which is my way of making concepts clearer when related to the real world.
Consider Object-Oriented Programming (OOP), where terms like 'inheritance' can be better understood through real-world analogies. In OOP, inheritance allows an object to acquire properties from another, similar to a child inheriting properties or traits from their parents.
An analogy allows you to simplify tech's gibberish by relating to everyday life.
Let's explore a software system by comparing it to a construction site.
A typical site has various specialists: carpenters, plumbers, bricklayers, painters, labourers, and supervisors. Each has a unique role.
However, a construction project doesn't start spontaneously.
It begins with a client's vision, which is then shaped into a feasible plan by engineers.
This planning stage is crucial, ensuring the project's viability and avoiding future complications.
In software development, a similar process occurs. A project starts with an idea, which software engineers develop into a practical plan. They choose appropriate technologies and tools, similar to selecting materials in construction.
In both fields, some individuals execute these plans.
Bricklayers and carpenters in construction, or front-end and back-end developers in tech, use their tools to create something tangible.
They may not grasp the entire engineering concept but can effectively build based on patterns or instructions.
However, using tools doesn't equate to understanding underlying principles.
A bricklayer might construct a house based on experience without deep engineering knowledge. The house might stand, but its future stability is uncertain.
Similarly, a software developer can build applications using tools and existing code but might lack insight into the broader implications of their work.
In contrast, engineers, whether in construction or software, plan and build with a comprehensive understanding. They consider the broader impact of their decisions, ensuring sustainability and effectiveness.
This distinction is evident in tech roles. Software engineers understand the principles and implications of their work, while developers might focus more on tool usage.
WordPress developers, for instance, use templates and tools to build websites, similar to how a bricklayer uses skills to construct a building.
Project managers and site engineers in construction ensure adherence to plans and quality standards. In software development, similar roles oversee the development process, ensuring best practices and project requirements are met.
With these few points of mine here are my takes:
1. Software Developers are not Software Engineers as to how Bricklayers and Carpenters can't call themselves civil or Architectural Engineers.
2. Frontend and Backend Engineers are Software Engineers who know how to use a Frontend or Backend tool alongside applying Software Engineering Principles to them. The "Engineer" keyword makes the difference.
3. You don't have to be a Frontend Developer or Backend Developer to become a Software Engineer. You don't have to be a Software Engineer to become a Software Developer.
4. Ever wondered why the tools you use for building like node js call the document developers' documentation and your senior engineer at your company gives you guidelines in the form of engineering documentation. It is because you are a developer at that company and not an engineer!
5. Engineers are tool agnostic, meaning they're comfortable with using a variety of tools and also apply engineering principles to them.
6. it's really not a bad thing to be just a software developer, as far as there is an engineering guideline you are following.
7. I also saw someone mention that software engineer and developer can be used interchangeably. My answer is: No they can't.
In the shortest way possible, software engineering principles are guidelines that ensure the development of reliable, efficient, and maintainable software. Key principles include:
1. Modularity: Breaking the system into smaller, independent parts.
2. Abstraction: Focusing on high-level functionality, hiding details.
3. Encapsulation: Bundling data with methods that operate on it.
4. DRY (Don't Repeat Yourself): Avoiding code duplication.
5. KISS (Keep It Simple, Stupid): Simplicity over complexity.
6. YAGNI (You Aren't Gonna Need It): Not adding unnecessary features.
7. SOLID: Five design principles for object-oriented programming.
8. Separation of Concerns: Dividing a program into distinct sections, each with a specific responsibility.
9. Scalability: Designing software to efficiently handle growth.
10. Maintainability: Writing code that is easy to understand and modify.
Thanks for reading, please do well to share by retweeting, so that other people can understand this foundational knowledge.
I will try to answer your questions in the comments 🤌
Ọrẹolúwa retweeted
You need to understand that your first or current career may not be your final one.
Life is a journey, not a straight line.
You’ll evolve. Your interests will shift. Your goals will mature.
And that’s okay.
Don’t box yourself in because of where you started.
Ọrẹolúwa retweeted
Why is it that when women want to insult men, the first thing they strike is his pocket? The quickest blow is “broke.” The sharpest jab is “you’re too poor to afford me.” Not “you’re wicked.” Not “you’re unkind.” Not “you’re emotionally unavailable” or “you’re selfish with affection.” No. The insult always hovers somewhere between his account balance and his ability to sponsor her needs. Why?
And why, on the flip side, do men, when they want to insult a woman, reach first for her body? Her legs. Her past. Her perverse sexual history—or even just the suspicion of one. Words like “whore”, “ashawo”, “hoe”—they’re flung like arrows, not even to correct but to demean. Why?
I’ll tell you.
Because we insult from the lens of what we fear, and what we value.
To a large number of women, a man’s worth has been socially coded as his ability to provide. It’s not always intentional. It’s cultural. It’s systemic. It’s buried in the jokes we grew up laughing at, in the stories we were told, in the silent expectations that formed around us like fog.
So when a woman wants to wound a man, she reaches for his “worth” as the world defines it: his wallet. Because she knows it will sting. Because society told him that without money, he is not a man. And so to call him broke is not just to say he lacks funds—it’s to say he lacks value. That he’s unworthy. That he should shut up and sit down.
And men? They’ve been raised to see a woman’s virtue through the lens of sexual exclusivity. Her purity. Her modesty. Her restraint. Because for generations, a woman’s value was her ability to say no, and say it often.
So when a man wants to bruise a woman—really bruise her—he doesn’t go for her intelligence or her strength. He goes for what he believes is the most fragile part of her: her dignity, her “cleanliness.” To call her a whore is not just to shame her—it’s to tell her that she has nothing left that a man should want.
It’s cowardice on both sides. Lazy, inherited cowardice. We don’t insult each other from a place of originality—we recycle the wounds society has already stitched into our skins.
Women reduce men to ATMs. Men reduce women to hymens. And both pretend it’s power when it’s really just pain. Pain we’ve been taught to dress up as dominance.
And perhaps the saddest part? We’ve done it so often that it now feels normal. Even funny. Even deserved. But it’s not. It’s tragic.
We’re fighting each other with weapons we didn’t forge. And worse—we’re too obsessed with one-upping each other to ever drop them and fashion new insults.
Ọrẹolúwa retweeted
Techies, what’s one thing you wish someone told you before you started?
I’ll go first: You don’t need to know EVERYTHING before you apply for jobs.
Ọrẹolúwa retweeted
Effort is magic. Every drop of sweat, every late night, every moment of dedication, it all adds up. Create your own magic.
Ọrẹolúwa retweeted
You LOVE the smell of GOOD MUSIC, listen to me today 😊
Don't DM
Out NOW!!!
push.fm/fl/WC6CDURU
I just refactored my To-Do List and Calculator projects to TypeScript!😓
I’ve been learning the basics;
- primitive types, arrays, and interfaces.
- typing functions.
I feel so good about the progress I’m making!
github.com/devanike/Todo-Lis…
I’d love to hear your tips!
Thanks😃
1
6
378
It was fun revisiting React today!
I built a Counter App with increment and decrement buttons, and now I’m diving into a To-Do List App where I can add and display tasks. Feels good to get back into it and see my progress!
What do you think I should add to it?
4
229
Took a step back to refresh my JavaScript basics:
Scope, arrays, objects, strings & functions.
Built a simple calculator and solved HackerRank challenges.
Sometimes, revisiting the basics helps you move forward!
What’s your favorite way to practice core skills?
#JavaScript
1
193
Ọrẹolúwa retweeted
The video that changed the game for me.
After that I took LinkedIn seriously and networking seriously.