Jon Matzner

You should hire wonderful/smart people like Andrea from all around the world (you also happen to save money, but that's not the point)...

Rooting for Hunter on about five different axis

@SVP_of_Retail That's like asking if the Pope shits in the woods

@MatznerJon Is there still birdshit on the Ben Franklin statue?

"I was born for the storm, and a calm does not suit me."

@SVP_of_Retail Negative! Penn

@MatznerJon 1. Great Andrew Jackson quote. 2. You went to Westpoint didn’t you?

@InvestmentJoy Just don't run out of money. That's the rule. Stay in the game until you're smart

Your first deal will be ugly. Mine was a filthy little house nobody wanted. Buy the ugly one anyway. You learn more from one bad property you actually own than a hundred perfect ones you only watched on YouTube.

@Armysmostok18B "calm seas don't make skilled sailors"

@MatznerJon “Any port in a storm”

i guess that's one way to use AI

@Armysmostok18B you could also say very GRS back in alexandria for one night, before heading back energy ill take what i can get

@Armysmostok18B torta

@cdolan92 Man - congrats. Jealous of 5!!

Baptized #5 Onto dinner celebration!

@BPD1776 I never thought I’d say it, but there’s not enough Dolan in this picture

New bank in Pittsburgh!

GO JACKIE

If you're installing the Speed-Based Operating System and encouraging each of your department leaders to maximize speed (rather than minimize cost), there's a trap you need to watch out for. Departments may quietly transmute the speed directive into a focus on efficiency — which inevitably leads to sub-optimization. Here are two examples of how this might occur. A manager who is uncomfortable with the concept of protective capacity creates busywork and pushes their team members to be fully activated, claiming that this improves their average work rate. The manager of a busy estimating department chooses to batch similar jobs, claiming that batching reduces task lead time. It’s clear that both of these interpretations of speed improve local efficiency but reduce the rate of task completion as measured by someone outside the department. Accordingly, we need to guard against all attempts to improve local efficiency (particularly if they are performed in the name of speed). For this reason, you should insist that speed is calculated as it would be experienced by an external observer: - Internal tasks are not considered. - Lead time is the difference between time in and time out (time elapsed, not just touch time). A careful definition of speed will mitigate the tendency toward sub-optimization. And obviously, a necessary condition that tethers locally controlled operating costs provides additional protection against well-intentioned, but counter-productive, behaviors. * * * Another extract from my upcoming Field Guide to Implementing the Speed-Based Operating System.

Reppin the squad @jamesonhaslam

@Lauraet do it, it takes you back

i woke up missing the Gulf. Fired up about 15 of these, and now I'M BACK BABY. iykyk.

@ErikKaiser nah its the smell of fucking everything over there

@tylertringas @r00k @bkup_climbing Tyler don’t fucking tease me

@r00k Just built a Front-alternative inside @bkup_climbing’s full stack SaaS. Even before the UI is better, just having it embedded with all your customer data is a huge perk.

Why haven't you written your own email client yet? Why haven't I? Why would a loving god allow this?

@SMBderek I was a legend in my own mind, I assure you.

@MatznerJon Dude bring it back NOW

this was the header for my old wordpress blog from 2008. i don't know if the fact i still LOVE it...is a good or a bad thing?

We get good reviews