• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: August 15th, 2023

help-circle
  • How broken are we talking here? Like, installation is kinda borked but technically works broken, or purge it with fire and salt the storage medium broken?

    I have often busted my machine learning rig as it runs an ancient (but spacious VRAM) GPU. If I upgrade the drivers by accident, it takes an average of 1-2 days to make everything happy again.

    I used to be more cavalier with my boot partitions; I am no stranger to a busy box for repairs. Best moments are when I used to try and adjust a live partition to make more room for the swap partition (or vice versa).

    I have screwed up more Raspberry PI installations than I care to count. Usually by my own hand.

    I have completely broken Xwindows multiple times due to drivers, trying to go between desktop environments, and most frequently trying to get video cards to work that aren’t natively supported.


  • Friend, while I appreciate the time and effort on the docs, it has a rather tiny section on one of the truly worst aspects of pip (and the only one that really guts usability): package conflicts.

    Due to the nature of Python as an interpreted language, there is little that you can check in advance via automation around “can package A and package B coexist peacefully with the lowest common denominator of package X”? Will it work? Will it fail? Run your tool/code and hope for the best!

    Pip is a nightmare with larger, spawling package solutions (i.e. a lot of the ML work out there). But even with the freshest of venv creations, things still go remarkably wrong rather quick in my experience. My favorite is when someone, somewhere in the dependency tree forgets to lock their version, which ends up blossoming into a ticking time bomb before it abruptly stops working.

    Hopefully, your experiences have been far more pleasant than mine.





  • Yes. So much yes.

    Sure, at least half of the FAANG use Linux. But they use a homegrown Linux flavor often maintained by an entire dedicated team. Not some random ass Ubuntu or Mint ISO you downloaded; these images are custom tailored to the workflows, dev needs, security needs, and even package management needs of the corporation. They often carry a complete profile template that integrates with whatever they’ve chosen to enforce authentication, have a lavish on-board remote monitoring system, you name it.















  • Oh boy, here we go (inhales):

    Agile isn’t that bad. People just believe they are more productive if they are “heads down” and not held accountable for what they write/do.

    Functional programming isn’t that great and doesn’t solve all of the world’s problems; it just pushes the issues with state to other parts of your design, and doesn’t scale well in deeply nested solutions.

    IDEs with proper code support (i.e. automatic structure analysis, autocomplete, etc.) are one of the best ways to deal with a large codebase that needs refactoring. Doing widescale refactors without one is asking for trouble. If you believe you don’t need it, either your codebase is just that small (which is fine) or playing with fire.

    Much of the advice out there on architecture and tooling isn’t properly contextualized on the codebase, market, and team situation. If you believe you have the One True Architecture Solution, you are naive. (Ex. Microservices, large complex code pipelines, monorepos, etc.) Be especially wary of anything from FAANG engineering blogs unless you are also in another letter of FAANG.

    There. Got it out of my system. Have fun dissecting it.