“Isn’t 15 the minimum?”
“Well, yeah, if you just want to do the bare minimum. But look at Todd over there - he has 37 rambles”
“Well if you wanted people to have 37 rambles why wouldn’t you make that the minimum”
If you have not seen Office Space ... It has a couple raunchy things and it's general political correctness calibration is circa ~2000 USA so go in with about that level of culture expectations.
Having said that, it's a GREAT movie which is practically a comedic documentary of US office politics and tropes. Though some of the standards have shifted a tiny bit, the general culture is still relevant today in many if not most offices. The movie showcases culture and human nature more than any particular era.
Most of my middle management experiences has been between Office Space and Better off Ted.
One with "Don't care" as an answer and the other says "Care more" as its.
Those are the two extremes of the genre.
Ted Crisp: We do everything: industrial products, biomedical, cryogenics, defense technology.
Veronica Palmer: We want to weaponize a pumpkin.
Ted Crisp: Then so do I. Because?
Veronica Palmer: There's a country with whom we do business that grows a great deal of pumpkins and would welcome additional uses for them. As well as cheaper ways to kill their enemies.
Ted Crisp: Well, finally, the pumpkin gets to do something besides Halloween.
I believe this showcases, succinctly, corporate “ethics” in our society.
Absolutely anything to make a buck and strengthen trade.
there is white people rapping and Michael Bolton is ashamed of his name. Tread carefully folks!
I couldn't buy rated M games or R rated movies, but I could certainly download them... which led me to my first graphics card and RAM upgrade, installing a TV tuner card, and eventually to PC building. Doing all this while in grade school was the best tech education I could get, especially back in the 90s.
Someone please save my soul..
If you're in a startup of <10 people and someone isn't communicating with the rest of the team, it's not going to work.
I can see how this feels dystopian in a giant corporation, but that's because everyone is there for the paycheck.
In a startup, people are making sacrifices to make the thing work. They could get a higher paying, less stressful job.
Picking a startup and not being engaged is disruptive.
The term implies that it's currently starting, i.e. high growth or just out on the market.
While obsidian is a small team, neither of these would apply as it's 5 yrs old at this point and while I don't have any hard/official numbers, I hardly ever hear about it either nowadays, making me doubt the growth metric too.
This seems to happen a lot: Someone writes some highly exaggerated career advice that has good intent at the core but turns into overly weird suggestions by the end. They might be trying to be memorable or to make an impact by exaggerating the advice.
Then some people, often juniors, take it literally and start practicing it. They think they’re doing some secret that will make them the best employee. Their coworkers and managers are more confused than impressed and think it’s just a personality quirk.
As a manager I found it helpful to skim Reddit and other sites for semi-viral advice blogs like this. With enough juniors in a company there’s a chance one of them will suddenly start doing the thing written in a shared post like this. Knowing why they’re doing it is a good way to help defuse the behavior (assuming they don’t really benefit but rather do it because they perceive it will look good)
Most people doing "agile" do literally the opposite of what is on the manifesto.
So… what’s the point of a “sprint”? We don’t even do monthly releases. It’s hilarious.
I suspect we do “agile” in name only so they can pretend to the board that there is a system at all.
When I'm considering a refactor, I write up my thoughts in English (which often helps clarify things rather than focusing in code at first). And then I point the rest of my team, to the post and say something like, "I'm going to tackle this next Wednesday, let me know if you see anything wrong with the approach". People who care and have options can chime in, if they're too busy they can ignore it. But everyone is given the chance to comment.
But where I find the real value is when I'm working on a new algorithm or analysis approach. Our internal blog software natively supports LaTeX math blocks (like GFM), so I can write out my algorithm ideas using formal math notation. I've pre-found a bug or bad idea many times just by translating my English into LaTeX. I actually find the expression of those ideas in a blog post the key tool to solidify ideas before I code them.
I'm under no illusions that most of the team even reads what I write, but the work of formalizing it for semi-public consumption really clarifies my thoughts and keeps me from spinning too much while I'm actually writing the code.
These aren't super formal academic quality publications, more like semi-formal ramblings, but I think the difference between hitting "publish" vs just typing in a channel slows me down enough to really think through things - and those who do end up reading them are reading slightly more thought out idea than a stream-of-consciousness rambling which means they'll get more out of it too.
Getting more eyeballs on that idea also helps. Both in the different knowledge and expectations / assumptions they have and in proofing how clearly the idea's communicated. Really helps reveal areas where there's ambiguity you hadn't even realized because it's not even a confusion spot you'd consider with your knowledge.
Now, I've consulted at places that use Microsoft Teams file shares for their "documentation", and I feel like I'm back in 2005. Confluence would be a dream.
The last 10 years I've seen jira and confluence groaned about, what has replaced what they do?
My personal preference is to have some kind of "Off-Topic" or "Open Discussion" channel that is communal. I'll then make a point of consistently posting half-developed ideas to that channel. Especially the ideas that I know are going to morph as the team discusses them. I find that helps do two things:
- Helps create a culture of collaboration rather than one of "whatever the lead dev says goes".
- Provides Cover For/Reduces Pressure On anyone that is less comfortable putting their thoughts out there for discussion.
As the parent comment said, the fundamental idea in the post isn't bad, but the mechanism may need tweaking for a given team.
Just make a "random" channel, where most people keep notifications off, and use it for everything random, from lunch invitations to "i'm selling olive oil", etc.
I agree that if it becomes a top-down expectation or a performance metric it would be terrible. The practice at Obsidian was emergent and bottom-up. Maybe that's because of the small team size and flat structure. Also why the article states "They should be muted by default, with no expectation that anyone else will read them."
this is no different from best practices for programming though. People take a rule that generally works well, but a manager who doesn't understand it tries to enforce it blindly ("more unit tests!!") and it stops working
computer engineering & social engineering share a lot of the same failure modes (which is good news, if you are very good at debugging computers, but find people & politics confusing, you can unlock the latter once you see in what ways your insight in one domain can transfer to the other)
The problem that this post is trying to address, is that these kinds of informal rambling channels -- which have enormous value -- almost never happen organically.
some folks -- i guess like you? -- read this and think, "oh, great. a mandate that fixes a problem i don't have, and now might be something i'm forced to participate in against my will"
and other folks -- definitely me, and i believe the OP as well -- read this and think, "oh, great! an idea that might help me with a problem that i have, and might be something i can point-to as one possible solution to that problem"
> We have no scheduled meetings, so ramblings are our equivalent of water cooler talk. We want as much deep focus time as possible, so ramblings help us stay connected while minimizing interruptions.
Emphasis in the quote is mine, to call attention specifically to the fact that this is what Obsidian is doing instead of standups.
Taken in that vein, it sounds positively miraculous to me.
The fully remote org I work at does async standup threads, they're great, they work just like they're described here except they're vastly easier to track and search, and nobody has any allusions of them being anything more than just remote asynchronous standups.
I feel like it’s a common pattern that organically forms. People want to express themselves, they don’t want to distract group chats, so they make a space to do it.
It all comes down to company culture.
In my experience, "rambling" channels build up organically... as you have a thought, you share it with someone relevant, not just drop it into a channel and see who reads it. Over time, small group chats evolve naturally, and assuming everyone has communications skills, topics that become relevant to the whole team are then shared with the whole team.
I agree that such discussions are healthy, maybe even required, for a functional remote team. But let people organize themselves - don't prescribe specific methods that teams must follow. The last thing we need is a formal framework of how to have organic discussions.