Platypus

Those are arguably the most “made for humans” languages—they’re made to make humans laugh and/or headbutt a railroad spike in frustration

Sekiro, and nothing else has ever come close. It’s so smooth and so fast that I drop into the flow state with no trouble at all.

In my experience, very, but it’s also not magic. Being able to package an application with its environment and ship it to any machine that can run Docker is great but it doesn’t solve the fact that modern deployment architecture can become extremely complicated, and Docker adds another component that needs configuration and debugging to an already complicated stack.

Hey, I’ve actually done that! It was almost a year ago now, so I can’t remember my exact strats for those missions, but I might be able to help.

First of all, those two missions are brutal–I had to retry them a lot before I got the S. It seems like you’ve got the right basic idea for both: move fast and play the objective above all else.

For builds, I had the most success running Zimmerman in the right hand and laser lance + pile bunker on the left hand/shoulder. You can swap lance/bunker to basically always have a melee available to one shot any MTs that are in your optimal path. For the real fights, building up poise damage with Zimmerman and then staggering with lance before finishing with charged bunker is an insanely fast kill that only costs Zimmerman ammo. It takes some skill and a little luck to land it on Iguazu (he’s one slippery bastard) but if you can lance him into a corner then he’s toast. The same basic principle applies to the refueling base fight, but you have to do it twice. The biggest thing to know is how much poise damage you need to build up before lance will stagger --it’s crucial that the lance induces stagger to set up the bunker.

Good luck!

Edit: I see you got it–congrats! That’s a tough achievement.

It’s been steadily overrun by bots, and I guess the community hit a breaking point

Fair enough–there is one specific boss that comes to mind where a specific prosthetic is supremely useful, as well as some mini bosses. All the “enemy with sword” bosses like Genichiro are pretty straight up, though.

Juzou the Drunkard is a brutal fight! I rushed Hirata Estate my first playthrough and got stuck there for a long time.

IMO spirit emblems are cool but ultimately a waste of time–they’re a lot of fun to play with in the open areas, but for ~a boss~ most bosses, it’s faster to just learn the fight than spend time farming tokens to try to grind it out with prosthetics.

You may know this already, but a slightly hidden mechanic is that the parry window is a while .5 seconds if you hold the parry button down–if you just tap it you only get a couple frames, but if you hold it, you will find the window far more forgiving.

Eh, depends on the language and the context. I still use 80 for C, but I’ve found 120 to be a much more reasonable number for Java.

Armored Core 6. Missions are pretty short, attempts on them can be abandoned without losing anything but your progress in that attempt, and there is absolutely no slack time–start to end it’s densely packed with new content.

I’ve been migrating one of my company’s apps from microservices back to monolithic Java. It’s wonderful. I haven’t touched a line of yaml in weeks.

I’ll save you the watch, it’s a 20 minute Balatro ad with some pedestrian commentary on what makes games fun sprinkled in.

Because cross-platform apps inevitably feel out of step with the OS they run on. Native apps can use system components and behaviors and will almost always run better because they don’t need to be wrapped in a cross-platform framework. Admittedly a platform-locked app isn’t going to be a universally perfect Lemmy app, but it can certainly be a platform-specific perfect Lemmy app.

With no disrespect to Voyager, its devs, or its users, this is why I can’t use that app despite its impressive feature set and high level of polish–the ui feels fundamentally wrong on iOS, and the fact that it’s a very direct Apollo clone but not written in native swift makes it feel like a knockoff.

I presumed it to be a standin for just directly using Math.max, since there’s no nice way to show that in a valid code snippet

Not using thief is professional incompetence unless you’re doing something deeply cursed

Fair enough, though I contend that for a common-case application like a database-backed REST API where the architecture is basically standardized there is no meaningful time difference between writing crappy code in a clean architecture and writing a crappy pile of spaghetti.

I’ve been tasked with updating some code a senior programmer (15+ years experience, internally awarded, widely considered fantastic) who recently left the company wrote.

It’s supposed to be a REST service. None of the API endpoints obey restful principles, the controller layer houses all of the business logic, and repositories are all labeled as services–and that’s before we even get into the code itself. Genuinely astounding what passes for senior-level programming expertise.

That’s what’s really irks me be about JS–you can do just about whatever but you’re not supposed to.

It’s an imperative language, but best practices are to use it functionally.

You can omit semicolons, but best practices are to use them.

You can use sloppy equality, but best practices are to always use strict.

It’s admittedly quite good at what it was originally supposed to be: a voice chat service for playing games that’s easy to join, use, and share. The troubles began when they started trying to pivot to be a general-purpose public internet space provider, because the platform was never supposed to be that and they’ve done absolutely nothing to support it.

Only the ones who don’t grow up to be total code monkeys

Smex ftw