Can you give an example of "mandatory happiness messaging"? What does a structured program for that look like?
1,813 karma · joined June 15, 2022
Can you give an example of "mandatory happiness messaging"? What does a structured program for that look like?
I personally have never seen it work, but of course I've also only seen a handful of data points.
Adding a caption here for anyone on a screen-reader, before I give commentary on it:
* X-axis: "serve our study" vs "serve our work"
* Y-axis: "practical steps" vs "theoretical knowledge"
* which gives 4 quadrants: how-to guides, tutorials, explanation, and reference
So I'm joining a new place recently, and it's another one of those "documentation-heavy" places where (of course) every new hire conducts the ceremonial ritual of updating the docs wherever they could use improvement. I really like having this ontology in my head now; I can see it being very useful.Also, I wonder if the relative distributions of each one could tell you something about the team's health — or even just the kind of work the team does?
For example, between two teams who are both documentation-heavy, what does it means if one team's docbase is 80% tutorials, whereas the other team's is 80% reference guides? It would be fascinating if anyone's already given thought to relative metrics/heuristics like this.
This seems like their way of reclaiming some agency over what happened to them, as well as trying to put a brave face on things. Also it probably helps them (re)connect with some sense of community — the article mentions they'd usually post these things on their internal forum, but they were ripped away from that community too quickly.
Some might even say it's a classy move — take a step back and reflect on the good parts, hand out some "thank you"s, etc.
I never got into the whole "posting on LinkedIn" thing — and I probably still wouldn't in this situation — but I think it is easy enough to empathize and see why someone might. These are weird and rough economic times, and they're just doing their best to stay afloat. Same as you or me.
Your explanation makes good sense. I guess I just wasn't seeing the forest for the trees. ;)
Cyberpunk isn't (fully) here yet, but until then at least we can tide ourselves over with pastapunk.
More broadly, this kind of thing often makes me think of the idea of "self-reliance" [1]. In other words, the accumulation of career experience parallels the gradual process of learning to trust yourself and your (ever more finely honed) instincts more and more.
[1]: https://archive.vcu.edu/english/engweb/transcendentalism/aut...
The short answer is: Yes, everyone falls. And then you get to learn how to pick yourself up.
Sorry to say, but your story is more mundane than you're making it sound. Everybody falls. You got to see firsthand how a low-support environment and an overly-emotional "leader" can completely fail to capture value from a provably skilled and valuable employee. And then, right after, you got to see the value of trusting your instincts, having good relationships, being on a team where you feel psychologically safe and feel like you truly belong.
Yes, you were a little bit lucky — specifically, your luck was that you got a good job immediately, whereas plenty of people (including folks more senior than you) sometimes get hit by bad luck in the job search process. But you would've found a good job sooner or later, so I wouldn't chalk up too much to luck.
Overall, you got to do some growing up, and it will serve you incredibly well in the long run.
Consider: How differently will you approach the next engineer you mentor? How differently will you deal with stakeholders now? How differently do you feel about the importance of onboarding, of second chances, of objective performance-review processes?
Every misstep has a dozen lessons we can extract. I'm impressed by how quickly you picked yourself back up. I hope you set aside some time to reflect and extract all the valuable lessons, too.
I've flirted with a couple of similar experiences and come away with a very similar feeling — "something really deep inside of me was fixed" — but I find a lot of it fades away after a while. Not all of it, but it definitely feels like 2 steps forward and 1 step back (or, more accurately, like 100 steps forward and 99 steps back).
Lately, it's all just a distant memory. I remember the objective fact that I was that person a few years ago, that I explored the universe while laying on the floor in some dude's living room (how's that for an objective fact?), that I experienced actual happiness for the first time in my life, that I managed to stay genuinely happy for months afterward. But it all faded away.
I've wondered ever since if folks who manage to maintain that sense of wonder afterwards do something different, or approach it differently.
Just one thing — add a couple more zeros. $100k/yr is not unreasonable for an enterprise offering here. They could introduce all kinds of B2B features for companies that want to use Twitter as a support forum (or, given Twitter's popularity, are forced into using it as a support forum).
Off the top of my head — things like rolling up different sub-accounts under one main corporate account, formalizing the ability for multiple support staff to work one account (and charge per seat!), having deeper integration with Zendesk and other ticketing systems, extracting metrics and showing dashboards for how support (and sentiment) is doing, introducing some AI/ML to help companies match Twitter accounts of their customers to internal customer IDs, enabling ML-powered DMing of targeted offers, introducing chatbots that can be trained to field support queries over DM, etc, etc.
Anyway, it's a really good idea. Maybe you should've bought Twitter.
A couple years ago, I changed my uBlock Origin settings to disable JS by default on every site. I only re-enable JS when necessary on a per-site basis.
I find myself having to do it a little more often these days, but it's still made everyday web surfing so much more pleasant — and secure, too.
I know this is a total sidebar: Do you mind sharing a little more about these classes?
Not knowing anything about this, my reaction on reading this was the exact opposite.
As a kid, I was always naively trusting of people's words, and I would expend huge amounts of empathy on trying to understand them based on what they were saying. I feel like a large part of growing up and understanding people is being able to look past that — trust what they do, rather than what they say.
If that was worth incrementing the counter, I wonder about the first three. There's a large, large delta between "can you elaborate" and "advertising."
The PM can bring those constraints to the table; the Engineer brings other constraints from their perspective; and the Designer brings even more.
Then they work together to creatively explore the problem space and converge on a solution together.
I'm sure I'll sound like a jerk because this exact idea is taken as gospel: I still 100% disagree, though.
It is a bit incomprehensible to me. How could a non-technical person decide what is to be built? It would be like a farmer deciding which crops to plant — without knowing the critical details of the soil, the seasons, or the local environment.
IMHO, the role of a PM is three things:
1. Collaborate with Engineering and Design (as well as other relevant folks, like PMM) to collect, filter, and synthesize raw customer data. Together, turn it into a clear statement of the problem to be solved. If the PM needs to be fed some "leadership" kool-aid, then, sure — tell them it's their job to make sure the collaboration happens.
2. Build absolutely bulletproof reasoning around why this problem is the most important one to solve now. Maintain and update that reasoning as the data, the vision, and the solution all evolve. (This is the "value risk," in some modern product lingo.)
3. Continuously rally every internal stakeholder around that reasoning, and clear obstacles in the way of a successful business outcome. (This is the "viability risk.")
I think we actually mostly agree with each other. Your point about having a proper feedback loop — based on real data, rather than politicking and optics — is absolutely gold (and sadly rarely done).
Giving a PM sole ownership (or even "leadership") over the what to build piece, though, is a subtly slippery slope. Down that path lies the inflation of ego, the end of equal collaboration amongst the Product Trio, and the eventual snuffing out of psychological safety as everyone else checks out and stops feeling any real ownership in the product.
(D) Uncover how amazing their future would be, if they could resolve what's stopping them
You want them to be articulating the implications of a solution — i.e., the benefits — so that they really feel the need. Then you don't even have to pitch that hard; you just gently offer your solution to resolve the need they're actively feeling. (As a bonus, you also get to hear the benefits in their words. That lets you use those words to refine your sales pitch for the next prospect.)
Anyway, these 4 steps are really just a Twitter-ified version of SPIN Selling by Neil Rackham [1] — a book which, despite its age and its title, is a very good sales book.
(The reason its so good is because it's one of the only ones that uses actual data. They studied many actually successful salespeople, identified the patterns and formed hypotheses about what works, then taught that to new/struggling salespeople to validate their hypotheses. The SPIN acronym is the mnemonic for what they found.)
[1]: https://www.amazon.com/SPIN-Selling-Neil-Rackham/dp/00705111...
I've personally opted out entirely, instead of just going for the freeze. (In their terminology, a "freeze" lets them keep all your data and continue harvesting new data, whereas an "opt out" instructs them to delete all your data entirely.)
Another important detail: At my company (and presumably many others), it's not just your base salary that's sent over to The Work Number. It's also full details about your equity comp.
I've grudgingly disclosed my base salary as needed (leasing applications, etc), and it's easy enough to do without involving The Work Number because most employers are fine with generating an employment-verification letter. But I don't see any reason why the average landlord would need to know about my equity package, so I found that bit especially unsettling.
Presumably, the idea of having the musician playing is to give the doctor a heads-up in case they slice into a valuable area of the brain. But, by the time the music playing is affected, the slice would have already happened — so then, what's the point?
I agree it's a great way to harvest social media likes (which presumably helps pay the medical bills, so I suppose it's nothing to sneeze at). But it's tough to see how it'd meaningfully help a fine-grained surgery. That abstract on PubMed ^ seems to say much the same:
> ...playing music did not improve or modify surgery.
It's basically the natural outcome of reasonable people responding in reasonable ways to seemingly-reasonable incentive structures.
(I do agree there's probably a more efficient way, but I think it might also be one of those slippery-slope situations where there's a lot of gravity pulling sufficiently-large teams to eventually have their own component library. In other words: Suppose they start off with the best of intentions and repurpose an existing library. Then come the inevitable months of customization, forking, racing to integrate upstream updates, etc. Finally, someone pipes up and says, "Hey, why don't we build our own so we can control our own destiny?" Stakeholders get excited, and then it's off to the races.)
It's good to finally see some innovation in the datepicker space.
Companies grow old and fearful. They stop taking risks and treat failure as a "bad" thing to be avoided. In so doing, they become blind to new frontiers.
That, in turn, finally opens the door for a new wave of hungry startups who are willing to take risks and embrace failure. They come in, disrupt the old guard, and spend 10-20 years becoming giant corporations in their own right. In time, the cycle repeats again.
It's been a very long time (20+ years!) that some of these companies have been going. If they're just starting to become fearful and risk-avoidant, then perhaps the next wave of interesting startups is finally < 10 years away.
(For what it's worth, the current bear market also has me thinking it'll be a good time to start a startup in the next 5-10 years. If I were still young and spry, I'd be champing at the bit to save up a few bucks, stockpile some ramen, and go for it.)
"Oh, you know that 32 GB machine you've got? We're replacing it with this new 16 GB one. If the test suite is too slow on your new machine, I guess you'll just have to make the tests faster."
Strongly agree with this. I hold the line on this for every team I lead (which, sadly, is not every team I consult for, so sometimes I have to keep my mouth shut and spend my political capital elsewhere).
Many junior/mid-level engineers have simply never seen commit messages and source control done well. Additionally, because many folks starting out in the field don't know how to truly use git beyond memorizing a few basic commands [1], they also never harvest any of the benefits of writing great commit messages.
I've got a stash of links that I find myself often sending to engineers who are on the way up, and the tpope article on git commit messages [2] is one I find myself sharing around constantly.
[2]: https://tbaggery.com/2008/04/19/a-note-about-git-commit-mess...
I'm asking because I used to do exactly this and feel much the same way as you — I felt it was nice to preserve the historical context.
At some point, it dawned on me that, amidst all the anecdata I'd acquired, I'd never once benefited from having those commits cluttering up the history.
These days, I usually advocate "squash & merge" for the 80%+ of teams that lack the discipline to write good commit messages for every one of their branch commits. And, for those rare teams where every engineer writes thoughtful commit messages on their branches (a true delight!), I savor being able to do "git rebase && git merge --ff".
Either way, we end up with a lovely linear history of (hopefully) atomic commits.
Centuries? I haven't taken a close look at VR (though I'm flirting with buying a headset soon, just for kicks...) but I'd always assumed it was more like 10-25 years away.
What are the hardware breakthroughs that you think would do it?
The science around teenagers needing more sleep, and doing better in life/school/everything if they start their day later, seems well-established at this point.
Additionally, there's plenty of known-better ways to learn beyond the rote-memorization-and-standardized-test system that's still de rigueur.
Are there no schools out there that put these things together and make an attempt at something better, especially for high-performing kids? What if school started at (say) 10-ish, and it gradually became more and more self-directed as kids headed towards graduation? What if it also mixed in all the latest cutting-edge research about how kids learn math/science/languages/etc? What if it also got creative with the curriculum and mixed in all the topics that people always say should be in schools, like "how to do your taxes" and whatnot?
I remember getting to college and being wildly unprepared for everything. School before then was devastatingly boring and fostered very little independence. Then college came along, and it was both brutally difficult and had almost no guardrails of any kind.
It was quite a transition, and it makes me wonder why there aren't more varieties/experiments around radically different approaches to schooling. At minimum, for high-performing kids, you'd think the modern world would have something.
(I see the full 11 hour deposition is also on YouTube, but I think I'll save that for another day.)
So far, being 10 minutes in, I see a little bit of what you mean, but I haven't gotten to anything "unhinged" yet. He just seems like a bit of a smug nerd who's clearly enjoying going toe-to-toe with one of the country's top lawyers.
Do you remember anything that jumped out for you from the deposition? I'd love to see more of what you're getting at.