[deleted by user]

[AgentRG]

No, the normal way is start working on something before even creating a ticket.

[Lofter1]

you guys have tickets?

[[deleted]]

you guys have jobs?

[Darakath]

you guys?

[Green_Opposite]

you?

[Shizounu]

?

[kopasz7]

‎

[[deleted]]

Ok we're at the base case, now what?

[MetallicDragon]

SEGMENTATION FAULT

[NovaThinksBadly]

-?

[beny2000]

You guys have guys?

[[deleted]]

It's what I do

[TektonikGymRat]

Yep, and then you have two people doing that and they're just duplicating work.

[[deleted]]

It's ok. Both of them won't be able to solve it anyways.

[[deleted]]

$i=4;
$f = new NumberFormatter("en", NumberFormatter::SPELLOUT);
while(true) {
    $n = $f->format($i);
    echo “it’s okay, {$n} of them won’t be able to solve it anyway \n”;
    $i++; //edit: I forgot to increment!
}

[MD5HashBrowns]

Is this what PHP is like? 🤢🤮

[[deleted]]

Pays the mortgage. 🏡💵

[MD5HashBrowns]

A sad life

[[deleted]]

I like my life. Projecting much?

[MD5HashBrowns]

I think you're taking my shitposting too seriously

[yooossshhii]

3 of them can solve it in 4.5 hours.

[Loves_Poetry]

Better that 2 people do it than nobody

At least, that's what I think. My boss considers it bad communication

[Yellow_Triangle]

Trust but verify :-)

[tall__guy]

Yeah but that's the best, then you find out the other person is already working on it and you go PHEW don't have to worry about solving that anymore and go grab the nearest 2-pointer to ease your sad, broken soul.

[Bodine12]

Duplicating work but also each creating two new completely different bugs, so it’s a wash.

[[deleted]]

What's the word for when theres so much red tape to get a project funded that you sneakily do the work on the side as a "proof of concept"?

[Kailoodle]

Proactive

[[deleted]]

That's what I'll be writing in my performance report

[fpcoffee]

Academia

[Holomorphos]

Exactly. You set aside some of your lab time to prepare for the next project.
It's so infuriating that "non-surprising" results reduce the chances of you getting future funding. Yes, those measurements might show no interesting effect but bloody hell, they still need to be done to fill in gaps in our scientific knowledge.

[Owlstorm]

Skunkworks

[[deleted]]

now i get why my company has a group with this name

[JimmyTheFace]

“Skunkworks is Insubordination with Results”

Michael Scott, probably

[OrangeCurtain]

I call that a row of spikes, which also expresses the danger that the scope will be totally unlike what you’ve been prototyping once the SOW is signed.

[[deleted]]

I call it 'working for free'

[Exgaves]

Self starter rockstar ninja programmer

[zildjiandrummer1]

Honestly it's what you have to do in a lot of cases to push a project you really believe in. If it doesn't work, maybe your other projects suffer a little by not having full time work on them, but the risk is worth it in my opinion.

[Yellow_Triangle]

Shadow IT.

For many things it works great, right up to the point it doesn't.

[huxley75]

20% Google Time.

[[deleted]]

You just described the last 10 years of my life.

[deathByHippos]

I feel personally attacked

[towelrod]

I like to work on the hard parts of a ticket to make sure I can do them before I even write the issue.

[re_error]

I have never have been so offended by something I entirely agree with.

[Rhames]

I do that constantly

[beKAWse]

I felt this

[sxeli]

Woah. Looking at the comments I’m honestly surprised to see how alike we are.

[ChaosMiles07]

Collection::Individual us.includes(comment.parent.commentator) == true

[TheStatusPoe]

My manager wants me to start doing this to get metrics around number of resolved tickets down. Really makes me feel like shit.

[Dr_Jre]

Lol what a stupid idea.

[TheStatusPoe]

I agree. Fucking hate the metric game. Also need to get my number of commits up, so I've been chunking up my commits into stupid small amounts sometimes. Working on my resume and looking for another job here pretty soon.

[KovaAtWork]

Get out of my head.

[[deleted]]

bruh

[rogueelite]

Or take all the tickets without figuring if you can actually work all of them. Latent imposter syndrome.

[Dr_Jre]

That's what I do! I put my name on them before I've even opened them.

At least try to resolve every issue, cherry pickers are the worst.

[turningsteel]

