@Lensflare which good stuff from other languages that Go doesn't have?
I'm not sarcastic btw, just want to learn

@Lensflare never written a single line of Java in my career, but love Go btw

This manager is really out of touch if he/she thinks devs stop getting raise after 25. But even if that's what he/she thinks, saying it out loud like this dumb. Did he/she consult other people?

Here's my variant of your pattern:

Cook A:
- Makes soup
- I warned him of potential issues with his approach to cooking soup
- He ignored my suggestions

The soup was delivered, he was promoted to head cook, and no longer made soup. The soup is now my responsibility. The issues I warned him about started to appear. Management be like "what the hell did you do with the soup? It was perfect when cook A was in charge"

@iceb it depends. A simple email, or announcement via slack works for me. Something like this:

Hey team, these are our weekly updates:

- Team A has successfully implemented their CRUD Restful API backed by MySQL . Here's the API specification *insert link* and the architecture diagram *insert link*

- Tooling Team has finished the terraform migration project. Here's what you need to know *insert link to document*

...

Let's say I worked a ton on Restful before, I can assume that if there's something special about their Restful API implementation, then it would have been mentioned already. So I'll skip this.

But I don't know much about terraform, I'll definitely check out their project doc.

I get your point, there will certainly be people who are too busy or lazy to engage in these activities. But from my experience, if they are too lazy to read docs, then they will just doze off in meetings as well, so nothing is improved.

this fucking junior just reported that I "didn't mentor him enough" to my manager! Meanwhile he couldn't accept the most basic feedback!

@johnmelodyme I talked to my cousin's boyfriend, who's also a dev in 2017. I asked him if his company followed any git model, he said no. After some more exchange I found that he does not know git, so I asked how he managed source code, he said google drive. I thought he was kidding but after asking again twice he still kept a straight face. You'll be amazed at how low tech some companies are.

A company I worked for did exactly this in 2012. Why not simply use an ORM for this?

@IntrusionCM tell them throwing the exception allows them to write the exception message to a file, trigger a print job so that they can shove the paper up their ass, which is a more conventional error handling method than logging.

@jiraTicket https://go.dev/blog/waza-talk

Not admitting your own mistakes and lack of knowledge is a big red flag.

At my current company devs are encouraged to make presentation for the sake of knowledge sharing. I once attended a presentation on Golang concurrency. In the first slide the presenter wrote "concurrency means doing multiple things in parallel". It's funny how some people failed to google some fundamental knowledge. It's ok not to have a degree, but at least do your fucking research before presenting something. Sharing false knowledge is damaging.

@rantydev true, in my case he has the excuse of being a junior. A good tech lead should know how to write good comments.
But I'm not surprised, I've seen a fair amount of incompetent tech leads before.

Your senior tech lead and my junior dev would make a great pair! Check my latest rant to know why

@nullcoffee he will enjoy it. Tbf he has only begun working as a dev for a few months, his code comprehension is weak. That's why he wants each line of code to be accompanied by a comment in plain English so he can understand it faster.

@lassiecoder we do code review for every PR, usually it requires 1 senior dev approval before it can be merged, but everyone is welcome to share their opinions. We don't have code review sessions with the whole team every week, but when code smell is detected anyone can raise a ticket

@magicMirror this is a nice idea, will ask him to do this, maybe he'll see the problems lol

Refactoring is fine as long as it has a purpose, and is agreed upon. Many times I've seen devs refactor something they don't understand into something they THINK is easy to understand without consulting other devs.
The result is often equally hard to understand codes written in a different style. It could be worse if the refactored codes are not well covered by tests.

I hate it when managers try to "help" by getting involved directly. Most of the time they are just nuisance. Many of my debugging sessions are prolonged by my manager. It goes something like this:

Manager: hey we got a problem in production. Let's check it together.
Me: No, just 1 person is enough, also easier to focus.
Manager: No, let's do it together. 2 is better than 1
Me: *big sigh because I know he will just be in my way*
Me thinking to myself: okay, it looks like X is malfunctioning, and X is controlled by Y, so let's check Y, should I add some more debugging logs?
Manager: Hey man I think the issue is Z
Me: No, Z is working fine because blah blah. I checked it already. See this, it's expected.
Manager: oh right, that's true
At this point I lost my thought and had to start over

To all managers: if you want to support your dev, please just let them work in their preferred way, provide them enough information, point them to the right person. Get involved only when you're asked.

1) I'm using a Sony WH-1000XM4 that is far from a big ass headphone
2) I'm typing on my Macbook's keyboard
3) I'm never fond of stickers
4) I have some tissues to clean up after lunch, not for wiping tears

Guess I'm not a trve dev

@AlmondSauce like all meetings*
FTFY

Also ninja, rock star, jedi, etc.

Do we have the same manager?
https://devrant.com/rants/4712544

It's super common for this to happen. Everytime you ask they say the requirement won't change for the next 5 years. And then it changes 5 days later

I spent 9 months building a specific tool. Then one day the business people said they found a third party solution and would like to use it. So 9 months worth effort of my team went to absolute waste. Our year end review's gonna look bad

@KennyTheBard did he consult you or someone with more experience about the approach before? Telling someone more experienced than you about what you plan to do in a PR often saves lots of CR time

@OldManOfTheC this is true lol. My manager insists that we need to move faster, bad codes will be tolerated with a todo comment. Of course no one fixes them

Please tell me that you're leaving that shithole

Manager: what's blocking you? Can you move faster?

You can be honest and polite at the same time, and it gets you somewhere.
For example when my boss asks me for feedback, instead of telling him that he's a micro managing degenerate piece of shit that should go fuck himself, I told him that he should trust his employees more, give them more freedom. He thanked me for that and said some nice words about me to upper management.