6 ms·
I understand it's tongue-in-cheek, but #2 is actually worrisome: > There’s even a “no meeting Wednesday” meme in the company, which you might as well call a “f
by crazygringo 14y ago
I understand it's tongue-in-cheek, but #2 is actually worrisome:
> There’s even a “no meeting Wednesday” meme in the company, which you might as well call a “failure to communicate” death wish. Software needs to be talked about and debated, not simply written. It’s lunacy to be writing and shipping code at a blistering pace, instead of letting things bake a bit in committees representing broad swaths of all semi-affected parties.
There are a lot of companies where failure of communication is a very real thing, and where semi-affected (or totally affected) parties are completely ignored. In my experience, ideas for code do need to be talked about and debated, not simply written. Facebook has had a lot of very public privacy/other failures that could probably have been avoided if there was more communication going on.
If you're just writing code at a blistering pace, without a lot of communication, there's a good chance you're not writing the right code.
- neilk 14y agoNo meetings != no communication.
- aloneinkyoto 14y agoMeetings != Communication (always avoid double negations)
- petercooper 14y agoExcept (No Meetings != No Communication) != (Meetings != Communication)
- ninh 14y agoIf you define "No meetings" as !meetings, and "No communication" as !communcation, which to me sounds reasonable, then they are in fact equivalent. This becomes apparent when you create a truth table for it: !meetings != !communication meetings | communication | expr F | F | F T | T | F T | F | T F | T | T This is the same truth table one would get with "meetings != communication" so they should be logically equivalent.
- lifeformed 14y agoBut in dealing with language here, there are subtle differences in connotation between the two options. Just like how saying "not bad" isn't that same as saying "good".
- cbs 14y agoBut in dealing with language here, there are subtle differences in connotation between the two options. We're not dealing in language, formal symbols exist to remove the ambiguity of language. Plain and simple, the symbols used don't mean what the poster thinks they mean.
- hackinthebochs 14y agoThe symbols are simply shorthand. Trying to parse it as a mathematical equation was your mistake, not his.
- cbs 14y agoPies and cactus. Jackalope. If you read the above as anything other than a nuanced and well reasoned response thats your mistake, not mine.
- petercooper 14y ago"No meetings != no communication" is analogous to saying "Without meetings, people may still be communicating." "Meetings != communication" is analogous to saying "At meetings, communication doesn't necessarily occur." In terms you would personally appreciate: (No Patrick Hernandez != No Dancing) similarly is not equivalent to (Patrick Hernandez != Dancing) One says without Patrick Hernandez, there may be dancing. The other says with Patrick Hernandez there certainly is not any dancing ;-)
- ninh 14y agoYou're referring to implication then, i.e. P => Q <=> !P || Q and in that case, I definitely agree. ;-) That's also why I started my comment with a propositional "if" on how one could define "no meetings" and "no communication" to show that there is something to be said for the P != Q interpretation. In short, I believe neilk should have used => instead of !=. Or just plain english. ;-)
- cbs 14y agoActually, yes, it means exactly that. neilk incorrectly used a comparison operator to try and point out the logical fallacy known as affirming the consequent. But thats not what was said. At least thats what I think is happening here. I can't be sure because instead of using logic symbols they used symbols that are ambiguous at best.
- hackinthebochs 14y agoIt should be obvious that != in this context is read as =>
- jrockway 14y agoMeetings are a very expensive way to communicate. A concise, well-edited email is more difficult to prepare, but cheaper for the company. If something takes you an hour to write but the ten recipients can understand it in six minutes, you saved nine hours of time over having an hour meeting. That's like having an extra person on your team, without having to pay them or buy them a computer! (That's why a textbook costs $100, but a semester of class costs $2000. Economy of scale.) Of course, if you anticipate the discussion to mostly be back-and-forth, then a meeting could be necessary. But have an agenda and stick to it. If you just want to socialize with your coworkers, duck out early and hit the pub.
- anthonyb 14y agoEmail and face to face communication are completely different beasts though, particularly for tougher issues.
- jrockway 14y agoSure, but not all issues are "tough". Many people never write and always meet. And that's the wrong balance that annoys engineers.
- anthonyb 14y agoEngineers typically go the other way though: always write email and never meet. Then they wonder why their project goes south because the specs are incomplete or the users aren't happy. I think it's largely a knee-jerk reaction against bad meetings - hour long no-point crapfests - but they don't have to be like that.
- sardonicbryan 14y agoAgreed. On my team at Kabam, we have meetings, but 1) They are as small as possible, typically including just 2 or 3 people. 2) Are always optional. 3) Typically last around 15 minutes. It helps to have plenty of space/rooms where you can just pull someone aside to hash out a quick issue, and a mature, responsible team that doesn't need baby sitting to get stuff done.
- jackowayed 14y agoI work at Cloudera, and engineering has work from home/no meeting Wednesday. It allows people to work wherever they prefer and are most productive, and to have the whole day to focus with minimal distractions. That said, we do still communicate as needed for the active work. But we do so in terms of emails, chat messages, and sometimes phone calls between only the necessary parties, without any long scheduled meetings or meetings that provide value in the longer term (eg. interviews or longterm planning meetings) as opposed to helping someone do the right work today. It works great, we've been doing it for basically the whole life of the company, and I don't see it stopping.
- lupatus 14y agoI work from home / where ever every day. And, it is wonderful. I can even take as much unpaid time off as I want, whenever I want, as long there is no disruption of business services to our clients. This works because I get paid hourly (I don't work = I don't get paid) and we have very fine granularity in tracking what work was done when. There is also high trust amongst all the team members that everyone is being honorable.
- goblin89 14y agoIt does work, but has its drawbacks, for one it's communication requiring extra skill (and effort) when people don't see each other frequently. Seems that way to me (I currently operate in an environment similar to yours).
- clwoodson 14y agoMeetings are fine if they have an agenda, someone to enforce the agenda, no extraneous parties, are timeboxed and have a predetermined outcome should no consensus be arrived at. "We're going to shelve this unless we can come up with an acceptable solution within 30 minutes"