Yep. They changed her pretty drastically from the way she is in the books (which was probably a good idea), but way, WAY overcorrected. I also don’t really like the actor for the role, but that is secondary.
- 0 Posts
- 33 Comments
Fair. Don’t take this as pressure to watch this. But for what it’s worth, “Harry Potter but horny” is exactly what I grew tired of after S1, and they drop that hook pretty thoroughly.
S2-5 is more like “there’s no such thing as a chosen one. We’re all just fucked up in different ways, and the only way to get meaningful change done is if we try to be better, together - regardless of if we ever manage to grow past that damage”.
Except Alice. Fuck Alice, she never not sucks.
The Magicians? Do yourself a favor and continue on (well… Depending on where you stopped, I guess.) To me, Season 1 is a difficult sell. It’s all over the place, and some of the characters are… Not super likeable, ahem. Season 2 gets much better, and season 3+ are my favorite seasons of television, ever.
smiletolerantly@awful.systemsto
Programmer Humor@programming.dev•You can do anything at Zombocom
15·2 months agoYou had me cracking up at
parses HTML with regex
smiletolerantly@awful.systemsto
Programmer Humor@programming.dev•POV: You're a programmer
17·4 months agoPrisoner Of War:
Because a commit should be an “indivisible” unit, in the sense that “should this be a separate commit?” equates to “would I ever want to revert just these changes?”.
IDK about your commit histories, but if I’d leave everything in there, there’d be a ton of fixup commits just fixing spelling, satisfying the linter,…
Also, changes requested by reviewers: those fixups almost always belong to the same commit, it makes no sense for them to be separate.
And finally, I guess you do technically give up some granularity, but you gain an immense amount of readability of your commit history.
Same. And even if you were to fuck up, have people never heard of the
reflog…?Every job I’ve worked at it’s been the expectation to regularly rebase your feature branch on main, to squash your commits (and then force push, obv), and for most projects to do rebase-merges of PRs rather than creating merge commits. Even the, uh, less gifted developers never had an issue with this.
I think people just hear the meme about git being hard somewhere and then use that as an excuse to never learn.
Is this about the straight werewolves author?
smiletolerantly@awful.systemsto
Programmer Humor@programming.dev•My skill prevents bugs, unlike your fancy compiler, peasant.
2·6 months ago… are entirely possible, even if rarely the right choice.
smiletolerantly@awful.systemsto
Programmer Humor@programming.dev•My skill prevents bugs, unlike your fancy compiler, peasant.
4·6 months agoOr a CLI with
clap.
smiletolerantly@awful.systemsto
Programmer Humor@programming.dev•My skill prevents bugs, unlike your fancy compiler, peasant.
7·6 months agoCurious what you are talking about. Multi-threaded sharing of memory for example is also easy with rust, it just doesn’t let you wrote and read at the same time, and so on.
smiletolerantly@awful.systemsto
Programmer Humor@programming.dev•My skill prevents bugs, unlike your fancy compiler, peasant.
14·6 months agoYeah. Once you get used to the (verbose, but by no means unergonomic!) syntax, you’ll probably never be happy with another language again. Job-wise, I am currently mostly using Go, and while also a nice language, I miss the confidence and security I took for granted with rust.
Not to mention just how goddamn expressive rust can be. Let bindings like if ok/err, else return? Assign from a match on Some(Ok(x))? Filter, map, and friends on any iterator? Oh my GOD the error handling with the question mark iterator? 100% confidence that if it compiles, no error, possible null value, or case is unhandled.
And all this WHILE giving you the amazing security benefits!
Ah, damn, caught me proselytizing again.
smiletolerantly@awful.systemsto
Programmer Humor@programming.dev•My skill prevents bugs, unlike your fancy compiler, peasant.
137·6 months ago- if your skill is so great that you would never cause the kinds of bugs the rust compiler is designed to prevent, then it will never keep you from compiling, and therefore your complaint is unnecessary and you can happily use rust
- if you do encounter these error messages, then you are apparently not skilled enough to not use rust, and should use rust
In summary: use rust.
A Short Stay In Hell
Short novella based on this exact premise. If you have never encountered it before, I urge you to give it a read. It’s excellent. Also very disturbing.
Chat, is this AI-generated ads on Lemmy?
Sehr basiert. Pinguin sei mit dir!
Ich kann meine Partnerin leider nicht überzeugen. Sie ist Informatikerin, braucht keinerlei properitäre Weichware, aber lässt sich von den kleinsten Kleinigkeiten abbringen
I’m too lazy to insert the “look what they need to mimic a fraction of our power” meme here, so… Please imagine it instead.
I’m switching jobs in a couple of months, and I am SO glad to be leaving a (very well maintained!!) python codebase with type hints and mypy for a rust codebase.
It is just not the same.





Lmao. Lmfao, even.
Here, I’m gonna save you some time and summarize the article for you:
Ahem. Maybe I editorialized a tiny bit. Not much though, trust me bro.