You know what I realized we should always say no for demo driven application development.

We should always ask for enough time do a proper development and if its not enough, shouldn’t write a single line.

Because once we deliver a working demo. Its release ready for them because its FUCKING WORKING..

And trying to explain why this is just a demo and cant be put to production is even bigger pain in the ass than saying no in the beginning.

LESSON LEARNED .

An SQL Query walks into a bar and sees two tables. He walks up and asks, 'Can I Join You?'

Interviewer: Question 1: What's the most important skill of a software developer?
Me: Thanks for the opportunity, I'll show myself out.

8th day on the job:
1st Project: 90% done.
2nd Project: 5% done.
3rd Project: 5% done.
4th Project: not started.

I think I will be burned faster than I expected

I'm curious..

When does programming suck for you, and when is it fun?

Like I hate programming, when I run into an obscure use case that opens up some serious errors with my some, or gasp, all, of my architecture and forces me to rethink everything - especially DB design, ugh.

I love programming when my architecture and DB design create naturally readable code and everything falls into place and I feel like a genius.

I guess, in short.... plan before you code?

And then, plan again.

But don't plan too much.

The love/hate of my programming life summed up right there I think.

How about you?

Windows is like a submarine... as soon as you open a window, the problems start.

Me after discovering devrant

On the last working day of our CEO.
CEO: As a software company, if we are to build an airplane would you ride on the airplane that we built?
Everyone was silent.
Me at the back of my head: I'll ride. I know for sure that the airplane will never start.

Created an account on Juststickers.
This is the email I get