Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

What is the difference between method and algorithm? [closed]

+0
−0

Closed by System‭ on Jun 24, 2018 at 16:14

This question was closed; new answers can no longer be added. Users with the reopen privilege may vote to reopen this question if it has been improved or closed incorrectly.

Could you please let me know the difference between method and algorithm? Can a method be computed into an algorithm? Can an algorithm be based on a method?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

This post was sourced from https://writers.stackexchange.com/q/37184. It is licensed under CC BY-SA 3.0.

0 comment threads

1 answer

+1
−0

I would say, in plain English, a "method" is an approach to accomplishing something without any guarantee of success.

An "algorithm" implies greater accuracy, dealing with well-defined and consistent objects with a greater certainty of reaching a specific goal.

The terms are definitely confused in usage between these two things, but in general I think this would be a good division of meaning between the two.

e.g. I could have a general method for dealing with employee conflicts, but it doesn't rise to an "algorithm" because people and their conflicts are too varied to produce a step-by-step solution that always works. Each situation requires individualized understanding and thought. There is no "one size fits all" solution.

Whereas, something like a recipe for baking a cake is very much an algorithm, the ingredients and methods are very well-defined, and following the instructions precisely without error will result in a cake.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

0 comment threads