3
sjwsjwsjw
20d

when you don't know how to front end css and you get help from your tech leads and now you have to sit through the slow nitpicking of various dogshit mismatched overhangs and pixel jiggling that already exist in your product and may or may not be related to your ticket

well at least at the end of the call they helped you fix the shit for your ticket

Comments
  • 1
    It shouldn't, but it always amazes me how developers do this ... to other developers.

    Like you know folks did this kinda unfocused rambling / bikeshedding about other things to them and they hated it.... but they'll do it to other devs.

    DAMN IT PEOPLE FOCUS, fix problem 1, then let's talk about 2 through 9999.
  • 1
    @N00bPancakes
    True. Though there is the other side of the coin where people make a single mistake, and then continue to build on that mistake over time; the defect propagates. CSS is particularly bad about this given its inheritance structure.

    99 bugs on the wall
    Fixed one
    112 bugs on the wall
  • 1
    @SortOfTested

    Yeah there's certainly a time to coach about other things too. Particularly if 1 is related to 67, 68, 69 and so forth. Can't just ignore that.

    But I'm a big believer in answering the question first... then do the splain'n about how that leads into all the other things. Gotta meet folks where they're coming from

    Particularly when it comes to UI, just so easy for folks to get off track. Personally I have "no talking about the UI" rules at times if only to focus on "what do we want this to do / think of the logic here" and then we can talk about a button later on ;)

    Granted that has more to do with my personal experiences.
  • 1
    @N00bPancakes
    My approach tends to be:
    - hear the question
    - analyze the question
    - explode the question
    - check for fundamentals deficit
    - check for more critical failing contributing
    - prescribe xanax
Add Comment