My dumb CEO just hired an even dumber CTO. The new CTO asked me the following questions...

1. What is GitHub?

2. What is JSON?

3. What’s an array?

4. What is Get and what is Post?

5. When an iPhone is offline, can it call an API on our server to tell us it’s offline?

6. I know you’ve spent 11 month the writing this backend in PHP but can you change it to Java now?
Me: Why?
Dumb CTO: Because it’s better.
Me: How?
Dumb CTO: because it is.

7. I know you’ve started to rewrite this codebase I Java but can you convert it to Node.JS now?
Me: Why?
Dumb CTO: Because Facebook uses it.

8. What is MySQL? Why aren’t you using a database instead?

9. What does NULL mean?

Somehow, I doubt that asshole is remotely qualified for the job.

Fakin shyt for brains.

GF: What are you doing there?
Dev: I've been trying to reproduce a bug for two hours now...
GF: You need two bugs the opposite sex, otherwise they won't reproduce.

From a sad true story.

My first poem for programmer girl 😘😘😘

My life is incomplete without you,
You are semicolon of my life

You are my increment operator,
you make my value increases

I am username and you are my password,
without you No one can access me

You are my initializer,
without you my life would point to nothing (NULL or “0”)

If I were a function you must be my parameter,
Because I will always need you

Can you be my private variable?
I want to be only one who can access you

You are my compiler,
My life wouldn’t start without you

You are my loop condition ,
I keep coming back to you

My love to you is like recursive function,
It will never ends & Will never enter into infinite loop

Forever and Ever

try {
♥️
}
catch(e) {
🍺
}

#happyvalentinesday

My girlfriend doesn't talk to me anymore after I said I helped the new girl to do some penetration testing.

Had to explain the difference between front and backend.

Restaurant:
Waiter == frontend
Cook == backend

Today I come across something interresting in SQL Server.

I was optimizing a report query and in the SSMS windows runned in 10 seconds for 3000 rows.

Put it to a stored procedure took me 5 minutes for getting 100 rows.

I was like WTF?

After some research I found out that the problem was that I was using the Stored Procedure parameters in the query.

Created local variables for the parameters and poof... 10 seconds again.

So if you are creating Stored Procedures in SQL Server DO NOT USE THE PARAMETERS FROM THE PROCEDURE. CREATE LOCAL VARIABLES.

Thought I would work on a side project this evening to make my life easier at work. *spends the next 4 hours setting up my works dev environment at home.*