Every Application Eventually

Recorded live on twitch, GET IN

### My Stream

### Best Way To Support Me
Become a backend engineer. Its my favorite site

This is also the best way to support me is to support yourself becoming a better backend engineer.

MY MAIN YT CHANNEL: Has well edited engineering videos

Discord

[vulpeeze]

It's all libraries?
Always has been.

[nekilevi]

Typing transforms possibly obscure runtime errors into obvious compile-time errors, and the greater the complexity and dynamics of code changes, the greater the benefit of typing

[Jake_Beaver]

I think the argument is not about people don't need to learn, but don't overcomplicate the simple parts of the app just because you know how to

[hinzster]

Every call to a library has two sides, the inside and the outside. If you think you can just use the library from the outside without even thinking about what happens on the inside you are setting yourself up for really difficult to find bugs in your program.

[Salztorte]

The funny thing is, you can use complicated types and make every place where you use the type so much easier

[pokefreak]

I love the absolutely incoherent diagrams he always makes

[snakedoc]

"Nonsense type masturbation" had me rollin'

[EduardTen-vh]

Typescript is just parody to normal typed language

[ashrafibrahim]

Him without a jacket is like a cat without it's fur. It can exist, but should it?

[panthonyy]

That is some great piece of experience being shared here. Types are a foundation of professional coding or at least should.

[alexhiatt]

recently I've hit this for the first time ever, at about 4k SLOC I've noticed my codebase breaking into a few discrete segments that could be viewed as 2 internal libraries plus application code

[janisir]

I can't imagine complaining about typing of all things.

[Davi-itin]

This is inaccurate because it went from "complex types are for libraries", which is a fair statement, to "your app is a series of libraries" which can also be a fair statement, but it never established that "all libraries have complex types". This means you CAN have an app which is a series of libraries, none of which have complex types. It is up to you as a lead, or a sole dev to keep your team and their abstractions in check

[portobellomushroom]

Libraries are great for getting something that is agreed on to be good. Libraries are terrible for getting exactly what you need

[gurupartapkhalsa]

I actually notice the movement of every functionality to modules and libraries as a corporate programming trend, I believe the idea is to create re-usable code, which in practice we have never in the past decade at the ISP I work for actually re-used one of these modules. There are always new requirements, new platforms, new libraries, new dependencies, the fancy new frameworks, whatever, and at the end of the day it simply creates a completely pointless extra cycle of maintenance and slower compile times with absolutely no benefit to the end product.

[RemotHuman]

what if everyone always made their internal libraries completely abstracted and decoupled from the rest of the code, and then published those libraries every time. then we'd have more libraries

[HappyCheeryChap]

Sounds like a case for Detective Bookman.

[StuartLoria]

TS feels overcomplicated, and engineers love complexity and riddles.

[RCKT_DEV_]

the "nonsense type masturbation" got me dying

[Marxone]

classic, hiding spaghetti monster behind "simple" interface and the one time you need to do something quickly you will let the monster out and it will never come back.