• 0 Posts
  • 9 Comments
Joined 1 year ago
cake
Cake day: July 7th, 2023

help-circle
  • Not necessarily. Also depends on competency of whoever is looking at using your software/investigating and the legacy of the things you described. A whole different scenario if it’s because you forgot to write something in a ticket and someone coming to call for help with docker when you have a docker setup guide they never look at.




  • Additionally, don’t copy and paste anything until you understand it. If you don’t understand what code golf is being spewed, don’t take the top answer. If you don’t understand any answer, you probably don’t understand the underlying systems well enough and need to re-evaluate what your asking for.


  • Ilflish@lemm.eetoProgrammer Humor@lemmy.mlMeetings
    link
    fedilink
    arrow-up
    4
    ·
    8 months ago

    Moving jobs I went from 1 meeting a week to multiple a day and all It has done is made me think my new job has no idea what is important priorities shift almost daily due to other meetings that I’m not a part of and nothing gets done properly because we dont have time to refine.

    The goal should be to have as few meetings as possible because it means they are unnecessary. If you have a plan for your backlog set, you don’t need to meet up for an hour every week to sort it out





  • Worked with a Japanese company has this and they refused to acknowledge anything as a bug if it didn’t get discussed in the spec. Oh, this new feature does not interact with the old feature well, just a limitation. Write that up as a new feature. It was killer trying to assign anything as a bug for this reason since you could only get them to fix stuff that explicitly contradicted their Japanese spec.