• 13 Posts
  • 506 Comments
Joined 1 year ago
cake
Cake day: June 4th, 2023

help-circle








  • When this whole ‘training’ trend started a few years ago, there were companies offering image and video labelling services.

    It turned out they were mostly sweatshops in low-income countries, where people sat in front of monitors and just dragged boumding boxes around sections of images and picked from an icon menu. Here’s a car, here’s a person, here’s an apple. That sort of thing. You didn’t even need to know how to read or write.

    Of course, the quality was questionable, so they needed a second layer of supervisors verifying the choices. But even with that, the cost was way lower than having an engineer or QA person do it. IIRC, there was a bit of hue and cry when stories came out of big tech companies supporting sweatshop conditions.

    Sounds like it’s still ongoing.













  • I can think of only two reasons to have a venv inside a container:

    • If you’re running third-party services inside a container, pinned to different Python versions.

    • If you do local development without docker and scripts that have to activate the venv from inside the script. If you move the scripts inside the container, now you don’t have a venv. But then it’s easy to just check an environment variable and skip, if inside Docker.

    For most applications, it seems like an unnecessary extra step.