Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)TH
Posts
8
Comments
406
Joined
2 yr. ago

  • Much less than that now assuming you do average mileage, probably 5 years tops before major maintenance. Around 50k miles, most direct injected engines start to have problems due to significant carbon buildup on intake valves, because PCV and no fuel in the intake valves anymore. Just Google - it's a huge issue that is affecting virtually every brand.

    I'm the market for a slightly used car right now. Avoiding anything with over about 10-15k miles and I want something fairly luxurious for the size. It's depressing knowing I'll still be spending $30k and it will have a shorter life than either of my sports cars.

  • So if Michigan does not have an explicit law defining age requirements, could a 12 year old run in a political parties primary for president and get on the ballot? Or could Schwarzenegger get on the ballot for POTUS?

    Am I correct in understanding their opinion of the primary election as having nothing to do with federal constitutional requirements for POTUS?

  • I agree, writing meaningless tests helps nobody and just creates extra work everyone. Unit tests should prove functionality and integration tests act as a vise. Much like you said, if a test breaks in that scenario, then you know something in another class has violated that contract. Good tests will have meaningful names and prove functionality, especially in the backend where it is especially important..

    You mention (what I would consider) a bad practice of allowing merges without review. While that should be possible on personal projects with only one dev, strict review guidelines should exist so that nobody can just "push to prod". CICD is your friend - use it so that staging and prod never break. Again, I'm used to working on systems used by scores of millions of users so I appreciate forced automated validation. Nobody likes dumb breaks on a Friday before vacation.

  • That does sound like a nightmare. I'm assuming you mean failed test when you say "red boy", and that made me wonder about PR practices. I'm used to a very strict review environment and fairly quick review turnaround or requests to go over the code. I've heard horror stories about people not getting PRs reviewed for days or weeks or some people just plain refusing to review code. I work on microservices that are all usually less than 10,000 lines though, not something with over a million lines of legacy code.

  • For conversion of videos after download. I don't use tdarr. Doing what you suggest works for Sonarr, but not radar because of different base images. Two different groups maintaining those projects I guess.

    Edit: this is the issue I'm speaking about in particular:

    https://github.com/mdhiggins/radarr-sma/issues/41

  • Yep. When I was still doing QA, I saw some pretty terrible practices and tested code that barely built. Now as a software engineer, I have no QA and rely heavily on my own testing practices, namely, unit testing first, integration testing and system/e2e testing. I can't guarantee the code is bug free and there's parts I know that could be refactored (tech debt), but I know each piece is tested and does what I expect it to. As corny as it sounds, I'm a big fan of TDD. Unit/IT/E2E don't replace QA in my opinion, but better set QA up to focus on the bugs that matter and not basic stuff.