At my first job, I was on a small team and my boss did all the code reviews.
He would leave comments like:
- "This is really awkward, change it to..."
- "This variable name is awkward and confusing"
- "You have failed to understand..."
- "You are overthinking this. Keep it simple and do..."
- "This causes unnecessary overhead. Think about it..."
Every review, I would have to re-write everything to exactly how he wanted it, variable names, logic and all. To the point that the code was not mine.
I would very much disagree with what he wanted. Any type of constructive push back would be met with enormous backlash.
But it wasn't always what he wanted me to change, - the way he delivered the feedback irritated me the most.
In my following jobs, I have had many reviewers for my code. I've had 30+ other people review my code. They have all been much nicer. And deliver feedback that I actually agree with.
I am thankful when someone finds a bug in my code, or an easier way to do something. Using a function that I am not aware of. This way QA won't find the bug, and I am learning.
Anyways, my advice is to look at how the person is delivering the feedback. Take note of that, and know it is them if they are toxic. And when you do a code review for someone else, be sure not to be that person.
I’m unsure why an engineer would want to be back in the office. There are a lot of distractions and unnecessary stress.
From my point of view, engineers who depend on others to get their work done like to be in the office. Because it makes it look like they are collaborating and getting work done.
From a manager point of view, this looks like collaboration as well. And would benefit the project. This is why they want people in the office.
I disagree with it. There are engineers who like to manipulate other people and it is far less likely to happen in a remote environment.
Nice, - I like the simplicity of your UI. Though I can't read French, it looks like you've got some nice features there.
No, I haven't thought of thought of that. Very cool idea.
I'd like to make the API accessible via JS from all domains, but using an API token. I'm starting to get a lot of requests to use the API, however, most everyone wants to call the API directly via JS. Right now they have to go through a proxy like NGINX or some server side proxy.
No company likes laying off people. Makes me think, - is the author not believing the market right now? Because it is terrible. No company likes losing
I believe what was going on was some Spiritual Warfare.
It's interesting that she was working with the two different sides. And they were actively pulling against one another. This isn't uncommon.
God was showing her what true love and compassion looks like at the Catholic hospital.
The devil didn't like that. He wanted to deceive her into thinking she could be a psychic, and that she can control the universe with her own free will. She was also actively deceiving her clients, who were turning to her instead of God.