Yeah I didn’t rate him at all either, and it definitely started off a lot slower, but by the end I was properly into the story of season 2. It’s a really shame as like you said season 1 was incredible, they just didn’t have the same budget for S2. I would have liked to see more as we would have had a different actor and it never really got finished.
My list:
Too soon:
Too long:
The jury system is bullshit and needs to go.
To counter this I used to visit some factories for a big contract manufacturer in the UK. They would often make say lasagne for the supermarkets and for the “premium” brands. Whilst they were all made in the same place, the “premium” brands products had much better quality ingredients in them and different ratios of the good stuff (say meat) to filler (say pasta sheets).
For some things it’s the exact same materials, but for many it’s different. You have to do blind taste tests to see which ones you prefer.
I find the opposite with some hobbies. If you buy a cheap acoustic guitar it’s going to be horrible to play and will probably sound crap. That might discourage you from continuing. More expensive guitars have a much better resale value too, so you’d probably be out of pocket for less if you buy a nice one and sell it again than if you bought a crap one and no one else wanted to buy it.
It didn’t click with me with either, I tried it for a few hours then put it down and forgot about it. A couple of Christmases ago I went back into it with a mindset of “just focus on the story missions rather than exploring every nook and cranny” and I got far enough that it really started to click and I was hooked.
The story is incredible, pretty much the whole way through. The progression and combat is delightful. The world is beautiful so you end up exploring it whilst naturally following your quest markers. To top it all the expansions are amazing and have really incredible moments.
Keeping it simple and moving on was a smart move. Your portfolio doesn’t need to be super fancy unless that’s the specific skill you’re selling (fancy designs and UI). Most jobs aren’t doing anything with threejs. Most jobs are crud apps, so focus on demonstrating skills to do with that.
Svelte is also cool but the majority of jobs aren’t for svelte Devs, and most aren’t for Greenfield projects with bleeding edge tech. Where I am for FE it’s something like 60% react, 30% Angular, 10% Vue/svelte/whatever else. Just focus on building things which show you can do what the jobs you’re looking to apply for need.
If you’re going full stack then just focus on one stack and focus on building (preferably novel) actual things that all work together. If you have full projects showing you can self direct and implement semi complex systems from start to finish in a stack that’s close enough to what employers are looking for you’ll have a lot more luck landing a job.
It’s doable once you know what you’re doing. I can do it all via the cli, but I personally use gitkraken most of the time and it’s just so much easier and more ergonomic.
I also see a lot of the Devs who insist they know what they’re doing create horrible messes of their branches super easily via the commit tree. People should just use whatever works best for them to get the job done.
The expansion was absolutely incredible. I thoroughly enjoyed the game on my second play through after a few years to forget as much as possible, then the expansion gave me so much more to explore. It’s a lot more tragic, and I had to turn on no frights mode lol, but the ending is beautiful and fits into the main story so so well.
!Oh man the DLC ending was incredible. The tragic story that unfolded as you played was incredibly sad, but then inviting the prisoner to join you at the fire and add their song to your music was beautiful and moving.!<
Those devs really caught lightning in a bottle. I can’t wait to play whatever they make next, whenever it’s ready.
Btw. You can use >! and !< blocks to create proper spoiler tags.
You basically haven’t played any of the game then lol. It’s a long slow burn but it’s absolutely beautiful. Make your way through that tutorial section and get your ship, from there it really opens up.
Yeah “why” comments are absolutely fine, “what” comments are useless at best and can be harmful at worst.
I feel like this constant flood of “write comments” posts are from CS students who are told to comment everything by their lecturers. Descriptive variable and function names help explain the “what” of code pretty well most of the time.
Sure with some old languages like C89 where you are limited in your variable name length you probably do need comments to explain wtf is going on, but most code bases aren’t as constrained.
I’m definitely there with you. I actually forgot that hot existed because it’s basically a ‘new’ sort.
On the one hand it’s handy because it makes me browse Lemmy less and do more productive things instead, but it isn’t good for encouraging growth of niche communities and topics if everyone is just looking at the same few posts.
We test the shit out of our Apis. We do more API level/integration testing though.
I.e. a test will be something like “if the db is in this state, and we hit this endpoint with these params, does it return what we expect and update the db correctly”.
Our app is primarily about users maintaining stuff on big datasets with complicated aggregation and approval logic. So setting up a scenario and checking the app does what the business logic says it will do is what we want to know.
It makes refactoring wayyyyy less painful to just know that the app will always behave itself. Rather than testing whether a function can add 1 + 2 correctly, we can test each endpoint does what it’s supposed to do.
It gives us loads of confidence that the backend is doing what it’s supposed to. If you do a huge refactor you don’t need to worry about whether you broke the test or if the test is failing correctly. If the tests all pass everything is working as it should.
Downside is longer test execution times (because a temporary db needs set up) when running the full suite. Worth the trade off for us though.
It’s more for library devs when writing their libraries. Using TS means you’re writing in one language and then distributing the compiled version for users.
As users can use things in a lot of different ways you have to do a lot of type “gymnastics” to make your library API as useful as possible.
That means spending a lot of time setting up types when a jsdoc and .d.ts file will do the same thing for library consumers.
It’s really a non issue. If some library devs think they can ship code which is easier for them to maintain correctly, and end users have the same developer experience, then it’s totally cool.
Of course people with no nuance are using this as an argument for why no one should write in typescript (because they don’t like it for some reason). This thread has a bunch of people doing this. That creates drama, but there really shouldn’t be any. TS is bae for me, but I totally get why library devs might want to not use it.
It’s gotten a lot better in recent years tbf in terms of those kinds of resources. Beginner recommended languages like Python are still a pain because it’s super easy for a beginner to bork how they set it up, but on the whole there’s plenty of online code sandboxes and other ways to get started.
Your point is definitely valid though. Why on earth would we want someone who’s just showing an interest in programming to write their own compiler??? Wtf? If someone wants to get into baking you don’t send them out into the fields for 6 months to grow some wheat.
When I was a kid I mucked around with html and css to make some GeoCities sites. I decided I wanted to learn how to code so I got a book from the library called “how to code games for beginners” or something. The thing never told you how to set up an IDE or compile the game. So I was just frustratingly typing out the code examples into notepad without a clue as to what to do. I think this was during the dialup era so it wasn’t like there was a wealth of info online.
I ended up abandoning programming for quite a few years. It just seemed like nonsense because writing graphics libs for C in notepad does feel like nonsense to a child. I wonder what life would be like if I had some better resources at that moment in time and decided you continue pursuing it.