Details
-
AboutAspiring Game Dev I started coding around 2012 and I still consider myself fairly new to it. Im a junior in college and I'm currently working on my very first real game, ASCII Adventure. It's a text adventure rpg type... thing.
-
SkillsFairly fluent in C++
Joined devRant on 11/18/2016
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
School course on C/C++ was so shitty I resorted to YouTube where I found this awesome channel called TheNewBoston10
-
Programming is 10% science, 20% ingenuity, and 70% getting the ingenuity to work with the science.2
-
Please don't comment in front of the code like this:
doSomething(); // does something
Please just stahp
Do this:
// does something
doSomething();
Much better and friendly for everyone10 -
when having a bug, instead of trying to prove, that you did everything right, start proving that you were wrong.
Then you'll get the yield earlier and you debug more efficient. -
Become a life long learner.
Learn new languages, they will teach you new tricks for your current one.
Have a personal project, it will help keep you level and forward focused when your day job just isn't doing it for you.1 -
(clicks on HTML tutorial video)
(ad starts playing)
"You need a website, why not do it yourself?!"
Arghhhhh that's exactly what I'm trying to do 😡9 -
I'm sure this has probably been posted before, but it never fails to drive me nuts, and customers never stop doing it, so:
Why do end users think "it's broken" is all they have to put into the support ticket?
It's a web app, not a goddamn pretzel.
If the turn signal on your car stops working, do you drop your car off at the mechanic, hand them the keys, and say "its broken, fix it!"?
While I'm on the topic, "I tried to do {x} and it gave an error" is better than "its broken", but still: why do you think what the actual error says would be completely irrelevant, especially when we put in the effort to give you relatively meaningful error messages?
I mean, is "there was a problem sending the email" so utterly gibberish to you that it is indistinguishable from "error: 0x000351e6"?
If so, I'm sorry, but you're too stupid to use a goddamn computer!5 -
When you go from compiling/testing code on every line change to not checking for hours and it just works when you run it.
😎
Not always, but sometimes. -
Today I learned: typing "man ascii" into the terminal on Linux will print out the ascii table.
Guess I don't need to go online to find it anymore9 -
Fuck yeah!!! After five days of fiddeling round in assembly without any sort of tutorial finally, im there :)16
-
Yesterday, I decided to rewrite the code of a project I'm doing for a week. I rewrote all the code with a better agility (is it the good word? ) and I ran it. It worked the first time! It worked the first tiiiiime!4
-
Will there be someday a messenger on DevRant? I think it can be good to continue some discussion in private and get to know each other.6
-
Focus on algorithms first and syntax last. Solve problems, then code.
If it uses power, has an I/O interface, and stores code, you can do stuff.
Dont get caught up in the little shit like specific code formatting and who's right or wrong between tabs or spaces. (It should be TABS anyway.)
Don't take shit from anyone.
Be confident not cocky.
Learn GIT as much as you can.
Don't burn out.
Get up and stretch.
Don't argue with your Operating Systems professor about why you shouldn't have to learn Linux.
Don't fall into the "I want to be a game developer" trap. Make your own games on your own time. You won't learn shit at school about it.
9/10 of the real world workforce is who you know, so don't be a dick. Those people might be the difference between Ramen noodles and steak dinner for you.
Charge market competitive rates and set an hourly rate that defines the clientele you deal with.
Don't ever, EVER, do trade or spec work. Free work don't pay the bills. Always start the clock when you're not sleeping, eating, or shitting. If you're emailing, calling, texting, or otherwise interacting with or on behalf of a client, bill them. Don't be a bitch when they decide they don't want to pay you. Get yours. Watch "Fuck You. Pay Me." at least once a month on YouTube.9