HackerTrans
TopNewTrendsCommentsPastAskShowJobs

teoingdri

no profile record

comments

teoingdri
·2 anni fa·discuss
Here’s a clip of Jon Stewart laying it out for you:

@11:00 > “And that, ladies and gentlemen, I present to you, is why we need courts. Whatever flaws the American justice system has, and they are legion, especially for non billionaire former presidents, it does appear to be the last place where you can’t just say whatever the fuck you want regardless of reality.”

That’s the energy I want to bring to congress.

https://m.youtube.com/watch?v=qmxzQJt80XI&t=660
teoingdri
·2 anni fa·discuss
> Why would jurors be harder to buy than career politicians?

Because the juries are selected from random pools.

Are you truly sincere in your question regarding the ability to buy off career politicians vs random peers?

Are you aware of jury tampering laws?

> The other obvious problem is jury selection. You can basically choose the outcome by selecting the "right" jury.

I was unaware you are so passionate about reforming the current jury system.

What groups are you currently working with to improve the existing system?

I can agree there are flaws in the current system but rather than throwing my hands up in defeat I think such problems can be addressed.

How would you better address the issue from the linked article?
teoingdri
·2 anni fa·discuss
Love Clojure, but am repulsed by the idea of a “responsive DOM network stream”.

This feels over engineered to me. The classic cool factor influencing the “if we could vs if we should”, bolstered by developing it as a software engineer on a performant dev box with impeccable internet connection; hell, maybe even a local dev db clone.

I suppose you could argue server side caching would alleviate some of the pains of a design like this, but you’re still performing redundant server round trips for the stream when a piece of data goes in and out of view.

Does the tech have any local caching options to make this a little more sane for a worst case an end user?