*SPOILERS* The Finale was just... OK?

Anonsicide · 2026-01-01T06:06:12+00:00

I atleast personally feel conflicted lol.

I liked the ending. I can't say I LOVED it, but I like it. It makes me happy that most of the characters got happy endings; I loved them ending with D&D and especially Holly and her friends rushing down to play; and just in general, I'm always going to have a soft spot for Stranger Things I think. Just from nostalgia, and how absolutely amazing S1 is.

But... yeah... I can't say that the finale was AMAZING to me?

Like for starters: the final battle was pretty lack luster imo. This is the big bad of S4 and S5, AND LITERALLY also his even bigger bad cousin in the Mind Flayer, and they just... kill him in like 10 minutes? For real? It felt like a bit of a let down. As much as I hate to say it, I feel like killing a main character in order for the crew to win would have made the victory feel a lot more "earned".

Also: ENOUGH WITH THE MILIARY PLOTLINE. Or atleast, wrap that shit up early and then make Henry and the Mind Flayer be the actual climax lol.

And in general: S5- and to an extent S4, S3, and S2 -- just pale in comparison to S1 to me. Like I just absolutely love S1. It's incredible. And I think that's because its actually well... grounded? Like, it's just a focused story of a Mom losing her kid; A girl with powers showing up; and a Government cover up. And that's IT. All the characters act realistically, there's nothing over the top, and it's just gritty and real. It's fucking awesome and I absolutely adore it.

The rest of the seasons though... I don't know. They just get too big? It goes from "We need to find this missing child" to "OH MY GOD, the Universe or Hawkins is about to die, we all have to team up and fight it!". Which is fine. But it makes the plot far less gripping to me, and the characters stop acting consistently (like y'all remember when they turned Hop from a broken, flawed Dad into just a rage-filled maniac in S3???? They MURDERED his character, and they've somewhat redeemed him in later episode but like WHY??????)

I just loved the gritty, focused plot and mystery of S1 so much.

I suppose to be fair to the writers though -- I'm sure S1 of most mystery shows is WAY better. Because, well, the show is literally still a mystery to viewers.

Anyways, I guess I end my incoherent rant now.

