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

When i ask for a raise -

Boss : Are u joking ? I can see u hardly working.

When I ask for a leave -

Boss : Are u joking ? Who will do your work ?

I am starting to realise that there really is nothing more permanent than a temporary fix.

*spends day working on really hairy JS problem*
Boss: How is this any different from yesterday's product?

*cranks out an hour's shitty HTML*
Boss: Good job today, I'm impressed!

Manager: The thing you working on. We need this now! Like end of the week.

Me: Desirability is not do-ability.

Manager: く( ・◇・)ヾ？

Me: I am still in the middle of figuring out how to do things in the first place, so there are some technologies to research and some problems I yet need to solve. I am in no state to just write down my solution. I don't even have enough information to even estimate how long it is going to take. I am getting there. And yes, I can rush things, but need I remind you that you want solid data as a result that actually means something? As this is *why* this whole project was started. We have some old project doing the exact same thing, but whose output we don't trust. I wonder how that came to be. Additionally, this whole project was on hold for months until I took over. So I neither understand nor accept this sudden sense of urgency. And by the way, you recently added manpower to this project. And adding manpower almost always decreases the productivity in the beginning due to on-boarding and communication overhead. Last Monday, I didn't write a single line of code due to that. So no, this week will not do, as I am also on vacation starting on Thursday that was requested and was approved by you at the beginning of the year. See you in January.

So, our clients missed their internal deadline this weekend so we as vendor were also forced to work for the weekend and implement new features in a very short period. I implemented new features and my project manager stayed to support the testing and sent me home as I already had tickets bought for the movie.

As someone who hasn't done any developing in a long long time he even tried to implement some changes and complex JavaScript dom manipulation that they asked during testing so that I could be with my gf.

Few hours later he called me and with a sad voice said he is simply too slow and needs my help after all . I came and we stayed until 00h and solved everything. He paid for the movie and taxi.
The thing that impressed me was that he was willing to took over my job so that I wouldn't break my deal.

Best project manager ever!

P.S. Yes my gf went alone at the movie and yes we are still together xD

This is me at 5 in morning 😭😭

Just cut 2 seconds off the load time after roughly 2 months of refactoring. The code looks beautiful though.

How to troll your coworkers at the office - http://fakeupdate.net

If your coworker forgot to log off their system, you can prank them with fake update screen. Also has the option of BSoD *maniacal evil laugh*

My manager started a company and I was his first employee, he literally started it because he wanted to make use of my talent.

So one day I finished my project on Friday and took in advance Monday and Tuesday off. Went back Wednesday to find my manager angry like "you didn't finish your project, you costed us money with our client company (a big ass famous one) I am putting you on probation and you could probably get fired if you don't get yourself together" and he said that my colleague had to do my whole work that I supposedly didn't do.
So I went to the code and checked. And I found that what my colleague did was re write my code in a different structure and pretended like he did everything and did do anything.
Got passed off so I wrote an email to my manager with the commits and links to them and their builds and made sure it's well explained, and titled the email "resignation letter" with me expressing at the end how angry I am and informing about my resignation.
Later on he replied saying it was a misunderstanding and there was lack of communication and he could give me I raise.
I insisted.
One week later I got hired by the client company and suddenly I was sitting on the other side of the meeting table. And it felt so damn good.

For my passionate coders out here, I have some tips I learned over the years in a business/IT environment.

1) Don't let stupid management force you into making decisions that will provide a bad product. Tell them your opinion and why you should do it that way. Never just go with their decision.
2)F@#k hackathons, you're basicly coding software for free, that the company might use. Want to probe yourself? Join a community and participate in their challenges.
3)No matter how good you are, haters are common.
4)Learn to have a good communication, some keywords are important to express yourself to other developers or customers. Try crazy things, don't be shy.
5)Never stand still, go hear at other companies what they offer, compare and choose your best fit. This leads me into point...
6)if you've been working for over a year and feel that you have participated enough in the companies growth, ask a raise, don't be afraid...you're wanted on the market, so either they negotiate a new contract or you find another job.

I'm sharing these with you as I made many mistakes regarding these points, I have coded for free or invested so much time in a company just to prove myself. But at the end I realize that my portfolio is enough to prove that I'm capable of doing the job. They don't like me? Or ask me stupid questions that I can google in 5 minutes. I'll just decline the job and get something better. Companies end up giving me nothing in return compared to the work I have put into it. At the end after some struggles you'll find a good fit and that's so important for your programming career. Burnouts happen quite often if you're just a coding puppy.

If some of you still have additional tips be sure to post them under here

I am surrounded by incompetent fucking idiots, from the team lead that does a half arsed job at coding and then wonders why nothing further down the chain works to whole component teams that seem to be lagging so far behind they don't even know what the current code base looks like.

And who's in the middle of it all running around fixing all the problems these fucktards create, why yes it's me.

I would leave to let it implode and see what they'd do but I already know, they'd leave it till I got back so I could fix it all for them.

Feel like going around with a rolled up news paper and whacking each of them on the back of the head while screaming "no, bad code monkey, bad, fix your own bugs"

I hate being the go to fix it guy sometimes.

Found this on our project. I think that it is the best condition ever.

My work started working on an adult goods site and every once in a while I hear phrases like "Wait, go back to anal", " Can I take a look at sex toys", etc. We're all pretty professional about it, but I still get caught off guard when I hear those convos haha.

Hate when my boss says, "hey you, over there, can please automate this stuff, is a pain in the ass..."

A programmer

So you're behind a corporate proxy. What can go wrong will go wrong. Believe me.

No money no life!

Here's my piece of advice for new devs out there:

1 - Pick one language to learn first and stick with it, untill you grasp some solid fundamentals. (Variables, functions, classes, namespaces, scope, at least)

2 - Pick an IDE, and stick with it for now. Don't worry about tools yet. Comment everything you're coding. The important thing is to comment why you wrote it, and not what it does. Research git and start using version control, even when coding by yourself alone.

3 - Practice, pratice and pratice. If you got stuck, try reading the language docs first and see if you can figure it out yourself. If all else fails, then go to google and stackoverflow. Avoid copying the solution, type it all and try to understand it.

4 - After you feel you need to go to the next level, research best practices first, and start to apply them to your code. Try to make it modular as it grows. Then learn about tools, preprocessors and frameworks.

5 - Always keep studying. Never give up. We all feel that we have no idea of what we are doing sometimes. That's normal. You will understand eventually. ALWAYS KEEP STUDYING.