BUT WHY? THERE IS NO REASON FOR THAT SHIT.

Works on my machine and my 30 or so production node servers /shrug

Hahahahahahah

What a fuck

If i saw your shit in recent, i would of marked it as spam too

Definitely not

I get chu fam.

Nope. Nooope

Wtf stops you?

Sounds like you are working with assholes

Maps.google.com is probably much, much faster then anything anyone could make

Typically, refuse. Its not my fault marketting made terrible decisions.

I'm not going to fix their fuck ups.

Wtf is wrong with you

This is dumb on so many levels

Works on my computer :^)

Wooow, you found some public keys, congrats! /s

OP, really? Are you new to how public/private keys work?

The name REALLY says it all.

10-12usd...

HAHAAH GET FUCKED.

I'm curious to see the question

@theKarlisK
Thats what i write.

Helps when your computer isn't a PoS.

Been using ubuntu 18 since it got released. I'm never going back!

@SukMikeHok whats the point of abbreviation there?

Dude, testers are awesome. I wish my girlfriend was a tester.

Seriously, if you don't like testers or tests, then your a shit programmer.

@Brolls @monkeyname

Probably payments/banking.

I work for a pretty big payments company and do 6 figures, but thats in AUD. So /shrug

Dumb.

@Chill
I've been doing this for awhile... Our team still fucks it up so hard. Just less often :P

As the others said. Its okay to get it wrong, just on next sprint, go through the stories and figure out what blew up and why. Then apply that going forward.

So... Generally your story points are:

1- quick, you know what to do and its simple
2- you know what to do but theres a bit of work.
3- some knowledge of what to do, but there might be some minor unknowns.
5- not sure what to do and there are some unknowns -- feels like theres more work then a 3.
8- lots of work to do. Might have some unknowns
13- loads of work or loads of unknowns.
20- this is not a story to do work. But a story to make more stories.
40- you've failed at making stories.

So, its generally about taking your smallest task. Assigning a story point to it, and working from relativity.

With so many people in your team. I suggest having physical cards, having a set of numbers for each person.

Then all at once reveal what you think the story point should be. Then highest argues why, then lowest argues why, then revote.

I've interviewed quite a few those

OP, your reviewer is a tool.

@legacyJanitor

Im a bit confused... a&&b and a?b:null do different things, can i see an example?

Simple really. Do work at work, fuck around for the rest of the time. Its not hard.

I can dig it.

PUT A RING ON HER RIGHT THE FUCK NOW.

./CLAP.

God damn thats amazing.

But... Its a pretty fucking cool golf cart.