Details
-
SkillsC
-
LocationSão Paulo, Brazil
Joined devRant on 10/8/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
-
Java
It's my favorite language because I started learning programming in Java when I was in school.
The most annoying thing in Java is I don't feel like writing System.out.println each time.12 -
found this gem today.
P.S.
captcha - Completely Automated Public Turing test to tell Computers and Humans Apart.
ahh, seems promising!!3 -
Blisk, a browser with multiple device testing for developers, went from free to subscription model.. Time blocking features that they offered before, for free.
That's suicide. That's how you lose your install base...
Just deleted it and went back to http://material.io/resizer.3 -
Use that Tab button. It's there for a reason. If you are too lazy to use it then use an IDE that formats the code.
Also learn to comment your code wherever needed and in English. If you don't know where it's needed, Google is your friend if not your senior. -
Linus Torvalds, while writing about the future of Linux in his autobiography 'Just For Fun', said Linux will be used in cell phones in near future. He wrote this in 2000. After 16 years, we see Android (based on Linux Kernel) in over a billion cell phones! What a visionary! Makes me wonder!3
-
You should leave undefined to the browser and keep null for yourself.
Don't '' var keep = undefined; ",
Do " var keep = null; "1 -
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 -
Use .editorconfig files when working with multiple developers. Otherwise your file encoding and code style will get fucked up eventually.
-
#include brain.h
/* Hello world. I am new to this community and just wanted to announce. I am here! About me? I am a student from Hannover in Germany and some dudes told me about this social app. Currently we are learning basics of C (I guess it is version 89) */6 -
Needs repeating:
Q: Why do programmers always get Halloween and Christmas mixed up?
A: Because Oct(31)==dec(25)2 -
0. Plan before you code. Document everything. You won't remember either your idea or those clever implementations next week (or next month, or next year...).
1. Don't hack your way through, unless that's what you intend to do. Name your variables, functions etc. neatly: autocomplete exists!
Protip: Sometimes you want to check a quick language feature or a piece of code from one of your modules. Resist the urge to quickly hack in the test into your actual project. Maintain a separate file where you can quickly type in and check what you're looking for without hacking on your project (For example, in Python, you can open a new terminal or IDLE window for those quick tests).
2. Keep a quiet environment where you can focus. Recommend listening to something while coding (my latest fad is on asoftmurmur.com). Don't let anything distract you and throw your contextual awareness out of whack.
3. Rubber ducks work. Really. Talking out a complex piece of logic, or that regex or SQL query aids your mind greatly in grasping the concept and clearing the idea. Bounce off code and ideas with a friend or colleague to catch errors and oversights faster. Read more here: https://en.wikipedia.org/wiki/...
4. Since everyone else is saying this (and because it merits saying), USE VERSION CONTROL. Singular most important thing to software development aside from planning and documenting.
5. Remember to flout all of the above once in a while and just make a mess of a project where you have fun throwing everything around all over the place. You'll make mistakes that you never thought were possible by someone of your caliber :) That's how you learn.
Have fun, keep learning!3 -
There is no shame in using google to program.
'Back in the day' we had phonebook sized books of documentation on our desks we would reference constantly.
Why?
No one is going to memorize a phone book sized book. Not to mention three or four of them.
Being a good dev is about creativity, not memorization.12 -
After having put up with 5mbps at home for months (naked dsl), finally decided to ring up and see if there was an issue. Turns out there was! All fixed now. Speed now more than triple what it was before. Aw yeah.12
-
well a 🖕🏼 to everybody who thinks CSS isn't really "coding". Stop shaming CSS and people who love it because the moment you would be asked a simple alignment problem, you'll shit your pants.
No! not because it's a hard thing to do in CSS(there are tons of ways to do it.) but because you are ignorant and have prejudice.
🖕🏼 you again!12 -
Hello, would you like to hear a TCP joke?
Yes, I'd like to hear a TCP joke.
OK, I'll tell you a TCP joke.
OK, I'll hear a TCP joke.
Are you ready to hear a TCP joke?
Yes, I am ready to hear a TCP joke.
OK, I'm about to send the TCP joke. It will last 10 seconds, it has two characters, it does not have a setting, it ends with a punchline.
OK, I'm ready to hear the TCP joke that will last 10 seconds, has two characters, does not have a setting and will end with a punchline.
I'm sorry, your connection has timed out... ...Hello, would you like to hear a TCP joke?11 -
1. Set your podcast player to 0.5x speed
2. Listen to your favorite dev podcast
3. Imagine they're all drunk
4. Profit -
1. Start programming to solve a beautiful problem.
2. Setting up my IDE.
3. Creating nem project.
4. Start coding, but dig into first little problem.
5. After 10 hours give up.4 -
Windows 10 just randomly rebooted for updates while I was typing. Code. Into Visual Studio. WITH LOTS OF UNSAVED CHANGES!
W. T. F. MICROSOFT? How could you even call this a "product"?!4