I've been using git for 12 years, it's not that I don't understand it. It's that I do, and it was never designed to be this used. We know things now that they didn't back then, and it's time to try again having learned a lot.

Also, anyone who advises submodules is a moron, those things are trash and always have been.

@12bitfloat Theres no such thing as a function that can take any T.

That's the issue.

Sure if you define T it works, but you can't say: give me any function that returns the object it gets.

That's crazy. It's totally crazy.

@hinst I've been using typescript for 3 years, and guarantee I'm in 99th percentile for understanding it.

The fact that you never ran into this specific issue is fortunate, but doesn't make the issue non-existent.

@homo-lorens Look man, I know more about Typescript than 99% of its users. If I'm struggling to type things that take less than 10 lines of code to implement in JS, it's on typescript.

"Use any"

I'm a professional. And I have no problem with "get gud" being the solution to an issue.

It's still a very under-developed system. Or do you think it has no room to grow?

Constraints are not always a bad thing, totally agree.

Where this fails -- though -- is that some constraints are more tradition than they are valuable.

I've worked with Typescript soooo much. Sooo friggin much, I guarantee you I'm upper 1 percentile at this point.

I've also been programming for a decade since before Typescript was around.

Typescript pretends to be a super set of Javascript, but it simply is not.

https://medium.com/@shadywillowcree...

@Eklavya It's great for large scale simple projects, but I've had nothing but hell with it for doing the more complex stuff that JS is capable of.

It's really more when you start having infers as defaults for generics because otherwise you'd have to rewrite the inference everywhere it was used... I mean, I can't even get into it in a comment section save to say: typescript generics have ruined this project so many times now. And I have learned so much more about them than I ever wanted to.

@vintprox I'd challenge you to embed a link where they show some understanding of what their users are dealing with.

If you have any integrity at all, avoid AWS. https://mkorostoff.github.io/1-pixe...

Vultr is the best looking I've found so far.

@linuxxx My first one took very little time as well. This one... I gave up. I found a hack to get around it. Good enough for me.

@dontknowshit This is not something I want to be good at. Dark Souls, ofc. Compiled languages, why not? But the arbitrary configurations of something that routes http(s?) requests? The pay off is just so low knowing that with any language on earth (not brain-fuck) I can do more advanced string manipulation in far less time.

I mean, the real solution here is that someone needs to make something like https://regexr.com/ for nginx.conf so you can see what it would mostly do with any given url.

I'm sure it's super nice, but holy crap it took 5 hours to get it to proxy_pass some stuff, and I'm still fighting to make it do it with https. Pretty much every-time I approach it, it takes multiple hours to get a few lines changed and working. It doesn't help that proxy_pass is involved.

Setup graphql if you can, and be diligent with foreign ids. You'll thank yourself later.

The part that gets me is how my manager always wants quality, with as few hours on clock as possible, as many corners cut as possible, and as soon as possible. But quality is the first thing to cut, every time.

I can take no pride in saying: "Check out this thing I made, it was done on time." If quality was at least somewhat more important than deadline, I could focus on the job. But instead it's all about focusing on just how many cut corners line up with some arbitrary date.

It never saves time in the end. Every cut corner is eventually a refactor job.

Morons.

I know your feel. Here's a tool that's helped me before: https://www.npmjs.com/package/madge

It's not a cure, but it might ease the pain a bit.

It's one of those frameworks that thought it would be really clever to have abstract classes that you extend every time you want to do anything. Which, in itself is obnoxious enough... usually you're just trying to pass in a few config arguments, and it's way overkill (see React Components). But to really salt the wound, they make it so there's fuckin 3 classes you extend, or more. What's really getting my goat right now is that I have the exact same code for 6 different implementations of this class with a few really key words replaced. Absolute utter bullshit. I really hate opinionated frameworks. They think they "know best," but tools are only as useful as the conditions in which they work, and this one only works in a shallow theory.

Save the money you'd spend on college. Spend that money instead on going to a coworking space, or coffee shop... anywhere where you know: "I'm HERE to learn code." Start working on personal projects, and never ever stop. Try everything. Then, once you've really found code for yourself, start figuring out how to be corporate about it. Go to some big corporate meet and greets and be direct about "I'm here to learn how about real industry standards" or some ass kissing like that. They'll go on and on about all the modern buzz words. Get those buzz words under your belt, alongside an actual understanding of code, and you'll be golden.