Can someone explain the leading and lagging indicator in this paragraph?
> OKRs, given they typically focus on change are usually leading indicators focused on shorter time windows and KPIs, which represent the health of what the organisation seeks to sustain, are usually lagging indicators focused on longer timeframes.
A leading indicator predicts something about the future, e.g. an OKR of cutting spend predicts that you will indeed cut spend. When you set a new OKR it will take a while before it shows results—it leafs ahead of them.
A lagging indicator is the result of something that took place in the past; 99.99% uptime over the last year indicates you probably had some good practices in place (redundancy etc). If those practices were to change, it would take some time for the kpi to actually change—it lags behind.
OSX has absolutely nothing in common with what’s now called Classic.
I’m sure you’re aware that OSX and, indeed, the current macOS is a UNIX like operating system. Hence, it’s more BSD and Linux like.
To aid legacy Macintosh applications, such as Photoshop and MS Office to run on OSX, an emulator was provided in early OSX releases that would detect old apps and run them in the emulator.
These apps were later modified to use a Classic (mostly) compatible set of libraries known as “Carbon”. This allowed them to run native but still have their older codebases.
The Carbon UIs were often written with a framework called “PowerPlant”, part of the Metrowerks C++ IDE.
Essentially, it gave large old codebases time to rework their code to the NeXTStep frameworks called “AppKit” and “FoundationKit” (rebadged as “Cocoa” by Apple).
Carbon APIs have now mostly been deprecated or removed as nowadays applications are written in Objective-C, the preferred NeXT language, and mixed with C++. Or, if they’re trivial Mac only apps, they might be written in “Swift”.
I do recall at Agfa in Belgium we had an effort to get the existing Mac products out of CodeWarrior’s compiler and into the g++ tool chain. It was non-trivial as the compiler Apple had provided for C++ wasn’t up to date. We had an Apple tech guy on site and he relayed the issue back to Apple and fixes to the compiler we’re made. Still, the code was PowerPlant based so looked old fashioned.
At another gig, Macromedia ported Flash from “CFM” to “mach-o” format (Classic Carbon to g++) and it failed to run. It turned out the g++ linker couldn’t handle code segments more than 32mb. Flash was a single blob of a binary. Apple released a new linker.
I think much if the reason why Apple moved off g++ to clang was due to the difficulty in maintaining g++ on their fork.
Within JPM Chase, the "JP Morgan" or "JP Morgan Private Bank" brand is used for (V)HNWI banking and the "Chase" brand is for retail (although Chase does have a Chase Private Client arm for almost-HNWIs). Due to the nature of catering to VHNWIs, "JP Morgan" of course offers wealth management services.
Morgan Stanley is a completely different company with no (current) ties to JPMC.
The reason JPMC and M-S share the name "Morgan" is because the investment and retail sides of the bank were split during the Great Depression due to Glass-Steagall, almost 100 years ago.
I really like Ben Thompson's position in VR adoption - he compares it to the PC adoption. It was enterprise first, then consumers. Users learned how to use a PC at work, and once the price drops enough, they bring one home.
Thompson was high up on the Microsoft / Meta VR deal.
IMO Zuck has a great grasp of the trajectory of VR/AR in 2015. Meta is singlehandedly trying to will it into a common place. To some extent, they had succeeded way more than a lot of other commenters give them credits for. VR is way far prevalent than it was 2-3 years ago.
Oculus Quest 2 certainly wasn't driving the instant paradigm shift like the introduction of an iPhone in 2007 (15 or so years ago). Though you'd argue that precursors to iPhones were WAP phones, Blackberry's. They laid the ground work (Blackberry was also an enterprise-first adoption). As an interface, handheld devices are much closer to our familiarity with PC so the jump wasn't huge. Plus it has a killer use case -- everyone needs a phone.
I am very impressed by the clear vision in 2015 that we're still seeing it play out in front of our eyes in the VR/AR/Mixed Reality space. What hasn't happened or wasn't mentioned the killer use case -- the utility why people would need to be in VR/AR/XR mode.
The web and smartphone landscape in 50 years might very well look quite similar to what we have today. VR will remain a niche and most people will carry around a smartphone with even more capabilities.
> OKRs, given they typically focus on change are usually leading indicators focused on shorter time windows and KPIs, which represent the health of what the organisation seeks to sustain, are usually lagging indicators focused on longer timeframes.