I did not create this and could not find a link to true creator. Still pretty funny though

How would you start to change the world through code?

!rant

What's your dream GSDR/GWDR setup?

(Get shit/work done room)

Spacious desk, three 21" monitors. MacBook Pro laptop and windows/ubuntu desktop.

A nice big dry erase or smart board on the wall.

Hardwood/hard carpet floors.

One empty wall so that I may bounce a tennis ball against it while I contemplate.

Electric piano.

A tough padded bench for naps and laying down to change perspective.

Very good lighting.

Close proximity to a gym.

I guess I'll have to move out of my parents first though 😅

I now understand the double tap feature. It's really useful when your reading devRant while eating.

!Rant

Lessons from this picture:
1. Not all opportunities are to be taken. Some are traps.
2. A person can become so determined to destroy another person that they become blind and end up destroying themselves.
3. You fight best in your natural element and environment. Here the bird has advatange in his natural element.
4. Know your limits, we all have them.
5. Sometimes the best response to provocation is not to fight.
6. Sometimes to accomplish something you need team work, you will not always win alone.
7. Stick to what you do best and don't pursue what will kill you.

👍🏻👍🏻👍🏻

If you ever feel you're not self-confident enough, think about the guy who told his manager at Google about the great idea he had been working on: a T-Rex that jump over cactus when there's no internet connection in Chrome.

!rant

After over 20 years as a Software Engineer, Architect, and Manager, I want to pass along some unsolicited advice to junior developers either because I grew through it, or I've had to deal with developers who behaved poorly:

1) Your ego will hurt you FAR more than your junior coding skills. Nobody expects you to be the best early in your career, so don't act like you are.

2) Working independently is a must. It's okay to ask questions, but ask sparingly. Remember, mid and senior level guys need to focus just as much as you do, so before interrupting them, exhaust your resources (Google, Stack Overflow, books, etc..)

3) Working code != good code. You are an author. Write your code so that it can be read. Accept criticism that may seem trivial such as renaming a variable or method. If someone is suggesting it, it's because they didn't know what it did without further investigation.

4) Ask for peer reviews and LISTEN to the critique. Even after 20+ years, I send my code to more junior developers and often get good corrections sent back. (remember the ego thing from tip #1?) Even if they have no critiques for me, sometimes they will see a technique I used and learn from that. Peer reviews are win-win-win.

5) When in doubt, do NOT BS your way out. Refer to someone who knows, or offer to get back to them. Often times, persons other than engineers will take what you said as gospel. If that later turns out to be wrong, a bunch of people will have to get involved to clean up the expectations.

6) Slow down in order to speed up. Always start a task by thinking about the very high level use cases, then slowly work through your logic to achieve that. Rushing to complete, even for senior engineers, usually means less-than-ideal code that somebody will have to maintain.

7) Write documentation, always! Even if your company doesn't take documentation seriously, other engineers will remember how well documented your code is, and they will appreciate you for it/think of you next time that sweet job opens up.

8) Good code is important, but good impressions are better. I have code that is the most embarrassing crap ever still in production to this day. People don't think of me as "that shitty developer who wrote that ugly ass code that one time a decade ago," They think of me as "that developer who was fun to work with and busted his ass." Because of that, I've never been unemployed for more than a day. It's critical to have a good network and good references.

9) Don't shy away from the unknown. It's easy to hope somebody else picks up that task that you don't understand, but you wont learn it if they do. The daunting, unknown tasks are the most rewarding to complete (and trust me, other devs will notice.)

10) Learning is up to you. I can't tell you the number of engineers I passed on hiring because their answer to what they know about PHP7 was: "Nothing. I haven't learned it yet because my current company is still using PHP5." This is YOUR craft. It's not up to your employer to keep you relevant in the job market, it's up to YOU. You don't always need to be a pro at the latest and greatest, but at least read the changelog. Stay abreast of current technology, security threats, etc...

These are just a few quick tips from my experience. Others may chime in with theirs, and some may dispute mine. I wish you all fruitful careers!

I think devRant should have a feature to not procrastinate, you will need to enable it somewhere in the settings. So if it detects you are using devRant for too long it will prompt a dialog to tell you to stop procrastinating.

BTW, I think this will be the first app to deliberately try to get users out of it XD

There are 10 types of people in the world: those who understand binary, those who don't and those who didn't realize the joke was in base three.

Did this on my first programming exam.

int index = 0
int value = 0
try {
while true {
value += array[index]
index++
}
} catch NullPointerException {
System.out.print("Sum: " + value)
}

The task was to add together all numbers in an array.

I somehow aced the exam, but got called in to teachers office this is not the way to use exceptions.

when you have some problems and see

You know you're getting old when you have to increase the font size of your editor... 😫

One component is used over 30,000 times. How many unit tests do you think we have for it? Zero. Fucking zero, Zip, Zilch, Nada, None.

WHAT THE QA FUCK!?