And how would you describe your political tendencies? I have a theory that more MLs are gonna be into static typing and more anarchists are gonna be into dynamic typing.

  • footfaults [none/use name]
    ·
    11 months ago

    Most of the code that is being written is view classes or form classes for Django, so really there's not a lot of times where we are writing code directly that references those where autocomplete matters. Like, a great deal of our code is in form_valid methods and you never call those in your code, the framework calls them.

    Same with Celery, where we have the code for the workers in a separate repository and we are calling send_task instead of having a Signature to directly call apply on

    • invalidusernamelol [he/him]
      ·
      11 months ago

      That's fair, I'm usually writing a ton of tools and such from scratch and using an API for a very popular GIS software where getting those objects recognized properly saves me tons of headaches debugging because I now know I have a Point Geometry object and not a Point object based on proper type hinting in my utility functions.

      Also means if I write some function that required a Point Geometry object and a Layout object to work, I can put it in the docstring and also type hint it so other programmers in the office are able to really quickly tell exactly what they need to provide for the function to work.

      It's nice to have in that really rapid development situation for sure, my commits and changes usually have a 10-20 minute turnaround to get things working since everyone in production is using my main branch. I have all the other devs working on forks so they can isolate their code from the central repo that everyone is always referencing for their tools.

      When you only have 5 minutes to debug a production tool, having a ton of built in links to the bajillion different methods Arc objects have is necessary.