cannabis, ranting, software engineering
I remembered what it was. -- Software Engineers really need VERY HIGH Reading Comprehension skills and WRITING skills. Code is a symbolic language. you need to be able to read both code and error messages and interpret what they mean and apply that meaning to your structural understanding of the application you're working on. This takes MASSIVE literacy. And you have to be able to WRITE comprehensible error and log messages. OMG this is my high horse now.
IT'S NOT READY. IT HAS A DEPENDENCY THAT HAS NOT YET BEEN RELEASED!!
Why is the idea of releasing discrete testable units of work sequentially so hard for some folks to understand?
PM: Feature 2 Depends on Feature 1 Right?
PM: So we can release them both on Friday right?
Me: No. We're releasing Feature 1 on Friday.
PM: But feature 2 is basically ready too right?
Me: Yes. But if something goes wrong with Feature 1 we won't be able to roll it back if you also immediately release Feature 2
PM: But Feature 2 is ready?!
nerdy, kinky, queer, animist, feminist, technologist
*Due to increased bot signup, manual approval is required. Please write some applicable request text on signup.*
This Mastodon instance is for tech workers, academics, students, and others interested in tech who are LGBTQIA+ or Allies.
We have a code of conduct that we adhere to. We try to be proactive in handling moderation, and respond to reports.
We're not a free speech absolutist. We're not interested in Nazis, TERFS, or hate speech.
This instance is meant to be a friendly, welcoming space to all who are willing to reciprocate in helping to create that environment.
If you’re ever unsure, ask first. Use CWs where required.
If you’re accused of causing harm, either take some responsibility or ask moderators for help.
Our moderators are here to listen and respond to reports.
This instance is funded in part by Patreon donations.