You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
-
96<blushes>Thanks so much, I appreciate it</blushes>Yaakov Ellis– Yaakov Ellis StaffMod2023-08-02 21:15:27 +00:00Commented Aug 2, 2023 at 21:15
-
88Quite right. It should also be mentioned that Yaakov also did the reverse, helping me to understand the concerns of moderators at times. He deserves a good deal of credit here.Philippe– Philippe StaffMod2023-08-02 23:31:04 +00:00Commented Aug 2, 2023 at 23:31
-
9@Philippe Does the "good deal of credit" include a raise? Ok, non-public data. Still, "value" to the company ought to somehow be reflected in "value" received by the employee. No response actually expected here, merely food for thought and, perhaps, a strong recommendation.Chindraba– Chindraba2023-08-03 00:10:05 +00:00Commented Aug 3, 2023 at 0:10
-
35@Chindraba_on_strike you're correct that I won't discuss the remuneration of any team member in a public forum (or actually, at all), but I trust that Yaakov knows how I feel about the work that he does (in as much as I am in a position to evaluate the work of someone outside of my reporting chain) and I have assured that when we talk about the incident internally, Yaakov's name has been mentioned as a strong contributor to the positive outcome.Philippe– Philippe StaffMod2023-08-03 04:57:01 +00:00Commented Aug 3, 2023 at 4:57
-
13I trust Yaakov more than anyone on the actual community team. Take that as you will. He's a huge asset to the company, and the community!curiousdannii– curiousdannii2023-08-03 06:43:07 +00:00Commented Aug 3, 2023 at 6:43
-
4I hope this process of communicating and (better) understanding of each other will continue after the dust settles!Sybille Peters– Sybille Peters2023-08-12 11:47:11 +00:00Commented Aug 12, 2023 at 11:47
Add a comment
|
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. stack-overflow), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you