Add a blog post: "Uh, I like my job?"

[daniloc]

Changes

Adds a blog post:

• First-person POV of what it is to work in a high-execution org like PostHog
• Effectively an ad to support the ambitious hiring we've got slated for the coming year

(To that end: we can/should schedule this for a time where it makes the best impact)

Checklist

• Words are spelled using American English
• Titles are in sentence case
• Feature names are in sentence case too
• Use relative URLs for internal links

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
posthog	✅ Ready (Inspect)	Visit Preview	Dec 10, 2024 4:41pm

[corywatilo]

I’m still finding the experience to be extremely weird

Is this associated with our value of being weird? (I think without that context, it could come across as a bad thing but in our case, it's actually good, so linking to some writing about this being a good philosophy might be nice?)

The rest of my feedback is about things I already shared in 360, so just as reminders:

It doesn’t readily change, except in calamitous, company-wide ruptures

This is an example of something that is obviously very eloquently phrased in a high-brow way, but also somewhat hard to digest/scan (to us average people) without reading 3x, which I think can have a negative effect on our generally easy-to-read style of writing where we use smaller words that don't take any mental processing to understand what we're trying to say.

That and you managed to use "ass", "bullshit", and "fuck*" a total of 5x in a single blog post, which would represent a 100% increase on any use of this in our repo. (Currently we have 4 uses of "ass", 1 of "bullshit", and zero f-bombs.)

[mariusandra]

Hey, some free feedback from the sidelines.

I think the content itself is great, but I will echo's Cory's feedback and say the f-bombs and long words distracted me from reading it --> they break pacing and take me out of the flow. Somewhere 1/3 of the way in, due to the elongated words, I started skimming and skipping sentences to "get to the end already", which is a shame as the content itself is really worth reading!

And a big +1 to less f-bombs in general. Those have a time and a place, but this isn't it. When used improperly, f-bombs make the author look like a try-hard Mark Manson, which I believe isn't what we're going for here :D.

[andyvan-ph]

I haven't had a chance to do a line edit yet, but I love this article. This is all valid feedback, but very fixable. I'll dive in when I get 10 minutes to thread the line.

[mariusandra]

Agreed, and overall I liked it.

Re: f-bombs, the above reminded me of an article by the aforementioned Mark Manson. It's now paid, but fully available under archive.is here. It's about using "potty mouth" words. The tldr is that sometimes they really do add value, and you shouldn't apologize about that. Other times it feels like loud noise. Getting it right seems to be a subtle art, and when in doubt, I'd lean towards having less of them.