Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Honest question, not trying to start anything. Just want to understand the perspective.
Without these meetings, would you ever be interested enough in other teams' work and read their documents? But you may find something cool and realize they you can leverage some of their work for your future work?
Or if they solved a problem you have solved and may want to see how someone else solved it?
Of course you can read the docs and emails people send, but would you? -
@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. -
For the sake of being able to integrate with a service the docs are fine but for knowledge on what is available and how it was designed to A show possibilities B better understanding of the perform area is really hard to convey in documentation.
Two meetings a week is a bit much though.
Recommended sounds optional to me. @KDSBest has it right. If there is a agenda it seems perfectly fair. If not suggest it to management with supporting arguments and don't show up until they change it.
Then only attend the ones you are truly interested in and ask questions. That should give you maximum visibility.
I wonder when there will be the first manufacturer to introduce the "cool" new notch design to normal screens....
Bored, stuck in a long ass meeting. When suddenly someone brings up the program I made. People start complemen...
I fucking hate corporate environment. We have a weekly meeting in our tech department where a team is chosen at random to present the project they're working on, architecture and such. You know what? We have fucking documents, for both product scope and technical architecture. If you're interested in our work, go fucking read our docs. If you have a question, slack us or send us a fucking email. Why the fuck do I have to attend a 1-hour meeting every week for this bullshit. Oh and some dude from upper management has a brilliant idea: from today they decide to host 2 such meetings per week, 1 within the tech department, and another within the whole company. So we had to attend the same fucking meeting twice in 1 week!!! Fucking genius!
I'm so fucking tired of these meaningless meetings, but attendance is recommended because "this is how you reach staff level" as they told me. Fucking bullshit. I may try a few more years for the sake of financial stability, and then find a small shop where people just leave me the fuck alone with my codes.
rant
corporate
bullshit
meeting