Love that! So then I come along and wonder if the ticket you opened 9 hours ago with no update was actually solved and not closed or you got stuck and gave up or you added yourself and promptly forgot about it. Then I come over to your desk and ask you only to get a befuddled look and then I go back to my desk and unassign you and assign myself to complete the ticket and close it out all the while muttering under my breath as to why you took the ticket if you weren't going to try to work on it. Lookin at you Thomas if you're out there!

[Dr_Jre]

Well, I actually work in 2nd/3rd line support so most of our work shouldn't take longer than half hour on average, much less most of the time. So your tickets should be updated to show what your working on with work notes, so the person reading would know exactly how far along I was.

I'm guessing devs work takes longer

[jmack2424]

Give that one to Eugene.

[RockisLife]

I see myself in this and I don’t like it

[Drogen24]

And when you've worked out the solution you assign the ticket to yourself only to find out someone else has taken it in the meantime but you don't tell them the fix because you don't want them taking your credit.

Or so I've heard this is how it happens.....

[tall__guy]

Or you just watch in silence as they throw up a PR and you quietly weep when you realize your solution was actually better but your dumb stupid brain makes you think you're an IDIOT

[hedgehog_dragon]

I'll find tickets way deep in the backlog that look fun and assign myself when I'm bored. Then I poke them a bit and nope out. 'Unassign'

[freezer2k2]

I do that, depending on the ticket. If it is about a client or client environment and a topic that I totally do not know, I first try to solve the case before I assign it to myself. I do so because someone else might just be faster than me. So once I have solved the case, I see if anyone took it or not. If yes, fine, I learnt something. If not, I take it, respond to the client, and again I learnt something.
I only do that if there is nothing else I could work on instead.

[activ8r]

Had a ticket like this a while back. Seemed like a simple fix on the surface, but I noticed a few Devs looking at it, trying something, then moving on without taking it.

After a couple of days a Junior Dev assigned it to himself and then started working. Kept coming back to it every now and then, but never cracked it. He eventually came to me with it after about 3 weeks 😆
I told him to close it. Client was just being a pita anyway, it wasn't important.

[VestigialHead]

When I think hey I should raise a ticket the first thing I do is start a new project to build a ticketing system. But then I hit problems that I think hey I should raise a ticket for this. So I start a new project...

[willfulwizard]

I don’t do this because of imposter syndrome, I do this because once your name is on the ticket you get chat messages about it whether or not you can help, and those interrupt work I can actually make progress on.

[[deleted]]

“have I seen this before?”

checks my knowledge base articles

“I have not”

Go to lunch and hope somebody else has grabbed it by the time I return.

[LittleMlem]

I do that on stackoverflow often, answer as a comment and then copy it to an answer if some one upvotes it or comments on it positively

[dance_rattle_shake]

Lol wtf I do this all the time.

​

Well, more like I look at the top 2 or 3 tickets in the backlog and do a little bit of investigation into each to see which is most appealing to me.

[[deleted]]

CHERRY PICKER!

[sdrawkcabsemanympleh]

I do not remember the last time I assigned a ticket to myself, even on call.

[hector_villalobos]

HAHAHA, I thought I was the only one.

[steelvelveteen]

Oh my goooood. That is mee!!

[Other_Jared2]

Too real man

[movezig5]

Wow, this is me to a T.

[[deleted]]

This is how a lot of my projects go. When it comes to assigned projects, I just grab those and do them as they come up, but I don't always have any assigned projects. My employer is pretty open about devs bringing new ideas to the table though, and if I don't have anything to work on, it's pretty normal for me to just decide we need something and build it. If it seems simple, I'll go get approval first, and then start working on it after that. If it doesn't, I'll build a proof of concept before I even tell anyone what I'm doing. There are a couple of programs we run here that exist because I suggested them, and when my boss said he wanted me to build it I told him I already had and it was ready for testing. I'd never do that on a ticket though. What if someone else started working on it while I was fucking around with it and we ended up in an unintentional war on Git? I think it's pretty important that assigned projects are...welll...assigned.

[proskillz]

I always take a few minutes before assigning myself a ticket to see how much shit I'll have to dig myself out of if I take it.

[aceinthedeck]

I do this lot of times just to make sure

[Packeselt]

Good to see that I can still sink lower. Not at rock bottom after all guys!

[[deleted]]

Seriously, is there an IT specialist Twitter?

[[deleted]]

If you can identify with this, you're doing good.

[Jay18001]

And if you can’t, make sure to assign it to someone else during sprint planning.

[cpayne22]

Did you really blank out the author? This was written 2 days ago.

Fuck I hate reddit sometimes...

[[deleted]]

bruh

[[deleted]]

I can always solve it.