Details
-
AboutSoftware Engineer
-
SkillsC/C++
-
LocationOrlando, FL
Joined devRant on 4/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
-
When you spend hours figuring out where the bug is, with no luck, and then you wake up in the middle of the night knowing exactly what and how to fix...3
-
When I drink and code at home I put "while drunk" at the end of a commit so I know which ones to look back over later. This system worked great for me until yesterday when I included that in a PR for a work repo.8
-
When you accidentally leave a console.log in your code that goes into production that says: "I'm fucking working!!!" and notice it a year later when fixing a bug.2
-
you'd think by now people would understand version control. a whole days work gone because of bad merging.4
-
Laughing about avoiding Windows update and publishing a meme about it on slack
Devops guy runs a remote cmd to my computer to restart and update
Me waiting for 30 mins
Conclusions : " avoid it silently"2 -
Client: we love Internet Explorer, can you show me how the best way to use it?
Me:
Step 1: Open Internet Explorer
Step 2: Search & download Chrome.
Step 3: Close Internet Explorer
Step 4: Move Internet explorer to the bin.
Step 5: Never talk about using Internet Explorer again.3 -
There is a special place in hell for people who drink the last of the coffee and don't make a new pot!3
-
when you're dead tired but can't fall asleep until you figure out this piece of code. then once you figure it out, you're so pumped you can't sleep. fml. catching up on devrant it is then2
-
How to be a successful developer:
1. Identify a problem that you don't know the answer to.
2. Spend 10 minutes searching Google for a solution, trying various keyword combos.
3. Click the link to the solution in Stackoverflow.
4. Find the solution with the most +1's.
5a. If solution looks good, implement the solution in your code.
5b. If solution is not applicable, return to step 2.
6. Test your implementation.
7a. If the problem is solved, bask in the glory of success and return to step 1.
7b. If the problem is not solved, move your hand vigorously through your hair, pulling out several strands. Exhale loudly. Next return to step 2.4