Waiting to see if anyone notices

Sleeplessness !

I 😍 non-ascii characters, how about u?

That pain

"I will go to sleep after i fix this bug" 10min later I look outside, North Korea and the USA are fighting a nuclear war, russia invaded europe, hitler rose from the death and there's even more javascript frameworks

Interview went well until i asked my questions about them.

"Are pet-projects a thing in your company"
... no.

"Can i attend programming gigs in a workweek, and are they paid by the company"
... no, no

"Any restrictions on the IDE"
... yes we only allow visual studio
"Wait, frontend web development in vs?"
... yes

"Do you develop in other languages then JavaScript"
... only Java

I calmly stood up, told them "I dont think that the company and I are a good fit. Thanks for your time."

Me brute forcing into the appartment (where i rent my room) modem:

*tries all most easy/logical combinations*

Nope.

*tries more difficult ones*

Nope.

*hmm.... no please not both just blank....... 😷*

Admin access granted.

😩

(Years ago)

Me: I just found out, "Co-worker X" is making 15% more than me, despite him being a shitty developer and putting us 2 weeks behind schedule? Not fair. I did about 70% of the work on this project. I want a raise of 30% to make me feel appreciated at least.

Boss: Well, unlike you, he's already finished college and has a degree in software engineering. It's a company thing to base salaries on educational attainment.

Me: I have two weeks left on my contract, after that I'm gone. I hope his degree will help you meet the deadline.

* Product was delivered two months late, buggy as hell and the company faced penalties and other crap.

> finds awesome software
> finishes trial period
> looks at pricing
> looks at bank account
> cries in a corner

Code comments be like....

When your boss wants it done now but you're on vacation

When you get a little confused

I hope they know what they're doing!

When you prove its a hardware probelm

Wait... Why didn't anyone thought about that?

Interviewer: what leadership experience do you have

Me: 3 years experience in an administration position

Interviewer: Good, where?

Me: in a WhatsApp group

Q:What's more dangerous than no documentation ..

A:Wrong documentation ..

To the new devs:
Never push production on friday

So...

It seems that I am building a toolbar for IE11.

Send me your wishes and love.

P.S. Not a joke

Sales employee Bob wants a clickable blue button.

Bob tells product owner Karen about his unstoppable desire for clickable blue buttons.

Karen assigns points for potential and impact (how much does a blue button improve Bob's life, how many people like Bob desire blue buttons)

Karen asks the button team how hard it is to build a button. The button team compares the request to a reference button they've built before, and gives an ease score, with higher score being easier (inverse of scrum points).

These three scores are combined to give a priority score. The global buttonbacklog is sorted by priority.

Once every two weeks (a "sprint") the button team convenes, uses the ease scores to assign scrum points. Difficult tasks are broken up into smaller tasks, because there is a scrum point upper limit. They use the average of the last 5 sprints to calculate each developer's "velocity".

The sprint is filled with tasks, from the top of the global button backlog, up to the team's capacity as determined by velocity. Approximate due dates are assigned, Bob is a happy Bob.

What if boss Peter runs into the office screaming "OUR IMPORTANT CLIENT WANTS A FUCKING PINK BUTTON WHICH MAKES HEARTS APPEAR"?

Devs tell boss to shut the fuck up and talk to Karen. Karen has a carefully curated list of button building tasks sorted by priority, can sedate boss with valium so he calms the fuck down until he can make a case for the impact and potential of his pink button.

Karen might agree that Peter's pink button gets a higher priority than Bob's blue button.

But devs are nocturnal creatures, easily disturbed when approached by humans, their natural rhythms thrown out of balance.

So the sprint is "locked", and Peter's pink button appears at the top of the global backlog, from where it flows into the next sprint.

On rare occasions a sprint is broken open, for example when Karen realizes that all of the end users will commit suicide if they don't have a pink heart-spawning button.

In such an event, Peter must make Bob happy (because Bob is crying that his blue button is delayed). And Peter must make the button team of devs happy.

This usually leads to a ritual involving chocolate or even hardware gift certificates to restore balance to the dev ecosystem.