- 0 Posts
- 23 Comments
I was rather happy with Netflix for nearly a decade. The price was reasonable and family members could also watch. When I moved out I upgraded to the 4K package (split 3 ways between family members) and it was fine at first.
But there were several caveats:
- 4K only works on TVs, on my 1440p monitor I could only watch 1080p. Sucked, but it’s not too bad
- Price kept going up, in the end it was 18€ a month. That’s okay split between 3 people, but otherwise far too much for what is offered
- Series that I liked kept getting cancelled, while trash was getting renewed or they messed up the later seasons (Looking at you, The Witcher…)
- They cracked down on password sharing, suddenly you need to be in the same WiFi to count as home or you need a travel code (limited to 2 a month and only for 2 weeks each), so if you regularly move between places it’s a no-go for a service you pay for
I finally cancelled it, sick of their shit. Which also has the benefit of no longer having to take care of the account for the family. Unfortunately my dad accidentally took over the account (while trying to create a new one) and keeps paying the 4K price (I suggested at least going down to 1080p as the quality is shit either way). Simply idiotic :-/
Personally I tried out Real Debrid and it has been pretty alright so far. The quality is better too, which is ridiculous.
Yeah, I’ve worked with the leave it alone types. What do you get in return? Components of your system which haven’t been updated in the last 20 years and still run .NET 3.5. They obviously never stopped working, but you have security concerns, worse performance (didn’t matter much in that case) and when you actually need to touch them you’re fucked.
Why? Because updating takes a lot of time (as things break with every major revision) and on top of that if you then decide not to update (yeah, same coworker…) then you have to code around age old standards and run into bugs that you can’t even find on Stack Overflow, because people didn’t have to solve those in the last 20 years.
Git is mainly tracking and saving changes, which works great for text, but not that well for data (especially binary). You won’t lose your data, but the Git repo will keep growing too fast.
The big question here is: How often does the data change? If you just use it as a convenient format and rarely change things, it should be fine. Though as mentioned: It might make sense to export to SQL before putting it in Git then. As long as the size is reasonable too (Not storing gigabytes of data).
Alternatives can be other sync services (Dropbox, Seafile, …) to keep your Git repo lean or even better: Set up a SQL server so the data is always in the same spot. Of course that depends on if you have internet everywhere you work (but you probably do).
You can’t trust the result if you only do one pass, because the result could be compromised. The entire point of the first pass is a simple: Safe, yes or no? And only when it’s safe do you go for the actual result (which might be used somewhere else).
If you try to encode the entire checking + prompt into one request then it might be possible to just break out of that and deliver a bad result either way.
Overall though it’s insanity to use a LLM with user input where the result can influence other users. Someone will always find a way to break any protections you’re trying to apply.
I still haven’t found a proper command or tool to do a multi-commit git blame.
Like I want to know who changed the logic in this line. But the last commit was a format refactor. And the commit before that just changed a tiny detail. So now I’m digging through the entire file history just to find the spot where this one line was introduced or actually changed.
If you have any tips for that, I’m all ears.
That works for newer projects, but on older projects there’s a dozen commits for any given line and a handful of Jira tickets that have something to do with it, but none that say “Change exactly this”. A comment why you made an interesting design decision costs a lot less time than trying to unwrap the commit history… Especially when you can’t even find a clue on why this was done as the commit might simply be “Implemented feature XY”
The code shows what happens. But comments should explain why it was done this way.
Sometimes the code started simple and readable, till you ran into a weird edge case a year ago. Now the code no longer looks as obvious and another developer might scratch their head when they read over it. A small comment can help out there quite a bit.
Or you’re doing something stupid in code not because you want to, but because management forced you to. So you put a comment there that the code isn’t wrong, management wanted that behavior.
I’ve worked in a company that used linear code most of the time. And at first it felt really easy to read and work with. If you wanted to know what happened, just jump to the entry point, then read over the next 200 lines of code, done. No events, no jumping around between 10 different interfaces, it worked at first.
But over time it became a total mess. A new feature gets added, now those 200 lines get another if/else at several spots, turns into 250 lines. Then a new option is added that needs to be used for several spots, 300 lines. 400 lines. 500 lines… things just escalate.
You can’t test that function and bugs sneak in far too easily. If you want to split it up later into new functions it’s going to be a major hassle. There also was no dependency injection or using interfaces, other classes were often directly called or instantiated on the spot. Code reuse was spotty and the reused functions often got 5+ parameters for different behavior.
It was horror after a while.
The company I work for now uses interfaces, dependency injection, unit tests, but all the way down a function might still have 50 lines tops or so. It’s slightly tougher to find out where things happen, but then much easier to work with. You need a certain balance either way.
This would actually work well with a tag system. Like you have predefined content warning tags. “Porn”, “Nudity”, “Gore”, “Violence”, “Sexual assault”, or whatever might be in the text/image/video. Users could then filter tags in their settings.
Defining the tags and enforcing them in communities would probably be the biggest hurdle.
You never heard of pair programming?
With juniors Tim would pretty much be training them and nudging them on to write better code.
With seniors, like the short article says, it’s more a sparring match, trying to find the best solution. You also find a lot of edge cases when someone else works with you together.
I haven’t been in a company yet where they have a full time floating position for pair programming, but if it’s a senior doing it I can see how it’s very beneficial for product quality.
I’m from Austria, we don’t have that issue in Europe. But people here (luckily) are a lot less into monster SUVs. If I see even one of those taking up the entire lane or blocking my sight at an intersection I’m getting annoyed.
Going to the Kia website I can actually view cars in stock in the entire country. So I could immediately pick a Kia Picanto (that’s the cheapest one) up for €15,840. Or a Kia Rio for €17,440. Though I just saw on the Kia page, they discontinued the Rio (No more new cars coming).
Ah, from Google (and the MSRP), now it’s $20k on their site directly. See: https://blog.clutch.ca/posts/6-cheapest-new-cars-in-canada
There are cheaper options actually. My Kia Rio cost 14k€ (and that was with a deal) back in 2015. So it’s not that far off I guess. But that was actually the new price, with navigation, camera for driving backwards and so on with 7 years warranty on top.
Prices suck of course, but on the low end they are still affordable. Mid-tier is probably a lot of leasing (as you’d have to spend a big chunk of life savings on a direct buy) and high tier is only for rich assholes (or company cars).
Maybe I don’t get the nuances, but isn’t this just the free market?
It gets legalized, tons of shops open up. Turns out after the initial rush it’s not very profitable to have half a dozen shops in the same town? Everyone competes, lowers their prices, some shops have to close (the ones with the worst locations). Duh?
Yeah, my experience was mostly from that time. For example with an original Galaxy S (custom ROM + overclocking).
I also had a OnePlus One, which was unlocked of course, but the key combination to get to the bootloader was super unreliable or straight up didn’t work at times.
Funny thing is: Now that it’s easier to install a custom ROM I’ve just been running stock for years.
My ISP doesn’t support IPv6, now what?
It’s really bullshit.