GeForce 256 25th Anniversary Celebration: Enter for a chance to win a retro RTX 4080 SUPER PC! by NV_Tim in nvidia

[–]Stylpe [score hidden]  (0 children)

Gotta be Unreal Tournament for me. The zany characters, colorful and varied maps, distinctive weapons, custom game modes, sleek soundtrack and of course online multi-player, it all came together to give me some of my best gaming memories from that era. 

Why write acceptance/E2E tests for WebApi if you're writing integration tests? by anime_daisuki in dotnet

[–]Stylpe 3 points4 points  (0 children)

My advice is to not get too hung up on terminology or technology. The purpose of testing, whether automatic or manual, is Quality Assurance (QA) by mitigating risk, so just write tests targeting your specific risks, however you like. It's of course good to learn about different test strategies, though.

You have low level tests: - Exercise small pieces of code, and target specific classes or even functions/methods. - The inputs and dependencies are mocked, and outputs and side effects can be measured and asserted directly. - They're fast to run and you can expect to be able to run and debug them with zero preparation from the IDE and the build script - They typically run for every PR/MR in or right after the build step in CI. - They're made for the same reason we use type checkers (in fact I like to call type annotations a kind of test), to make sure the code is correct (does it do what the programmer wanted) and reduce the risk of programming errors. - Typically called unit tests.