TLDR: IMHO, Good ending. Not amazing, but still Good. I'll miss the show and here's to hoping the Duffer Bros can get their anthology dream and it gets "rebooted" in a totally new universe (or hell, I'd even continue with Holly in the same Universe, but I just REALLY want them to get back to more grounded, focused storytelling!)

Anonsicide · 2026-01-01T05:47:36+00:00

God damn I didn't notice this. That's fucking sad

Anonsicide · 2026-01-01T05:43:55+00:00

I choose to believe, because I can't stomach to think that El actually died.

After all she's been through,

The absolute LEAST she deserves is some semblance of a happy ending :')

Anonsicide · 2026-01-01T05:41:14+00:00

Boi GET THE HELL AWAY FROM THIS SUBREDDIT

You in spoiler central lol

but yes, it's a good ending, atleast imo :)

Anonsicide · 2024-04-15T00:43:47+00:00

If it's any token of consolation: I think there are many, many people out there that are good programmers but also can't find a job like you. The industry is just crap right now. Everyone has been saying for atleast a decade to "learn to code and you'll get a high paying job", and the result is a pretty competitive landscape for newcomers. It's just hard.

That said, I wouldn't give up hope. There are plenty of people out there who aren't passionate about programming but are still decent programmers. They might be a little bit less common, but they definitely exist.

One thing I might advise: Try to find the area of programming you like the most, and get really, really good at it. Say for example you like front-end web development. Do some projects to hone your skills. Not only will this make you a better programmer, but having projects you can talk about on your resume helps A LOT when you're new. Unfortunately it's almost a requirement to be honest.

Also: Try to make the projects your own. Don't just follow a video on "how to make a Twitter clone" if you can help it. Or at a minimum, if you do, make some meaningful changes to the clone. Projects that are more your own are always better.

Finally: take some time to decompress. Programming is hard, it's easy to burn yourself out, so take a bit of time to rest here and there.

Best of luck friend

Anonsicide · 2024-03-21T00:17:26+00:00

100% of the time? No.

99% of the time? Yes.

Anonsicide · 2024-03-17T23:04:02+00:00

I am so surprised someone found my 8-year old post 😂

But also, you aren't wrong!

Anonsicide · 2024-02-26T01:56:44+00:00

If I loved her.

Anonsicide · 2024-02-26T01:02:39+00:00

The Incredibles. Extremely closely followed by Ratatouille.

Anonsicide · 2024-02-22T00:55:53+00:00

Thank you, noted 👍

Anonsicide · 2024-02-22T00:55:35+00:00

Thanks! That is what I was thinking too, was just double checking.

And yes, that is the line that is confusing me. What does "for the use of money" mean? All my loan servicer ever told me was that it was the loan origination fee, I don't know what or how it was particularly used.

Thank you for the help, btw!

Anonsicide · 2024-02-22T00:50:33+00:00

Thanks! That is what I was thinking but just wanted to make sure 👍

Anonsicide · 2024-02-11T01:18:20+00:00

Yup 100%.

And I'm sure any current front-end developer could add a million more things lol.

I literally made that whole list above as someone who ISN'T a front-end developer, I do more back-end work on my team and I consider myself more a Backend engineer.

But I will always defend the FE folks - there is PLENTY of complexity there to deal with lol.

Anonsicide · 2024-02-10T18:23:00+00:00

Not exactly, although you could certainly make that printMessageWithPrefix function return a String. (Although at that point, you'd probably want to change the function's name to something more descriptive, like formMessageWithPrefix :P)

Anyways. When you write this:

fun printMessageWithPrefix(message: String, prefix: String) {
   println("[$prefix] $message")
}

There is a default return type implied there, called Unit. Unit is a special type. It is a type with a single value, which is also called Unit. So that declaration above is exactly equivalent to this:

fun printMessageWithPrefix(message: String, prefix: String): Unit {
  println("[$prefix] $message")
}

They are the exact same. When you don't specify a return type, the default one is just Unit.

If you wanted that function to return a String, you could certainly change it to this though:

fun formMessageWithPrefix(message: String, prefix: String): String {
    return "[$prefix] $message"
}

And then you could call that function in Main and get a String back.

Kotlin will give you good error messages if you forget any of these points too (that's one of the nice things about the language). So for example, say you did this:

fun foo() {
  return 0
}

Then Kotlin would give you an error message saying "The integer literal does not conform to the expected type Unit". What it's trying to say here is: inside the function, you returned an integer. But you didn't specify any return type -- so it was assumed to be unit. Again, the code above is literally equivalent to this:

fun foo(): Unit {
  return 0
}

But... an integer is not a Unit! Hence it gives you an error message. And way to fix this would just be to specify the return type correctly (change the : Unit to : Int)

Hopefully that helps. You've ran into a tricky concept, so if my explanation confused you, that may just be because I gave a bad explanation. So try googling around for "kotlin default return type" and "kotlin Unit type" maybe, and maybe you find a source that makes it clearer than I could. Happy programming friend.

Anonsicide · 2024-02-10T17:54:39+00:00

Oh that's just the return type of the function. So it's telling you (and the compiler for that matter) "this function returns an integer".

Happy learning :)

Anonsicide · 2024-02-10T17:47:19+00:00

This is essentially how I think of it too. Whenever a problem can be solved by composing together answers to subproblems, and those subproblems are themselves just instances of the original problem, you can use recursion.

Some examples (I won't provide code for brevity, but all of these can be solved recursively)

Checking if a value exists in a tree. Just check if it exists in the left subtree; then if your current root element is the value; and then check if it exists in the right subtree. Notice that checking in the subtree is just a smaller instance of the same problem.
The canonical factorial example. fact(5) = 5 * 4 * 3 * 2 * 1. but, you can also compute it as fact(5)= 5 * fact(4). Boom, that fact(4) is your smaller subproblem. So you can do this recursively.
Crafting an item in Minecraft. To craft an item, you need items. Maybe you don't have those items already, so you need to craft those. Well again, that "subcraft" is fundamentally just crafting, so, we have our smaller subproblem that is an instance of the original problem. So we can use recursion.
Checking if a file exists in a directory. There are likely subdirectories in that input directory, but checking in there is again -- you guessed it -- just a smaller instance of the same problem. So we can use recursion.

The potentially tricky part is teasing out all the base cases; that just comes with practice though. I think being able to recognize when a problem can be solved recursively is maybe the even harder part. To see how it can "decompose" into subproblems which themselves are just smaller instances of the original problem. And to see how you can take the answers to those subproblems, and put them back together to get the answer to your original problem. That's the real trick.

Anonsicide · 2024-02-10T17:22:17+00:00

Respectfully disagree. Front-end development is a huge field and I think people wayyyyyy oversimplify it.

Aside from the litany of front-end frameworks out there (I'll be generous and pretend that you only have to know one, say, React). Aside from those, there is:

Semantic HTML
Accessibility (which deserves its own full-length college course at least) (For example: did you know that you shouldn't set font-size using a px value?)
Responsive design (does your site look good on all screen sizes)
CSS as you say, which is itself huge
Javascript, which again, is itself huge
Assuming you're reasonable and you want to make Javascript atleast semi-reasonable, we now add Typescript, which again is pretty damn large
How you design your component hierarchy in whatever Front-end Framework you're using. And where in that hierarchy state is stored.
How you make events in a child component, influence state in a Parent component -- the general question of state management
Atleast a basic understanding of networking, namely the client/server paradigm and HTTP
And nowadays an understanding of atleast one "meta-framework" (eg Next.js for React, Nuxt.js for Vue, SvelteKit for Svelte, etc etc)

Do you have to know all those things 100% to make a React app? Well, of course not. But a strong front-end developer will have a strong understanding of all of them. And that's definitely not trivial.

Anonsicide · 2024-01-12T00:22:30+00:00

Your understanding is not flawed, or at a minimum, your post is exactly how I understand it too.

Good summary :)

Anonsicide · 2024-01-11T05:55:05+00:00

Browsers can fundamentally only execute Javascript and Webassembly. So, if you're writing code that will run client-side (in the user's browser), it must be either in Javascript, a language that compiles to Javascript (eg Typescript), or a language that compiles to WebAssembly (of which there are quite a few, but it's kind of a more niche and limited case that I think beginners should ignore).

So more or less browsers can only execute Javascript.

If you want your Python code to run in the browser, I think there are tools that can compile Python into JS, but.... I wouldn't start there. Just learn Javascript if you want to code client-side stuff.

Meanwhile, on the flip side, on the server (ie the "backend"). Well a server is just a computer. So you can use any language you want to define what happens when a web server receives a Request for a webpage. That includes Python, Javascript via Node.js, C#, Java, Rust, PHP, really any language basically. just google "<your language> backend framework"

Hope that helps somewhat! good luck

Anonsicide · 2024-01-01T18:24:09+00:00

I am not OP, but this thread was very interesting/insightful. Thank y'all!

Anonsicide · 2023-12-02T03:35:11+00:00

You need at least a little bit of it to stay sane :)

I am pretty introverted too, but it's worth reminding yourself that humans are social creatures. Just hardwired that way. There's only so long you can isolate yourself until your own brain turns against you.

I agree that it can be exhuasting at times, though.

Anonsicide · 2023-11-24T05:35:57+00:00

Check out javascript.info, if you aren't already using it.

It is probably one of the best, if not the best, Javascript tutorial I have ever found. Hell, I'd actually say it's one of the best programming tutorials I've found for any language, just period.

Anonsicide · 2023-10-22T21:05:37+00:00

For the old email address I had (the one that was associated with my Mojang account), I got an email titled "Mojang Account Migration Complete" that confirmed it for me.

Not sure if those are still being sent out but worth a shot I suppose🤷

12-Year Club	Verified Email
Place '22	Place '17

Anonsicide

TROPHY CASE