GoReact aids in teaching and learning by facilitating top principles recommended by the Coalition for Psychology in Schools and Education.
The Coalition for Psychology in Schools and Education CPSE, working with the support of the American Psychological Association, identified and validated a set of principles from psychological science as the “most essential for facilitating successful classroom teaching and learning.”
While all of the principles are worthy of review and resonate with great teaching that we practice or have experienced, I wanted to highlight two that jump out as being especially easy when using GoReact to capture performance and provide appropriate feedback. Although these principles were directed at preK-12 specifically, many of our customers have shared their successes implementing these concepts when targeting young adult and adult students both inside and outside of formal education.
Fresh off the Boat is a new show on ABC. It looked funny so I decided to watch it with my wife. But the Comcast app on my iPhone was having problems streaming the commercials. We watched the first two commercial breaks one and half times each. And for some reason the airplay streaming wasn’t working so I couldn’t watch it on my television. Off to a bad start, but undaunted, I downloaded the ABC app. After spending a minute proving that I had ABC through my Comcast account, the show streamed to my TV just fine. But each commercial break included a promo spot for the very show I was watching. Do they even know what show I’m watching? If they did, shouldn’t they stop advertising the show and just show it to me? When the baby woke up and we had to take a break for minute, we got to watch the commercial break again with another promo, before I could resume.
These apps are very careful to make sure that you see each commercial break at least once. And I wouldn’t mind so much if each commercial break didn’t show the same commercials. The exact same commercials. It’s like the apps are really commercial apps and not show apps. I just want to watch the show. Is there an app for that?
Maybe next week I’ll just watch the show live. Where is my cable box? Wait, isn’t ABC broadcast over the airwaves? In HD? I wonder if it will have better commercials…
We spend too much of our lives in ambiguity. So many outcomes, so many possibilities! Even an enumeration of the combinatorics would be a staggering waste of time and so we consent to let things play out. But we don’t completely let go – of course not! We make decisions in the moment, we strive to utilize consistent tactics, even strategies as well as we can. And when we have successes they are the result of our efforts, and yes, some luck. And when we have failures they are bad luck, and yes, maybe poor planning. We can press forward in uncertainty but Sir Arthur Conan Doyle’s Sherlock tells us, “It is a capital mistake to theorize before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts.”
Certainly, the exploration of risk is rewarding and I don’t mean to take the fun out of it! But making data-driven decisions removes the worst outcomes. And less negative risk means less unpredictability and this is a good thing for business. It is predictability that allows us to make wise investments, to outmaneuver the competition, and it is the predictable inflow of money that keeps the lights on. This is why getting to “know” is so vital. Reorganize your processes to identify and weed out the worst variables first. Answer every question amounting to “why this won’t work.” You need not wait until all questions have been answered, but there is a critical mass that should be addressed before safely riding the long tail of uncertainty. But knowing where you stand on the most key factors of success puts you on the threshold of good decision making. If you decide to stop, you can do so early and with good reason. If you need to pivot, you have the wisdom of understanding just how it should be done. And if you should indeed continue on, do it with confidence that comes from really knowing where you stand. The earlier you know, the less risk you take on and the less time you spend
The decision to move forward in light of the data is much more sound than the decision to move forward despite the risks. Get to “know” then make the call.
I’ve enjoyed listening to the Startup Podcast over the past couple of weeks. It’s encouraging to listen in on seemingly normal guys as they put together a brand new company. In episode #13 they talk about rapid design prototyping with Google Venture’s design team. The team walks them through a design sprint to discover what their mobile app should be.
Fake it ’till you make it… or don’t.
In Gimlet’s case they should not build a mobile app, and I can’t tell you how many months of development time I’ve saved by NOT BUILDING an idea that we’ve had. In a relatively short amount of time you can design out a website or app and see if it’s going to really meet your needs or if it’s just a cute idea. The world is full of cute ideas – I don’t want those. I want a great idea that can work.
Save yourself some time, developer. Don’t build it until you’ve seen it.
This recipe has been passed from my Oma to my father to me and is a family favorite that will always remind me of July barbecues and Schmuhl family parties and funerals. It’s not a traditional German potato salad, but where it lacks in pedigree it makes up in flavor and texture. Serves about 15. Enjoy!
~3/4 jar of mayonnaise
1 medium onion
10 boiled eggs
Squirt of mustard
Salt and pepper to taste
Boil small pieces of peeled potatoes until soft (smaller and longer means creamier)
Drain the potatoes and dump them in a large bowl
Dice the onion and add to the potatoes
Stir in about 1/2 of the jar of mayonnaise
Mix in the seasonings to taste
Peel and dice 7 of the eggs and softly stir them in
Let sit overnight.
Add the rest of the mayo and season again to taste
Slice the remaining 3 eggs and lay them out across the top of the bowl
Sprinkle the top with paprika for color
The key to this dish is that that it always tastes better the next day. Prepare it at least a day before so that you can add more mayo and seasonings as the potatoes suck in that flavor over time. The texture and creaminess is determined both by how long you cook the potatoes and how much mayonnaise you end up adding. I generally push it close to the boundary of mashed potatoes with good results.
I’m learning Python and needed a decent IDE to get my work done – I’m so spoiled! I installed PyCharm and have found it sufficient. Today, after several days of using it, I finally noticed that the tip of the day is blank! This is fine, I unchecked the box, but what I wanted to point out was the missed opportunity: the tip of the day is your chance to educate the user on helpful functionality, to increase product retention through brand loyalty. And what is done with this opportunity?
Tips not found. Make sure you installed PyCharm Community Edition correctly.
Nope I won’t. If you can’t take ownership of this problem (first take: don’t show the tip by default if it isn’t working) at least in the tone of the presentation, then I know enough able you to move forward. Disable the feature and wait for the functionality to be proven in the future. This is a very matter-of-fact approach that could be softened by different messaging:
Woah. I can’t find any tips! Click _here_ if you have some time to help diagnose what happened with your install. In the meantime we’ve disabled this feature, you can get to it again from the Help menu.
See, I already want to buy whatever software would give me this kind of lip service!
Today I was reviewing the Moab documentation for an upcoming training and I ran across several feature gems that I thought were worth calling out. I’ll call them some of the “not-so-secret ingredients” that makes Moab great.
Scheduling with Partitions
Moab uses partitions to logical divide available resources in your environment. This allows you to separate geographically or by hardware configuration. For example, because a given job can only use resources within a single partition, you may want to create a partition to group nodes on the same local switch so that you can guarantee the fastest interprocess communication speed. Another cool benefit of partitions is the ability to set partition-specific policies, limits, priorities and scheduling algorithms, though this is rarely necessary.
In an effort to conserve power, Moab can automatically turn off idle nodes until they are needed again. This can be a significant savings if you’re not maxing your capacity all the time. To save on time, Moab can keep a pool of nodes on standby so that there is no delay when additional resources are needed. Moab comes with reference scripts for IPMI, but can be configured to work with iLO, DRAC and xCAT as well.
Using configured targets, you can use historical resource utilization as a factor for job priority. In essence, this would prevent a user with relatively infrequent workload to get buried in the backlog of jobs from much busier users. This kind of thinking extends to groups, accounts and other groupings as well. There are a number of configuration settings for fairshare that allow you to tweak performance to your needs, such as caps, evaluation timeframe, and consumption metrics.
You can associate multiple reservations through reservation groups. This allows each reservation to share the same variables. These variables can then be used in job triggers to automate tasks like email notification, script execution and internal Moab actions, such as creating another reservation. Of course, you can always override the inheritance by setting a variable locally on an individual reservation in the group.
There is an equation for watts to decibels, given a sensitivity of x decibels, (1w/1m)! Wattage must double for each increase of 3db. See here and here for more info. So that sensitivity (SPL) score is a pretty crucial starting point for a speaker. Not that adding more amplifier watts is not impossible, just moderately costly. But then again, in the case of an amplified PA speaker with 700 watts peak (and 350 RMS) then you’ve a lot of power. By my calculations, taking a 98db SPL woofer up north of 122db, and a 110db SPL tweeter up past 134db – past the threshold of pain! Also, I’ve read that perceptively, humans believe +10db makes one sound twice as loud as another.
BUT distance from the speaker matters! On a ratio of 1/d^2, the sound gets softer the further away you are! If pumping 350 watts through that woofer gets us 122db, standing 52 feet away from it, it will sound just like it we only pumped in 1 watt at 1 meter = 98db. That’s still plenty loud.
It makes sense to me now why stage monitors are always like 100-150 watts. Even with all the noise on stage, you’re pretty close which means they’re pretty loud.
Here’s what that speaker system sounds like as the watts are increased:
Contrast that with another system with a higher SPL:
For reference, here is a reference table for decibels:
I just watched a documentary on Netflix that was based on Jared Diamond’s book, Guns, Germs, and Steel: The Fates of Human Societies and I’ve been moved. Jared lays out the major factors for why some societies are wealthy and others are in poverty, and they all boil down to one thing: geography. It’s not this simple, but the idea is that temperate climates, combined with high-yield crops like wheat which allow for farm animal domestication, allow people to spend time developing new technologies to fulfill and build wealth. Where these things have not existed, we find poverty and the conquered.
Well worth my time to watch, and I’ve added the book to my list to learn more. It’s quite sad, but also encouraging.