5

Working with a data scientist on an update to a machine learning api that has dinner logic change with a new model.

He's wondering why his PRs are falling.

He's trying to merge into development from a branch created off of main.

He's renamed all the functions and classes and never updated the call points.

He's using new packages but never includes them in the requirements file, so the docket builds are failing.

His class method definitions don't contain self and are throwing syntax errors.

I've been working with him for 4 days to get him to understand branching, linting, unit testing, and not blindly copy and pasting snippets from jupyter notebook into production api code!

Comments
  • 6
    Data scientists are not software engineers. I wish they would swallow this pill soon.
  • 0
    @aviophile he's a good date scientist too, but the CTO wants them knowing the entire stack so they can maintain it internally
  • 1
    "bro... other people have to touch this...."
  • 0
    Just because they know how to do data modelling and write a few lines of code, they think they know it all!
  • 1
    @lungdart
    CTO want the Data guy to add code to production?
    ......

    huge Red Flag.
  • 0
    @magicMirror Not necessarily if he/she knows their stuff. However, we know not many of them are that good!
  • 0
    He wants more guys on the web platform as there's some big features coming down the pipe from the sales guy.

    It'll all work itself out.
  • 1
    @AjDevNull
    Oh. you mean me, and that other guy? 🙃

    Then sure - we know our stuff!
Add Comment