I saw a cybersecurity role, applied, and went through technical interviews before I got invited to interview with the founder, who made it clear that, in his organization, they do not value hardwork.
In his words, "We're customer centric and all that matters to us is the number of clients you can bring into the organization."
I politely reminded him that if I wanted a sales role, I would have applied for one.
He then tried to persuade me from the angle of an elder who knew what was best for me and in a bid to diminish my work and get me to agree with him, he told me the company would employ me as an intern (despite my experience).
He also made it clear that he had read some of my articles from my time as an AI researcher and expected me to bring that thought leadership to the organization.
It was the first time in my life I had heard someone associate internship and thought leadership in the same sentence.
At some point, he admitted that he had deliberately asked me the same question multiple times just to see if I would get angry. Apparently, from all indications, I seemed to have a "good head on my shoulders."
Thankfully, I wasn't applying from a place of desperation, so I walked away.
But I have thought about that experience several times, especially when I think about young people desperately searching for jobs, trying to get their foot in the door, pay their bills, support their families, and build a future for themselves.
Some people have been searching for months. Some have exhausted their savings. Others are dealing with the pressure of unemployment, family expectations, or the fear of falling behind.
And sadly, some organizations and founders know this. They take advantage of people's desperation, while expecting them to take on responsibilities far beyond what they are willing to compensate for.
I was fortunate enough to walk away from such a terrible offer, but I keep thinking about those who don't have that luxury.
I have dated girls from poor homes, and I have dated girls from rich homes.
The girls from rich home had somethings in common.
(1) They love their dad, and they don’t fake their love for you.
(2) They’ll hardly bill you.
(3) They’ll push you healthily to become another version of their dad for their kids.
(4) you have to be a strong willed man to marry them. They question things they don’t understand, and they don’t hide their feelings.
I will talk about my experience with the poor ones later.
When I got laid off from Microsoft, I got into a company in Lagos that felt paying 600k naira a month was doing me a favour. I had to take the offer to keep body and soul together.
Was there for 6 months until I fell out with the MD and started looking out. That was when I started my training outfit but couldn't quite get traction.
Anyway, after leaving this NGO, I spent another 5 months in the wilderness, literally. Ate rejections almost every other day. Was living on the goodwill of friends and relations. Basically wondering what to get out of life.
An Antler rep came knocking at the time and was in the process of fast tracking my application to the Antler cohort at Kenya. Guess what? My passport had expired. Ran to go fast track my passport, after a few days emailed the partner but was told it was too late.
I remember laying in my room laughing hysterically, mulling to myself, "who I offend?"
Thankfully at that time, I applied to Andela and the process started for another 2 months. I got into Andela and my monthly salary was my previous annual salary. This trend continued in a subsequent company. Use am run one or two that year.
But the point is, while I was enjoying this new reality, I asked myself, "why did you worry all those times?" In hindsight, there was no reason to. I should have just chilled for 5 months, enjoyed myself.
But we are human and can only understand life in hindsight. As long as you believe this it will work out for you: EVERYTHING will turn out better than you expected, just stop worrying.
@elite_developer “Backend is easier”
Just say you have been writing structural and technical debts.
No field is easy if you really know what you’re doing.
@Dokeezy@LMDiddy14 Dude, CR7 draw the defenders to himself, if you watch from the other angle you will know that there are at least 2 Portugal players in the box and 1 is on the other wing with only one opponent defender. Bruno could have make a cross to the other wing to use the advantage.
@CFC_Janty And that’s the advantage they don’t know they have.
Cristiano Ronaldo being on the pitch will always be a threat to the opponents either he score or not, they can’t count him out so they will always have like 3 players marking only him, and that is a big advantage.
@SahilExec 2. For the security issue, it will be the password being plain text only if the password hashing was not implemented in the createUser function. but since we are not shown the content of the function, we will just assume that the password is being stored as plain text.
2/2
@SahilExec 1. Honestly, the race condition in the sign up will only occur if the database unique constraint is not enforced on the email field in the database. No in-code handling will fix it.
1/2
@ashoKumar89 If the 2 actions are not possible, I will pull the last card which switching the JWT secret key, this action will force every user to login again due to invalid JWT token.
@ashoKumar89 JWT expire 30day is already a security risk. I will assume blacklist token system is not implemented.
With a leak like this, I will quickly implement force logout for user’s stolen device. If the device is unknown, I will do a force logout for users in the geolocation.
@ashoKumar89 1. User input is not sanitised.
2. Raw data are passed to SQL query
3. No error handling.
Number 1 & 2 gives room for dangerous attacks like SQL injection and data corruption too.
Number 3 can cause a serious problem like a system crash in production.
@EOEboh Index works just like the table of contents at the first page of a book.
It gives you an easy link to anything you are looking in the book, but if any update is made to the content of the book, the table of contents will need to be updated too.
@javarevisited Check the metric and monitoring to get the endpoints under heavy load.
Stop the bleeding by increasing rate limiting on the endpoints.
Add cache for the most frequent requested data to ease the hit rate on database.
Check the metric and monitoring again to see if is under control