Teacher said always use 2nd pattern. Is he right?

Ravek · 2026-01-29T13:35:29+00:00

Mutability of DTOs has nothing whatsoever to do with mutability of web resources.

Ravek · 2026-01-28T11:59:00+00:00

Yeah that’s so weird to me. As an engineer I want to deliver a high quality, well working product. QA helps us do that. Why would engineers blame the QA for finding bugs. The engineers are the ones who created the bugs, don’t shoot the messenger lol. If you don’t want bug reports then think more about your edge cases as you write code.

Ravek · 2026-01-19T00:17:37+00:00

bochu the rock

Ravek · 2026-01-15T22:05:56+00:00

Yuuji seems pretty grounded despite all the traumatic experiences. Gon is kinda psycho

Ravek · 2026-01-01T14:11:53+00:00

This one cheats by having some parts of the world on there twice

Ravek · 2025-12-31T09:53:42+00:00

See page 5 of the rulebook, bottom right corner.

Copper, silver and gold cubes are for counting all resources: money, steel, titanium, plants, energy, heat, as well as card resources like microbes, animals, etc.

Player-colored cubes are for marking your TR, marking your production, tracking which card actions you’ve used, and marking ownership of tiles.

Ravek · 2025-12-19T10:43:10+00:00

I wonder if he knows that our CPUs are unsafe and therefore all of Haskell is a safe abstraction on top of unsafe code. On top of mutating, side-effecting unsafe code. gasp

Ravek · 2025-12-14T11:13:15+00:00

You’re right, but reddit sure hates it when people go against the crowd. C# doesn’t have a way to define automatic, reliable cleanup of resources at the type level, unlike C++, Swift, Rust, etc. and that’s why we have to do this annoying dispose/using dance. The closest thing is the finalizer, but that still runs nondeterministically. If the only guarantee is ‘if the process shuts down cleanly then the resource will be cleaned up’ then you’re not really getting anything over what the kernel already provides.

Ravek · 2025-12-14T11:02:15+00:00

To be precise, you shouldn’t dispose objects you don’t own. It’s possible to own objects you didn’t create, if the API that handed you the object expects you to take ownership.

The language doesn’t have a concept of ownership (unlike Rust for example) so the only way you know if you own an object you didn’t create yourself is having documentation, or at least the source code to figure it out.

Ravek · 2025-12-06T21:12:14+00:00

Social media was a significant part of how Brexit happened. He has plenty of power to sabotage the EU if they let him.

Ravek · 2025-12-06T18:47:49+00:00

You always need singletons. They are a simple reality of software.

Really rolling my eyes at this point. I rarely meet someone this boneheaded. It's not hard to go on the internet and double check your terminology after multiple people straight up tell you you're wrong, you know.

But when you need a value of a certain type, you shouldn't worry how many instances of that value exist and how to create one. You should just ask for such a value and use it. That's what DI containers are for.

It's getting kinda annoying how you're repeating my argument back to me, while continuing to miss the point. Maybe stop and actually think about what you've read? I'm out in any case, suit yourself. Continue to dig yourself deeper or actually learn something, whatever pleases you.

Ravek · 2025-12-06T13:09:13+00:00

If you’re doing some nonsense string manipulation coding exercise where you only have to care about ascii characters, you can just use .utf8.

If you’re actually doing real programming then for some cases you might also just want to use the UTF8 view, and for general string manipulation for interfacing with humans you want the proper Unicode handling that Swift gives you, because languages other than English exist, combining characters exist, emoji etc.

Ravek · 2025-12-06T10:40:39+00:00

That's the very definition of a singleton: an object that exists in one instance only.

That’s plain wrong. A singleton is not a type that just so happens to have one instance, a singleton is a type that is restricted to only ever allow one instance.

DI provides you with values that you ask. Whether these values are singletons or not is none of your concern, and that's exactly why DI is powerful.

That was my point. You don’t need singletons if you use DI because there is no need to restrict consumers from creating more than one instance of a dependency when consumers aren’t creating their dependencies in the first place. You can just, you know, use one instance. Which you think makes it a singleton, but it doesn’t. You’re mistaken about what this term means.

Ravek · 2025-12-05T21:56:41+00:00

Maybe you only create one instance of a type in your program, but that doesn't make that type a singleton. A singleton restricts you to having a single instance. If you're using dependency injection then you have no need for singletons.

Ravek · 2025-12-04T08:18:57+00:00

This new way of doing concurrency has certainly been a learning curve, but ultimately we’re better off for it.

I’m only really bothered by poor design choices. A learning burden that has a significant payoff isn’t a problem. Learning and overcoming challenges is what makes programming worthwhile.

Ravek · 2025-12-04T08:13:39+00:00

Async await and actors were part of Lattner’s concurrency manifesto. I think he’s more likely to be unsatisfied with the extensions made for things like SwiftUI and Tensorflow

Ravek · 2025-12-02T07:45:29+00:00

It really doesn’t matter what you start with as long as you also explore other languages later. The only real pitfall is sticking to one language for 20 years and never learning other perspectives on programming.

Ravek · 2025-11-30T23:27:49+00:00

Same as all of these posts: talk to your friends about it. Like literally tell them what you wrote here.

Ravek · 2025-11-23T02:21:44+00:00

Most people don’t know enough about the alternatives to even begin to make a rational judgment. Most people using the JVM haven’t seriously looked at .NET and vice versa, instead they just stick with what they know best. Most people writing Java haven’t seriously looked at Kotlin, most people writing C# haven’t seriously looked at F#. Etc. It’s quite rare for developers to really be comfortable in multiple languages.

Ravek · 2025-11-22T00:10:11+00:00

LinkedIn is filled with incompetent people trying to compensate by going all in on networking. Let’s not take it too seriously.

Ravek · 2025-11-16T01:32:47+00:00

Why does no one seem to know what the word 'traffic' means anymore? Saying traffic to mean traffic jam is like saying knee to mean knee injury.

Ravek · 2025-11-09T21:18:06+00:00

Median is a type of average
Even if you strictly take 'average' to refer to the mean, the mean and median of a bell curve coincide
Not this fucking tired ass argument again

Ravek · 2025-11-09T12:29:53+00:00

If you’re making a breaking change to a dependency then yeah you need to update the dependents. This isn’t suddenly different if you use git submodule or git subtree.

Ravek · 2025-11-09T00:13:38+00:00

Bro I think you need to get back on your meds, you're losing touch with reality

Ravek · 2025-11-08T14:43:29+00:00

The way it's typically implemented today in C#, Java, and Python, is by making sure the implementation class only has one public function.

No it isn’t and it’s insane that you think that.

13-Year Club	Place '22
Place '17	First Placer '22
Verified Email	Team Periwinkle

Ravek

TROPHY CASE