Pinned Tweet
Hi, I’m Limah Temitope - a backend software engineer.
I help design and build reliable APIs, authentication systems, and backend services that are secure, scalable, and easy to maintain.
I started posting consistently about backend concepts a few months ago.
This is a creative recap (inspired by TikTok). Thanks to everyone who has viewed, commented on, and liked my content. 😍❤️
I have more tips and projects to share. Stay tuned!
If you’re not following me on TikTok, please do 🙏
tiktok.com/@limtech001
The effects of procrastination are;
1. Loss of time: since procrastination means avoiding to process or complete tasks, the day might end up being unproductive.
2. Loss of goals: the procrastinated tasks will impact the goals set to be accomplished and can be detrimental.
3. Lack of self-esteem: not being able to complete tasks or accomplish goals can be frustrating and make one develop low self-esteem in a way that “this and that are not meant for me”, you might start developing negative feelings about your abilities to accomplish your goals or mental factors such as anger and depression.
4. Stress: worrying too much about starting multiple procrastinated tasks in due time which can result to poor performance in each task.
The reasons behind procrastination that some of us don’t know are;
1. Lack of energy: this may be due to illness, discomfort, or stress.
2. Lack of focus: this may be due to distractions, overwhelming tasks (having so much to do at the same time), mental fatigue, or being disorganized.
3. Lack of failure: this is not very common to notice because most of us lie to ourselves about this. When we fail at a task, the fear to make us appear incompetent to others or ourselves and avoid being psychologically uncomfortable can become worrisome.
We then say that “it’s not for me”.
Failure is to let us know where we are getting things wrong not that we’re incapable of doing them to succeed.
We should definitely assess the situations or causes and address them.
Strategies for psyching ourselves out and managing procrastination;
1. Get organized: use time and project management strategies such as schedules, goal settings and other techniques. Breaking complex tasks into smaller tasks and prioritize.
2. Put aside distractions: distractions are time-killers and are the primary way people procrastinate. Putting aside distraction is one of the primary functions of setting priorities.
3. Be accountable: holding ourselves accountable by telling someone, writing it down on the wall we face every single time, or posting it on the internet. This is not to seek approval but to put our mind on the goals and take responsibility for our decisions.
4. Reward yourself: rewarding oneself after every accomplished goal is a motivational medicine to do more.
The effects of procrastination are;
1. Loss of time: since procrastination means avoiding to process or complete tasks, the day might end up being unproductive.
2. Loss of goals: the procrastinated tasks will impact the goals set to be accomplished and can be detrimental.
3. Lack of self-esteem: not being able to completed tasks or accomplish goals can be frustrating and make one develop low self-esteem in a way that “this and that are not meant for me”, you might start developing negative feelings about your abilities to accomplish your goals or mental factors such as anger and depression.
4. Stress: worrying too much about starting multiple procrastinated tasks in due time which can result to poor performance in each task.
There's a new version of this post
The reasons behind procrastination that some of us don’t know are;
1. Lack of energy: this may be due to illness, discomfort, or stress.
2. Lack of focus: this may be due to distractions, overwhelming tasks (having so much to do at the same time), mental fatigue, or being disorganized.
3. Lack of failure: this is not very common to notice because most of us lie to ourselves about this. When we fail at a task, the fear to make us appear incompetent to others or ourselves and avoid being psychologically uncomfortable can become worrisome.
We then say that “it’s not for me”.
Failure is to let us know where we are getting things wrong not that we’re incapable of doing them to succeed.
We should definitely assess the situations or causes and address them.
Depends on the workload.
For CPU, I’d prioritize it for computationally intensive tasks like complex calculations, data processing, and CPU-heavy workloads.
For RAM, I’d prioritize it for memory-intensive tasks like running multiple applications or processes simultaneously, handling large datasets in memory, and workloads that require a lot of memory to operate efficiently.
Day 2 of your backend journey, and you’re already talking about Node.js?
I checked your profile and saw that you’re a frontend developer, so the fundamentals and other crucial aspects of software development may not be entirely new to you.
Maybe you mean day 2 of learning Node.js? I think that distinction matters because someone new to software engineering might get the wrong idea.
A backend journey doesn’t start with a programming language. There are fundamentals to understand first.
DAY-2 of My Backend Journey in Public.
Today, I covered Modules & Global Objects in Node.js.
I learnt that if we want to import data from one file into another, we can use the require keyword.
However, we cannot directly access variables and functions from another file.
To share data between files, we have to export the required variables and functions from one file and import them into another by storing the imported information in a variable.
Another concept I learnt is Global Objects.
As we know, in JavaScript, we have the window object, which is a global object provided by the browser not by the V8 Engine.
In Node.js, the global object serves a similar purpose to the window object in the browser.
The global object is not a part of the V8 Engine; it is a feature provided by Node.js.
We also have global This, which is the standard way to refer to the global object in any JavaScript environment.
Thankyou @namastedev_ for the wonderful Explanation Your explanations never made me feel like I was a non-techie. Wow, sir! You explain even the fundamentals so well!✅
It took me some time to realize that multitasking to perfection is a lie.
From my experience, the brain cannot focus on multiple things at a time and execute them perfectly. I figured it out when I tried to understand why tasks felt overwhelming and stressful.
I started working towards making it feel less overwhelming by executing one task at a time and prioritizing them from easy to complex.
Sometimes, requests can be executed synchronously, not asynchronously.
Time flies, and it often feels like there’s too much to do and not enough time.
Time is a valuable and non-renewable resource. It cannot be saved for later, purchased, or replaced once lost. It moves like a no man’s business.
Procrastination and avoidance consume time that could be better spent. Rushing through tasks often leads to lower-quality outcomes.
How do you stay on top of everything when responsibilities pile up?
In my experience, effective time management is about self-management; knowing what you want, planning how to achieve it, and executing your plan efficiently.
Don’t postpone tasks that can be executed immediately because you might have piled up tasks for later.
Two implementations can produce the same result, but that doesn’t mean they’re equally good.
One might work today but become difficult to extend when the requirements change.
Another might take more thought upfront but make future changes easier to manage.
The challenge is knowing when to keep things simple and when a problem genuinely needs a more thoughtful design.
Paying more attention to decision-making process, not just whether my code passes the tests because the quality of a backend isn’t measured only by what it can do today, but also by how well it handles tomorrow’s changes.
#backendengineering #softwareengineering
I’ve learned to pay attention to the reasoning behind an implementation, not just the result.
Why this approach?
What problem does it solve?
What happens when the requirements change?
Can another developer understand and maintain it?
Because writing code that works is important, but understanding the decisions behind that code is what helps you build better systems.
Don’t just make it work. Understand what you’re building.
#BackendEngineering #SoftwareEngineering
TWIK Episode 6 is out! 🎥✨
Have you ever wondered how different software applications communicate with each other?
In today’s episode, I broke down APIs (Application Programming Interfaces) in simple words 👇🏽
📌 What I covered:
1️⃣ What an API is
2️⃣ How APIs allow different software applications to communicate
3️⃣ How requests and responses work
4️⃣ Why APIs follow defined rules and formats
5️⃣ How an application can interact with a backend without knowing how it works internally
Expert claims ❌ Clarity ✅
If you’re learning backend engineering, understanding APIs is one foundation you don’t want to skip.
💬 What would you like to know about APIs? Drop your questions in the comments!
#API #SoftwareEngineering #BackendEngineering #TWIK
I wrote about a few weeks ago.
xitter.cf/limtech001/status/2104…
Replying to @Limtech001
I'd love an episode on what happens when the server is slow but not down, that's where beginners get lost
Do we really have SEs on Facebook and Instagram?
If yes, kindly follow.
Facebook-facebook.com/share/1FHJN8M5f…
Instagram-instagram.com/official__lima…





