doug

[doug @priorax]

@GoodThingsFest as a heads up, if you click the logo of your page on mobile it goes to /old-home which is a page that doesn't exist. Doesn't really matter in scheme of things but figured it's worth making sure you knew

[doug @priorax]

@creatine_queen @housecor From my experience, the longer a test environment that uses microservices sits the further it drifts from production because no one keeps all the services in-step

[doug @priorax]

@mjovanovictech Sorry, I thought you said controversial? Is null collections something anyone thinks is a good idea still?

[doug @priorax]

@MLBalatro Will this weeks deck/stake be announced here as well or do we watch out for the week summary and the wheel just gets spun there?

[doug @priorax]

@SlexAxton @QuinnyPig Increasingly serious problem in the industry that I hope we somehow manage to fix

[doug @priorax]

@vencordapp @shifkey @IceSolst Backing up, I'll apologise for over speaking! "Privacy nightmare" just implies this is more private, but there's no clarity to me for why/how unless I go to the effort to audit every package because they are all potential entry points for malicious actors

[doug @priorax]

@vencordapp @shifkey @IceSolst Entirely fine and agree with that @vencordapp, I don't really care either way, they just asserted "more secure" and didn't say how/why and it's just a personal pet peeve of mine when people assume open source implies secure.

[doug @priorax]

@shifkey @IceSolst To clarify here, I'm not saying either is more or less secure, just saying that "just because it's open source doesn't mean it's more private by default". Unless you're auditing all code from all deps you never truly know for sure (and even then, how often do node deps bump?)

[doug @priorax]

@shifkey @IceSolst What makes this better for privacy?
> Much better privacy, since Discord has no access to your system
Sure. But now I am giving access to my system to some random codebase full of packages I don't intend to audit but that has no reputational stake on the line, right?

[doug @priorax]

@taavisaft @enunomaduro And personally I don't understand why that downloaded a file from the internet that way when Invoke-WebRequest exists, but, not my script, I don't care enough

[doug @priorax]

@taavisaft @enunomaduro First bit - ignore the need for signed scripts/security policy
Second bit - legacy to support tls1.2, no clue why people still include it but I'm sure there's a reason
Third bit - iex instead of Invoke-Expression because using aliases makes it harder to understand?

[doug @priorax]

@gadboit @svpino What's best is what helps you be most productive.
It's all subjective based on the person doing the job, the task and even sometimes practical limitations.

[doug @priorax]

@Saul_Loveman @ChShersh @KingRomstar I see you and raise https://t.co/BUQr0d1qJI
So amazing that you can still pay for it but (I think) you can't create any resources via the aws console

[doug @priorax]

@RyanRodemoyer2 @MysBhd Out of curiosity, how much experience did those people that took 4 hours have with c# in general?
I feel like I've had junior engineers follow the documentation about handling relationships (https://t.co/E612EJD2IM) in a much shorter time than that (and 0 attributes in sight)

[doug @priorax]

@RyanRodemoyer2 For what it's worth, EF Core does come with "run arbitrary sql and still get the object mapping" for you (https://t.co/uzQmVPz6sI), great for hot paths
Even then I have had EF save me on a hot path more than once by preventing a Cartesian explosion I missed when mentally modeling

[doug @priorax]

@RyanRodemoyer2 Keep in mind git was originally designed to be used via email on a fairly large project. Having a merge commit to verify who authorised a merge between trees makes sense. It might not make sense in smaller projects, but it has its place as an audit tool and isn't a design mistake

[doug @priorax]

@ComputerGoBrr @MiseryCut3 @karljobstgaming I have no clue what the truth is (nor do I overly care), I just know it's somewhere in the grey.
If the lawsuit was more narrow in scope? Would be a very different conversation
When it's as broad as this is and I haven't examined all the evidence in detail, I can't pass judgement

[doug @priorax]

@ComputerGoBrr @MiseryCut3 @karljobstgaming There's also things you just can't talk about while you're in a lawsuit and I haven't (nor do I want to) read the court docs.
For all I know it might have been a case of "I can speak to cheating because I do a lot but cannot speak about this without fear of letting strategy slip"

[doug @priorax]

@Tobihbest @DavidKPiano @ThePrimeagen @angular I mean, we're talking things that "stuck around", so past tense, not the modern tech we have now

As far as replacing angular.js it was pretty damn common, and angular 2 lead to a lot of people I know moving to react.js as a replacement
And, yeah, it just kinda stuck around

[doug @priorax]

@MiseryCut3 @ComputerGoBrr @karljobstgaming Courts can be (and often are) wrong and that's why we have an appeals process. unless an appeal is done we can only speculate.

But that doesn't mean you're helping yourself in the court of public opinion if you get your own messaging wrong.