2021.10.24 11:55 WaspishDweeb Looking for non-sketch 'avant-garde' black metal
In the style of Deathspell Omega (fuck Aspa), Imperial Triumphant or polish bm-bands like Furia or Medico Peste - the latter I know to be a bit uncomfortably close to NSBM projects. You folks got any recs?
submitted by WaspishDweeb to rabm [link] [comments]
2021.10.24 11:55 slanten85 Should I submit my SAT scores to UChicago?
2021.10.24 11:55 Illustrious_Row6195 What do you do when you get bored?
2021.10.24 11:55 swagNextTuber 11 Beauty Products on Amazon You Need in Your Life Right Now
|submitted by swagNextTuber to TrendingQuickTVnews [link] [comments]|
2021.10.24 11:55 CulturedGrass Don't be fatphobic guys it's not my fault I weigh more than an elephant.
|submitted by CulturedGrass to gayspiderbrothel [link] [comments]|
2021.10.24 11:55 Prize_Guest How does one find brand name perfume on sale or is it something that never does?
2021.10.24 11:55 Neat-East-1054 Hodl
2021.10.24 11:55 SpektrumKid Question from a noob: what’s the best hood for errand biking in LA?
Personally I’d commend Santa Monica for almost having safe biking infrastructure.
But as a current New Yorker, I can’t recall seeing any protected bike lanes at all in LA last time I visited.
Have things changed since 2017?
submitted by SpektrumKid to BikeLA [link] [comments]
2021.10.24 11:55 thumbsdrivesmecrazy Raising Startup Funding In 60 Days With No Product - Step by Step Guide
In the following video guide, Karan Bajaj, former CEO and Founder of WhiteHat Jr, now BYJU’s FutureSchool shares his 3-Step method to raise startup funding in 60 days with no product: How to Raise Startup Funding In 60 Days With No Product
Here are the key steps explained:
2021.10.24 11:55 Wonder_bread423 I haven’t heard from them in 5+ years and today I get this. I’m disfellowshipped, should I even reply? I’m dying to know the topic...
|submitted by Wonder_bread423 to exjw [link] [comments]|
2021.10.24 11:55 sunshineangel5 meirl
|submitted by sunshineangel5 to meirl [link] [comments]|
2021.10.24 11:55 SirRHellsing IDK where to ask this but can someone walk me though the ebay shipping process?
I'm from Canada btw
My main question is
2021.10.24 11:55 n3rding ccccc
2021.10.24 11:55 Thendrail Anon tries drugs
|submitted by Thendrail to greentext [link] [comments]|
2021.10.24 11:55 tokenmaker1111 GIF by TokenMaker#7810
|submitted by tokenmaker1111 to MoonbeamAmbassadors [link] [comments]|
2021.10.24 11:55 Comprehensive_Moose5 Expensive braces
|submitted by Comprehensive_Moose5 to memes [link] [comments]|
2021.10.24 11:55 PracticalStudio5681 What do you think happens first, Bitcoin 100k or Ethereum 5k?
|submitted by PracticalStudio5681 to ethtrader [link] [comments]|
2021.10.24 11:55 squawkalley Baldwin fatally shoots Hutchins Update: Gun used for offset target practice, live and blank ammo stored together
|submitted by squawkalley to CWEB [link] [comments]|
2021.10.24 11:55 MaryAngelSinger Mary Angel singer-songwriter recording her first album
|submitted by MaryAngelSinger to RepublicOfMusic [link] [comments]|
2021.10.24 11:55 HardcoreHorse2313 Spell idea: Light beacon
Idea: a spell that can be targeted at an enemy building/wall/hero, that makes the friendly units around it (within a certain radius) switch to that target AFTER they have finished attacking whatever they're currently targeting, and it only works if the spell is still active (it will have 2-3 seconds of duration).
Further explanation: I'd like to use a simple scenario to make you understand what I'm trying to say. Let's assume that you have a bunch of dragons destroying a base. 2 of them are attacking a gold storage, and right next to it is a tesla and a dark elixir drill. Just when the gold storage is about to get destroyed, you deploy this spell on the tesla to make those 2 dragons attack that tesla next. Note that the rest of the dragons won't be affected since they are out of its radius. To balance this, the spell will only work on troops in a short radius around it (maybe the same as the lightning spell), and it will only work if the dragons finish the gold storage during the duration of the spell. I think this will be a huge help for troop pathing, and especially for queen walks, or to prevent the queen from walking to a target/direction you don't want her to. You will have a very short time period to act quickly to make her re-target, and she would also have to be in range of the spell for it to work. This obviously needs tweaking and refinement but I'm just throwing the raw idea out there.
- Spell only works on troops in a short range around the building it target
- The friendly troops have to finish the building they are currently attacking during the duration of this spell for it to work (this will basically guide them to their next target when they finish a building and try to calculate which building to attack next)
- It won't affect troops' favourite/preferred buildings. For example, if a giant and a pekka are in its radius and you aim it at a gold storage, only pekka will attack it, but not the giant since its not a defense.
- Lab upgrades can increase the duration of the spell
- This will be a crucial spell if you have a queen charge planned
- It won't defy the range limits of the troops, for example if you put it on a building which the queen can't reach, she will NOT be able to target that building (but again, she would also not be in the radius of the spell, so this scenario is unlikely to happen anyway)
- May also be used to force a wallbreaker to hit the exact wall you want it to, but probably a waste of the spell since you can get much better value in most other scenarios.
This is just an idea I came up with, of course its probably highly unbalanced/broken, completely useless or stupid. But I just wanted to share it. I'd like to hear your thoughts on this!
submitted by HardcoreHorse2313 to ClashOfClans [link] [comments]
2021.10.24 11:55 The_Dream_Shake_1994 Asked to speak at a health law society meeting at a local law school. Looking for input.
Hello friends. My name is The_Dream_Shake_94 and I'm a 3rd year med student in a state that doesn't respect women's rights. I'm pretty into health care policy, so I got approached about being on a panel of med students, law students, dental students, pharmacy students to discuss the intersection of health care and the law.
I was given some starter questions to prepare. I have my answers down for them, but I know my experience might not be indicative of everyone in medical school so I was wondering if yall could give some input if you're particularly opinionated about any of the questions. That way I can bring a more well rounded set of idea when I speak. Thanks for the help!
2021.10.24 11:55 Funnylife_2021 Korean former president Moo Hyun
|submitted by Funnylife_2021 to korea [link] [comments]|
2021.10.24 11:55 colacodacoke I just showered and I always have these flakes on my scalp that I can peel off. They’re always at the same spots too. What are these?
|submitted by colacodacoke to DermatologyQuestions [link] [comments]|
2021.10.24 11:55 Dwight-D TDD and git commit workflows
I've recently made a point of improving my git commit discipline instead of just squashing my mangled
wip: foo style commit history before merge and I have some questions about best-practices when it comes to my workflow. This is what I typically do for a new feature (sorry in advance for wall of text):
I do pretty lax TDD, generally I might start off with sketching out the feature on a whiteboard at a high level as a sequence diagram or something. Then I write the code for the top level interface I/O, defining the high level API of my feature, make an integration/E2E test calling that API, and then assert on some outcome, like finding some new data in the database or whatever. This test will of course fail until the happy path implementation is done.
Then I start breaking the feature down into smaller components, maybe I will outline the high level flow at the application layer by defining new subcomponents & routines and calling them from the high level API to sketch out the equivalent of my sequence diagram in the top level API, even though none of these components are finished yet. Then I litter the new underlying code with
NotImplException or whatever as placeholders so my code compiles until I'm done with the implementation. Then I start adding more granular tests for some of those subroutines, maybe add in some more test cases covering error handling etc in the high level API test I started off with etc. In this way I flesh out the implementation until it's complete and I can run all the tests on my high level API without errors, and maybe do another pass of error handling and test coverage to top it off.
However, I'm not sure how to handle checking in my commits as I go about doing this. I like to commit at various points here e.g. when I add new interfaces, when I finish the implementation of some subroutine or component etc, just to have my work backed up and documented.
If I check these commits in in roughly the same order as I write the code I will of course have a series of commits that compile, but where the tests fail, there may be dangling code, runtime exceptions, empty function definitions etc. These are essentially WIP style commits but that still have some structure and context provided in commit messages etc. Is this okay or considered bad practice?
I can see an alternative approach where I could try to structure my workflow with even more discipline. I could skip checking in that first high level API & test and other interface definitions with unfinished implementations, and restrict myself to adding finished chunks of tested and working but not yet called code that makes up the subroutines comprising my larger flow.
By doing this I will avoid checking in unfinished code paths and broken test suites. However, this is basically the reverse of my actual work process, so I feel like it doesn't capture the spirit of how and why the code was written which might make it harder to understand the thought process behind the changes. It would also require me to restructure my git history quite a bit and get into some pretty complicated git workflows in order to "skip" all the work that lead up to me discovering the finished chunk I'm about to check in, which of course introduces a lot of overhead that provides questionable value.
Alternatively, I could just structure my work in a different way. Instead of starting from the high level implementation I could try to think ahead to the low level components I will need and start with them, writing small and atomic functioning & tested code blocks and checking them in as I go. But doing this I see a risk of wasted work as I make incorrect assumptions and may end up having to rework them later anyway, or risk doing stuff I end up not needing.
I would be grateful if you could share your workflows that involve some level of testing and commit discipline, or your thoughts on mine.
submitted by Dwight-D to AskProgramming [link] [comments]
2021.10.24 11:55 CapAmericaJr Venezuelans Break Off Flakes of Gold to Pay for Meals, Haircuts