this post was submitted on 24 Aug 2023
396 points (98.1% liked)
Asklemmy
43936 readers
463 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Meetings and discussions are work
We found a manager.
The dude is right though. The most important part of being a programmer is designing an elegant solution. That requires talking the problem through, solliciting feedback, getting ideas… you meeting with ppl and talking to them.
The second most important part of being a programmer is realizing that you’re not doing this alone. Once again, you talking to colleagues to discuss what they can expect and when, likewise what you need and when.
Meetings are super important. Unless your a code monkey or if it’s office gossip or me having to spend an hour explaining why a job estimated to take 4 weeks will not be done next Friday. And no, “trying a little harder” or “realizing how important this to the client” isn’t going to change that.
They CAN be work. They frequently are an impediment.