makavele:


Let's talk about this for a while and while we are at it; let's reason like adults . .

The snapchat application: what does it do? social connection
Instagram? what does it do? social connection

How about the paypal app? financial connection

and the Uber app? transportation connection . . .

Now imagine paypal starts to do snaps as a feature. so while sending money to your loved ones, you could add one or two "snaps" like like snapchat
or imagine, you could now use "instragram" to transfer money to somebody's paypal account.

It misses the objective; why the app existed in the first place . . . Try to incorporate another external feature and see it dead on arrival.
Facebook tried integrating p2p payments and taxi hailing into their app. Ask yourself how many times have you used facbook's p2p payment system. Then compare that with PayPal, skrill, perfectmoney, and crypto currencies (in their dedicated application).

And how many times have taxis being hailed using facebook?
How many times do people use the dedicated apps like Uber? Taxify?

Well, you get the idea.

Go back and read the SOLID principle of programming. It's not only for classes and methods; it extends into the overall Dev ops.
There was a hot debate here sometimes why Computer Science degree holders are way better than self-taught programmers. I chose to stay neutral but now I am beginning to reason along that line too. This is something any body would have learned in the fundamentals.
Self taught always think they have learnt it all cos they shipped a product; but they are missing the whole fundamentals.

Now feel free to counter my position; but do it nicely and not like that rabid dog; who has enough to purchase a daughter
but could not purchase his family out of poverty. He got his chance but missed it; and has been ignored since 6am today.
He will be e-buried in my collection of memes.

makavele:


Please don't tell me you are feeling intimidated. I can literally smell it in your post.
Let's carry on the conversation as I replied in my previous quote.

resosdigital:

You miss the point bro.

You drop a screenshot with literally everything blurred out.

Drop the links to the repo then I will begin to shiver.

resosdigital:
Principles developed by who and where?

Tested, validated and universally accepted by who and where?

Look at Amazon- started as a book selling and lending app but now is a full fledged ecommerce app. But not just that though, you have amazon prime cast TV incorporated, amzon drive, Amazon go, merch by Amazon, Amazon art etc.

Why didn't amzon go out of business because they shifted from their reason of existence. Or why did users embrace the new features and additions even if they were not book related.

Think jumia. Now, jumia pay, jumia food, jumia travel and so.

I still maintain my stand that it is still down to the developer and company.

After all the app is yours, you could integrate any features you want without having to worry about any principles.

And by the way, the fact that we share different opinions on this matter, doesnt make one smarter than the other.

makavele:

modestbrowser:

Goodbye toy soldier....

makavele:
And now going back to your questions of principles developed by who or where?

Who developed the Waterfall method, or the Agile methods? how about Scrum. It's already quite obvious you are self-taught. I really have no problem with that. But this is where "you" might have a problem.

A customer needs a web app. After shipping, your web app consumes 956MB of RAM. And takes forever to search the DB records. Oh good Lord! Customer complains. A computer scientist will not even have this issue because before shipping, the apps are already tested and optimized for memory usage and performance, disk io rates; and bandwidth consumption; cpu usage etc. Well, no self taught tests for these things and that would even be an understatement.

So back to bedlam. Customer complains. You go to google and search "my application is using too much memory" . . "how to transverse a DB quickly" etc
and you get some results talking gibberish . . e.g.

The big O notation, a pigeon vs an email in file transfer; use Recursion instead of endless for loops; use memcache; integrate redis; use quicksort
blah blah blah

And you start wondering what the heck has Big O got to do with an html/css application in php and bootstrap;
and why must i spin up Redis for this simple laravel application. what the f*k is quicksort?

then you start googling again: "what is Big O" , "how to implement big O in PHP" . . . "how to implement Redis".... like seriously?
And when you start to get brain fogged with all the information that don't even scratch the surface.

You go back to the codes and start reducing your if else statements, or probably creating more nested loops and vice versa.
You start refactoring by grouping together code blocks into functions and reducing lines of code blocks.

And guess what? YOU DID NOTHING !!!

And that, my friend, is the problem derived from a lack of understanding of principles.

resosdigital:

You make a lot of points but all this have absolutely nothing to do with the question. A chat app that allows people to make payments.

And for your information I am a computer science graduate from futo. So believe me when I say I dont make rookie mistakes.

And you dont need a sermon to drive home your points.

resosdigital:

You make a lot of points but all this have absolutely nothing to do with the question. A chat app that allows people to make payments.

And for your information I am a computer science graduate from futo. So believe me when I say I dont make rookie mistakes.

And about self taught developers, do you know Jeffery way of laracasts.com the official training site of laravel. Well, he is a college drop out and self taught programmer. Do your noun certificate has nothing to do with it.

Come to think of it. If uber decides to incorporate a sort of on demand payment processing into their service, do you think anyone in this world will care about your principles.

And you dont need a sermon to drive home your points.

makavele:


Congratulations: well you get the point !
An app that allows a payment system . . I say Nay, you say Yay.
At the end of the day, the app maker is pleased to do as he/she desires.

modestbrowser:

I guess you haven't heard of WeChat b4.
What a man.
Chai

makavele:


That response was not about the app; but your question of principles

Congratulations: well you get the point !
A comp sci graduate who negates the use of principles? I want to believe otherwise !!!

An app that allows a payment system . . I say Nay, you say Yay.
At the end of the day, the app maker is pleased to do as he/she desires.

And yes, I know Jeffery and a host of others. The problem is . . they learn in reverse. but over time, will become just as good as one with the core fundamentals or even better.

