Irem πŸ’» (@eniola_merem) header
Irem πŸ’» (@eniola_merem) profile picture

Frontend & Mobile Engineer(React, React Native, TypeScript) β€’ Building products people actually finish onboarding β€’ πŸ“§ [email protected]

Excellence
Joined April 2022
Photo by Irem πŸ’» (@eniola_merem)Photo by Irem πŸ’» (@eniola_merem)Photo by Irem πŸ’» (@eniola_merem)Photo by Irem πŸ’» (@eniola_merem)Photo by Irem πŸ’» (@eniola_merem)Photo by Irem πŸ’» (@eniola_merem)Photo by Irem πŸ’» (@eniola_merem)Photo by Irem πŸ’» (@eniola_merem)Photo by Irem πŸ’» (@eniola_merem)Photo by Irem πŸ’» (@eniola_merem)
Hi, I’m Eniola. I build web & mobile apps for startups. Simple where it should be. Scalable where it matters. Here’s what I’ve learned (and what you’ll learn here): 🧡
18
15
1
142
3,358
Irem πŸ’» retweeted
To everyone currently sitting on an idea: What's stopping you from starting? Is it time, confidence, technical skills, resources, or simply not knowing where to begin? Let's talk about it. Someone in this community might have a helpful perspective.
2
1
13
167
Irem πŸ’» retweeted
I thought it would be interesting to document what being a SCRUM Master actually looks like, how I'm approaching the work, and what I'm learning along the way. Here's a little breakdown of my responsibilities. πŸ§΅πŸ‘‡
Well, guess who's been nominated as Scrum Master for a group project? Looks like I'll be putting my coordination, communication and team management skills to the test. Let's see how this goes. Time to practise what I've been learning πŸ₯‚
3
15
227
I thought it would be interesting to document what being a SCRUM Master actually looks like, how I'm approaching the work, and what I'm learning along the way. Here's a little breakdown of my responsibilities. πŸ§΅πŸ‘‡
Well, guess who's been nominated as Scrum Master for a group project? Looks like I'll be putting my coordination, communication and team management skills to the test. Let's see how this goes. Time to practise what I've been learning πŸ₯‚
3
15
227
4/4 β€” Delivery, communication and continuous improvement Ultimately, the goal is to get the product delivered. I'll be paying attention to: β†’ Whether we're meeting our agreed milestones. β†’ Whether the deliverables meet the requirements. β†’ How well the different teams are collaborating. β†’ What needs to be adjusted when things don't go as planned. β†’ What we can learn and improve throughout the process.
1
1
6
One thing I'm learning already is that managing a technical project requires more than knowing the terminology. You need to understand people, processes, technology, priorities and trade-offs. I'm excited to put what I've been learning into practice, make mistakes, learn from the team and become better at this. Let's see how this journey goes!πŸ₯‚
1
5
Irem πŸ’» retweeted
To the men who build,lead,debug, design and carry teams: Happy International Men's Day. #internationalmensday#elyonlabs
2
8
15
167
To everyone currently sitting on an idea: What's stopping you from starting? Is it time, confidence, technical skills, resources, or simply not knowing where to begin? Let's talk about it. Someone in this community might have a helpful perspective.
2
1
13
167
Good morning, X! β˜€οΈ You don't need to have your entire life figured out before you start making progress. Work on that project. Learn something new. Send that application. Try again. Small, consistent efforts count too. Keep going, builders!
18
6
61
552
Irem πŸ’» retweeted
One thing I'm learning about building software for businesses: A good information system is about more than automating tasks or putting existing processes online. It's about understanding how a business operates and identifying how technology can help it work better. This is why the different phases of system development matter: β†’ Planning: Understand the business, its goals and the problem that needs solving. β†’ Analysis: Study existing processes, identify gaps and gather the actual requirements. β†’ Design: Map out how the system should work, including its architecture, database, interfaces and workflows. β†’ Implementation: Build, test and deploy the solution. β†’ Business Process Management: Evaluate and continuously improve how the business operates using the system. Something that stood out to me is that you shouldn't rush into implementation. If you don't understand the existing business processes, you might end up automating an inefficient process instead of improving it. And that's an important distinction. As developers, we need to understand not just how to build systems, but how those systems support business operations and create value. Technology should improve the way work gets done, not just digitise the way it's already being done. That's one lesson I'm taking with me. πŸ₯‚
2
1
9
158
Well, guess who's been nominated as Scrum Master for a group project? Looks like I'll be putting my coordination, communication and team management skills to the test. Let's see how this goes. Time to practise what I've been learning πŸ₯‚
6
1
1
21
512
Irem πŸ’» retweeted
A long feature list is not a strategy. Launch the 3 that prove the idea, then let users decide the rest. If you could only launch with 3 features, what would they be? #buildreport #elyonlabs #mvp #productstrategy
6
11
158
I've been so caught up with work, building, learning and figuring things out that creating content has taken a back seat lately. But there's a lot happening behind the scenes, and I can't wait to share more of it. Sometimes, the work comes first.
11
91
Good morning, X! β˜€οΈ Another day to learn, build, grow and make progress. May today bring you clarity, good news, unexpected opportunities and solutions to the things you've been figuring out. Remember, even the little steps count. Keep showing up and trust the process. Wishing you a beautiful and productive Wednesday! πŸ₯‚
17
5
51
488
Chowdeck is hiring!! Role: Senior Backend Engineer Tech stack: Node.js, MySQL, Redis, AWS, Google Cloud, and other technologies. Beyond the paycheck, Chowdeck employees get: - Full medical coverage - Smart, kind colleagues invested in your growth - Housing Assistance - Transport Assistance - Lunch allowance Apply here: linkedin.com/jobs/view/44904…
9
40
4
244
41,197
Hi People, My name is Fortune, an SEO content strategist and LinkedIn content manager. I help founders and startups build a powerful online presence that communicates their value and attract the right opportunities. You'll be seeing more of me on your tl. Let's connect🀞
16
9
1
31
1,754
One thing I'm learning about building software for businesses: A good information system is about more than automating tasks or putting existing processes online. It's about understanding how a business operates and identifying how technology can help it work better. This is why the different phases of system development matter: β†’ Planning: Understand the business, its goals and the problem that needs solving. β†’ Analysis: Study existing processes, identify gaps and gather the actual requirements. β†’ Design: Map out how the system should work, including its architecture, database, interfaces and workflows. β†’ Implementation: Build, test and deploy the solution. β†’ Business Process Management: Evaluate and continuously improve how the business operates using the system. Something that stood out to me is that you shouldn't rush into implementation. If you don't understand the existing business processes, you might end up automating an inefficient process instead of improving it. And that's an important distinction. As developers, we need to understand not just how to build systems, but how those systems support business operations and create value. Technology should improve the way work gets done, not just digitise the way it's already being done. That's one lesson I'm taking with me. πŸ₯‚
2
1
9
158
Irem πŸ’» retweeted
One thing I wish more developers starting out understood: You can learn product thinking even while building small projects. If you're building a to-do app, don't just build it because you saw it in a tutorial or because it's a popular portfolio project. Take a step back and ask yourself: β†’ Who would actually use this? β†’ What problem does it solve? β†’ Why would someone choose this over the alternatives? β†’ What would make it genuinely useful? β†’ What small details would improve the experience? For example, a to-do app for a busy student might need a different set of features from one designed for someone managing multiple work projects. The difference isn't necessarily how much code you write. It's how much thought goes into what you're building. You don't have to wait until you're working on a big product to start thinking like an engineer. Even your smallest projects are opportunities to practise understanding problems, making decisions and building with users in mind. Don't just learn to write code. Learn to think about what you're building and why. That's a skill worth developing early. πŸ”¨
4
4
15
215