@Akintola_steve You're correct but there would always be external factors even in relationship e.g work, finance, friends etc. The strength $ stability of any relationship is in their ability to handle external pressures. Confidence in your relationship often comes from how well you handle these
One thing about system design that people don’t talk about enough is failure.
Everybody likes to draw pointers flow like:
Client → API → Database
Beautiful.
Now let your database go down. 😂
What happens?
Do you allow your API start returning errors immediately?
Do your requests queue somewhere?
Do you have a fallback?
What happens to the data?
How does the user get affected?
That’s where the actual system design starts getting interesting.
@r_clocke Exactly, like I was already like saying, it's all well and good,Messi had won it already and Las las Egypt still African team. But I didn't see that comeback at all!
@Benn_X1@Bored_again_ Just asking curiously, how does that person classify as a senior engineer or be an exceptional talent? The requirements talk about people who understand software system at enterprise level because the goal is to have people who are able to bridge enterprise software and AI.
This whole married man moving to his wife apartment argument on here has been interesting.
A key truth is that marriage is so much about value system. One of the most important thing a couple has to do is establish their value system.
People response here shows their value system
Marriage exposes weak skills
Marriage has no hiding place. If you cannot talk well, it will show. If you do not know how to manage money, it will show.
If you avoid hard talks, it will show.
Love alone will not cover these gaps. Bills will come. Stress will come. Real talks will come.
Marriage exposes what you skipped learning as an adult.
It does not shame you, but it will pressure you to learn fast.
You either grow the skills, or the home stays tense.
That is the truth.
🤷♂️
and time consuming because it's user facing, requirements are more vague, has frequent updates and more open to criticism.
So in summary it's subjective and depends on individual preferences. None can be said to be "easier".
I have been following you and @segun_os_ conversation. The word "easier" can be very subjective, however some things are clear. Backend is more technically demanding as it's broader and requires deeper understanding of software while frontend is clearly more mentally demanding...
I was responding to your counter argument where you changed the argument to frontend is not EASIER than backend.
Your response is to cherrypick what to respond to and then create a new argument.
This is classic strawman argument, and exactly what you did by giving a new meaning to "more difficult".
It’s becoming a circle, and I’ll like to stop here.