Skip to content

Lessons we’ve learned on real projects (page 89)

The links, tools and tips our engineers and designers share with each other, one “today I learned” at a time.

lessons shared
3,447
people sharing
86
database started in
2016

  • mitelman.engineering

    Practices for a new Python project local setup in 2021:

    Intro The goal of this tutorial is to describe Python development ecosystem. It can be helpful for someone coming to Python from another programming language. They say that you should stick to algorithms and data structures, that you can learn a new language in just a couple of weeks, that it’s just a new syntax. I completely agree that algorithms and data structures are extremely important but when it comes to language it’s slightly more than just syntax.

    Flavio Juvenal

  • arxiv.org

    Using AntiPatterns to avoid MLOps Mistakes:

    We describe lessons learned from developing and deploying machine learning models at scale across the enterprise in a range of financial analytics applications. These lessons are presented in the form of antipatterns. Just as design patterns codify best software engineering practices, antipatterns provide a vocabulary to describe defective practices and methodologies. Here we catalog and document numerous antipatterns in financial ML operations (MLOps). Some antipatterns are due to technical errors, while others are due to not having sufficient knowledge of the surrounding context in which ML…

    Flavio Juvenal

  • b-list.org

    Against service layers in Django:

    *This post now has [a followup](/weblog/2020/mar/23/still-no-service/).* Recently I've seen posts and questions pop up in a few places about [a …

    Rebeca Sarai

  • forum.djangoproject.com

    Structuring large/complex Django projects, and using a services layer in Django projects:

    Hi all, This is a long post so I’ve copied my two questions for a TL;DR. I’ve also bolded the questions within my post so you can grasp for any context if you think that it’d help your answers. is there any publicly available (paid is ok) literature or training available that covers how to best structure a large, ongoing, mature Django project? Does anyone have any experience writing complex Django applications with a services layer as discussed in the linked style guide? How has it gone ...

    Rebeca Sarai

  • forum.djangoproject.com

    Where to put business logic in Django? Discussion:

    I’m curious if there’s any consensus here. Obvious answers are: Models/Managers - make them FAT is often cited as the default but can have performance issues and in large projects become unwieldy to reason about Views - obvious place to put them but can also grow too large and not performant, plus do you really want all the calculations done on the fly? Templates - not advised to put much logic in here, bad for performance, hard to reason about Separate Python file…this is what I see larger si...

    Flavio Juvenal

Book a call

Found it useful?
Let’s put it to work.

Tell us about your product and the problem in front of you. We’ll bring what we’ve learned on real projects.

Tell us about your product, and we’ll bring what we’ve learned.

Still prefer the good old email? Contact us