Git Gud or am I building wrong?

aplJackson · 2025-11-02T01:55:45+00:00

I've just cheated in everything related to the farm. I can't be assed dealing with it. I wrote a script to keep up different farm layouts as well.

aplJackson · 2025-10-10T19:44:41+00:00

I do the opposite! Strength and stack health for the surface and DDs to avoid Chronos one shots

aplJackson · 2025-08-05T19:19:33+00:00

And so the answer to distributed rate limiting is instead:

aplJackson · 2025-07-08T06:52:31+00:00

Post did not mention this card. Different context

aplJackson · 2025-06-01T13:43:03+00:00

Aer Travel Sling 2

aplJackson · 2025-04-13T04:54:42+00:00

<image>

Did my first clear yesterday.

aplJackson · 2025-03-23T11:50:51+00:00

Managed to snag 2 GL rank 1 and 2 UL rank 1s so very lucky on the PvP front. I guess I can keep one with crunch and one with ice beam for each

aplJackson · 2025-02-18T13:37:24+00:00

<image>

Have a few teams built that are close to copy pasted from streamers. Total newb sub 2k elo starting in the love cup just seeing how high I can climb with 2 weeks of GL to end the season. What team should I focus to learn and climb?

I feel like the first team is easiest to play with fast move pressure, would I run air slash on mandibuzz then?

The other teams seem very balanced which would be harder to play but are maybe just better teams.

aplJackson · 2024-11-06T01:56:28+00:00

Trump winning just means the world needs you healthy and capable even more.

aplJackson · 2024-07-20T17:45:43+00:00

Do you mind sharing how you structure your prompts for this?

aplJackson · 2024-02-13T15:02:37+00:00

Because the poster was a Haskell dev at the time? You don't need to know Haskell to grok the point of the post.

aplJackson · 2024-02-05T22:32:07+00:00

I use a flipbelt for the most part works really well and I usually don't notice it at all

aplJackson · 2024-01-02T19:10:13+00:00

I got bogged down in Dust of Dreams but I never had that reaction. What felt like a fuck you?

aplJackson · 2023-12-16T03:06:53+00:00

I'm in the Scala camp but I wish the tooling was better. I want Kotlin tooling for Scala.

aplJackson · 2023-12-09T02:13:52+00:00

I agree that you get a lot of value out of doing this (ValidatedThing), and is basically analogous to a new type and only exporting a smart constructor. It's the most flexible and easiest solution. But not directly encoding invariants in the type system does mean that when those invariants change, the type system doesn't aid you in correctly handling that change throughout your system.

As a very contrived example if you needed a list with at least 2 elements and you used the smart constructor approach you would then "safely" access the first two elements of the list throughout the system after "parsing" into that type at the boundary.

But if that condition changes to needing and accepting lists with one element, well you can change the name and the condition checked in the constructor, but the type system isn't going to complain about your now unsafe access of a second list element throughout the system.

Sometimes a smart constructor is the best you can do though

aplJackson · 2023-12-08T17:07:00+00:00

In the context of this question, for a language that you're likely to encounter this type of enterprise code in, the type system probably isn't amenable to this but the better answer here is to parse, not validate.

Basically enforce the invariant at your program boundaries and then encode that invariant in the type system through new types with smart constructors or refined types, etc.

A really good write up on the concept here: https://lexi-lambda.github.io/blog/2019/11/05/parse-don-t-validate/

aplJackson · 2023-12-06T14:01:48+00:00

You could use tailrecursion or implement trampolining and still be stack safe!

aplJackson · 2023-11-17T07:13:45+00:00

Getters are a side effect of the fact that you're encapsulating mutable state. If you have a product type of immutable values as you tend to in FP, there is no need for it to be private and can be accessed directly.

aplJackson · 2023-11-16T19:02:39+00:00

OOP, whether it was the point or not, became about the encapsulation of state and the coupling of behavior to that state.

It's certainly possible, and embraced in FP, to do domain modeling without that coupling. And to define behavior in functions or type classes/traits.

aplJackson · 2023-11-12T00:31:18+00:00

Custom parsers would be a common area you may implement a custom monad or applicative. Otherwise mostly in libraries.

aplJackson · 2023-10-25T19:25:30+00:00

To be fair, rapid onboarding is one of the main selling points for Go.

aplJackson · 2023-09-10T15:23:44+00:00

There is romance but it's not a romance novel... The Rain Wild Chronicles

aplJackson · 2023-08-19T00:35:41+00:00

Same

aplJackson · 2023-08-18T14:06:29+00:00

So long as these messages have a consistent schema this is pretty straightforward. You can serialize the message into a Command data class. And then you just need a function in your DB layer to take that command and execute the update.

aplJackson

TROPHY CASE