Hi, guys. :D
I just found an interesting simulation program IBM made. It’s a free simulator that teaches you how to program a robot and simulate it to battle robots made by other people!
Here’s the link: http://www.ibm.com/developerworks/java/library/j-robocode/
Learning to code with fun things like this in your spare time is a great way to learn programming languages. Once you get the basics down, you’ll definitely be able to move on into more interesting and challenging projects with code.
Hope this helps some of you.
No problem! Thank you for making that blog!
EVERYONE, FOLLOW http://lifeandcode.tumblr.com! She has many awesome programming tutorials and posts. :D
Yup! :3 Well, a lot of these are blogs run by programmers, but they do talk about programming a lot. mrlinux xplusplus syntaxcoloring codus jdeveloperblog 42codes mkstl Hope this helps. :D *If anyone runs any programming/design blogs, feel free to message me and I can add you on a blogroll or promote you. Thanks! <3
I LOVE YOU ALL.
deliarious, congrats on being the 200th follower! :D
“Problems” vary according to the person.
Usually it’s just something sentimental everyone experiences while programming. The concepts may seem simple, but applying them to certain assignments/exercises in class are what can make them difficult. I personally am not a fan of using recursion in Java. It’s not efficient at all, and most developers avoid using it.
Well, you seem pretty knowledgeable. Maybe you should make a tutorial site for all of us. ;D
“We’re switching to Waterfall next week…”
“Time to upgrade Eclipse!”
“3+ years of experience with Visual Basic, 3+ years of…”
“public static void ….”
“On the whiteboard, show me how you’d do [unlikely problem] in [unfamiliar language]”
“We’re gonna need you guys to work on some in-house software.”
“Can’t you use Java?”
Q: Can anyone help me with this problem?
A: nvm, I figured it out.
I know, right?
When I was a freshman in compsci in Algorithms class, my professor was awful. The guy in the Stanford U videos taught me everything I needed to know. I also linked his videos in the tutorial section on this site, but maybe I should link the playlist. :D
Glad to know it helps!
1. Wake up with an idea. Mull over it during
2. By 1 P.M., you’ve decided it’ll be a great way to get into that new language you’ve been wanting to try.
3. Hack out a few basic components. Get excited when they work beautifully.
5. Time for actual lunch. Come up with an extension to your idea that’s even more exciting than the original idea.
6. Get started on the extension, which spawns three more amazing ideas.
7. It’s 2 P.M., and the extension has become its own project.
8. It’s 4 P.M. and the components you hacked out before won’t play nice together. Ask Stack Overflow.
9. Incorrectly copy/paste your code into SO such that you’re missing a brace and the community thinks that’s your problem. It’s 6 o’clock. Tumblr break.
10. Read all the articles linked from the #programming tags. Read the articles they link to.
11. It’s 8:30 P.M., and you’ve got 11 tabs open. Not including Reddit and Tumblr.
12. Finish arguing over IRC about how Scala is the next big thing and oh maybe I should get back to that project.
13. 10 P.M.,
dinner ramen should be sufficient.
14. Open up vim and get back to that project.
15. *multiple “what the fuck” moments while reacquainting yourself with your 4-hour-old code*
16. “This is idea isn’t really that great anyway. I’m sure tons of people have tried and failed.”
17. Read xkcd/Cracked articles/TV Tropes.
18. “I’ll just get back to that project in the morning.”
19. It’s 3 A.M. and maybe sleep or something I guess but ycombinator and
20. goto 1
I thought so too at first! Glad I can unite all of us~ XD
I love how all of our sleeping patterns (or lack thereof) are alike.
I usually get submissions between 2:00AM - 4:00AM EST. :D