Post

@CodeWisdom #Code is always a medium to the solution, not the solution itself
English

@CodeWisdom Yes, Fully Agreed!
"First, solve the problem. Then, write the code"
Really Good Advice!
English

@CodeWisdom Richard Hanming thought otherwise with “The purpose of computing is insight, not numbers.”
English

@CodeWisdom This one is so far from reality. In an era of cloud computing and TDD, 'solving' a problem on paper has no value if not proven by tests and that you can ensure it scales well once deployed. This is for me deprecated.
English

@CodeWisdom "Ignore the problem, write bad code, blame someone else, repeat"
English

@CodeWisdom Who's John Johnson? Google finds so many people with this name.
English

@CodeWisdom Nah too easy, first tr like sht before even thinking really about the problem, wasting time and nerves 🤣
English

@CodeWisdom Le me who wrote the code before solving the problem : “I should’ve think of that before”🙇🏻♂️
English

@CodeWisdom First, understand the problem (or need...I.e.Business Requirement), then create a solution that fulfills the need, then write the code that implements the solution.
English

@CodeWisdom Solve the problem as far as possible, break it down in different sub-problems, start writing the code for the sub-problems, iterate through the solutions and see how to improve it.
English

@CodeWisdom Meanwhile me who creates the new problems without fixing the previous one.
English

@CodeWisdom Sometimes we have real-life problems to solve with help of computers. Sometimes we have the real-life problem + the complexity of an existing computer program to solve the problem. In the second situation we can only write code with less cerimony to try new ideas very fast.
English

@CodeWisdom Many times, how to write the solution in code is the very next problem.
English

@CodeWisdom And do remember: Algorithm matters the most, languages come and go
English

@CodeWisdom Sounds good, doesn't work. In anything other than university projects.
English
















