& cplSiteName &
Comments
Newest First  |  Oldest First  |  Threaded View        ADD A COMMENT
thebulk
50%
50%
thebulk,
User Rank: Light Sabre
7/31/2015 | 1:56:01 PM
Re: Diving for Data
I can see the point about not in pairs, its much easier to point fingers when there are just two of you. 
Sarah Thomas
50%
50%
Sarah Thomas,
User Rank: Blogger
7/31/2015 | 10:42:29 AM
Re: Well, no
But there's a difference between, say, letting events fail and canceling them entirely versus finding new ways to make them successful -- ie. try a new format; if it doesn't work, try another versus try a new format; if it doesn't work, cancel the show and fire everyone. Just a random example I made up.
mendyk
50%
50%
mendyk,
User Rank: Light Sabre
7/31/2015 | 10:38:01 AM
Re: Well, no
The concept of being dismissive about failure ("if you're not failing, you're not trying") is ingrained in the Silicon Valley-insipred mindset, but as we learned in our time at Uncle Buck's Mortuary there is a tipping point for the number of failures in any group, and that tipping point isn't always easy to see until you're on the wrong side of it.
Sarah Thomas
50%
50%
Sarah Thomas,
User Rank: Blogger
7/31/2015 | 9:37:48 AM
Re: Well, no
She's referring to the whole startup mentality of "failing fast" and often and creating a culture where employees aren't afraid to take risks. Obviously a decision that leads to a DDOS attack or hack can't be moved on from quickly (but you can learn from it!), but decisions around new features to an app probably can be. Throw it out there; see what sticks.

There is no moving on from a vegan burrito though.

 
jabailo
50%
50%
jabailo,
User Rank: Light Sabre
7/31/2015 | 9:31:56 AM
Diving for Data
I was speaking to someone who did a lot of diving.  He said he would never dive two at a time.  He'd dive alone, or in a team of three, but not two people.   The reason is when two people dive, one always thinks the other has taken care of something that should have been.  

I don't know if this is true, but it sounds right.  Sometimes you get into a tug of war between two parties, and bringing in more helps stir the pot.

Like right now, I have a client situation where routing from them to my web service is causing issues.   They get timeouts during critical hours.   But when we test it's always good.   They say its our server.  We say it's their gateway.

Then we brought in our ISP's networking engineers.  They made the same accusations.  Then they blamed ingress from their trunk ISP's network.   Now it seems like routing is the problem.  One location tests at very fast speeds. Another times out.  Unfortunately the client is the one who times out.

I threw out "SDN" at the team and asked if they were using it and if so couldn't they adjust my virtual server location to optimize for the client instead of me.

No response so far.  Not sure if the tech has made it into the mainstream.  Or even the acronyms! At least here.

 
mendyk
50%
50%
mendyk,
User Rank: Light Sabre
7/31/2015 | 9:20:12 AM
Well, no
Not all wrong decisions can be "quickly moved on from." Unless we're talking about inconsequential decisions, like whether to have the vegan burrito or the carnivore platter for lunch.


Featured Video
Upcoming Live Events
September 17-19, 2019, Dallas, Texas
October 1-2, 2019, New Orleans, Louisiana
October 10, 2019, New York, New York
October 22, 2019, Los Angeles, CA
November 5, 2019, London, England
November 7, 2019, London, UK
November 14, 2019, Maritim Hotel, Berlin
December 3-5, 2019, Vienna, Austria
December 3, 2019, New York, New York
March 16-18, 2020, Embassy Suites, Denver, Colorado
May 18-20, 2020, Irving Convention Center, Dallas, TX
All Upcoming Live Events