27

I've been working on implementing a fairly large feature on a project at work--

**Sorry. I should rephrase that**

I've been *trying* to work on implementing a fairly large feature on a project at work.

It's slightly complicated because I'm not as "in the know" with the project as I should be. I get tossed around projects a lot as the only designer+developer so I've got my hands in a lot of buckets... Or git repos I should say... My source tree has a lot of tabs open and each project is run by someone with their own ideologies on how stuff should be done and laid out and what not. Basically jumping between these projects leaves you mildly capable on all of them but not amazing at any of individual one them--

--I digress.

There's a bug I've been trying to fix.
--Stupid simple bug, literally just a casting issue or something but there's so much data in this one object that it's taking a few solid minutes of concentration to figure out which variable is busting it all up. It shouldn't take long to fix...

But it has. It has taken 4 days.

FOUR. DAYS.

...To fix what is basically a null reference exception.

Every time I sit down to work on this bug real quick I get pulled away to do a wireframe or change a flow chart or diagram or colour or print styling.

Every. God. Damn. Time.
4 days. Soon to be 5.

My commits are real low at this point guys.

Please boss man, just let me code...

Comments
  • 9
    Try to get a whiteboard where you write down all current assignments and who requested it.

    Whenever you get a new one write it at the bottom of the list.

    If they need it prioritized they at least see exactly what gets down voted.

    Might help.
  • 3
    @Voxera that's not a terrible idea! Although I find everyone needs everything prioritized haha
  • 3
    @IDontGiveADuck point is they see everyone else’s requests.

    Ask them to get permission from all above them first ;)
  • 2
    @Voxera right! True :)
Add Comment