I think my intent is less different from what you stated on how it comes across.
Especially this bit "I’ve worked with people who are so unafraid of being wrong that they can’t be trusted.". Hopefully the article doesn't come across as "be mindless" in the workplace. In fact in the conclusions I state that this is no substitute for hard work and thinking critically.
> "first construct a hypothetically ideal workplace and then explain how to operate"
I don't think this is what I stated but I know it wasn't the intent. Hopefully, working on a psychologically safe workplace isn't hypothetically ideal.
I'm definitely learning a few tricks on what I should be clearer by reading the comments though so thank you.
Author here. I really hope it doesn't come across as "blurt out falsehoods with confidence all the time"- I do mention in the conclusion that this is no substitute for working hard and thinking critically.
One thing I have a problem with in the workplace is what goes unsaid because everyone in the (chat) room already understands the premise and are on the same page versus things they have not even thought about.
For example, let's say there is an azure function that does something but is failing some of the time. I'll say something like hey me sending a message to the service bus again fixed this issue for me. Three people will yell at me and say sending this message doesn't do what I think it does. I'm sorry how do you know what I'm thinking? A week or so goes while we struggle with this problem. It isn't even a big problem because we can all clearly see the code and can read what it does but people are so confidently incorrect about their own code. Finally about a week later someone else has a revelation. Oh resending the failed message seems to fix the problem. And I'm thinking how did you not get that conclusion from what I said.
I feel like I'm missing some context because I feel like the senior developers in the room want to manufacture a crisis so they can rewrite the whole function but how do I ask this question out loud?
I mean I fully support that the code needs a rewrite. It is difficult to read and frankly the approach isn't very good but it feels like we are hesitant to making small incremental improvements today lest management thinks it is good enough and refuses to pay for a rewrite? Am I overthinking this?
This was a christmas holiday project. Wanted to look at Go from a web development perspective but it actually ended up being more about web page scraping.
I am aware that amazon already allows you to see the total but again, this was more an exercise in web development than providing a new feature.
https://github.com/nlopes/acdc
Still lots to do but I've been having a lot of fun.