• Whitebrow@lemmy.world
    link
    fedilink
    arrow-up
    39
    arrow-down
    2
    ·
    1 year ago

    The programming team that is working hard on your project is just one dude and he smells funny. The programming team you’ve met in your introductory meeting are just the two unpaid interns that will be fired or will quit within the next two months and don’t know what’s happening. We don’t do agile despite advertising it. Also your project being a priority means it’ll be slapped together from start to finish 24 hours prior to the deadline. Oh and there will be extra charges to fix anything that doesn’t work as it should.

    • Littleborat@feddit.de
      link
      fedilink
      arrow-up
      9
      ·
      1 year ago

      I think we work in the same company, the dude does not smell funny to me but maybe that’s just me.

    • Punkie@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      edit-2
      1 year ago

      A lot of outsourcers do this. Here’s my experience with a few companies.

      • The “team” you meet are competent, English speaking fronts. They are the demo models of the people who will work on your projects.
      • After the contract is signed, these people are swapped out with randos of varying competence.
      • In some cases, some of these randos are further hidden behind aliases: people with names that are actually more than one person sharing logins and passwords.
      • They will string you along, trying to charge maximum hours worked without regards to product or services delivered.
      • Most of these companies have a “bucket of crabs” mentality: the managers are horrible, the staff incompetent, and once the gain some skill, they leave for better companies. They backstab one another, hijack projects to fuck over coworkers, and lie and cover their tracks. Some of this is cultural, like a caste system, while some are just racist.

      At one time, these people were pretty good, but they realized they had skills and left for other countries for better pay and better working conditions. The bids got more and more competitive, cutting costs until they were literally filled with low-skilled labor who can’t be promoted or leave for economic or competence reasons.

    • gjoel@lemmy.ml
      link
      fedilink
      arrow-up
      6
      ·
      1 year ago

      When you have a great programmer working on your project he will be cycled to a new project in 2-3 months. Your new senior developer who silently takes over the project is part time because he’s working on finishing his education.

      No one knows how anything works, except that one guy, who left the company half a year ago. That’s how all software development is.

      • tool@r.rosettast0ned.com
        link
        fedilink
        arrow-up
        3
        ·
        edit-2
        1 year ago

        Throw in a mysterious comment that says “Don’t change anything below this line or everything breaks” and it’s complete.

        “We don’t know why this works, but it does, don’t touch it.” would also be acceptable.

    • what@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      Programming teams I’ve worked with are a joke.

      Company A: We got hacked and the lead dev argued for days it wasn’t a hack. Malware was actively being served to customers during this time period because she refused to deal with it and there was no security team.

      Company B: programming team was the IT guys nephew and some random UI designer who hadn’t finished college and was never able to be employed after finishing college…

      Company C: We interviewed a candidate who was way over qualified and would make our life so easy because he was eager and hungry. Instead we hired a bootcamper who had never heard of docker (half our infra is docker), react, or anything other than vanilla JavaScript. She failed our practical but still got hired because the hiring manager wanted and assistant. She has become a glorified project manager, but still has the title software engineer.

    • herrvogel@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      In my company we have a very modern agile workflow where QA is top priority.

      At least that what we advertise. In reality it’s all an unorganized clusterfuck where I’m pretty sure I am the only one who bothers to write automated tests. Who’s got time to write tests bro just push that shit out ASAP we’ll deal with it when the client calls us in the middle of the night to complain about previously-working shit being broken now.

      • grue@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        I’ve worked for one company that actually did it right (complete with pair programming, even). It was pretty nice.

        Too bad we were apparently the “experimental?” team and the only one in the whole company doing it that way.