Hi!
I'm Hazel, and this is your guide to the Pilfer pet battle on Argus.
I'm going to start with a super quick strat for world questing, then go through family
specific teams for the Family Fighter achievement.
Pilfer lives here in the Antoran Wastes.
I don't know what he could possibly be stealing out here but it's time for it to stop.
First up, the fastest strategy for when you just wanna get your World Quest done and go.
This also doubles as the Beast Strat.
First is any raptor with more than 263 speed set up with Exposed Wounds, and second is
your Zandalari Anklerender or Kneebiter with Black Claw and Hunting Party.
Any third beast should do but another Falcosaur won't hurt, especially if you're not rocking
the full attack breed of the first one.
Starting with the Exposed Wounds raptor, use Exposed Wounds and then promptly die.
Bring in your favourite Zandalari Comborender and use Black Claw, then Hunting Party.
The first round is only OK but after that it really kicks into high gear.
Problem solved.
Next is Aquatic.
I'm using my Ghost Shark with Huge Sharp Teeth, Ghostly Bite and Dive, a Sea Calf with Water
Jet, Bubble and Blood in the Water and in third is my new Lagan eel with Deep Bite,
Dodge and Dive.
A Slithershock Elver would also work assuming that your breed sports more than 263 speed
which mine regrettably does not.
Starting with the Ghost Shark use Dive, then Ghostly Bite.
Sure, you stun yourself, but he's recovering over there for at least one of those rounds
so we're good.
After Ghostly bite you pass your stun round and use Huge Sharp Teeth twice before your
Ghost Shark double dies.
Bring in the Sea Calf and use Blood in the Water, then Bubble, then start spamming Water
Jet.
His bleed falls off before we get Blood in the Water back up so we can just stick to
Water Jet until the Sea Calf dies.
Out comes my eel so I'll use Dive, then Dodge, then Deep Bite three times.
Repeat that cycle one more time- Dive, then Dodge, then Deep Biting.
Those early bites just tickled but by the end we're really quite chompy.
Next we'll do Critter.
I'm using the Darkmoon Rabbit and it is key that it's a Darkmoon rabbit set up with Huge
Sharp Teeth, Dodge and Burrow, a Sneaky Marmot with Jab, Blinding Powder and Smoke Bomb and
a Darkmoon Hatchling with Trample and Predatory Strike.
This one is kinda long so buckle up.
Starting with the bunny use Dodge, then Teeth, then switch to the Marmot.
Use Blinding Powder, then Jab three times, then Blinding Powder again.
Switch to the Darkmoon Hatchling.
Use Trample three times, then switch back to the Rabbit.
We'll use Burrow, then Dodge, then Huge Sharp Teeth three times.
Burrow again, then Dodge, then Huge Sharp teeth again until your rabbit finally dies.
He's about to Cannon so I'll bring in the Marmot and use a quick Blinding Powder.
Swap to the Darkmoon Hatchling and seeing as he's below a quarter health, Predatory
Strike.
I knew I kept that lanky purple bird around for a reason.
Next we've got Elemental.
I'm using a Pandaren Water Spirit with Water Jet, Dive and Geyser, a Ruby Droplet with
Absorb, Bubble and Draing Blood and third is a Nightshade Sproutling with more than
263 speed useing Lash and Blinding Poison.
That sproutling could be swapped out for a Forest Sprout over 263 speed with Refuge or
even the Bound Stream with Dive.
Starting with the Water Spirit I'll use Dive, then Geyser, then Water Jet twice.
I swap in my Ruby Droplet and use Bubble, then Drain Blood for the Damage, then Absorb.
Switch back to the Water Spirit.
Geyser again, then Dive, then Water Jet one more time before the spirit's done.
Bring back the droplet and use Absorb, then Bubble, then Absorb again.
For a bit more damage and to wait out the bubble cooldown I'll swap in my third pet
and use Lash, then Blinding Poison, then spam Lash.
My Nightshade doesn't quite finish it off but he does eat the cannon, leaving my droplet
to Drain Blood and seal the deal with Absorb.
He's still got all his health points, look at that!
Next is Humanoid.
I'm using a Sister of Temptation with Agony, Curse of Doom and Lovestruck, and second is
Squirky with Punch, Stampede and Bubble.
I threw a Lil Bad Wolf in third but didn't need it.
Starting with the Sister use Lovestruck, then Curse of Doom, then Agony.
She dies to the cannon, at which point we'll bring out Squirky.
Use Bubble, then Stampede.
Stampede itself is doing weak damage but that 100% damage taken debuff affects both the
end fo the Agony and the Curse of Doom, which is really nice.
After Stampede Two good Punches finishes the fight.
Next we'll do Mechanical.
I am for possibly the first time ever using a Rabid Nut Varmint with Rabid Strike, second
is my Pocket Cannon with Explode and third is my favourite Darkmoon Zeppelin with Missile
and Decoy.
Starting with that rascally Nut Varmint spam Rabid Strike until it won't let you anymore.
In my experience you get four.
Roll in the Pocket Cannon and pick any damage shot.
Press it twice for one shot, then use Explode while he's still got that Rabid debuff.
On the Zeppelin, throw up your Decoy and start spamming Missile.
It never lets me down.
Next we've got Dragonkin.
First slot is the Twilight Clutch-Sister with Tail Sweep, Phase Shift and Twilight Meteorite.
Second and third slots are my Nether Faerie Dragon and Sprite Darter Hatchling respectively,
both with over 263 speed and set up with Arcane Blast, Evanescence, and Moonfire.
Start with that Clutch Sister and use Phase Shift, then Meteorite, then Tail Sweep three
times.
Use Phase Shift, then Tail Sweep, then one last Twilight Meteorite before the Clutch
sister dies.
Bring in a faerie dragon and use evanescence, then Moonfire, then three Arcane Blasts.
Again- Evanescence, Moonfire, Arcane Blast away.
When your first dragon dies and the second one comes out, follow that same pattern.
Evanescence, Moonfire, Arcane Blast three times.
Or as many as it takes for him to keel over already.
Next is flying, and I bet you've heard this song before.
First slot is a Skyfin pet with Wild Magic, and second is Ikky with Savage Talon, Black
Claw and Flock.
Start with the Skyfin and lay down Wild Magic, then heroically eat the cannon with your finny
little body.
Bring in Ikky and use Black Claw, then Flock.
That almost does it but before you go AFK hit Savage Talon at least once to really polish
things off.
Next up is Magic.
I'm dusting off my Nightmare Bell and setting it up with Shadow Shock and Dark Rebirth.
Second is the Lofty Libram or other book pet, more than 263 speed and take Shadow Shock,
Amp Magic and Curse of Doom.
Any third pet will do, I slung along my Twilight Fiendling but your favourite Surge of Power
pet is also a safe just in case bet.
Starting with the Bell, use Shadow Shock four times, then Dark Rebirth.
Shadow Shock another three times before you lose your bell.
On the book use Curse of Doom, then Amp Magic, then start mashing the Shadow Shocks.
The Magic racial is almost always underwhelming but versus the cannon pets it feels like cheating.
Last is Undead.
I'm using my Unborn Val'kyr with Curse of Doom and Unholy Ascenscion, and second is
a Restless Shadeling featuring more than 263 speed with Shadow Shock, Plagued Blood and
Phase Shift.
That could be easily swapped for a Ghastly kid with Diseased bite and Ethereal.
Third slot can be any Undead Pet, I brought a Ghost Maggot and included Survival just
in case.
On the Val'kyr, use Curse of Doom, then Unholy Ascenscion.
The Shadeling's about to do a lot of work over here.
Go Plagued Blood, then Phase Shift, then Shadow Shock six times.
You really just Shadow Shock him to death if we're being honest.
So, that's Family Fighter Pilfer!
Thank you so much for watching.
Subscribe for the rest of the Family Fighter guides and other super cool WoW videos.
Let me know what you think, share your own strategies in the comments if you like and
have a wonderful, wonderful day.
Bye!
For more infomation >> Pilfer Pet Battle Guide and Family Fighter Strategies - Duration: 7:35.-------------------------------------------
BF1 Martini-Henry Sniper Weapon Review & Guide - Spring Patch Weapon - Duration: 5:48.
-------------------------------------------
Battlefield 1 - PERINO MODEL 1908 Waffen Review ► BF1 Guide (DLC Waffe) - Duration: 5:53.
-------------------------------------------
A NON LEADER'S GUIDE TO CREATING A REVOLUTION - Duration: 4:40.
A NON-LEADER�S GUIDE TO CREATING A REVOLUTION
Throughout history there have been a number of movements, initiatives, and projects that
played an integral role in making the world into what it is today.
Whether they shattered unnecessary boundaries, forged relationships many thought would never
be possible, or enabled us to connect with one another like never before, so much has
already been done for which we should regularly give thanks.
And at the core of each of these movements there always lies a leader who either invented
the now-revolutionary idea or was the one who had the courage necessary to bring it
into the public eye.
Despite so many great changes having already been made, we all know that our world is far
from perfect.
And while certain political, environmental, or spiritual figures may be at the forefront
of efforts to instigate bigger level changes many of us would love to see implemented,
what about the issues still being swept under the rug?
Are we all expected to stand on a soapbox with a megaphone at a busy intersection?
And if so, what about those of us who claim to not have a �leadership� bone in our
body?
The good news is, we truly can all make a difference, and that�s why I�ve put together
this non-leader�s guide to creating a revolution.
Let me start off by clarifying that when I say revolution, I�m not referring to something
as grand as you are likely imagining.
To me, a revolution is any change that directly impacts your way of being.
If it extends beyond you, awesome.
But even if it�s something that solely you experience, it can still be, in my opinion,
revolutionary in nature.
So how can we as non-leaders create change?
The answer is quite simple: You must recognize and then embrace the power that comes from
being a follower.
To illustrate this, I�d like to reference a 2010 TED Talk given by writer and entrepreneur
Derek Sivers, who uses footage of some party-goers at an outdoor event to share an important
message.
The video begins with one individual (the leader) dancing on his own on a hill, an action
that most of would immediately laugh at or mock.
The leader, in true leadership fashion, is seemingly completely unfazed by what others
may or may not be thinking of him and his actions.
Eventually, the leader is joined by another individual (the first follower), whom he openly
embraces.
As more time passes, the pair is joined by a small group, and then another, until eventually
the vast majority of attendees are now partaking in what they once saw as embarrassing or foolish.
The question that Derek poses is, who deserves the most credit for creating this movement?
Most would answer that it is the courageous leader who danced to his heart�s content
despite the risk of ridicule.
But the truth is that it is the first follower that instigated the revolution.
It�s the first follower who transformed the leader�s actions from simply being outside
of the norm into a movement � a movement that eventually reached a point of critical
mass where it became less popular for an attendee not to participate than it would be for them
to dance along.
That first follower recognized the potential power that he had within himself and then
embraced it by joining in with the cause that he believed in.
We too have that same potential with every change that we would love to see take hold
in this world.
Rather than seeing yourself as one tiny fish in a massive sea, see yourself as a key player
bringing your cause that much closer to a point where it is publicly acknowledged.
Thankfully, the world is blessed with a plethora of leaders and inventors who, more than anything
else, are looking for people to believe in their efforts.
So if you feel that you aren�t meant to be a leader, or you lack the resources to
make that possible, recognize that you�re inherently rich in your ability to empower
others.
Do you enjoy uplifting personal development content like this?
I release a new article and video like this every week!
Join my mailing list HERE to have the newest content sent directly to your inbox.
All new subscribers receive 3 free tools designed to help you conquer all forms of anxiety within
48 hours of signing up!
-------------------------------------------
Paper Clay: An epic guide to an epic craft material - Duration: 7:11.
hello and welcome to fiction forge thank you so much for joining us for our very
first episode today we're going to show you how to make an awesome crafting
material full paper claim take the place basically just like this amass a accepts
its blended instead of added in layers and additional ingredients are added to
the mix in order to give it additional properties which make it much better for
sculpting
there are many brands of paper clay available to purchase both online and at
well-stocked arts and crafts stores they offer a high quality clay but are
relatively expensive they even seem to be some books available on the subject
and look at some of the war some stuff people have managed to pull up with them
there are some pros it is cheap and easy to make yourself the ingredients are not
hard to come by it is non-toxic and safe to handle it there hardens so there's no
need for a kill it has great strength to weight ratio it is very easily shaped
and colored it can be frozen for use another time and now here are the cons
it's not weather proof without a waterproof coating the weight stuff will
rot not preserved or frozen the final result will not be consistent if not mix
well when made correctly you can make some truly awesome stuff with this
material there are some of our past projects that are made almost entirely
from the paper clay
is what you'll need to get started a source of paper the finer the paper the
finer the clay pre pulped paper starch basic uses PVA glue some linseed oil to
use as a preservative plaster of Paris a drill and a paint stirrer attachment a
blending one and water to add as you make good so we got everything we need
yet to make those paper clay so we're going to start by taking each of the
ingredients individually adding them into the bucket and then mixing them
with the troll in the pastry so let's get started
so once you get it with the sort of points where you can grip it in an
election keep shape then what we like to do is move on to a secondary form of
blending but in the form of this blender warm
we are mending without fighting gendered stuff that is going to be perfect for
stoking the fire until it was a drying order and create a smooth finish without
this trouble this yet is the next line down stuff it will be perfect for being
the lion's share of the software and then we just switch to the finer stuff
and the skinny all right so now we're happy with the
consistency and texture of our package Mike what are going to make with it
join us next time and we'll be showing you how to make some truly unique and
beautiful places to keep your phones we call them plant gaudiya it's keeperfill
creeper it's more like a creature for your cactus that's like in God we are
God that's more like a sense or your succulent
you mean like bodyguard feel Bush sort of that's a friend for your flowers you
see sounds like a buddy be a bonsai yes I know me feel hurt
I stood the sculpted floor for you guys now this bit goes if you want to give us
a hand and help us make this a regular thing then please like and subscribe
we would also love to hear from you your thoughts and your ideas please leave
them in the comments below
-------------------------------------------
Introducing The Bard College of Glamour In Xanathar's Guide To Everything - Duration: 8:28.
- The Bard College of Glamour is for
the rock stars of the D&D Multiverse.
They have strong connections to the Feywild
and they inspire devotion in their fans.
I talk to Jeremy Crawford about this new subclass
in Xanthar's Guide to Everything.
- So, the College of Glamour was a subclass
that in our brainstorming came up
partly inspired by a bard that was in
my previous D&D campaign.
Michele Carter, one of our editors, played a bard
in my campaign whose father had been whisked away
to the Feywild and was raised there
and throughout the entire campaign we described
her bard's magic as being suffused
with the power of the fey and so I thought,
what if we made a whole college about this?
That, that, a college of,
of, of bardic magic
that would not only be used by people in the mortal world
but would also basically be the college
that would be engaged in by bards in the Feywild.
And so thus, the College of Glamour was born.
Also aesthetically, Mike and I early on talked about
essentially, having figures like Freddy Mercury in mind,
ya know, so this bard who is just
crazily fabulous and beguiling
and, again, like we do with all of the subclasses,
we wanted it to feel different
from the bards in the "Player's Handbook".
"Player's Handbook" we have the College of Valor,
which is very much about sort of wading into battle
and inspiring one's companions.
Very much kind of a scald in a historical sense.
We have, then, the lore bard
which is much more about knowing all these great stories
and manipulating other people's minds and emotions.
A bard who could be seen as almost a bit of an intellectual
but also as sort of a trickster.
It's kind of open ended enough that you can push
that bard in either direction.
So we felt there was a place for a bard that was instead
was all about the beguiling magic of the Feywild
and so the College of Glamour, play testers really liked it.
And we refined it to really just enhance
what they liked about it and that is this, this bard
who is able to beguile people using their class features
and not just using spells.
A bard who once they're a high enough level
can make it difficult for people to even attack them
because essentially the people become their fans
because again, again, full disclosure,
in addition to being inspired by stories of fey creatures
and their beguiling abilities, we were also again inspired
by the idea of the College of Glamour
sort of being a pop star
and so there's a little thread in some of the class features
of basically people becoming
the College of Glamour's, that bard's, fans.
Like, you know, we're gunna do what you say.
We're not gunna hurt you.
This is the bard who is just unbelievably fabulous
and, as we say in the book, a bard who could be pushed
in a heroic or a villainous direction.
On one hand you can imagine members of this college
bringing great delight to people.
You know, the bard who brightens the dreary lives
of peasants wherever the bard goes,
who has, you know, just a wondrous, colorful magic,
who soothes their broken hearts, you know,
brings this magic that's so beautiful
it just pierces them and they, you know,
they cry tears of happiness but you could also imagine
a member of the college who is manipulating people,
getting them to do what he or she wants
and can be a bit of a terror and in this,
this bard is very much an appropriate
sort of representative of the Feywild itself.
A beauty that is a double edged sword that can, you know,
cut in your favor or it can cut against you
and so this bard is an interesting contrast
and a very intentional contrast
with the Circle of Dreams in the druid.
Where there we leaned into kind of how the beauty
of the Feywild can soothe and protect,
here we're leaning into the fact
that that beauty can be perilous and you don't always know
if it's on your side
and, but also with this subclass,
whatever way that, that, that blade of beauty is cutting,
it must always be fabulous and that was, that was, it was,
it's funny, College of Glamour
is actually one of the earliest
subclasses we talked about including
when we were coming up with the whole set of subclasses
for the Unearthed Arcana series
It's just cause for some reason it just tickled me and Mike.
We were just like, we definitely want to do this,
we, hopefully testers like it and thank goodness they did
and now it's in the book.
So a member of the College of Glamour
can acquire their abilities in a variety of different ways
and we always like to leave it pretty open ended
for our players to decide exactly how they became
a member of their subclass in terms of their story for why.
We give suggestions, so, one way that a member
of the College of Glamour may have become a member
is by being from the Feywild, you know?
Perhaps you were whisked away as a baby
and you actually grew up in that fey realm
and because of that you are now suffused
with this strange magic and it alters
what you can do as a bard.
You can easily imagine, though, another member
of this college who maybe studied under a fey being.
Perhaps, you know, found a glade in a forest somewhere
and heard a dryad singing and became her student
and a result of her tutelage became a member
of the College of Glamor.
So, I think there could be a lot of, actually,
really great stories, not only for this subclass
but also for many of the subclasses in the book.
For, how did you become a member of this subclass?
It's particularly easier to do that when you're in a class
that does not get it's subclass at first level.
Cause some classes, right when you pick the class
you pick subclass and so often your story
for a class like that, for why you are a member
of a subclass is kind of inextricably intwined
with why you became a member of the class itself.
In contrast, when you're a member of a class
where you pick a subclass at second or third level,
that little time delay then gives you a chance, story wise,
to think more specifically, well why am I a member
of this subclass and not another and how is that related
to my character's past, how is that related to where
my character is going down the line in the campaign,
how might it inform the story the DM wants to tell
with me about my character?
Cause I know a lot of DMs like to sprinkle in things
in a campaign tied in with each character's story.
I know it's something I do as a DM.
I always try to have something in the campaign
for every character at the table that relates
to their background, someone who is important to them
in the past, it might have to do with their subclass,
and again I think the College of Glamour in in particular
is very rich in terms of coming up with character's stories.
You know, again, it could have been a dryad
you studied under.
It could have been a satyr.
You heard a satyr's beguiling pipes and then wanted to know
well how can i be a beguiling as this strange being?
And again, the College of Glamour give you a chance
to play a character who is a bit like a satyr
in terms of entrancing people with performance.
- The Bard College of Glamour is part of
"Xanthar's Guide to Everything".
You can purchase that book on www.dndbeyond.com
by clicking on the link in this video description.
I'm Todd Kenreck, thanks for watching.
-------------------------------------------
The Druid Circle of Dreams In Xanathar's Guide To Everything - Duration: 8:23.
- The Druid Circle of Dreams is
deeply associated with the Feywild.
Where that can be a very dangerous realm,
the Druid Circle of Dreams essentially
can provide comfort and safety
and protection to those around them.
I talked to Jeremy Crawford about this
new Circle for the Druid class
in Xanathar's Guide to Everything.
- We brainstormed all sorts of things,
and any time we brainstorm, it's funny,
either Class options or Monsters,
I will always look for an opportunity
to insert something that has to do with the Feywild,
because in my home campaign, I always
have things from Feywild, or otherwise
known as Faerie, whether it's Hags
or beautiful Fey creatures who will help you,
or perilous beautiful ones who harm you.
I love this kind of Fey connection.
There's so much great folklore having to do
with the Fey in the real world
to draw on for D&D adventures.
It's also an aesthetic that I know
that not only I enjoy but many D&D players enjoy.
It's an otherworldly quality, it's resonant
because it's something that is in
so much folklore, but feels alien
at the same time, and so when we were
brainstorming for the Unearthed Arcana series,
and then the eventual Xanathar's Guide,
as usual I took my opportunity
that we need some Fey thing for the Druid.
And part of that is because the Druid
is often associated with animals, plants,
Elementals, but also Fey creatures,
and that association with Fey creatures
goes all the way back to First Edition,
where Druids, among their spell options,
had things like Call Woodland Beings,
where you could suddenly call forth
various Fey creatures to assist you,
and it's also appropriate that this
association exists because even in
Irish mythology, Druids are often
in the same stories with creatures
from what would be called the Otherworld.
Often they're actually opposed
to each other in the Irish myths,
but again, D&D so often transforms things
from other sources, and so in D&D,
it's often now the Druids who are befriending
these Fey creatures, or even controlling them.
So the Circle of Dreams is meant to be
a subclass that leans heavily
into the Fey side of the Druid.
Its identity is to be, the Druid
who channels the power of the Feywild
to help his or her friends, to
be a little tricksy in terms of
having teleportation, which is something
we include often with Fey beings,
but to largely be one who is emphasizing
sort of the group support angle of the Druid.
We often have multiple goals
whenever we're creating a subclass.
We want a good story, we want fun abilities
in and out of combat, but we also wanna
fill role gaps that exist among
the subclasses that are already in the game.
So we felt like, we already have, in a way,
in the Player's Handbook, the Nature Wizard
in the form of the Circle of the Land.
We already have the Druid who focuses
on shape-changing, largely to engage
in battle, with the Circle of the Moon.
So we wanted this Fey Druid that was
focusing more on helping allies
through healing and whatnot,
so Circle of Dreams has enhanced healing abilities.
Also the themes in the subclass
draw both on what we refer to as the Seelie Court
and the Unseelie Court in the Feywild,
so there are things that basically
have to do with both sunlight and moonlight,
and the whole thing is sort of wrapped up
in this package of the Circle of Dreams,
because we're leaning into kind of
the dreaminess, the dreamy side of the Feywild,
and also there's sort of a poetic nod
to the fact that this is the Druid
who brings you comfort, and not only heals you,
but also has abilities to protect your group
while you're taking a rest, and then over
the course of the playtest process,
one of the things I added in to the subclass
that is now in the final version,
is that the Druid can basically
have you travel through dreams,
once the Druid gets up to a high enough level,
by casting a special form of Teleportation Circle
where you teleport to the last location
where you had a long rest on the same
plane of existence, and this is a really
flavorful ability that I'm looking forward
to seeing it being used in campaigns,
because I think some groups are gonna figure out
that this could be a really clever way
to deal with certain obstacles in games,
and also a way, an escape hatch,
but it's also gonna be fun to have
the Circle of Dreams Druid always
need to remember, okay, where's the
last place we took a long rest on this
particular plane of existence?
Now, what that means is when you
visit a plane of existence for the first time,
you have no place to teleport back to,
so basically you've gotta get that
night of rest on each plane of existence,
so essentially you have, all right,
I now have an anchor, a place that I can then
transport us through the dream realm back to,
and as long as you have that place, you have
that hopefully safe place you can go back to.
I can see some DMs messing with the group
if their foes start figuring out
they're doing this, and basically camping out
on the previous long rest locations,
of all right, we've traveled back to that inn
where he had our last long rest, oh look,
the Orcs are waiting for us in our room.
- [Todd] Yeah, that's like the fourth or fifth time
they've used that, someone's gonna figure it out.
- Again, it's a fun, flavorful,
and can potentially be a campaign-defining
kind of ability, so I think people are gonna
have a lot of fun with this subclass.
We know with other Fey and sort of
ancient type themed things that
players really love this stuff, like
people love the Oath of the Ancients
Paladin in the Player's Handbook.
Circle of Dreams very much is meant
to stand side by side with something
like the Oath of the Ancients,
and feel like the kind of thing
like the ancient, cultures associated
with the ancient Druids and with
Elves, that this would be a very
natural role for them to fill.
The Feywild is often perilous, but
the Circle of Dreams Druid is able to
take that magic and use it to their
friends' benefit, not unlike actually
a Fey being, because the Feywild is perilous
often for non-Fey beings, people who are not
native to that strange realm, and so in a way
the Circle of Dreams Druid is like
a Fey creature, in that they're able to
make that Fey magic be helpful, and it
often is, even in a lot of folklore.
To the friends of the Fey, the realm of Faerie
is one of the most wondrous places
you could visit, with wine that is more
delicious than wine anywhere else
in the cosmos, with the deepest sleep
under a tree that you've had anywhere,
even better than the sleep you had
in the softest bed, and so it's really,
the Druid is functioning almost like a Fey being,
in being able to use that magic in that
wonderful, nurturing way, rather than again
being kind of perilous and suspect as so often
the Feywild is to people who visit it.
- The Druid Circle of Dreams is available
in Xanathar's Guide to Everything.
You can purchase that book on dndbeyond.com
by clicking on the link in this video description.
I'm Todd Kenreck, thanks for watching.
-------------------------------------------
The Best Places in Toyama | japan-guide.com - Duration: 10:18.
Toyama prefecture lies along the Sea of Japan
a unique location with a large coastline as well as mountain ranges that make up a majority of its interior
here you can find traditional farmhouses tucked away in hidden mountain villages
a stunning route that cuts through the heart of the Japan Alps
one of the country's deepest gorges
and a multitude of other experiences worth going for.
On this trip we're going to attempt to explore Toyama prefecture's most captivating attractions in four days
Here's the plan
we start our journey by taking the shinkansen to Toyama prefecture
On the first day we'll visit Kurobe Gorge and stay in Unazuki Onsen at the entrance of the gorge
On day 2 we head over to the remote village of Ainokura and spend the night there in a traditional farmhouse
The third and fourth days will be spent traversing the Tateyama Kurobe Alpine route
with a night stay at its highest point before going home on day four.
My name is Raina Ong, staff writer for japan-guide.com
and today I'm on assignment uncovering the best places to go in Toyama.
Day 1
To get to Kurobe Gorge, we'll first take the Hokuriku shinkansen from Tokyo to Kurobe-Unazukionsen Station.
From there we're going to transfer to local trains to Unazuki Onsen town the entry point into the gorge
Then we'll take the Kurobe Railway as far as possible into the gorge to Keyakidaira Station
explore a bit
and then head back to spend the night in Unazuki Onsen Town.
We're at Unazuki Station and we're going to be taking that cute orange train over there into the Kurobe Gorge and back
The Kurobe Gorge is the deepest v-shaped gorge in Japan
and some say the view at the gorge is pretty gorgeous
So this rock wall over here is known as the "hito kui iwa"
which is, when translated, becomes "man eating cave."
I'm staying in a ryokan tonight in this beautiful Japanese room
and tonight's dinner will be a multi-course meal
and I'm looking forward to it
Day 2
After a relaxing night at Unazuki Onsen
today we'll take the train to Shin-Takaoka here a direct bus will take us to the remote village of Ainokura
where we will explore the quaint town and stay overnight in one of the farmhouses
It's day two and we're at an Ainokura one of the villages where you can see
traditional Japanese gassho zukuri farm houses like the ones you see around me
Gassho zukuri is a style of construction where the steep thatched roofs are said to resemble hands in prayer
The best way to depreciate Ainokura is to stay at one of the farm houses
and that's what I'll be doing tonight
Day three
Today we bid farewell to our farmhouse and travel back to Toyama station to begin our traverse of the Tateyama Kurobe Alpine route
It is a spectacular journey carved through the northern Japan Alps connecting Toyama and Nagano Prefecture
will be taking different modes of transport to complete the route starting with the train at Toyama station followed by a cable car
then bus
tunnel trolley bus
ropeway
another cable car
and lastly a tunnel trolley bus once more
However today, we'll only be going as far as the midpoint at Murodo and spend the night there
I took this train from
Toyama all the way to Tateyama station where I am now
and today we're going to the highest point on the Tateyama Kurobe Alpine route
We boarded the the bus in the cloud, but here Murodo we've broken through them
and behind me over there, that's mount Tateyama where it's the highest mountain in the region
Day four
Our last day is relatively easy
We complete the rest of the Alpine route
see Kurobe Dam along the way
and then head home
We're at Kurobe Dam, our last stop for this trip
and fun fact the dam is also Japan's tallest at 186 meters
Thus ends our whirlwind tour of Toyama
I hope this video has been enjoyable and perhaps even inspires you to experience Toyama for yourself
For more information about Toyama or to watch another video click the links on the screen now or head over to japan-guide.com
your comprehensive up-to-date travel guide firsthand from Japan.
Thanks for watching and be sure to subscribe for more videos about Japan
Happy travels
-------------------------------------------
An unhelpful guide to suga - Duration: 6:35.
-------------------------------------------
Diablo 3 2.6.1 Demon Hunter Build: Shadow Impale GR 112+ & Speed T13 (Guide, Season 12 PTR) - Duration: 12:48.
hey folks this is rhykker with a diablo 3 patch 2.6.1 season 12
demon hunter guide the shadows mantle impale build is one of the builds that
is being super buffed in the coming patch it has already completed a greater
rift 112 on the test servers leaderboards this bill was already one
of the most powerful builds for the demon hunter in season 11 but in season
12 it's gonna be even stronger so this video will be a refresher lesson on how
to run the build we'll go over the gear and the skills but real quick I just
want to mention that if you want to get your name on the Rikers Raiders 2017
t-shirt you only have a couple days left until the end of September link in the
description below on how to do that alright dive it into a gear overview
this requires the full six piece of the shadow set you could make do with five
pieces and a ring of royal grandeur but to fully optimize you're gonna have to
go full six-piece this is the melee demon hunter now you're still throwing a
knife but you're holding a melee weapon it's the closest we're gonna get to a
full melee demon hunter and the two-piece bonus while you're wielding a
melee weapon your damage is increased a ton 4-piece makes shadow power gain the
effect of every rune and lasts forever we'll cover that more once we get the
skills and the six piece makes impale deal a crazy amount of damage to the
first enemy it hits and that's the core of this build using impale as your
damage dealer so because of that we need Karla's point another mandatory item for
this build this makes impale deal a lot more damage
and return hatred if you hit an enemy that's already been impaled this is
essential not only to our damage but also our resource management now the
great thing about this is that it's fairly easy to farm up a Karla's point
you're gonna go to your blacksmith and you're going to craft yellow daggers
you're gonna take these yellow daggers and you're gonna bring them to your
kanai's cube over here and you're gonna use the recipe to turn a yellow into a
legendary there are only two possibilities Karla's point and lord
green stones fan this makes it really easy to get yourself a good car lays
that's the good news the bad news is the holy point shot it is a la mort
difficult to get yourself a good holy point shot this makes impale throw two
additional knives and is an important item in dealing our damage as well as
recovering our hatred and then everything beyond that is just
supplementary to help this build run better and to optimize it and chain of
Shadows is gonna be really good for our mobility
this build is an elite hunter in order to do that in order to hunt elite so
we're gonna need a lot of mobility and this will make it so that every time we
throw our dagger we can then vault three to four times three to be safe
four if you time it perfectly for free free vaults three to four free vaults
before you need to shoot out another impale we're gonna use strongarm bracers
for extra damage the rune that we select on vault will facilitate this we're
gonna work in a traveler's pledge and a compass rose one of the best
supplementary sets in the game ups your toughness ups your damage this leaves us
with an open slot so we're gonna go with a convention of elements here for added
damage and to really maximize their damage we're gonna want to make sure
that we are full throttle attacking on our elemental rotation of choice which
we'll get to what element that'll be in a little bit you actually have a choice
here in our cube will want the dawn that's a one-handed crossbow that
reduces the cooldown of vengeance by a lot this will enable us to have 100%
uptime on vengeance a very powerful effect for our armor we'll go with an a
clicker ass here for more damage reduction and for our jewelry the
elusive ring for yet more damage reduction because of this ring we're
gonna want to make sure we are always vaulting around or if not popping shadow
power at least once every eight seconds to maintain that damage reduction we'll
take a closer look at what stats we want on the gear after we go through the
skills impale is our main damage dealer and what you're seeing me run right now
is the cold rune over penetration what over penetration does is pierce all
enemies in a line for cold damage this is the room that has the potential to
hit the most enemies the other option the other main choice here is ricochet
ricochet makes the impale Dagger strike two additional enemies now
between these two which you take doesn't make a huge difference
ideally it's gonna be what items you find that I'll determine whether you
take the cold rune or the lightening room if you have a lightning quiver then
you're gonna go with ricochet if you have a cold quiver
you'll go with overpenetration that said when pushing solo as far as possible
over penetration will make it easier to sustain your hatred the reason for this
is that enemies won't be dying quickly so you're going to be hurting enemies
together in two big packs and lining them up so that you can throw the knife
through a lot of enemies and they'll already be pierced so you're gonna
recover a lot of hatred with ricochet instead when enemies are dining more
quickly when you're progressing through a rift more quickly ricochet is a more
reliable source of triggering your hatred regeneration so next we'll want
to take shadow power the rune you select doesn't matter it's purely cosmetic
because you're gaining the effect of every rune shadow power gives you life
per hit that gives you a good amount of sustain it crowd controls enemies around
you it gives you damage reduction and increased movement speed next we'll want
to take vault rattling roll it's the rattling roll
rune on vault that will be triggering our strongarm bracers in this build
you're generally gonna be right up against an enemy's face so you'll fall
through an enemy to stun them knock them up and then deal that damage while
they're under that strong arm effect next we'll want vengeance dark heart and
our aim is to have a hundred percent uptime on this effect vengeance makes us
deal a bunch more damage and dark heart makes us take 50% less damage you'll
want to go with companion bore companion if you want to go full glass cannon you
can go with the wolf companion instead for an occasional damage buff but the
boar companion will passively give you more toughness then lastly fan of knives
bladed Armour is an effect you'll want to have up at all times this just gives
us extra toughness all right onto our passives awareness
gives us that extra life numbing traps will make enemies deal less damage call
the weak will make us deal more damage to crowd controlled enemies
ambush gives us a good chunk of added damage for our legendary gems will wanna
pay into the trap that's just more damage all the time we're gonna be
dealing damage enemies who are close to us so they'll be under that crowd
control effect will want a go cock of swiftness this will give us the added
cooldown reduction that we need in order to maintain 100% uptime on our vengeance
it also gives us some nice attack speed which translates into more damage and
dodge chance which is toughness and then lastly when you're pushing the highest
grid rifts you'll want a pain enhancer this is if you're able to build up a lot
of enemies around you that are under this bleed effect because then you gain
more attack speed aka more damage but if you feel you're not benefiting from that
and if you're doing content that's easier then a bane of the powerful would
serve you better here you'll want to diamond in your helm before cooldown
reduction and then in your torso and pants it depends on whether you want
more damage or more toughness if you want damage go with emeralds otherwise
go with diamonds for more toughness now as for the stats that you want on the
gear I'm gonna list things off my gear is not perfected so pay attention to
what I'm saying and you can check out the link to the d3 planner that shows
all the full stats that you want in the description below for your shoulders you
want dexterity cooldown reduction area damage and all resist the shoulders roll
with all resist ideally you'd rather have vitality but if you want the other
stats then you'll have to settle for all resist for the helm you want dex crit
chance impale damage for your amulet crit chance crit damage and then the
element of choice for your chest all defensive stats decks vitality and then
either life or elite damage reduction kind of whatever you like best and it's
always good to have a secondary resistance wherever you can get it for
your gloves you'll go with dex crit chance crit damage attack speed and if
your paragon levels are so high that you can afford to roll off dexterity and
instead put an augment to callousness despair on it for the decks then you can
swap out decks for area damage for your bracers you want elemental damage decks
vitality crit chance for your belt all defensive stats ideally decks vitality
life % always for your pants' decks vitality all
resist for your boots decks vitality all resist impale damage for your compass
rose you want decks crit chance crit damage and then just flat damage for
your convention of elements or elusive ring you're gonna have one in the cube
one equipped to yourself just equip whichever one has rolled better you'll
want crit chance crit damage cooldown for your car lace point you want decks
attack speed percent damage and for your holy point shot you want elemental
damage decks attack speed crit chance impale damage now a note on cooldown
reduction break points there's two important break points here and the
first is to maintain 100% uptime on vengeance and that's a total of 37
percent cooldown reduction now you can achieve that by maxing out
your cooldown reduction and paragon points
that's one getting a max diamond in your helm number two and then number three
getting max cooldown on one piece of gear so I only have seven here you need
an eight for instance on the shoulders and then lastly what'll get you over
that final hump is your go cock of swiftness at max stacks that only
happens in combat however if you want to also achieve 100% uptime on your blade
armor your bladed armor from fan of knives then we're talking about closer
to 40% cooldown reduction and you'll need one additional piece of gear with
cooldown reduction on it now how exactly and where exactly you distribute your
cooldown reduction is up to you it doesn't have to exactly be on the pieces
of gear like this for the shoulders yes you'll want the cooldown reduction there
because there's no other offensive stat that you can put there you don't want to
give up or rather you want to minimize giving up damage for cooldown reduction
but for instance if you have to you could put cooldown reduction on your
gloves in order to have another offensive stat on your ring so for your
paragon points you're gonna want to get your total move speed up at 25% then
dump everything into dexterity if you want you could put into maximum hatred
if you're having some hatred issues for offense who want to max out cooldown
reduction then crit chance crit damage attack speed for defense you want all
resist then life then armor and for utility you want area damage life on hit
resource cost reduction now I'll just quickly go over some options for a speed
farming variant of this first off you need to be lightning cold will not do
for speed farming next you're gonna swap out your pain enhancer for a boon of the
hoarder gem that'll make lots of gold drop on the
ground and your cube you're gonna swap out your a clicker asks for a gold rap
belt which makes you gain more toughness when you pick up gold you'll want either
in your jewelry slot or equipped as one of your rings an avarice bad this every
time we pick up gold will increase our gold pickup radius basically we're going
to vacuum up anything on screen instead of add-on we can go with the Ingham
sword which reduces our cooldown by 15 seconds every time you kill an elite
pack in speed farming you're even more just hunting for elite packs you can
swap out your strongarm braces for Nemesis bracers so every time you touch
a pylon or a shrine you're gonna spawn an elite pack and then for your passives
because you won't need as much damage you can swap out call the weak for
tactical advantage for more speed and since enemy damage won't be too much of
a concern you can swap out numbing traps for blood vengeance to help with hatred
management when enemies are just dying faster than you can hit the multiple
times it becomes difficult to maintain your hatred and that wraps up this guide
as we get closer to the release on season 12 I'll post up a new tier list
video on the best builds going into the season so do be sure to check back we
don't yet know when season 12 will start thanks for watching special thanks to my
twitch and patreon supporters for making these videos possible if you enjoyed
this video please share it check out these other videos and subscribe to join
rikers raiders for more diablo guides
-------------------------------------------
Splasher - Yellow men can't jump Trophy Guide (Big Bounce Theory) - Duration: 3:11.
Splasher
-------------------------------------------
What to do when complex systems fail: A guide to chaos management (Aish Dahal) - Duration: 45:04.
>> Thank you, Jeremy.
And the opening slide is, I guess, something that most of us, as developers, and even as
probably product managers, must have done.
So show of hands for anyone who has kind of run either this or a Drop Table on a production
or non-production system.
Show of hands.
Non-production is totally fine.
Okay.
I don't see that many.
Interesting.
You all are great software engineers.
Never made this mistake.
Unfortunately some of us, like myself, tend to make this mistake.
Which means that in a production system, we tend to believe that this is probably a non-prod
box.
Make this one-off mistake where we just go in and run a command like this.
What happens?
The consequence can be something in between an hour's long outage that involves maybe
millions of dollars of customer impact to something that's like...
Restart the box or fail over to another AWS...
Whatever you call it.
But today's talk is going to talk about what happens right after you run this command.
What happens when your complex system fails.
So my name is Aish, and like Jeremy mentioned, I work for a company called PagerDuty.
And without talking a lot about myself today, I'm just going to dive straight into the topic
and talk about, first: What are complex systems?
So the title of the talk easily talks about what to do when complex systems fail.
So go with the definition of what's a complex system, let's just go take a line from the
English Wikipedia.
A complex system is a system that's composed of many components, which may interact with
each other.
Sounds very, very specific, right?
Definitely not.
This kind of covers almost any software.
Software has this modular principle, in which you have classes or objects or function, or
any different components that talk to each other.
This sort of inherently means that almost any piece of code that you ship, apart from
that one hello, world example -- or maybe even that too -- is a complex system.
You can ask me what's not a complex system.
Well, if you build a bottle opener, that's not a complex system.
So unless the software system that you build...
Nay, the system that you build is a bottle opener...
That's more than likely a complex system.
And again, you might ask me: What's the deal with all the complex systems?
But let's first address the elephant in the room.
The elephant in the room is: Why are you talking about failure?
And...
The second thing is...
Why are all of these emojis around?
Well, I am a Millennial.
So hence all the emojis in the talk.
So hold my avocado for a second while we take this detour into the world of academia.
So this paper was written, as you can see on the screen -- it's called how complex systems
fail, by Richard Cook.
Who was a medical doctor.
MD.
And it was written in the year 1998, about patient care and health care systems.
The paper talks about a bunch of scenarios on how things fail.
But again, the object of this talk was not to describe how things fail, but rather to
talk about what to do when things fail.
But there's a very great quote from the man himself, Richard Cook, about failures in general,
and failures of complex systems.
To quote him: Failure-free operations require experience to deal with failures.
Now, let's take a pause here and think for a moment.
Failure-free operations require experience with failure.
This is very, very counterintuitive.
This means that in order to deal with failure, you need to have prior experience.
Now, wait.
Isn't this more like a chicken and egg problem?
Don't you mean you have to have experience to go and fix things, which means you have
to go and break things first?
So this is what this talk is about.
Here's the structure of today's talk.
First, we'll talk about a horror story.
The horror story is not like one of those high budget Hollywood movies.
It's just an operational nightmare that any one of us could be in.
And this is like from my experience, what happened to me in the past.
When we did not have a good operational and an incident management framework in place.
The second part of this talk deals with lessons learned from the story.
So in the story that I'll be telling you, we'll be seeing a bunch of failure modes in
dealing with failures.
Systematic failure of multiple things, including communication, including tactical things,
as well as talking to the customers.
So the second part is dealing with how to actually deal with these failures and dealing
with failures in turn.
That's kind of very meta.
And the last part is a review about the things that we will be talking about.
So first, a story about failure.
So chapter one.
This is fine.
To kind of give you a background, this happened to me while I was an intern.
I was still in college.
I was at a small startup somewhere.
And it was the middle of the night.
I get a phone call.
And it was the CTO of the company, calling me to say...
Hey, it looks like this particular piece of software that you shipped is not working,
and it looks like this big customer is not getting their reports.
I didn't know what was the next thing to do.
I was told that there was some bridge number that I needed to dial in.
I was told that there was some HipChat room I was supposed to go in back then and talk
to other engineers.
Being an engineer who was still in college, that was the expectation of me.
I did not for one moment know what was the meaning of being on call.
I was roped into this incident call to deal with the systematic failure of complex systems
without actually being equipped with the knowledge of how to deal with these things.
Almost every engineer I knew was on call.
This was a 20-person startup.
So 16, 17 people were on the call.
Most of them were half asleep.
It was a Friday night.
Someone had even dialed in from a bar.
I could hear the background noise of people talking and laughing in the middle of all
of this chaos.
Most importantly, we were all trying to do the same exact thing.
We were trying to go to the last commit on GitHub, go to the commit, and see what happened.
Unfortunately, since all of us are doing the same thing, and had we been, like, smart enough,
we probably wouldn't be doing this.
But since we're all doing the same thing, we didn't get to the solution.
Like you guessed correctly.
The problem was with a database machine somewhere, and since we had a bunch of machines for different
services, we just didn't know what was going on.
We had no clue where to start.
So 16 engineers in the middle of a Friday night, someone dialing from a bar, an intern,
and the CTO of the company trying to just go and fix reports for this big customer...
Not even knowing what went wrong and how did this particular thing fail.
So the thing was that our logging service was failing.
The log aggregator was failing.
So the box ran out of disc space.
The database machine.
As a result, like, our reports were not being delivered.
That was the actual problem.
Just spoiler alert for people.
Now, that was now chapter 1.
This is chapter 2.
A dark and stormy night.
These lines -- was a dark and stormy night.
The rain fell in torrents, except at occasional intervals, when it was checked by a violent
gust of wind.
These lines are the famous antipattern in English literature.
If you look at them closely, whenever you write an English language-based essay or anything
that's not a poem, this is how you should not be starting.
Now, why am I drawing a comparison between English literature and an operations call?
That's probably...
That's definitely because any engineer that you asked on that call, on the call that I
was in, about...
Hey, do you know what we should do next?
Gave answers almost as out of point as these lines.
The answers used to be...
Well, like, there's a wiki somewhere.
There could be something out there.
But no one definitely had an answer about what was the problem, and what they were doing.
So it was almost as ambiguous as these lines here.
Most importantly, there was no clear leader amongst us.
It was like a herd of sheep where everyone was trying to follow each other.
There was no one to coordinate.
In the middle of this, we kind of make a segue to chapter 3.
This is the exec-swoop.
Like the title actually says it all...
The CEO of the company -- this was a tiny startup at the time -- jumped into the call
and started asking questions.
And these questions included things that, as an intern, I was definitely not aware of.
But there were also engineers on the call who were aware of it, but they didn't really
have the answers to these questions.
You ask me: What questions were we were talking about?
This was at 2:00 a.m. on a Friday night.
Can you send me a spreadsheet with a list of affected customers?
In the middle of the night, when you're dealing with fires, the last thing that you want,
literally the last thing that you want is an exec standing on your head and asking you
to send a list of the affected customers.
You barely know what the problem was.
You barely know what you're dealing with.
You're able to talk to the right sort of engineers who know the system inside out.
And in the middle of all of this, you're trying to get that one spreadsheet with some customers
who have been affected.
Apart from that one customer who initially put that request that things are not working.
So...
Like, we were kind of confused about what to do.
So you know what?
Adding more to the chaos, adding more to the complexity, we decided to do both.
Which meant that we first decided to get the list of affected customers, and then go and
deal with the actual problem.
Which meant the actual time, the total amount of time that we spent in dealing with this
incident was much longer.
We spent almost two hours trying to get this list.
It was finally at 4 a.m. that we got to know what the problem was.
That the particular log aggregator was not running and the servers were running out of
memory, which led us to finally go and fix the problem.
The story does not end here.
The morning after, the morning after didn't bring us any hope.
The morning brought us some more pain, some more agony.
I was getting the blame for the incident, despite being an intern.
And I had to go and do a lot of things despite just cleaning out the thing.
I had to add a cron, add another metric for monitoring, just because I was blamed.
The question you might ask that we all can see is...
What's wrong with the picture?
It's a cat image that's upside down.
I'm definitely not asking about the cat image.
I'm asking: What's wrong with the story?
If you follow Agile, DevOps, or any of these hipster terms, there's definitely a lot that's
wrong in the picture.
Despite being part of a new age startup, not one of those mammoth old companies that we
try to stereotype companies in, this was still the case.
So other things went wrong, but we can categorize things that went wrong into two distinct buckets.
The first one: We did not know the difference between a minor incident -- a minor incident
being a recurring thing.
Something that can be automated.
Something that does not require you to wake up in the middle of the night at 2:00 a.m.
and go and log into a computer.
Among all the things to do.
And the second category of thing that sort of went haywire was not having a framework
or a dedicated method to deal with a major incident.
Had it been a major incident.
So we'll kind of talk about: What's a major incident in a while?
But for now, bear with me that there's two different things.
There's a minor incident and there's a major incident.
Before we try to address these problems that we saw, let's move on to the second part of
this talk.
Lessons learned.
Lessons learned from this particular horror story.
Lessons learned from these mistakes that we made in the call.
And how can a good incident management framework address the concerns and the problems that
we saw on the call?
So before we start to talk about the framework itself, let's kind of see how can we deal
with the first part of the problem?
And the first part of the problem was: Not being able to identify whether it's a minor
incident or whether it's a major incident.
So the first thing that companies, organizations, and teams need to do is to define, prepare,
and measure what's a major incident.
So it's critical to define business failures in terms of business metrics.
So, for example, if you are an online retailer, it might be the number of checkouts per second.
If you're an online video or audio streaming platform, it could be the number of streams
per second.
At my current employer, PagerDuty, it's the number of outgoing notifications per second.
So defining your most critical business metric and tying it back to the engineering system
sort of helps you build that understanding throughout the company, about whether are
we in a major incident?
Is there a massive customer impact or not?
The second thing is: Get everyone in the company to agree on the metric.
This means right in from the CTO, the CEO, all of the execs, to someone like an intern
must agree that this is the metric that we're looking for, and once we cross this threshold,
we are in a major incident.
So like in the story, we did not really have a metric to talk about.
We are affecting one customer.
That was fine, but it did not require the entire company to be awake.
So defining these metrics require you to look at the amount of time and every you are going
to spend in dealing with these types of problems.
The second part with preparation.
So the best organizations prepare with failure beforehand.
Like Richard Cook said, to quote him yet once again in this talk, failure-free operations
require experience to deal with failures.
Companies have their own versions of simulating failures.
A few companies call it Game Days or Chaos Monkey or one of those buzzwords.
It could be automated, it could be manual.
It could be as simple as restarting all servers randomly on a Friday.
That's what we do at PagerDuty.
We call it Failure Friday.
This is to prepare your people to deal with failure beforehand.
And the most important part of this triad is measuring things.
So measuring the impact during these failure simulation exercises would help you go and
add and redefine those metrics.
If required, tweak them, and get other stakeholders in the business to agree.
Once you complete this triad, you need to make sure that failure should be unique.
If not, we should be able to automate the response.
For example, in my case, the failure was just something that was supposed to run on the
machine and clear up the space from old log files did not really run properly.
So if that was something as simple as going and freeing up space from that machine, in
terms of failure, that should not be wasting human time.
Human time is precious.
If you can automate it, just go and automate the thing.
So like I said, remember...
We should be only triggering major incident response if you are in a major incident.
So getting those 20 people on call and trying to solve the problem will only make sense
if it is something that could not be automated.
If it was a button click away to just go and clear up the log space, you should probably
have done that.
Well, apart from hindsight, let's just move on to the meat of this talk.
So the meat of this talk is talking about this framework that's inspired by the National
Incident Management System of the United States.
This is a framework developed by the Department of Homeland Security, and it's used for dealing
with national calamities and other incidents as classified by the national government.
When I use these bigger words, people give me a look and say...
Aren't we talk about software and IT applications?
How would something that was designed to deal with natural calamities...
How can something like that be applied to software and IT and operations failure?
Well, the core of this is to deal with failure.
When you try to categorize failure, the failure modes are kind of similar.
So the lessons learned from the NIMS framework can for sure be applied into a software failure
mode as well.
So the first thing, like most software developers know, is the singular responsibility principle.
And the single responsibility principle that I'm referring to is not about code reuse or
keeping your things dry, which is...
Don't repeat yourself.
Or just cleaning your code.
This is about: Whenever you get paged, whenever you get a phone call from your CEO, your CTO,
or someone, make sure that there's only one person responsible for one task.
Do not have a redundancy there.
The redundancy might be good when you're actually writing code and deploying it into distributed
systems.
But when you're talking about people, having the same task being done by two people in
the middle of the night is not the way to go.
Particularly not in a major incident, which might run for hours and hours.
So since I just mentioned the single responsibility principle, there can be different roles.
Based on the names, there are different roles that people can take when they join this incident
call.
So the first -- and when I say an incident call, an incident call I refer to as a major
incident.
If you have online utility, your customers are not able to check out.
What do you do?
It's an all hands on deck scenario.
So the first thing that comes to mind is the subject matter expert.
So the subject matter expert is sometimes what we call a resolver, or a responder to
the particular event.
They are the domain experts.
It could be someone from the team who built the service or knows about it well enough
to go on call with it, and fix the things that are necessary.
In my story, we had 15 engineers working on the redundant parts of the same system.
And we are all the SMEs or the experts.
You don't need 15 experts.
One person.
One person per logical component so as to avoid confusion in an incident call is sufficient.
Now, this is the mantra of the subject matter expert.
Never hesitate to escalate.
And this kind of comes on the back of things like...
Well, since I was an intern, and since...
Let's say that if I was on call, and I was called by my CTO, what's the first thing that
I do?
The first thing I should be doing, as with the framework, is just saying it out aloud
that I don't really have enough context on this.
So please escalate it to the next level.
Please put in someone else who kind of knows better about the system.
So that I am not on call for this thing.
So never hesitate to escalate.
As an SME.
The next and the most important role in an incident call is of what we call an incident
commander.
And before we kind of get into the details about what is an incident commander and what
are the roles and responsibilities, let's just take a slight detour.
The image in the background is of Gene Krantz.
He is known for being the flight director, I guess, for the Apollo 13 rescue mission.
So if you have seen the movie Apollo 13, you might have seen someone coming in with a vest
and trying to get everybody on board to work together as a team, and try to get a group
of astronauts stuck in space back to earth.
So draw a parallel there.
This is what an incident commander does.
If your database has been dropped or your business is not able to somehow function in
the middle of the night or the middle of the day -- it does not really matter -- the incident
commander is the sole point of contact.
The incident commander is the person who drives the entire incident call.
So this means that the incident commander is responsible for single handedly talking
to everyone, from the CEO right to the handlers on the call, and making sure that everybody
is working together as a team and trying to work towards the solution of the problem.
So what's the first thing that an incident commander does?
The first thing that an incident commander does is they notify that the company is in
a major incident.
And this we are talking about an internal notification.
So this actually means that jumping onto the incident call and saying it out aloud.
I have been notified that there is a major incident going on and I'm the incident commander
for this call.
Is there anyone else on this call?
Which means you're trying to gather subject matter experts.
That helps us make segue into the next part of our incident commander roles and responsibilities.
You verify that all subject matter experts are present on the incident call.
This is essentially just asking out aloud whether people from these different teams
for whatever thing that's going down are present.
And then you get onto the long running task of dividing and conquering.
So what do we mean by divide and conquer?
Isn't the incident commander the single point of contact for this?
Yes, but the incident commander is not the subject matter expert.
The incident commander does not need to know the ins and outs of the system.
The incident commander does not need to be a principal or senior architect.
The incident commander is just there to coordinate and help people work together so they can
work as a team.
So the incident commander's responsibility is to delegate all actions and not act as
a resolver.
The other key thing about an incident commander and an incident call is to communicate effectively.
This also means to maintain order.
To try to control the chaos that comes out of a tired set of people trying to work towards
systems-level solutions.
So the incident commander needs to take in human empathy during the call.
Which sometimes may translate to just asking people to drop off the call and go and spend
an hour outside.
They don't need to be in the call, if there can be someone else on it.
So the incident commander is also responsible for swapping in and out people from an incident
call, based on their judgment.
And effective communication also means sometimes people might be harsh towards each other.
Like all human beings, people sometimes get tired on an incident call.
They'll may shout at each other, not use the best words.
So the incident commander's responsibility is to make sure that the communication there
is also great.
Next, the incident commander is responsible to avoid the by-stander effect in the call.
What do I mean by this?
Rather than saying something like...
Please say yes if you think it's a good idea to do so...
So if I am an incident commander, rather than asking for permission to do something, you
ask for something like...
Is there any strong objection to do that?
You kind of get one of the suggestions from a stakeholder, preferably an SME, a subject
matter expert, on the call, and you ask the question: If there's a strong objection to
do that.
This helps avoid the by-stander effect.
We have seen it in, like, the place where I work, and other places as well.
That this kind of helps cut a lot of situations where a by-stander effect is seen.
Particularly in incidents calls, when you instead ask permission to do things.
The next thing is reducing scope.
I guess we all have been in one or more times where something is going on in a production
system, your company's core business has been affected, and just for the sake of information,
you leap into that incident call and just know what's going on.
So one of the key things about being incident commander is to reduce scope.
Which means not allowing people, apart from those who are required, to be actually present
on the call.
So this is just done to not burn out people.
Having more than the necessary number of people on a call just means there's a lot of crowd,
a lot of noise, a lot of more confusion.
There could be a clash of ideas or opinions.
People are opinionated.
Particularly engineers are.
Which means the incident commander's responsibility is to reduce scope.
Which means kicking our people from incident calls if you feel, as an incident commander,
that they should not be part of the call or their help is not required.
You could politely ask them to leave the call and say we will get you added back to the
call if you actually need the help.
The next part is maintaining order.
This is something that we kind of touched upon before.
But one of the things that...
Which we sort of talked about, in the communications part as well, was about: Reminding people
to only talk once at a time.
So not having, like, multiple people talk at the same time.
The next role is of the deputy.
And like...
In the old Western movies, the deputy is not responsible for a lot of things in an incident
call.
What the deputy does is the deputy acts as an assistant to the incident commander.
This means that the deputy is responsible for getting all subject matter experts up
to speed about what's happening.
So imagine that you are, again, in the middle of a chaotic incident.
Something has gone wrong with the production system.
And the deputy sort of calls you in, in to your phone number.
You are a subject matter expert, joining the bridge, joining the call.
So the deputy is the person responsible for giving information to you.
So you might be adding to the incident call five hours after it started.
Which means you probably have no context about what was happening.
So rather than having the incident commander stop all of his other tasks and come back,
and talk to you, the deputy kind of acts as the backup incident commander, calls you on
your phone, pages you, whatever, reaches out to you, gets you on the call, and fills you
in about what was happening.
In the middle of all of this, the incident commander can carry on with their responsibilities,
so that their standard workflow is not affected.
The other responsibility of the deputy IC or the incident commander, is to liaise with
the stakeholders.
Remember, I kind of mentioned that the incident commander is responsible for making sure that
everybody in the company knows we're in a major incident?
Now, in the middle of all of this, you might...
The incident commander might get an email or a message on their Slack or a phone call
from someone who is like a CEO.
So rather than having the incident commander interrupted by these external interruptions,
the deputy incident commander is responsible for liaising with the stakeholders and the
incident commander.
So the deputy incident commander acts as this particular liaison between this particular
call and the stakeholders.
So this could be someone who is an exec in the company or someone else who is not part
of the actual incidence response call, but wants to know about what's going on.
Talking about not being part of the actual incident call, but wanting to know what's
going on, there's a dedicated role in this incident management framework, and it's called
a scribe.
What does a scribe do?
A scribe documents the timeline of an incident call as it progresses.
So this is just someone typing on your chat medium.
Like, it could be...
It doesn't have to be a chat medium.
It could be a Google Docs or it could be your Slack, your HipChat, or a Skype.
Any sort of messaging or shared documentation that's accessible from people within the company.
This is internal.
The document at the time when the call starts...
This is the time that the incident call was started.
And then they start taking notes about what people said and how things are happening.
This kind of acts as a bridge between people on the call and people off the call.
So the scribe necessarily tries to get feedback from people who are outside the call.
So if I happen to know something that the SME in this particular incident does not know,
I can very well talk to the scribe on the Slack message or the Skype message and tell
them that it looks like whatever you guys are doing on the call, whatever you people
are doing on the call, it may not be really accurate.
There's an alternative.
And the scribe could, again, get that feedback relayed into the incident call, without having
you or someone else outside the call jump back into the call.
The next role is that of customer liaison.
In my particular story that we talked about, the CEO sort of jumped in and started asking
questions about customer-facing things, about which engineers did not really know about.
So the role of the customer liaison is kind of to avoid that entire thing, where an exec
comes in and starts asking questions about customer-facing things.
The role of the customer liaison is to act as the bridge between the customers and the
incident call.
This means making sure the number of...
People get tweeted all the time with "You know, your site is down".
Keeping track of those things, keeping track of support queries that you may get in your
downtime.
The customer liaison acts as this bridge between any customer-facing request and the internal
incident call, as such.
They also directly talk to the IC, the incident commander.
And rather than just talking to the subject matter experts and confusing them with these
things, they let the incident commander make a call for things like...
Whether to get that spreadsheet, or whether...
Should we go and focus on the problem first?
So the incident commander actually makes that call.
The request comes in from the customer liaison.
The customer liaison is also the person responsibility for notifying people outside of the company
about this incident.
So this involves sending out tweets about "Looks like we're having some problem with...
Some service".
Something like an API.
And the entire site is down.
Putting these updates on your status pages.
So this role is specifically targeted for the customer liaison.
Because they are in constant touch with the outside world, so they can have a better picture
about what to put on the outside world.
So what to put on the outside...
How do you translate this internal impact to the outside world?
The customer liaison works with the incident commander to frame that particular message
that is to be posted on the outside world.
And yeah, the customer liaison also keeps the incident commander apprised of any relevant
information.
So there may be a large number of customers complaining about this particular thing.
So that the incident commander can use their judgment wisely about the situation while
the call is actually progressing.
The next thing.
The incident commander role sounds a bit heavy.
So something that the operations response guideline proposes is to allow a great transfer
of command from incident commander, from one incident commander to the other, if necessary.
What does this mean?
This simply means calling in someone who is able to become an incident commander and giving
them information about how far the call has progressed and signing off as incident commander.
This is just to avoid burnout.
The next part deals with the thing that we saw in chapter 4 of my story.
The morning after one.
So blameless postmortem is something that the industry has talked about for years.
John Osborne from Etsy has written great stuff about it.
I won't spend a lot of time talking about blameless postmortems.
But the TL;DR of this is that postmortems need to be blameless.
You can blame someone for any incident.
At the end of the day, we are all human beings.
We are all more or less equally likely to make mistakes.
Be it someone who is a C-level exec, a CTO, or someone who just started at the company.
A new hire, an intern.
You're all likely to make mistakes and impact your company.
Blaming people for things that go wrong with complex systems is kind of pointless.
Remember, something that great companies do.
You really can't fire your way into reliability.
So firing people for making -- creating a major incident, or having a negative business
impact, is not the way to go.
So there's, like, a few gotchas about the role of incident commander.
One of the most common things that we get is: Who can be an incident commander?
Does it have to be someone really senior in the company?
The answer is no.
Anyone can be an incident commander.
Anyone who is able to kind of communicate well, knows the systems well enough, and is
confident enough that they can deal with the chaos.
Can become an incident commander.
And to kind of make sure that you are comfortable with being an incident commander, the three-step
mantra: Define, prepare, and measure -- comes into play here.
So if you want to be an incident commander, for example, or if I was an intern and had
I wanted to become an incident commander, the first thing was: Be prepared for it beforehand.
Run these chaos exercises, these game days, or run these chaos experiments before the
failure.
So you have enough experience to deal with an actual failure.
It does not really have to be someone really senior in the company.
And these are the lines from a major incident call.
Names have been redacted.
For example, you join in to have an incident call as an the SME.
And you have been trained.
Suddenly you kind of realize that you're probably four or five only SMEs on the call.
The first thing you do is you ask: Is there an incident commander on the call?
If you don't hear back anything, if there's just crickets around, you just say it out
aloud.
This is Aish, and I'm the incident commander for this call.
Well, you just say your name out.
I'm saying mine.
You can say "I'm Aish, and I'm the incident commander,", but that's probably not gonna
work out that way.
The next is wartime versus peacetime expectations.
So a lot of times we don't get paged.
Things don't fail.
Most developers don't go and run suko rm rf in production or drop tables in production
without taking a backup.
That's one of the things.
So what's an expectation for an SME, for you or me, or for someone who is an engineer who
works in a software development team and goes on call for things that they build?
Once in a while, things fail, but that's fine.
What's the expectation then?
What's the peacetime expectation?
The peacetime expectation is that you are just prepared to deal with failure.
That's it.
You can go have a life.
There's nothing about being on call that you should be worried about.
And the wartime expectation is to follow the guidelines and to stick with it.
Not just to go and join in an incident call about how things work.
You can kind of do that offline.
Now moving on to last section, the review.
These are some key takeaways from the first incident that we talked about.
And then the framework and how we can kind of talk about some major takeaways.
The first thing is: Shit happens.
Yeah.
Prepare for it.
Run simulations.
Prepare for it.
Train your people.
Make sure that your systems can deal with failures.
And things can go wrong all the time.
Just make sure that your company -- everyone, including the business, as well as the technology
part of it -- knows it well enough.
Develop on-call empathy.
So we might have seen this Twitter hashtag, #hugops.
Things can go wrong for anyone at any time.
So it's important to have empathy for someone who just got paged, who's working on a problem.
Don't try to intimidate him.
Just make sure you're a good team player and you follow the rules and have some empathy
on it.
If you're an incident commander and you're tired, feel free to step down.
There are no gold medals for on-call heroics.
No one has received something like the Victoria Cross for being an on-call hero.
Just make sure you don't become an on-call hero.
Don't try to burn yourself out to prove that you know how the system works and you can
deal with failures firsthand.
So before I leave all of you today, here is the one slide that if I were to condense this
particular talk into a minute-long talk or maybe a lightning talk, something that's a
key takeaway for most companies and teams that build software is that people are the
most valuable asset.
Don't burn out your people having them do something that can be automated.
Be it cleaning up logs, restarting a server, just putting up a cron.
These are things that can be done automatically.
You don't need to trigger an incident call and have ten people on there who have done
something as trivial.
People are your most valuable assets.
And thank you.
That's it.
(applause)
>> Nice work!
We have lots of questions.
That caused lots of discussion and debate, as anyone looking on Slack will know.
Firstly...
Everybody on Slack agrees that Mirabai should be the scribe on all calls in all situations.
That was an easy one to start with.
There's a question about where and when self-healing systems can be used.
Could they be used at nighttime, if sort of an incident that was in that area happened?
Can code roll back?
How much value is there in self-healing systems?
>> So like most answers, the answer is "it depends".
There's no one thing fit all solution.
So the generic thing has to be tweaked upon your needs.
But more or less, it should work out, and...
Well, it depends.
When you ask how it depends...
I need more specifics to kind of answer that question.
>> Follow-up question on Slack for later, then.
There was a question about how actually logistically you managed this process, in terms of things
like chatops.
Do you think that chatops work effectively when there's a need for a call around incidents?
>> Definitely, yes.
So if you...
I can give you an example from my current employer, PagerDuty.
So we have a chatops command to start a major incident call.
It's an in-house thing.
It's not Open Source yet.
But if you feel like a minor incident is getting escalated into a major incident, we have a
chatops command that automates the process of calling in the incident commander, the
deputy commander, the customer liaison, the scribe.
All these people get paged about these things.
So chatops definitely helps.
>> One of the questions is around the scale of company that this is appropriate for.
I'll just pull up a couple of examples.
So in situations where you're working in a really small team, where there might be actually
less people than even the amount of roles that are there, how does that work?
And don't you quickly end up risking getting in a situation where you've got 50% of your
whole company on the call and actually who's out there doing the work?
What sized team do you need to make this appropriate, do you think?
>> That's a great question and it's something that I get quite often.
So the most critical role -- and if you're a small company -- is to have the incident
commander.
Apart from the subject matter experts, who are the meat of the problem.
The people working towards solving the problem.
You'll need an incident commander and you'll need a scribe.
These are the bare minimum.
And the customer liaison.
You'll need three people on the call, apart from the people who are actually working on
getting to the solutions part.
So if you're a 10% team, I'll still recommend that you have three people there.
And this means that apart from the customer support person, the customer liaison, who
is not from the engineering org, who is from the customer support org, you have two engineers
on call.
Which is something that a decent 10% company should be able to do, I guess.
>> In that situation, are you just removing some of the roles, or are you seeing the three
people on the call merging some of those roles?
>> You end up merging all of these roles.
Which translates to the fact that the scribe would have to add as the deputy incident commander.
And some other roles would be mushed.
The customer liaison would also help the incident commander.
So there is definitely some overlap of responsibilities that will happen.
But that's definitely better than not having a structure at all.
>> Okay.
Final question, then.
What tools do you use in practice to implement these roles and procedures?
Are there parts of it that are automatable, that you can recommend?
Are there any specifics that you recommend we all go and look at?
>> Since you asked the question, a shameless plug.
We use PagerDuty.
But apart from PagerDuty, we use some great monitoring tools, which help us get the data.
And we use a bunch of Open Source tools.
Like the internal chat plugin that we wrote.
Which was just built on a bunch of Open Source chatbot commands.
So chatops, good managing, and PagerDuty for incident management.
>> Great.
Thank you very much!
-------------------------------------------
Using the Business Subject Guide - Duration: 10:19.
One of the most helpful resources for students on a library homepage are the subject guides
For students studying business the business subject guide is very helpful
Let me show you how to get to the business subject guide. If you're on the library homepage,
click on subject guides in the middle area, the Tab.
If you're from the Brooklyn Campus click on McEntegart subject guides,
and if you're from the Long Island Campus click on Callahan's subject guides
Now choose business on the left hand side.
See, we even have subheadings such as Accounting and Finance, Business Administration,
Economics, Global Business, and Marketing.
For the purpose of this tutorial we will choose Business Administration.
The rest of the guides function in the same manner as the one I'm about to show you,
so we only really need to look at one and you can explore the other ones on your own.
My recommendation to all users of the guides, which are created by librarians using LibGuide software,
is that you follow the tabs across the guide to conduct your research effectively
You can find books right from the guide,
you can find articles using databases can find websites recommended by librarians,
statistical information, associations and information on how to cite your sources.
So now let's go to the home page again, of the guide, and there are several RSS feeds from which you can find
a lot of really up to date information
CNN Business News, New York Times Business,
and if you scroll down to the right you'll have the Wall Street Business Management News.
This information is all right here for you and can be very helpful when you're in a time crunch yet
need to be up-to-date information in the business world.
Now for the next tab labeled 'books'.
You can actually stay on this guide, and search for books in the Library Catalog or ebooks or DVDs.
There is no need to go back to the library homepage if you would like to stay in the guide.
This is a one-stop shop
If you remember in an earlier tutorial in this orientation we search for books on business ethics.
You could type in the words 'business ethics' right in this box
and click on go and get a list of materials on that subject.
You can also use the advanced features of the catalog from here as well.
Also under this tab if you scroll down the librarians here offer a bibliography of books and reference and name
which is circulating collections on the topic and subtopics of 'business'
but only a sampling of what we have we couldn't possibly list everything it wouldn't be practical.
So here you can see the 'Concise Encyclopedia of Economics', the 'Encyclopedia of Management',
International Encyclopedia of Organization Studies, etc.
these are reference books that do not leave the library and as you scroll down you can see circulating books
that can leave the library as checked out on your ID
Class with Drucker, Managing, the AMA handbook of Leadership, etc.
Now, if you scroll up a little bit and look on the left hand side
you can see the different call numbers associated with the field of business.
For example HD4801 to HD8943 covers labor work and the working class
HF5410 to HF5417 covers marketing and HG covers finance.
These are the call numbers that indicate where an item is located within the library
we talked about that in the finding books and ebooks section.
One of the key tabs on this guide is articles/databases
This section first tells you what a database is.
Library's databases are online catalogs or indexes that contain information
about journal, magazine, and newspaper articles.
You can search these databases to find information about specific topics.
Databases provide citation information for each article and often include an abstract or summary of the article.
You know that from earlier tutorials and/or from your studies at the undergraduate level,
but I just wanted to point that out because not everybody is always sure what a database is
and you pay for the databases via your tuition.
If you find an article that you cannot seem to get full text right there in front of you,
you can use our interlibrary loan system, which we'll talk about later to retrieve the article if we can get it for you.
Now, I do want to point out before I go on the Harvard Business Review Advisory here.
Please read it when you get a chance, it is very important.
As you scroll down right in the middle of the page is a list of all the different databases that we recommend
for you to use for your business research.
You'll notice that ABI/Inform Complete is at the top.
This is merely because it's an alphabetical list however
I did want to show you how easy it is to get to via the business guide
so that you can reach it later when you are following the tutorial for finding an article in abi/inform complete
the Proquest database. Proquest is just a company that owns ABI/Inform Complete.
Now what I don't want you to forget about are
another subset of databases as you scroll back up and you go to article databases
Business Administration was your first option
then, Industries and Corporations. I click there, another set of databases appears on the left hand side
Country Watch, Credo Reference, Hoover's, Hoover's there will be a tutorial on this database.
It's very important it includes detailed company fact sheets, coverage of Industries,
information about executives, financial statements Etc, so please remember how to get to Hoovers.
Here is to find the article section. If you have previously viewed the
"I already have a citation does the library carry this journal" tutorial,
you have learned that you can use the journal locator tab from the library page to find out if
the library subscribes to a particular journal magazine or newspaper for which you already have a citation
you type the name of the publication in the search box and if the library carries it
a database or list of databases will appear. If you're already in this business subject guide however
You can click right in this box and do the same thing. You don't have to jump out of the guide.
So again, this is like a one-stop shop
Under the Websites Tab moving along in the tabs to the right,
You can see what websites the librarians have put here to recommend for doing research in your field
such as the Drucker Institute,
Global Edge which is on the left hand side.
Note that the librarians also do provide for you here within this tab at the beginning
criteria for evaluating websites on your own websites that you've gone out on the open web and
found and are trying to determine whether or not to use in a research paper.
You want to analyze the websites for their authority, accuracy, currency, relevancy, and purpose.
Going back up
The Statistics tab offer statistical sources in the form of websites and books.
Under Associations, we provide a list of links to relevant associations
such as the American management association and [a] society for human resource Management.
Finally on every guide we have a citing sources tab.
This tab contains information on plagiarism and how to avoid it
It also contains information on how to cite sources properly in APA style,
as well as links to guides on how to paraphrase
sorry, I didn't click on it and
Summarize properly as you can see we carry the different style manuals.
Business Majors often use APA.
Paraphrasing right here. You can go to these websites
There's information on Noodletools, which is a citation machine to which Joseph's College subscribes,
That will enable you to plug in your information it will create citations.
Here is the login page.
And information on how to create a Noodletools account and how to create a citation in Noodletools.
Plus we have Purdue OWL,
Diana Hackers research and documentation online,
plethora of information here for you
So overall, the business administration subject guide is an invaluable tool for your research.
We have subject guide for almost every major and growing.
I do recommend that you use this guide, as well as the other subject guides,
for practically all your research
while you are working your way through your studies here at Saint Joseph's College.
Thank you for listening to this tutorial.
-------------------------------------------
GUIDE TO HEALTHY TRAVEL w/ Mason Taylor of Superfeast - Duration: 32:24.
-------------------------------------------
Exploring New Plymouth, Taranaki - New Zealand's Biggest Gap Year – Backpacker Guide New Zealand - Duration: 7:48.
-------------------------------------------
Selling Online Guide - Ways to Sell Many Things - Duration: 1:25.
-------------------------------------------
The Dealmaker's Guide to Tech Risk - Duration: 1:06.
- Hi, I'm Joe Cincotta,
the managing director of Thinking.Studio.
Over the last 15 years we've had a chance
to work with startups and mid-size enterprises
that have technology at their core
and one of the challenges that I've seen
with investors and deal makers
is coming into those businesses to assess their value
and to really understand how to invest in them.
They get the finance,
they get the business model
but the challenge is the black box of technology
that sits right in the middle of that business.
So, we put together a guide
four simple questions that as a deal maker
or an investor you can come in and ask
and you can quickly assess
if there's a risk in that business,
so you can understand your risk
and essentially get back some leverage in that deal
because now you understand
where the challenges are that that business is facing
from a technology standpoint
not just a finance or business model standpoint.
Download it today,
The Deal Maker's Guide to Managing Tech Risk.
-------------------------------------------
Las Vegas new homes for sale buying guide - Duration: 5:44.
Las Vegas new homes for sale buying guide Success in buying Las Vegas new homes for
sale doesn't happen by accident Greater Las Vegas new homes for sale buyers
should be educated about the process of buying a new house in order to take advantage of
good deals and more importantly avoid deadly mistakes that they may not even be aware of
which we have discussed in a separate video did the Las Vegas new home builder build the
right home?
We have also explained the large median sales price gap between new homes and similar pre-owned
homes.
In this video we will discuss searching the MLS for Greater Las Vegas new homes for sale
listings, visiting the builder's office and making an offer on new houses.
Driving around and visiting builder's projects, looking at new model homes and after picking
one, having the builder's sales staff write the purchase contract is the wrong way to
go about getting a good deal.
The builder's sales staff job is to protect and serve the builder, not the buyer.
However, this is exactly what more than 60% of new home buyers do.
They chose to forgo bargaining with the builder and even if they did, they lack the data to
do so.
Let's talk about using the Las Vegas MLS to search for new homes listings.
To search for new houses please click the MLS advanced search.
Under the search button you will find Built Description, click it and you will find new
homes searches.
There are two other sub-categories, to be built means that the buyer picks a lot and
orders a new home from scratch.
Under construction means that another buyer has ordered the home, but had to drop out.
These homes are sold at a significant discount.
Buyers may have the choice of flooring or some upgrades.
Discount gained through buying these inventory homes turns into instant equity for buyers
who buy the builder's inventory homes.
Use control-click to check more than one status.
In the new homes MLS you can find the listings, however, it doesn't show the latest builder
incentives or the all-important sold comps for these homes.
We have access to the above information which in turn we will provide to our clients.
If you are serious about buying a new home, contact us.
Unfortunately, not all builders list their listings in the MLS.
If you can't you're your desired house in the MLS please let us know and we will
e-mail you listings from other sources.
Let's talk about the visit to the new home builder's project.
The reason new home builders have a sales office on premises is that they want to meet
the buyers on their own turf and their sales staff are trained to look out for the builder's
interest and not the buyer's.
If you visit the builder's office and register with them without prior registration by your
Realtor or without a Realtor accompanying you, then the builder will not allow your
Realtor to represent you in the transaction.
New home builders are forbidden by law to give a discount due to lack of Realtor participation,
so doing so does not cost you any less and in fact, could end up costing you more.
Another issue is that new home builder's model homes are built on the best lots, have
tens of thousands of dollars in upgrades and do not resemble an average home.
We always ask the sales staff to take our clients to see the less upgraded homes being
currently built so they can see a realistic comparable house before they want to make
an offer on a new home.
Let's discuss making offers on Las Vegas new homes for sale
Keep in mind that there is no difference between making an offer on a resale home and new house.
In both cases, the purchase price should be based on comparable sales that have sold in
recent months while adjusting prices based on the market conditions.
In both cases, the buyer should be able to bargain with the seller if the market allows
it, even though some think the builder's asking price is written in stone.
We have access to sold data for new houses in Las Vegas, Henderson and North Las Vegas
which we provide to our clients.
This along with the thorough understanding of the real estate market conditions and trends
will enable us to bargain intelligently and achieve a good deal for the buyer.
Lastly, many Las Vegas new homes for sale communities are being built in areas that
could be significantly influenced by the nearby commercial real estate construction.
For example, the recent completion of Downtown Summerlin project has helped sales and home
appreciation in the area.
We know what is going on in the commercial real estate market and will advise our clients
accordingly.
Like we said a great deal doesn't happen by accident, Masoud is widely known as an
authority on the Las Vegas real estate market and loves to bargain so we will make sure
that you don't overpay the builder.
If you are doing research, we have provided you with all the needed tools to conduct it,
but if you want to buy in the immediate future, contact us and we will set you on the right
course to success.
You will be in good hands, guaranteed.
If you want to buy or invest in Las Vegas new homes or condos please call us at 800-762-4917.
Please like and share and subscribe to our real estate channel for upcoming videos
On behalf of The Saber Team, this is Karen Saberzadeh of Realty One Group and www.lasvegas4us.com
wishing you a great day.
-------------------------------------------
Leading Large Scale Change: A Practical Guide - Duration: 2:02.
-------------------------------------------
"A Guide for the Homesick" | Teaser Trailer - Duration: 0:52.
[tinkling of rainstick]
[fade to sound of heavy rain]
[rainfall continues]
[bass hit]
[dreamy melody on electric guitar begins]
[bass continues in rhythm]
[a simple shaker instrument begins to play]
[drums, guitar, rain, and shaker]
[...]
[shaker fades out]
[guitar fades out]
[rain continues]
[tinkling of rainstick]
Không có nhận xét nào:
Đăng nhận xét