Welcome to android where Progress Bars are Spinners and Spinners are lists.

"Aah, time to make a new Android app"
*starts Android Studio*
AS: "Yo yo yo, before you proceed, update all these 512 things in your SDK"
*creates a new Activity*
AS: "Nuh uh, this shit won't work without this, install it"
*runs app on emulator*
AS: "Hoooold your horses, you need to install this, and this, and update this and this.. oh and also that"
*emulator finally runs, app crashes*
AS: "Ohh, ha ha, oopsies, your Gradle config is also screwed up, change every dependency to the newest version and then update them all"
*config finally done, runs again*
AS: "Umm, I am too lazy to sync it myself, so you must press the nice big button on top to sync it"
"Fuck this"
*closes Android Studio*
AS: "WAAAIT WAIT, before you go, a new Android update just showed up, you must upd..."
*alt+f4*

Date and time is not as simple as I thought they were

Copy & paste code. 😬

I always forget to commit my changes and then when someone reminds me, I usually commit 1 weeks work in one single commit.

when you're done with your code and user requirements change again.. :/

It's simple really...

Never make the same mistake twice.

There are so many new ones, try a different one each day.

One of many things my non-programmer friends needs to learn!

OMFG if I see one more single-lined if-else/for statements without proper closure brackets I'm gonna kill some people!!!

Happy Singleton's Day

1. take a screen shot of the desktop (wallpaper and icons)
2. take all icons and put them in a folder
3. set the screen shot as the wallpaper
4. hide the folder containing all the icons in the wallpaper
5. hide the task bar

My stupid TL was fighting for 20 min before begging me to fix my prank

:') remember this game?

When you've been away for two weeks...

"Whenever I see a door that says push I pull first to prevent conflicts"

Learn to debug, breakpoints are your friends. Never ask someone help without trying yourself to debug your code.
Debug an existing code is, I think, as important than being able to write your own code.

Comment your code ! Co workers and your future self will appreciate ! #wk26

There is always someone who posted your problem already on stackoverflow. Find him.

Thanks Google. We now have a color picker for hex, rgb and more in the Google Search.

2nd worst part of being a dev?

"It should only take 5 minutes"

5 hours later: "aaaaannnddd done."

Worst part of being a dev?
Unanswered stackoverflow question that exactly matches your problem

You know you have too many tabs open when chrome looks like a mountain range.

My teacher shouted at me - "Go to hell".
What really hurt me was 'goto'.

The best part of being a dev?

Want something?

It doesn't exist?

Build it yourself!

It feels like a superpower. :D

I wonder how a bug report on devRant may look like.
Something like a bug report and a fix on the same email?

If apple made a car, would it have windows?

First, solve the problem. Then, write the code.

Who has influenced most in your work?DEADLINE

My first boss. He sat next to me yelling “Think before you code“, “Hands away from the keyboard“ and stuff like that at me while doing my first few codings ever. He even made me cry from the pressure. Afterwards he bought me a muffin and told me he wants me to be a better programmer than he ever was

*starting a project*
"Okay so this has to be perfect"
*an hour later*
"Welcome to the jungle..."