Personal projects that try to incorporate some new tech (or at least new to me)

Another Team: How do we do this thing? What aws role do we need?

Me: You do it like this, and I don't know the role by this guy does and all you have to do is ask him for the name of the role to assume.

AT: Ok, great.

AT: We're going to do it like this (wrong way, completely against best practices and completely against what the company architects dictate)

Me: No... thats the wrong way. Don't do it that way. That is bad, because (Reasons A, B, C). Do it the way I told you it should be done.

AT: Ok! I see thank you!

3 hrs later

AT schedules a meeting to go over options to do the thing ... including the WRONG WAY and they still haven't talked to That Guy to get the role name they need.

Python. Oh dear Python. Why, oh why, when I have your function with parameters defined as an int, do you blithely accept a string and just go about your merry day? If I wanted you to be able to accept a string I would have let you accept a string. But no, I want ints. Its not a suggestion. Its a demand.

You're dynamically-typed thug life gets on my static-typed backgrounds nerves.

(I am fully aware of the reasons for it and why, but my goodness I do sometimes miss my static-typed compile error languages, rather than pseudocode that accidently compiles python)

Why, oh god why, is our microservice component responsible for translating our output back into your obscure namespace xml format based on a Guidewire policy models? Why are we not just sending you back a Json - which is our output - and you have to figure it out into your details? Who messed this up?