Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try [email protected] or [email protected]
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
That people (both the CTO and devs) eventually asking ME for suggestions. And acting on it even if on projects I've barely touched while working there. They been through multiple years of university and some have been through multiple jobs. I'm just a guy who knew a bit programming when I was hired as phone support 13 years ago.
I love the team though. It was just me and the CTO that did dev for many years, and now we are 7.
Something I heard a while back. A leader, when getting advice, should be the dumbest person in the room. Not because they are dumb, but because the surround themselves with people even more intelligent then themselves.
By the sound of it, your working with people confident in their own skillset. They also know when an outside voice might have a useful perspective. You also likely have a significantly different experience base to them. To you, something it obvious, to them, it's really not.
I once saw a project (7 figure) that was being used regularly outside. It's only when the field techs got to play with it, one asked how waterproof it was? It wasn't; at all. The head engineer was so laser focused on the technical, he missed the woods for the trees.
You can still be the smartest person in the room, and play the dumbest. Ask questions, you might find new data points you needed to make a sounder decision.
It's more intended as an aspiration. It can also be specialist intelligence. A salesman can know far more about what your customers will buy. An engineer can know your manufacturing chain inside and out. Both are weak in each other's area of knowledge. You can be weak in both, but leverage your intelligence to combine them.