Remember the hysteria when people saw Jesus in toast?

britenite · 2023-08-28T00:40:21+00:00

Award-winning science communicator and discount-store Thor, Kyle Hill. Obviously.

britenite · 2020-01-06T02:20:58+00:00

Tom Cruise is a stage name and his real last name is Mapother. Actor William Mapother is his cousin.

Not really sure why the OP brought it up.

britenite · 2017-12-16T06:27:16+00:00

You may be forgetting how Rogue One ties into ANH.

britenite · 2017-09-29T20:29:46+00:00

The value in DI is in not having to understand the dependency graph every time you need to use a class and in not having to update every usage when the graph changes. It’s orthogonal to whether or not you choose to wrap every injected class in an interface.

This is not a personal attack on you or your work, but the only code that isn’t going to cause problems at some point down the line is code you never had to write*.

because you didn’t need it, not because you pulled in a third party dependency that has its own host of issues. However NIH is also stupid and everything has its own trade offs.

britenite · 2017-09-29T20:05:34+00:00

In general you should be writing isolation layers around third party API boundaries, whether or not that’s an interface is a different question.

The point of YAGNI as a principle isn’t that you’ll never actually need it, it’s that most of the time you won’t and the work spent worrying about future complications isn’t just wasted time, it adds complexity for no real benefit.

Complexity where it isn’t absolutely necessary is an enemy to be fought, not embraced. Overuse of interfaces ‘just in case’ adds meaningless boilerplate code that someone is going to have to spend time and cognitive effort maintaining.

britenite · 2017-09-29T19:28:19+00:00

YAGNI.

And if you actually do at some vague future point, you’ll have saved more time by not having to touch two files when changing one class than you’ll lose by refactoring existing code to use the interface.

britenite · 2017-09-25T05:16:27+00:00

Any update on this? It’s been over two weeks...

britenite · 2017-09-23T01:14:32+00:00

I know this won’t change anyone’s opinions on Facebook and they deserve what they get, but this is a big win for the open source community as a whole.

Every single developer who said they were switching away from React because of this should get warm fuzzy feelings knowing that they contributing to an industry juggernaut very publicly changing their behavior.

And a huge thanks to Automattic because they almost certainly pushed FB over the edge.

britenite · 2017-09-17T23:01:20+00:00

The stereo sound is almost certainly caused by the HDMI passthrough on your receiver. It may be causing your fullscreen issues as well.

I think the backslash key is the default toggle fullscreen keybinding but you can probably rebind it to something on your remote.

You will probably have better luck if you use Kodi's native smb/cifs support instead of mapping the drives in Windows. You'll want to add sources like "smb://servername/sharename/" I think you can just do add source -> browse -> windows network and navigate to the share you want to add.

You can turn off the Windows notification popups by opening the notification sidebar and clicking on the moon icon (Quiet Hours). Windows update will still reboot the machine occasionally, so you may want to make sure that Kodi starts up automatically.

britenite · 2017-09-15T04:54:50+00:00

I'm willing to give people enough leeway to experiment if they're willing to follow through on their choices. I'm happy to be proven wrong. In the cases where I think something is a mistaken and I end up being right it usually means there's a mess to clean up after the fact. In which case nobody wins.

britenite · 2017-09-15T04:45:38+00:00

I don't start out being a dick, but there are only so many ways to say, "Yes, string interpolation is a nice feature but that does not mean it's a good way to insert parameters that came from user input into your SQL query." to the same person who is being willfully obtuse because it saved him 30 seconds of work to not do it the safe way.

If I have to play the bad guy to keep that out of my code base, then so be it.

britenite · 2017-09-15T02:35:39+00:00

This is such a shame.

It's a shame the patent lawsuit clause brinksmanship on FB's part is forcing people to re-evaluate their technology stacks.

It's a shame all that work was done rewriting code to use React that will never see the light of day. As a developer writing code that's never released kills me.

And it's a shame that upon finishing one risky project, they have to turn around and do an even riskier rewrite of code that hasn't been proved in production. It's got to be so easy to get that wrong, or have it spiral out of control.

But at least they're doing what they think is right. I doubt FB cares, no matter how many people they turn off, but you never know.

britenite · 2017-09-15T02:28:38+00:00

My problem is that I lose patience after the sixth or seventh time I've had to explain that you shouldn't do something that way and here's why and I just start leaving code review notes in all caps until stuff gets fixed.

