• 0 Posts
  • 35 Comments
Joined 2 years ago
cake
Cake day: August 19th, 2023

help-circle









  • Jellyfin is not there yet but it definitely can be. It can be done pretty easily without any centralised server.

    1. Sending people magic links to their accounts on their phones that auto log them into Jellyfin.
    2. Make IP dictionary to have people type “cat mug door end” which pings the server with a login from an IP.
    3. Show QR code.
    4. Scan with an authorised app which pings the server to authorise the device on behalf of the user.

    It’s passwordless 4 word input + phone scan that can be optimised for TV pretty heavily since you only need make something 10^12 unique to account for all IPv4.

    It will take around 15-30 hours to code though for a person familiar with Jellyfin on android TV and server.







  • I bought a used desktop with 4 SATA ports. Has i5 7th gen and currently 5 TB and an 500GB SSD and has max ram of 64GB. I guess the HDD are not included in the price?

    I’m not sure what your software requirements are but if you go the DIY route a desktop works. I made the BIOS auto turn on on power restored and have services start on startup so it gives the server feeling.

    Bonus is that you can use it as a gaming server and upgrade the components easily for a while depending on the motherboard.


  • He wrote for example the books Clean Code and Clean Architecture which are IMO opinion really good books although I don’t agree with every point he makes.

    Some really good points he makes are for example:

    • Functions that only do one job
    • Testing makes refactoring easier
    • The standard SOLID OOP stuff.
    • Tech debt is bad
    • Abstraction and encapsulation is good and allows developers to interact with the code on a higher level in terms of actions instead of writing verbose stuff. Essentially saying less code leads to less bugs
    • Insulate yourself from change
    • Duplication is bad
    • Two use cases that are very similar is not duplication and should not be refactored.
    • Don’t mix high level code with low level.
    • Build solid Entity classes to model the data and their interactions.

    Those comes with examples. He’s a tad bit overly idealistic in my opinion. These books fail to mention a couple of things:

    • Refactoring is expensive and the cost is often not justified.
    • Premature abstraction is the absolute devil
    • You don’t need to insulate from things that are very unlikely to change (like going from SQL to Document DB)
    • Less changes also lead to less bugs.
    • Too much emphasis on functions being few lines of code instead of just being simple.

    All in all though, very solid books. I read Clean Code in university and Clean Architecture in my first job and it really helped me wrap my head around different ways to solve the same problem. Excellent ideas but it’s not the holy truth. New programmers should read it and take inspiration, craftsman level developers should criticise it and expects can mostly skip it.