Website down 🤔
Does this mean an update is coming 🤔

My fellow coworker's commit history of last 24 hours. And my boss was surprised when I told him I'm leaving the company..

All this talk about Kotlin, scala, groove....

Typing 'ls' in the CLI, then realising you're using CMD. *Sigh*

KISS.
Keep it simple, stupid.

At the beginning the project is nothing but an idea. If you get it off the ground, that's already a huge success. Rich features and code quality should be the last of your worries in this case.

Throw out any secondary functionality out the window from day 0. Make it work, then add flowers and shit (note to self: need to make way for flowers and shit).

Nevertheless code quality is an important factor, if you can afford it. The top important things I outline in any new non-trivial project:
1. Spend 1-2 days bootstrapping it for best fit to the task, and well designed security, mocking, testing and extensibility.
2. Choose a stack that you'll most likely find good cheap devs for, in that region where you'll look in, but also a stack that will allow you to spend most of your time writing software rather than learning to code in it.
3. Talk to peers. Listen when they tell that your idea is stupid. Listen to why it's stupid, re-assess, because it most probably is stupid in this case.
4. Give yourself a good pep talk every morning, convincing you that the choices you've made starting this project are the right ones and that they'll bring you to success. Because if you started such a project already, the most efficient way to kill it is to doubt your core decisions.

Once it's working badly and with a ton of bugs, you've already succeeded in actually making it work, and then you can tackle the bugs and improvements.

Some dev is going to hate you for creating something horrific, but that horrific thing will work, and it's what will give another developer a maintenance job. Which is FAR, far more than most would get by focusing on quality and features from day 0.

This guy at my last internship. A windows fanboy to the fucking max!

He was saying how he'd never use anything related to Linus Torvalds because he hated him for creating Linux.

Two seconds later I saw him initializing a new git repo.

I was standing there like:

*should I tell him?*

😅😆

Hahaha

Java to Javascript is what Car is to Carpet.

GET THAT ASSHOLES, YOU FUCKERS

1 minute of Thread.sleep() for Tum, the best cat ever. Rest in peace, your memory will live on in my devrant avatar.

Why not! 😂

i -= -1

When u break up with ur girl n she ok with it

What is really hidden behind iPhone 8...

Rip iPhone
Miss u jobs

C# Programmer 😂😂😂

My friend: After a week of coding finally added 500 lines, now i have 1000,I'm so proud . How is your project going?
Me:

Sudo don't listen to me

Worst advice: "Forget Android, specialize on BB10, that's the future'

Sometimes I stare at the screen with my void eyes, questioning my abilities and say with a shivery voice "WTF" and refresh the website.

Then it works again.

Sorry for two memes a day, but I'm fairly certain we've all experienced a situation where we've wanted to use this response.

‎100% reliable test for HTML5

Yippppeeeeeeeee!
Guess who got a new MacBook Pro 2015 15" model 😍😍😍😍

NOT A RANT

Any Rick and Morty fans up in here :) ?

‎Ways of doing a for loop.

Explain recursion

Yeah okay

Study Finance they said... u don't need CS....

http://ozy.com/acumen/...

JavaScript logic.

Something like that..

This is just perfect 😂

I was a little too harsh on a colleague today.

He asked to help him get something working... After looking at it for a bit, I asked: "I don't get it, what have you been doing all day? Yesterday we split this element into two separate divs, and it worked perfectly, now I've see you've moved all the styles back to the container and there's only one div. The easiest way to get this to work properly is to simply undo everything you've done today."

He looked at me with puppy eyes and I realized I was too harsh. He wasn't _trying_ to break everything, he just hadn't understood why we split the element into two divs. So I lowered my tone a bit, and explained everything again, from the start, then did it again together with him and made sure he understood the separation.

But I still feel bad for how I talked to him. It's not like I shouted or cursed or anything (and I curse a _lot_ when talking about code). It was just condescending as fuck, and belittling. As if I was mocking him for not being as experienced as I am.

I'll do better next time.