wewbull

Getting interview practise is no bad thing. Being interviewed is a skill you learn to be sure.

I think a lot of people miss that interviews in the technical world are often not smartly dressed exams. Some are, but those are probably jobs where they won't mentor you and invest in you. They expect you to come fully developed.

Good interviewers are trying to imagine you as an every-day team member. Will you...

• ...work well with others?
• ...be engaged with the problem space?
• ...ask for clarifications or just make assumptions to avoid appearing "dumb"?
• ...let a lack of knowledge on something become a road block?

Knowledge is easy to give you. These things are much harder to teach.

Also, knowledge based questions might be designed to find your limit. So if you don't know something, that doesn't mean it's pointless from that point on. The interviewer may just have pushed you to your limit, and only they know if that was good enough. Keep going, stay engaged.

I don't know if any of that helps you design your bot, but maybe it gives you some ideas about being an interviewer.

Worse than that. Fraud. He's scammed people out of millions.

...because removing somebody's kernel maintainer priv and the industrialised genocide of people is remotely comparable.

This sounds like a scapegoat.

And with all due respect if "success" in being a restaurateur is mostly catering to influencers who care more about how your food looks than tastes and are often wasteful and don't even eat any of it, all while overworking the restaurant staff to make it happen... Fuck success.

Makes you wonder if a "Take a selfie with our prop food" menu item that was £2-3 would be a good idea. Deal with influencer crap quickly, still make a bit of money off it, and keep the actual customers who want to eat your food happy.

So important it's posted somewhere lots of people can't read it.

Here's something that might blow your mind. Coverage is not the point of tests.

If you your passing test gets 100% coverage, you can still have a bug. You might have a bunch of conditions you're not handling and a shit test that doesn't notice.

Write tests first to completely define what you want the code to do, and then write the code to pass the tests.

Debugging only teaches logic. Not structure. No amount cut, paste, debug with teach you the factory pattern.

Kodi isn't commercialised. I'm not sure what you're referring to. It's open source and always has been.

I also have the *arrs running on that same box so new episodes appear automatically. They require a browser or other client, so I didn't include it in my list. They just run in the background.

So that one doesn't talk to the Jellyfin process. It just understands the way Jellyfin organises things on disk. Right?

You then access the files via NFS, SMB or WebDav (the horror!)

Just checking I understand.

A few things for me:

• I had most of the parts to build a low power machine that's passively cooled. No noise whilst watching video.
• I can have a locally stored library so don't need a NAS running 24/7 elsewhere in the house supping power.
• I can have multiple things running on it like games as well as media giving me a PC gaming console (fans come on at that point).
• Never have to drive it through my phone or a tablet. It's just on the TV remote. Ease of use is great.
• No money to Amazon, Google or similar companies that just want to data farm me.

Kodi works very well for me with a local library. Serving it from Jellyfin was a mess (Jellycon). I think primarily this is a Kodi problem as really it should support DLNA servers much much better, and then a add-on wouldn't be needed.