As you could see in my analogy, the problem to our imaginary app was fixed in reverse;
which poses a threat in commercial standards.

resosdigital:

You still dont get the point.

Or do you think Amazon sat down with its developers to talk agile before deciding to incorporating any of their services

resosdigital:
And on the thought about self thought vs degree programmers.

I believe this comparison is baseless as the comparison should be rather be about good vs bad programmers.

makavele:


I actually took this same stand; I considered it baseless, I didn't comment about it..
But with the way bad programmers are springing up every nano second especially on Nairaland;
I might just go along with that guy that says programmers needs to be regulated by a board kinda.
At least, in Nigeria; for now !

modestbrowser:

I can bet my balls you wouldn't be on the list of programmers if a regulated body was achieved....

makavele:


Bros, please stop this . You are cracking me up real good here. Let me repeat myself. That post was more of a digression. Well I get you point. So let that one rest.
I don't know what methodology amazon uses; but methodology isn't something that is written on a whiteboard and decided upon
prior to making decisions.
Nobody says "hey, lets build a new integration?" shall we use agile, or otherwise?
or which TDD shall we employ?
Hahaha

That statement alone shows you don't even understand what I was saying all long; more like it's kinda beyond your scope
Your perhaps know the Google definition of it; but not the practical implementation of it. You would only when you work where it is being
practiced.
And I say that politely, please don't take it as an insult.

resosdigital:

You were the one who went off track.

Someone suggested that he integrate a payment processing into his app.

This is a marketing advice and discussion as the approach and technical side of this were never mentioned.

Only for you to say that it was against a programming principle.

What is the name of the principle and who propounded it if I may.

Or better still tell me how the above suggestion is related to big o and agile and redis?

makavele:


If you choose to live in self-denial, my friend, it's your choice.
I wasn't having high expectations; anyway.
You win; I am done !!!

resosdigital:


There is nothing like self denial.

The question of whether a payment processor should be integrated into the chat app is for marketers.

Programmers would only come in when the question how? Is asked.

makavele:


Let's talk about this for a while and while we are at it; let's reason like adults . .

The snapchat application: what does it do? social connection
Instagram? what does it do? social connection

How about the paypal app? financial connection

and the Uber app? transportation connection . . .

Now imagine paypal starts to do snaps as a feature. so while sending money to your loved ones, you could add one or two "snaps" like like snapchat
or imagine, you could now use "instragram" to transfer money to somebody's paypal account.

It misses the objective; why the app existed in the first place . . . Try to incorporate another external feature and see it dead on arrival.
Facebook tried integrating p2p payments and taxi hailing into their app. Ask yourself how many times have you used facbook's p2p payment system. Then compare that with PayPal, skrill, perfectmoney, and crypto currencies (in their dedicated application).

And how many times have taxis being hailed using facebook?
How many times do people use the dedicated apps like Uber? Taxify?

Well, you get the idea.

Go back and read the SOLID principle of programming. It's not only for classes and methods; it extends into the overall Dev ops.
There was a hot debate here sometimes why Computer Science degree holders are way better than self-taught programmers. I chose to stay neutral but now I am beginning to reason along that line too. This is something any body would have learned in the fundamentals.
Self taught always think they have learnt it all cos they shipped a product; but they are missing the whole fundamentals.

Now feel free to counter my position; but do it nicely and not like that rabid dog; who has enough to purchase a daughter
but could not purchase his family out of poverty. He got his chance but missed it; and has been ignored since 6am today.
He will be e-buried in my collection of memes.

makavele:


And I gave an appropriate response.

When I delved into core programming; it was a digression meant for you and not the app creator.
and I made that clear multiple times.

Cheers.

p.s.: this is a programming board; not the Business one . . . Based on your suggestion; he shouldn't have posted such a question here.

makavele:
And now going back to your questions of principles developed by who or where?

Who developed the Waterfall method, or the Agile methods? how about Scrum. It's already quite obvious you are self-taught. I really have no problem with that. But this is where "you" might have a problem.

A customer needs a web app. After shipping, your web app consumes 956MB of RAM. And takes forever to search the DB records. Oh good Lord! Customer complains. A computer scientist will not even have this issue because before shipping, the apps are already tested and optimized for memory usage and performance, disk io rates; and bandwidth consumption; cpu usage etc. Well, no self taught tests for these things and that would even be an understatement.

So back to bedlam. Customer complains. You go to google and search "my application is using too much memory" . . "how to transverse a DB quickly" etc
and you get some results talking gibberish . . e.g.

The big O notation, a pigeon vs an email in file transfer; use Recursion instead of endless for loops; use memcache; integrate redis; use quicksort
blah blah blah

And you start wondering what the heck has Big O got to do with an html/css application in php and bootstrap;
and why must i spin up Redis for this simple laravel application; when I have mysql or sqlite? what the f*k is quicksort?
i could just do a "db connect" and "for each" the living daylight out of it.

then you start googling again: "what is Big O" , "how to implement big O in PHP" . . . "how to implement Redis".... like seriously?

And you get answers like "the world has moved on to non-relational databases" and you start googling again
"differences between relational and non relational databases"

And when you start to get brain fogged with all the information that don't even scratch the surface.

You go back to the codes and start reducing your if else statements, or probably creating more nested loops and vice versa.
You start refactoring by grouping together code blocks into functions and reducing lines of code blocks.

And guess what? YOU DID NOTHING !!!

And that, my friend, is the problem derived from a lack of understanding of principles.

The global coding and marking market size is estimated to generate revenues of around $7 billion by 2023. Check out what you should know about Code Refactoring in Agile