This is like the saying blood is thicker than water, but the the full version:
The blood of the covenant is thicker than the water of the womb.
Sometimes you relationship with your FOC is stronger and better, because it is not built on genetic predisposition but rather it is a bond that you intentionally create.
Writing in the 1990s and 2000s, author Albert Jack[18] and Messianic minister Richard Pustelniak,[19] claim that the original meaning of the expression was that the ties between people who have made a blood covenant (or have shed blood together in battle) were stronger than ties formed by "the water of the womb", thus "The blood of the covenant is thicker than the water of the womb". Neither of the authors cites any sources to support his claim.[18][19]
Somewhat tangential, but from what I can see, the idea that "the blood of the covenant..." is the full version of the saying is a fairly modern invention.
I’ve been on teams that did generic names, and inevitably you end up with names like “work manager service” - whose work? Then it becomes an acronym, like WPS, and everyone ignores it anyways :)
Your site doesn’t explain your product very well. I know about GTD but I literally haven’t heard of any of the other products listed in the page. The screenshots are tiny and hard to parse on mobile. The descriptions of each feature include many paragraphs of philosophy before getting to what it actually _does_. I suggest “bottom line up front” and a clearer description of the product that better appeals to people who haven’t tried alternatives before.
Time to get a new TPM. Any TPM worth their salt should be doing everything in their power to catalog and mitigate those risks, and communicate them upwards. Lack of communication in both directions and adversarial conversations with engineers is a whole parade of red flags.
That said, Gantt charts absolutely have their place alongside Agile. Our budget and goals are set yearly so inevitably there’s going to be milestones and work back dates to meet, as well as cross-team/org dependencies to track.
The site doesn't do a good job of explaining what this is, precisely. It has several typos ("mailbox's", "corprate"). The "costco (sic) of helpdesk software" - what does that even mean? What's unique about this solution compared to other solutions on the market - why would I use this?
The "get started" button just takes to documentation about how to install it, but why would I click that without knowing what it is? The documentation is also broken, as mentioned.
To be fair, about 95% of open source projects fail to adequately explain what problem they're solving that other open source projects don't, what niche they're filling, etc. Or even attempt to objectively present why someone might use their software over another open source project and vise-versa.
Half the time it's not much more than "I didn't like the language that other thing was written in."
But it's a safer, more productive, higher performing, more diverse, and more just work environment. And not having assigned desks? Don't you know that this way you accomplish more with less. Constraints breed resourcefulness, self-sufficiency, and invention. There are no extra points for growing headcount, budget size, or fixed expense. Thinking small is a self-fulfilling prophecy.
Away teaming is definitely a last resort at Amazon, and has all the pitfalls mentioned here - much better to do a budgetary transfer so the host team is properly resourced to make the changes, assuming the feature doesn’t make it into the host teams operational plan.
Seems like Blind should get in on this game, since the premise of the app is that it requires a company email address. Use an LLM to extract insights from the comments and give them to prospective job hunters for a small fee, or even just run ads.
