-
Notifications
You must be signed in to change notification settings - Fork 780
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does the developer need algorithms? #18
Comments
Hello there, I'm a leaner and I found this roadmap helpful. When it comes to algorithms though, you would find that there are several of them and from a beginners point of view some of them look very complex 😞🙂. As you improve on your problem-solving ability (which also includes writing algorithms) and build projects, you would find that there are already written algorithms to solve common problems that you may come across. So in a nutshell, yes you need algorithms, both the ones you write and maybe (depending on the problem you're trying to solve) already existing ones. |
I would posit that well-documented samples of common algorithms, written in any particular language, would be beneficial to both novice and advanced developers. It will always help a novice developer to match a name with something they've unknowingly traversed. In my past while teaching myself Java, I've had the pleasure of saying, "Oh, that thing I've been using is called a Stack?" which ultimately leads to the questions of "why?" and "what other algorithms exist?". As for the more advanced users, it helps them by hosting examples for comparison. We can see how two language syntactically differ in their approach to solving a common algorithmic problem. That being said, I'd love to know how a PHP savant goes about solving more complicated algorithms. |
Reply
W dniu śr., 31.05.2023 o 23:42 Andrew S ***@***.***>
napisał(a):
I would posit that well-documented samples of common algorithms, written
in any particular language, would be beneficial to both novice and advanced
developers.
It will always help a *novice* developer to match a name with something
they've unknowingly traversed. In my past while teaching myself Java, I've
had the pleasure of saying, "Oh, *that thing I've been using* is called a
Stack?" which ultimately leads to the questions of "why?" and "what other
algorithms exist?".
As for the more *advanced* users, it helps them by hosting examples for
comparison. We can see how two language syntactically differ in their
approach to solving a common algorithmic problem.
That being said, I'd love to know how a PHP savant goes about solving more
complicated algorithms.
—
Reply to this email directly, view it on GitHub
<#18 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHYHS7KPXOTDHEMPIV4F7EDXI63NBANCNFSM6AAAAAAU5PDLTU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Serdecznie pozdrawiam,
Mateusz Rosiak
|
Many sources state that a developer must know basic algorithms and data structures. What do you think about this? Don't you think it's worth adding a block with algorithms?
The text was updated successfully, but these errors were encountered: