• helpmeimstuckdevelopingunderduress (unregistered)

    frist

    Build fail.

  • Smash (unregistered)

    I am having error posting comment ... I am having error posting comment ...

    I am having error posting frist comment. error i am having is: user helpmeimstuckdevelopingunderduress got first comment.

  • codercrap (unregistered)

    None of this is really related to actual management. This is just senior tech stuff. Nobody should care.

  • codercrap (unregistered)

    None of this is really related to actual management. This is just senior tech stuff. Nobody should care.

  • siciac (unregistered)

    But I documented that. In bold. In three places!

    Don't even bother documenting that, write checks for it in the start of the build script.

  • Kashim (unregistered)

    This is a WTF? This is every friggin' day. This is why you have to design your deployment instructions so that they are 4 steps or less, otherwise, they are doomed to fail, especially if you are making them for people who don't speak english as a first language. I deal with international customers all the time. If you're lucky, you get someone who knows the basics of how to move files around. If you're unlucky, you better have a way to directly access the device, or it could either take you weeks to get anything useful, or you might end up catching a plane to fix it yourself that way instead.

  • spadgas (unregistered)

    4 steps? flipping heck, i've seen it go wrong with one step

  • Zenith (unregistered)

    I miss when all you had to do was open Visual Studio, create a solution, create a project, add DLL references, and go. Then the tool monkeys came. And for every "problem" they "solved," three more sprung up in its place.

  • Dan Bugglin (google)

    LPT: If you need a quick workaround for path too long errors, subst.exe is your saviour.

  • (nodebb) in reply to Zenith

    I miss when all you had to do was open Visual Studio, create a solution, create a project, add DLL references, and go.

    That sort of thing only ever works in the simplest cases, and you're always left wondering whether some idiot colleague has not actually committed all the critical files into production or if you're just going crazy. So instead we have a different rule at work: official versions of the code are never sourced from any developer's own system, but rather only from a host dedicated to the task that rebuilds from the committed code versions only.

  • Zenith (unregistered) in reply to dkf

    Because your idiot coworkers never forget to include the fancy dependencies (and they are legion, undocumented of course) in TFS? Tell me, has NBC picked up your sitcom yet?

  • Joseph Osako (google) in reply to Dan Bugglin

    Praise be to subst.exe on the high.

  • moridin84 (unregistered) in reply to Zenith

    If they do then it doesn't build. If they check in code and it doesn't build on the build server then it's their problem. They'll probably even get an email sent directly do them.

  • eric bloedow (unregistered)

    reminds me of a story i saw on "not always right": "video is blue on blue on DE TING." the techs NEVER found out what "thing" the guy was talking about, every time they asked for ANY details, he just kept saying "DE TING!"

Leave a comment on “2017: The New Manager”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article