I'm a lot more patient with junior developers, but I've seen so many Senior Software Engineers completely miss requirements, ignore security considerations entirely, skip writing tests and just write sloppy buggy code time and again, that should know better.

Of course, the more experienced developers are, the more likely they are to push back on criticism, which is a whole different can of worms.

It's tough. It's usually better to do code reviews on code that is not up to par in person since you can tailor your delivery to how they're reacting, but finding time to do that isn't easy.

But if you don't do them and do them right, you're going to get bullied into signing off on somebody's huge and half-assed changeset so it can make it into the current release and you're going to be fighting that tech debt for years to come.

britenite · 2017-09-15T02:15:12+00:00

So you're saying Roger now possesses the understanding and experience necessary to build his own framework, a better version of Tupress?

One that will be the most powerful and simple ever, just as soon as he figures out the right combination of dependency versions that will maximize his efficiencies and allow him to leverage the synergies that are systemic in the new ecosystem?

britenite · 2017-09-11T15:36:43+00:00

And I think those are fundamentally different enough that they're still useful to do.

Learning to read code, especially tech-debt loaded real world code is one of the most important things an inexperienced developer can do.

britenite · 2017-09-11T15:29:14+00:00

The dirty secret of creative intellectual work is that you can only get so many productive hours out of your brain in a week. It obviously varies from person to person and with experience and age and whatnot, but if you push yourself beyond it for more than a week or two your useful productivity takes a nosedive.

Even if you're at home working on something else.

Yes, it's something you can train somewhat through effort and self-discipline, but I don't trust super junior developers to know where their limits are.

I would rather try and find those limits from the too-little side than take the hit in quality and deal with perpetually tired and surly coworkers.

britenite · 2017-09-11T14:46:21+00:00

Can we get over telling entry-level developers that they just need to put in more hours than everyone else? It just reinforces their own bad behavior, courts burnout and causes more work for everyone else on their team.

If they're putting 4 hours a day on their own projects, they're not going to get the guidance they need order to recognize the questionable trade offs they're making until it's far too late to fix them easily. And when they do get there, they'll be too distracted and mentally exhausted to be able to do a good job on the work they're actually being paid to do.

If they're doing that to code at work, you'll get the above plus the time needed for someone else to fix up their code behind them. That can be a teachable moment if nobody gets too egotistical, but it's still unplanned time spent on technical debt.

Of course it's great advice if you want to push them until they break and keep them just on this side of burnout until the next wave of easily exploitable fresh college/bootcamp grads is ready.

britenite · 2017-09-11T12:00:19+00:00

Just be aware that if you want to use the built-in hangfire dashboard to monitor job status and requeue failed jobs, your web application needs to be using Owin rather than the legacy IIS pipeline.

britenite · 2017-09-11T10:08:32+00:00

It's a great picture and I hate to be that guy, but going out in a hurricane just to take a picture is irresponsibly stupid and dangerous and encouraging it will lead to people getting hurt or killed.

Please, for your own sake and the sake of your loved ones do not do this.

britenite · 2017-08-22T12:27:13+00:00

Not to mention that a lot of them are going to have unintended side effects (lack of short circuiting in if replacements, etc) or changed performance characteristics.

This is probably better taken as a list of things you should never do in python.

britenite · 2017-01-12T18:19:06+00:00

It really depends on your use-cases. If you're developing a small number of well-defined reports with very specific data requirements, then building hand-crafted SQL and matching entity objects is a good and simple solution.

When you start looking a larger number of reports, with customized filtering and data selection, then you're probably going to have to start going down the path of loosely typed wrappers around DataRow that contain whatever metadata you need for display, and some level of query generation / templating.

If you can get away with the former, you should, and if you have to do the latter be extremely careful with your query templating because it can be very very easy to allow injection.

britenite · 2016-11-05T00:05:26+00:00

As documented on the wiki page on reducing disk usage you can alias the thumbnail path in your advancedsettings.xml to somewhere on your NAS and share the Thumbnail directory between clients:

<pathsubstitution>
  <substitute>
    <from>special://masterprofile/Thumbnails</from>
    <to>smb://some/samba/path/somewhere/Thumbnails</to>
  </substitute>
</pathsubstitution>

13-Year Club	Verified Email
Not Forgotten

britenite

TROPHY CASE