EvilZone
Programming and Scripting => Beginner's Corner => : PUnit May 16, 2015, 03:53:13 PM
-
well i've started programming in C# a while back and learned the basic stuff and coded some project. but for months now I didn't program anything, since I have no ideas and my laziness doesn't let me do it. what am i doing wrong, what should i do instead.
and to be honest i like to learn programming because i like to have that knowledge but also because i could make some money.
thank you.
-
Keep reading code. Its the minimum you gotta do to progress. All your doing is better understanding code but not embedding it in your head(Helps a lot if you enjoy reading so it doesn't burn your eyes or strain your head). If its been a while since you’ve done any sort of programming, go back and do some snippets of code that you remember(a refresher). Then do the fundamentals that you don't seem to grasp. Laziness doesn't go well with discipline which is what you need if you want to speed up the process of success.
-
Keeping to read code is a good way to maintain your level, but you can not actually get to higher levels through this. You could have a look at the theoretical side of computer science, but it has less to do with coding. I'm teaching classes at the university for people who starts studying computer science but didn't even look at a programming language until this point. Just reading the code is good and you get fit in your head understanding programs, but it doesn't help you program better. If you really want this to happen you have to write programs on your own. But maybe have a look around, there are some groups that are working on projects in their free time and need support. Maybe you could join one of them, so you don't have to think of something to program on your own.
-
well i've started programming in C# a while back and learned the basic stuff and coded some project. but for months now I didn't program anything, since I have no ideas and my laziness doesn't let me do it. what am i doing wrong, what should i do instead.
and to be honest i like to learn programming because i like to have that knowledge but also because i could make some money.
thank you.
What?.....
What am I doing wrong?: Not making anything
What should I do instead?: Make stuff
Learning how to program is not always easy. As with everything else in life it takes commitment. You can't just say you want to do it, learn a few things, and make a hello world program then stop. You have to constantly be working on it. There is always more to learn. Unless I am just misunderstanding your question, there not really any advice any one can give you. You just have to have more will to continue with your educational goals.
-
search on the internet for programming exercises, so you can practice and sharpen your skills. I also highly recommend joining a programming forum, like dreamincode.net (http://dreamincode.net).
-
To be truthful. This damm laziness is the root cause of everything ...
Dump this lazy nature somewhere in backyard, then head towards some serious tuts.
Don't forget patriotic slogan
A B C
-
i have to agree with most of the previous posts, my advice is try to dedicate some time of the day to programming, maybe 1 - 2 hours, or if your lazy, like 45 minutes. But During this time, try to throw the lazy attitutde away and practice, it can even be 30 mins tbh. Just keep practicing and reading code and soon you will make it a habit.
Good luck though, and i hope i helped.
-
If you want to be lazy AND learn, then hop on youtube and watch computer science or software lectures. MIT and Stanford have complete semesters uploaded as open courseware.
-
This is the most ridiculous thread I've ever seen. Like, what do you expect us to do now? Teach you autodidactism? lmao.
Imho, your 'question' already implies the answer: Do something else. Nothing wrong with that.
There ain't no such thing as "laziness", only a lack of passion.
-
You should go get some pussy. Pussy fixes everything
-
You should go get some pussy. Pussy fixes everything
This has in fact been confirmed by top scientists around the world.... Can't argue with the facts...
-
1) Stop being lazy.
2) Write code.
3) Write more code.
4) Go back and look at the awful code you wrote in step 2. Unfuck it. Make it faster. Make it use less memory. Make it more secure. If it's a script, make it OOP. If it's OOP, try to make it procedural.
5) Repeat.
If you're stuck on the bullshit tutorials, pick something you're interested in and write a program that involves that subject. Make a system to catalog your music/movie/porn collection. Write a browser plugin that downloads YouTube videos, whatever. If you find yourself doing the same repetitive task, figure out how to automate it. It doesn't really matter what you write, just write code.
As a corollary to that last statement, try googling "best way to <do something> in <language>". Look at the options, and don't settle for the first half-assed answer you see. While that's fine for prototyping or getting your feet wet, there are often lots of problems with the basic examples. Find a faster, better, more secure way of doing it. Then, test that shit and find what breaks, and fix it. Supply invalid input. Break things, fix them, then learn how to prevent them from breaking again.
The answers are out there - you may have to search for specific answers, but you can pretty much write any program in any language by searching StackOverflow and the likes. Just google it.
"how to save to a file in <language>"
"how to parse HTML in <language>"
etc.
Learning a computer language is just like learning any other language. You can sit in class, read about it, and wish you were fluent all day long, but until you get out there and start using it, you'll never know shit.
-
1) Stop being lazy.
2) Write code.
3) Write more code.
4) Go back and look at the awful code you wrote in step 2. Unfuck it. Make it faster. Make it use less memory. Make it more secure. If it's a script, make it OOP. If it's OOP, try to make it procedural.
5) Repeat.
If you're stuck on the bullshit tutorials, pick something you're interested in and write a program that involves that subject. Make a system to catalog your music/movie/porn collection. Write a browser plugin that downloads YouTube videos, whatever. If you find yourself doing the same repetitive task, figure out how to automate it. It doesn't really matter what you write, just write code.
As a corollary to that last statement, try googling "best way to <do something> in <language>". Look at the options, and don't settle for the first half-assed answer you see. While that's fine for prototyping or getting your feet wet, there are often lots of problems with the basic examples. Find a faster, better, more secure way of doing it. Then, test that shit and find what breaks, and fix it. Supply invalid input. Break things, fix them, then learn how to prevent them from breaking again.
The answers are out there - you may have to search for specific answers, but you can pretty much write any program in any language by searching StackOverflow and the likes. Just google it.
"how to save to a file in <language>"
"how to parse HTML in <language>"
etc.
Learning a computer language is just like learning any other language. You can sit in class, read about it, and wish you were fluent all day long, but until you get out there and start using it, you'll never know shit.
Decent as fuck. Beware, I'll pitch that cookie hard
-
What language are you interested in learning......
Sent from my SAMSUNG-SM-G920A using Tapatalk
-
Everyone is telling you to stop being lazy. I say FUCK THAT!
Every single programmer I know worth a grain of salt, is LAZY as all hell. That's part of what makes us programmers. The second part that makes us programmers is that we enjoy solving problems.
The best phrase I've ever heard for anyone wanting to learn a programming language is this: Don't learn programming, learn to solve problems.
If you don't have a problem that you're interested in solving, you're not going to enjoy the programming you're doing. If you're interested in a problem, you'll spend days learning how to solve it without even noticing the time, because you'll enjoy the process.
-
well spoken, but
spend days learning how to solve it
tends to be my definite understanding of NOT being lazy.
It's all a matter of view points, I guess. Some ppl say "it's not 'work', if you enjoy shit", but I'd disagree to that. Solving problems actually IS work, it's a whole shitload of; and true senses of pleasure mostly approach afterwards, i.e. after succeeding. But the solving process itself usually requires quite decent abilities of the "argh, shit drives me insane, but I'll never surrender for fucking reposes sake" kind. You know.
My POV.
-
You are both right, of course. Laziness is a perspective, and there is a fine line between efficiency and laziness.
Speaking from my own perspective and experience.
The more frequently I have to do something, the more likely I am to automate the process so I don't have to do it any more. That's both efficient AND lazy. The task becomes my problem, and if I can't do it by automating it completely or pressing a single button, I'm gonna be pissed that I actually have to do some work for once.
-
Some great posts, thanks everyone for the inspiration.
I'm back to programming and will be more persistent this time.
-
Laziness is the unwillingness to do work or expend energy. By spending the time and effort to automate you are not being lazy.....you would not be there drinking a coffee and watching tv all day....
Not being "lazy" whilst programming, no, but programming so that I can continue to be lazy once it's done. Drinking a coffee and watching things on youtube, browsing reddit is most of my day.
-
I feel sorry for you then. I can't imagine working in such an unstimulating job. I'd rather be working at mcdonalds all day than wasting my life youtubing and redditting.
Just because I'm browsing youtube or reddit, does not mean I'm not learning anything.
I'd rather be getting paid to learn, than paid to work.
-
Just because I'm browsing youtube or reddit, does not mean I'm not learning anything.
I'd rather be getting paid to learn, than paid to work.
Agreed. At my job I have around 8 to 9 hours of down time on may hands. Which is spent mostly reading RFC docs, other docs for python libs, linux man pages, etc...
-
8 or 9 hours of downtime? I don't know how long people work a day in your country, but thats the ENTIRE day where I'm from. If you have that much down time every day, you're being paid to do nothing.
And reading pydocs, man pages, rfc's, etc is a far cry from reddit and youtube. Learning is one thing. Wasting your life on youtube and reddit is another.
The life of a security officer ;-) paid to do literally almost nothing for more than minimum wage. That's why I've been on irc while I'm "working" if you ever notice I'm on for about 8 hours lmfao
Also techb, the problem I have is I can't just read docs on my phone, I need to be messing with it. Say I'm watching a udemy class, I can't just watch and retain I need to practice and move around in Android Studio. Also when im reading I find it hard to not try any of the code. How can you do that?
-
8 or 9 hours of downtime? I don't know how long people work a day in your country, but thats the ENTIRE day where I'm from. If you have that much down time every day, you're being paid to do nothing.
And reading pydocs, man pages, rfc's, etc is a far cry from reddit and youtube. Learning is one thing. Wasting your life on youtube and reddit is another.
I work 12 hour shifts for 3 days, the 4th day is a 6 hour so I get 42 hours a week. I technically get paid to drive around a mountain in a company truck and make sure nothing is on fire or stolen. Which, sometimes I do have to do things pending on what is going on. Like helping people with broken down cars of ATVs, running bears out of dumpsters and away from the workers, making sure shaft fans are running else the miners would suffocate underground. I've also been shot at from pill heads trying to steal copper. BUT, most of the time 'aint shit going on so hence all the down time.
I do reddit, but offline. There are plenty of subreddits for learning. Like TIL, news, world news, AMA's, and just the comments in general. I also dick off too, like watch movies and browse 9gag offline, youtube vids I download before hand and stuff. But the majority is docs and learning, cause it's what I like doing.
The life of a security officer ;-) paid to do literally almost nothing for more than minimum wage. That's why I've been on irc while I'm "working" if you ever notice I'm on for about 8 hours lmfao
Also techb, the problem I have is I can't just read docs on my phone, I need to be messing with it. Say I'm watching a udemy class, I can't just watch and retain I need to practice and move around in Android Studio. Also when im reading I find it hard to not try any of the code. How can you do that?
SL4A. Since I code in Python and do almost everything with Python I can test most stuff out. The stuff I can't test, like that requires root or internet or some lib that uses ctypes or something wont work, but I write the script anyway and test stuff that will work. Then, when I get home I can run and debug and shit. Makes it easier since at home I'm editing code instead of writing it all by scratch.