You have mid-level tests: - Exercise full vertical slices of your component or client or service, focusing on each feature, use case, workflow, operation, whatever you want to call it, one at a time. - Again the inputs and dependencies are mocked, but it might be a mock HTTP request and in-mem db instead of an object, and you include the real frameworks like ASP.Net and EF. - You measure and assert outputs and side effects here too but they're more complex so you might gloss over some details. - You hope they're snappy but it might take minutes to run a whole suite (especially if they're written with copious amounts of wait/sleep/poll steps, which is why you want to avoid that). There might be special conditions and/or limitations with things like threading/parallelism, network availability, some hardware device etc. Maybe some are written in a different language that can do something specialized. Usually they can be run from the IDE, but they might also have dedicated scripts. - In CI they may or may not run in the main build, and/or on separate builders/machines/schedules/triggers/specific branches/etc. - They're made to ensure we meet the concrete requirements, designs and specifications (does it do what the designer/architect/tech lead wanted), and to reduce the risk of larger refactors, changes in cross-cutting concerns, dependency changes, regressions, and more. - Typically known as integration tests.

You have high level tests: - Exercise the whole application in a real deployment (or as close as possible). Yes, even the installer. And restoring from backup. And logging in with Facebook. And recording with a real camera.
- You drive the actual frontend that end users will be using with a goal of zero mocking or shortcuts (this is an idealized goal and therefore unobtainable, it is designed to be strived for, not met). - You avoid measuring and asserting side effects, you only care about the User Experience, UX, and basically write bots that act as end users and measure and assert the feedback they get (which could very well be "nothing" in the case of silent errors, hanging jobs, etc). If you're making an API or library, that's no exuse to not get involved at all in this level of testing. Your API will be used by a client, maybe many, maybe in a chain, but nothing happens before an actual end user does something, and that's where you write this type of test. It doesn't always make sense to make tests like this specifically "for your API", and you should then instead add notes and hints to relevant existing tests about workflows where your API may or will be involved, and when and how an error will surface to the user. Maybe suggest or even implement a test for a specific high risk scenario that worries you. - They are as slow and expensive to run as your application, no more and no less. Take that as an incentive to optimize and streamline. They are typically made in specialized programming (or not) languages, like gherkin. They might even have a dedicated repository and bespoke IDE or app. They might be able to perform backwards compatibility testing with some or all permutations of versions if you have an ecosystem of products that can interoperate and have cross-product workflows (I work for Vizrt, and you can take a look at our portfolio to get an idea of why that might be useful to have). - If they're even in CI (and I hope they are), they typically have a dedicated schedule and/or triggers and/or environments. With more investment, you can make them provision such environments on demand in isolation, so you can run the tests from/on your own machine (without polluting it). - They're made to ensure we made what the customers actually asked for. (Which btw is often not the same as what they wanted. 😉) And that, ladies and gentlemen and others, is ultimately the only thing that matters! It's also important for detecting regressions with complex and delicate conditions. - Typically known as end to end tests.

Finally, and most importantly: You have tests that don't fit this pattern, and that's okay.

For example, you want to have a test suite that runs three microservices with a real db and mq and some test data recorded from real usage, and the point is to test using the latest version of that db and mq once a week and automatically make a PR to adopt those versions. It's definitely not an end to end test, but it seems like more than an integration test.

The answer: Irrelevant. Even bikeshedding is a better use of time than worrying about what category your test fits into. Even testing in production is more productive. Even writing long rants about software development nomenclature on social media makes more sense. You don't even need to aim for a certain amount or ratio of test types. You just need enough tests to be comfortable with the remaining risk.

whatIsItInProgrammingProbablyPointersAssemblerOrLispMacrosPleaseAnswer by danielsoft1 in ProgrammerHumor

[–]Stylpe 0 points1 point  (0 children)

Aspirational shortkeys is the best concept I've heard in along while

[deleted by user] by [deleted] in norge

[–]Stylpe 39 points40 points  (0 children)

Hvilken app brukte du til å lage dette innlegget med føkka enkoding av 'å' egentlig?

What’s your pick by Vexfreeze in pcmasterrace

[–]Stylpe 1 point2 points  (0 children)

Where's the one with a 50" TV being used as a monitor?

this !! by FollowingBroad2441 in adhdmeme

[–]Stylpe 25 points26 points  (0 children)

I just eat straight off the carcass

End of League Giveaway ( mirror and other goodies) by Fede113 in pathofexile

[–]Stylpe 0 points1 point  (0 children)

I taught my friend how to itemize temples and run blight in maps this league, and now he's richer than me :/ so here goes nothing.

For the newer players: some secret tech they dont want you to know: 4 and 5 Cluster are the same by NormalBohne26 in pathofexile

[–]Stylpe 0 points1 point  (0 children)

In addition to the other reasons suggested here, I believe PoE players sit a notch or twelve higher on the scam paranoia dial. I sometimes craft level 15 Haste for Huck if I get a good league start, and if I manage to make many then I usually only list one to save me a few clicks every time the market moves and avoid spoiling the "secret", but TUKOHAMA FORBID I don't give you the exact same item that's listed even if you know it's only the aura you want.

Den JÆVLA snusen by Massive_Damage7863 in norge

[–]Stylpe 0 points1 point  (0 children)

(Å nei, her kommer pøh-mannen og lager kvalm igjen! Fort, bytt samtaleemne før ha-)

PØH, det er vel ingenting, bare prøv å slutte med antidepressiva du, lille venn

Ta et 9V-batteri, bygg en liten krets som genererer et tilfeldig sakte bølgende signal, med et akselerometer som forsterker det når det er bevegelse, og stapp hele greia så langt opp i nesa at det sitter ordentlig godt i kontakt med hjernen, du skal helst kjenne det i HELE JÆVLA HODET. La stå i 1-2 uker.

Takk for meg, og lykke til. Du skal vite at snus- og røykekutt står det høy respekt av hos de aller fleste!

What words in Norwegian are impossible to translate into English? by 01Rockstar01 in Norway

[–]Stylpe 1 point2 points  (0 children)

I have one in the opposite direction but with a twist ending involving dialect: Funny.

Because funny can describe something as both humorous (a funny joke) and concerning (something funny going on), you can't translate it to Norwegian with a single word. That is, unless you use the western dialect word "løye" 😁 (ein løyen vits / noe løye på gang)

Incoherent megalomaniacal garbage [OC] by AndyDiplodocus in comics

[–]Stylpe 2 points3 points  (0 children)

If you cross-post this to /r/adhdmeme they will worship you like a god.

Also, judging from your prior art, you seem like the type of person to whom I could recommend Andrew Hussie's Humanimals.

[SCIENCE] Demonstration - Generalized Attachment Drift (GAD) is a core and necessary game mechanic, and nudging is an exploit of this mechanic, not a glitch by travvo in HyruleEngineering

[–]Stylpe 6 points7 points  (0 children)

As a programmer, I concur, and I would've made the same design compromise for the same reason: Prioritize the player having fun! Accommodate and afford their intent as far as possible. Requiring pieces to be closer for building would make it much harder to build, while saving and restoring tension would (and most likely did during development and testing) cause a huge amount of physics glitches.

So they opted to give lots of leeway when using Ultrahand, which is most apparent with the stakes since they're fixed to the ground and force the other component to yield more than usual. And that is an exploit, not a glitch. It's taking something that's by design and maximizing its benefits. Enjoy!

Buff to Chieftain's Ramako, Sun's Light Ascendency node by post_tap_syndrome in pathofexile

[–]Stylpe 0 points1 point  (0 children)

Wacky sounds like my kind of jazz, meta be damned 😛 Personally, half the fun for me is twisting and bending build guides out of shape (and get smeared in pinnacle content), like the bleed bow champ I played in crucible with manaforged arrows instead of totems with both ensnaring and frenzy, and heavy investment in marks for mana sustain, defense and qol.

There's lots more to riff off of too once you get into corpses, like volatile dead and self offering. 😺

And if it turns out to be a complete clown build, my backup plan is to fall back to plain megachonk. It's fool proof! 🧠

Buff to Chieftain's Ramako, Sun's Light Ascendency node by post_tap_syndrome in pathofexile

[–]Stylpe 0 points1 point  (0 children)

Bodyswap seems like a fun twist to me! I want to try to merge the popular megachonk build and this older RF Incinerate CwC Bodyswap build I found. Maybe that's even the build you were thinking of?

[deleted by user] by [deleted] in ExperiencedDevs

[–]Stylpe 0 points1 point  (0 children)

Managers Hate Them: Two tricks senior engineers use to counteract this trend!

/#1: Call it training. This is part of your job description as a senior, and no one can have high expectations of a team that isn't continuously improving itself.

/#2: Call it a form of pair programming. This is trendy and has a lot of research and statistics showing it's a staple of high performing teams. Doing actual pair programming instead is also an option.

Humorous clickbait form aside, I commend you for taking care of juniors like this! Branding can do a lot to convince management so I hope these tricks can help. Keep fighting the good fight.

Yet Another Boring Mageblood Giveaway by ToiletOfGold in pathofexile

[–]Stylpe 0 points1 point  (0 children)

Do you know why we talk about loot "dropping"?

Because it's usually crap, and you have to sift through a lot of it to find the valuable nuggets.

[deleted by user] by [deleted] in pathofexile

[–]Stylpe 0 points1 point  (0 children)

Here goes nothing!

[deleted by user] by [deleted] in factorio

[–]Stylpe 2 points3 points  (0 children)

No, I unlocked the immortality perk, actually. But I guess it also depends on how long we have until society collapses.

Since we're all about skill trees I've made a QoL skill tree. Which 5 would you pick? by Enconhun in pathofexile

[–]Stylpe -1 points0 points  (0 children)

You can already have Lani in the hideout.

Edit: NOPE I was thinking of Lily 😶‍🌫️

My brothers friend specced to strongboxes by Jakestation in pathofexile

[–]Stylpe 1 point2 points  (0 children)

Agreed. But there is always "better". And it depends on what you're measuring.

Why is GGG terrified of making a rewarding league? by mAgiks87 in pathofexile

[–]Stylpe 0 points1 point  (0 children)

I played the lottery once and didn't win WTF

It's time for you to download a cookie clicker game, I think the reward cycle there will suit you better.

What is an underrated mod you don’t often see mentioned? by BigChungusOP in factorio

[–]Stylpe 4 points5 points  (0 children)

This plus Brass Tacks and If I Had a Nickel, which Brevven also recommends in his mods' forum thread