|
If you have an exercise where you have certain limitation. The teacher want you to make a game that follows strict rules, how can you experiment? Can you experiment when you drive a car? No, a car drives allways in the same manner. You can't experiment and put a gas when want stop the car. The same with Conways game, if you have to use 2d array, make it with one loop. If you make it using only one loop, I will come back here and tell everyone that I'm a clown and I'm sorry. Please, don't compare CS to being self-taught. As self-taught you do whatever program you like to, and read whatever bookm you want to, and you can experiment how much you want. I would love to do that. But when you take a loan and you have to find solution to a problem, where you are restricted by instructions than you can't experiment. Of course, you can sweat and fight with it but the result will be not different from someone who copied it from internet.
modified 3-Jun-21 21:01pm.
|
|
|
|
|
Such a narrow view. If you were a horse they'd call that a result of blinders.
So you re-code that new nemesis of yours, that game. You make the instructor happy. And at the same time, figure out how to enhance it - make it do more - experiment with it. In fact, you could learn how to leave 'stubs' in your code for later additions.
The thing is, the world is full of mindless hacks creating unimaginative code. Where I work, they get that quality whenever they outsource - particularly to "foreign lands". It's just the way it is. It's not that the people in those places are less smart - they just turned a craft into an assembly line and they get to produce products, accordingly.
Myself? I will argue with whomever wants me to build an application (assuming it doesn't fit into the abstract ones that can handle most things as-is). Ultimately, senior management gets my point and agrees - even if one of them is debating with me. I explain why until they understand - and if they still want something, OK. They all understand that it's easier for me to just code sh*t as people request it then to argue so it's done correctly. Loved? Maybe not. Respected.
So, your exercise is only limited by a narrow view of following the instructions to the letter. You can make more of it . . . or continue your path to the assembly line in some field of endeavor.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
I always try to come with my own solution to a problem in my homeworks, but it always ends up with me being late and looking like an idiot with low IQ becuase everyone already did it, and than I at least try to rush it make it as easy for myself as I can and I end up with the solution that is all over the internet and I look like a fraud. Maybe I'm an idiot? And should come up with something revolutionary in three days, but well I can't... and then I wonder: Why do I even bother? Why not just memorize those algorithms because in the end of the day it doesn't make a difference.
modified 3-Jun-21 21:01pm.
|
|
|
|
|
Please, don't compare being self-taught and CS. When you are self-taught you can experiment as much as you want because you do stuff that you want to do, and if you come up with a solution for bubble sort and Conways game of life on the way, good for you. If I could do my own stuff, and wasn't bound by the limitations of the instructions I get, I would do the same. But if you have strict instructions with strict rules and the deadline, and the loan than you don't fight and play with prewritten algorithm that someone already invented, because after few days of sweating and hard work your solution is not different from one that people copy from internet. And when it comes to certain algortihms you only can do it in one way, like bubble sort for example. But I understand, It hard for you to swallow that you're not smart just because you can implement other people's solution. In fact,you are full of yourself if you don't realize that and think that your implementation of common algorithms is your own.
modified 3-Jun-21 21:01pm.
|
|
|
|
|
OriginalGriff wrote: Beginners don't have the skills to analyse a problem, design a system, implement it, document it, test and debug
Yet that is where they should start: At "analyze a problem". That is what software development really is about - far more than coding, testing and debugging it. Or, so it ought to be.
If you don't have to implement / test / debug, you can, early in your studies, analyze quite large systems and design the solutions - far larger problems than those you have the resources to code / test / debug.
While you are learning methodologies for problem analysis and solution design (at an implementation independent level!), you should, in parallel, learn implementation, testing and debugging techniques, applied to small, manageable problems for a beginning student. But that is not the main focus of a software developer's education. The problem analysis and (implementation independent) solution design is.
Modern education programs start with a typing course: Student learn to type "int main(int argc, char *argv[]) {}" first, and taught the finer details of lambdas, and only after that start asking what the problem is all about. That is to turn things upside down. But that is how we want it nowadays. Even if it is upside down.
|
|
|
|
|
I had actually one project that I hade to do for my school, and it was a small program that have different functions, but it was a whole program. This was the only thing I really enjoyed and loved to do and I learned much more about problem solving and algorithms than from those stupid exercises.
modified 3-Jun-21 21:01pm.
|
|
|
|
|
There is some truth to what you're saying, but it's also difficult to design "real world problems" that can be solved in a university setting. Depending on what school you're at, many of your instructors may not even have much real world experience, because there's quite a gulf between pure CS and software engineering. Many of your classmates probably wouldn't be able to handle real world problems at this stage anyway. In later years, there's typically a course or two where you work in teams, the same way you would in industry, because this introduces issues that don't arise when working on your own. The project that a team implements, however, might be something that's already been done, like a microkernel or a simpler version of MS Word.
|
|
|
|
|
I'm so mad at myself... I took a loan for be able to make this degree. I was so stupid, now I'm stuck and I have to continue that path to get a job. Well, nevermind I just memorize all those algorithms just to copy them from my memory and explain to the teachers and the interviews what it is that I copied - they don't even know the difference. Let them be glad. Let me copy and paste all this crap from my memory, and take money in the end of the day... Whatever... If there is something that you find you love to do, don't be too enthusiastic, it's a trap. You will never do in your life what you love to do even if it's related to what you love to do. Life is a torture, whatever path in life you take... Sorry for all those messages, I'm so disapointed with life...
modified 3-Jun-21 21:01pm.
|
|
|
|
|
Member 14971499 wrote: Life is a torture, whatever path in life you take... Sorry for all those messages, I'm so disapointed with life... |
I would very seriously advise you to seek help: talk to family and friends and don't let despair get the best of you. Pound for pound, grey matter and specially functioning grey matter is one of the rarest commodities on Earth and once you've be given a few pounds of it, you should take good care of it.
Getting back to your dissapoinmets with CS and without knowing anything about your program:
- Keep in mind that you cannot have any program tailored specifically for you. There are others in your class that might have different needs. Be considerate to them.
- There is no "perfect" method for teaching any science let alone "computer science". I put that in quotation marks because I'm not even sure it's truly a science or an art (Knuth titled his seminal work "The Art of Computer Programming"). Your instructor tries to teach you at the same time the syntax of a programming language, some basic data structures and algorithms and maybe give you a feeling for what real world problems might look like. It is hard to do all that. Be considerate of his efforts.
- There is always a balance between reinventing the wheel and blindly doing copy/paste from the Internet. Learn when you can get something already made and when you have to use your own grey matter.
To finish, let me tell you the story of my first program: first year; first CS course; language was FORTRAN (yes, I'm old). I meet a friend in second year and tell him I was bored with the homework (kind of like you) and he says "I have an interesting problem for you: write a program to find all the positions of 8 queens on a chessboard so that no one attacks another one."
I write the program and, surprise, it doesn't work. My logical conclusion is that the compiler has made a mistake and I decide to search for it. I get the assembly language listing of my program and start analyzing it. But to do that I have first to learn assembly. Then I start marveling at how the compiler knew how to translate program and in the process I learn about formal languages, LL(n) and LR(n) grammars.
Never finished my eight queens program but I've learned so much in the process. Don't get dispirited if you run into a silly problem like bubble sort or game of life. Turn it into an interesting problem if you can. For bubble sort read Knuth's volume on sorting an searching and try to solve some of his problems.
Mircea
|
|
|
|
|
Thank's  It was intresting and funy story and nice advice. I feel much better after reading this
modified 3-Jun-21 21:01pm.
|
|
|
|
|
It lets you ace the Google interview process! My coding is entirely self-taught, and whilst I know I could learn about sorting algorithms, I never needed to. That is, until I tried interviewing at Google, and there some HR drone gave me technical questions that relied on one knowing the details of sorting algorithms for the majority of them. Capped off by a couple of other questions where the accepted answer was actually wrong, but given the interviewer was not technical, there being no possibility to point out where the answer was wrong, I think I managed a perfect duck's egg score (ie zero), in spite of more than 35 years of fairly intensive programming experience on quite advanced codebases.
|
|
|
|
|
There is no point "reinventing the wheel." So, if you need to do a bubble sort in c# then google that and take one that works. It's faster and easier, but of course test it.
However, most of software development is making specific business functions and you can't copy and paste that off of the internet.
Some pieces of code are reusable, and that's a good thing.
Social Media - A platform that makes it easier for the crazies to find each other.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
ZurdoDev wrote: Some pieces of code are reusable, and that's a good thing.
Quite so.
That's essentially why we make functions/procedures to begin with. And templates.
To get quickly (and safely) through the parts that are the same so that we may get on with doing the real work.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
I feel that the whole point of your CS training is that :
- One day, you may be placed in charge of maintaining and extending those very libraries which you are using today,
- For which you need to know the internals of how those libraries are written. This training is the drill for that.
|
|
|
|
|
One way of looking at this :
(using the bubble sort example)
Do you understand how the bubble sort works? ; do you understand the underlying algorithm it uses and how it behaves with small data size vs. large data size (google big O ... ), do you understand how other sorting algorithms work and how they behave with small and large data size (i.e. quick sort, heap sort ... )
When you are asked to do some simple basic things like that, it is only a building block upon the rest of your CS education.
I'd rather be phishing!
|
|
|
|
|
semantics.
Some people say copy/paste, some people say OOP.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
Well, OOP is good in that sense that it doesn't require from you that you copy and paste it line by line. You just import some library and call an appropriate method so that you can focus on solving problems which aren't solved yet.
modified 3-Jun-21 21:01pm.
|
|
|
|
|
Member 14971499 wrote: I don't know what is the point of copying and pasting other peoples algorithms?
there are a number of problems which show up again and again in programming (call them patterns or algorithms or whatever). and as a professional programmer, you're going to spend a lot of time recreating them in slightly different ways, in different languages, on different platforms, forever.
might as well learn them.
|
|
|
|
|
Member 14971499 wrote: The funny thing that I always read on the internet is people writing something like "I was bored, so I created Conway's game of life". Like what? You didn't create anything. You just reimplemented someone's idea from a book or from a tutorial from a guy who also copied it from a book or a tutorial.
Then do it in a different way. Sure there is the "standard way" that every tutorial keeps copying, put that aside and find a more interesting way. Do it entirely with bitwise hacks, throw SIMD at it, use memoization on blocks, whatever you can think of. There is a standard way that perhaps you are expected to use in school, but there isn't actually only one way to do it.
|
|
|
|
|
Just get through it the best you can.
I have used very little of my CS degree in any of the work I have done in 16+ years as a developer.
bubble sort, never had to use it or understand it in any real world solution. That's me though. Other people's stories may be different.
get your CS degree so you can get your first couple of jobs, then after that, it is pure work experience.
If you are still doing this after 5-7 years, you will probably do it for life.
good luck.
|
|
|
|
|
Honestly I only ever use either quicksort or insertion sort. Though exactly once bubble sort has been the best choice due to particularities of the procedure that computed the results to be sorted AND particularities of the output I needed.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
I can 'sort' of relate. 
Seriously though, I remember the boredom of learning to code by typing lines of code from a textbook, building silly little programs that did nothing original. In the intro level classes, one could get by just by following the spoon-fed examples from the book without much critical thinking. I can only guess that in the copy/paste age the boredom level has increased as you aren't even bothered with the typing aspect...actually reading through the program as you are constructing it.
If you are in a formal program, you are just going to have to play the game. The classes will get harder as you progress and hopefully you'll feel more challenged. If not, there's all kinds of coding boot-camps and on-line courses that may be more what you are looking for.
At any rate, I would suggest that you start by creating development tools that could prove useful down range...a better FTP utility, a database scripting utility, a password keeper...it doesn't matter, just something that helps in your daily activities...whatever, just make it your own...design it and build it from scratch.
Don't confuse college exercises for real-world development. We're not just a bunch of robots copy/pasting code. (though done correctly, is quite acceptable) This job is at it's core is about solving problems for people using software...and getting paid well when you succeed.
IMHO, software development is a craft where you can take nothing, make something, and charge people for it, just like artists, writers, poets, musicians, actors, etc. What we do might not always be sexy, but sometimes creativity is defined by not even noticing it. (a developer somewhere figured out how to get rid of a couple of nasty nested for loops by using a struct/array and your app loads much faster, who knows? If you noticed at all, it likely only increased your expectations.) Is that creativity, or just not being satisfied with the current incarnation of the wheel?...or quite possibly the result of an angry customer/boss who just expects them to do their job?
So figure out what personal project you want to do and design and build it. Given the vast wealth of information at your fingertips, you are really only limited by your imagination and your will power. Good luck! BTW, I'd probably stay away from being a writer as your post has a few grammatical/readability issues. (of course, so does mine, but I'd be the last to call myself a writer!)
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
Think of it that way... Why do people learn Pythagoras theorem and its various proof? This thing is at least 2000 years old! Plus how does that help with everyday work?
Well, it's not at all about learning the algorithm by rote at all. It's about practicing your brain muscle, learning new ways of thinking, finding it yourself again easily when you forgot the theorem.
I see your complain 2 ways. Either learning algorithm is tedious, which often expresses itself as "boring", and you need to practice. Or it really is easy, and then you only have to spend 5 minutes on it and perhaps you can secretly do something else while the teacher is dronning on... Or add some fancy unrequested twist to your demo...
|
|
|
|
|
I spend a significant amount of time reading and analyzing stuff written by others.
I do this to learn, and the world is full of smart people willing to share their knowledge through papers and open source projects.
There is also no lack of software developers who manage to trick themselves into believing they have come up with simple a solution to a complex problem - here are two common examples:
- Synchronizing state across multiple systems is hard to get right, but can be done using Paxos or Raft. This needs to be properly handled when decisions will be made based on state information shared by multiple systems.
- Scheduling is hard, problems like job shop scheduling and nurse scheduling may sound easy, but you cannot even pick the right algorithm for a particular problem without understanding it.
There are often multiple algorithms that are known to provide a solution, but the performance can vary wildly depending in the input data.
So, IMHO, get on with the learning - don't just - as you say - copy and paste solutions written by others.
Espen Harlinn
Chief Architect - Powel AS
Projects promoting programming in "natural language" are intrinsically doomed to fail. Edsger W.Dijkstra
|
|
|
|
|
Basically you want to build starships without knowing what's a hammer.
I saw many like you, they think that being creative meant there was no need of knowledge. And they are fast to copy paste from other works without *thinking*. I fixed many of their "works" because they did not know what they needed, what they were doing, what they were copying and where.
If tomorrow I will enroll to run in the Olympics I will not win: I need to train from the very scratch to be able to participate, let alone compete. If you refuse to learn the basics then, by all means, change career now that it's easier.
There's no fault in realizing some path is not for you. Maybe you will find yourself better in electronics? The programming is easier and there's more tinkering, which seems to suit your mindset more than the somewhat rigid world of Computer Science.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
