11 ms·
Just Say No
- thenerdhead 4y agoGreat article! Yes fills time, no makes time. https://jondouglas.dev/saying-no-will-make-time/ https://jondouglas.dev/saying-no-will-make-time/
- geocrasher 4y agoLearning to say "no" is a super power. It also takes a lot of tact, and that can include redirection. Instead of telling somebody what isn't possible, I like to tell them what is possible and reset their expectations. My "No" sounds a lot like a "yes" that they get to execute themselves. "Hey, can you do XYZ for me, I really need it." "Oh, are you trying to solve ABC? There's an article I found that shows how to solve ABC without even having to do XYZ- can I send it to you?" "Sure!" Now I'm on the hook to DM/email a link, but not do XYZ. Solved. Does it work for every situation? You guessed it. No.
- ilyt 4y agoAnd for anything that's not the work you are contracted for "My consulting rate is $XXX/hour"
- sublinear 4y agoI disagree. One aspect of "tact" is that it's not always necessary.
- scarface74 4y agoI agree. Once my former CTO (and now friend) got to know each other, we had a common vision of what needed to be accomplished and sometimes bumped heads about the best way to do it (in hindsight he was right about 60% of the time). I was leading the “cloud native” initiatives. We had no time for “shit sandwiches”. I would just as often tell him that “you know in your heart that’s a dumb idea” and he would often tell me “I don’t have time for this shit can you just get to the point”. He was very technical. But focused on strategy. Of course this only happened behind closed doors and we would go to lunch afterwards. We got a lot done. Because of his mentorship on how to navigate politics and talk to and present to CxOs, I went from not knowing “cloud” in 2018 to working in the loud consulting department two years later. On his end, the company had sn exit for 10x revenue about six months after I left. It was a small company with only 3 million in revenue.
- latchkey 4y agoTwo heads are always better than one.
- geocrasher 4y ago"Does it work for every situation? You guessed it. No." I agree that tact is not always appropriate. Sometimes the only way to get the point across is to be point blank with the answer. "Can you do XYZ" "Nope, not in a million years." Does it work for every situation? You guessed it. No.
- ht_th 4y agoAs a teacher, I like to start with "No". Then, in the next paragraph, I explain why, come with alternatives, etc. This way I clearly and unambiguously communicate the answer, but I also try to be helpful. Over the years I learned that doing this the other way around, thus starting by being helpful and then saying no, resulted in people seeing wiggle room and started to negotiated with me.
- petre 4y agoIn Japan saying a definite no is kind of taboo and rather impolite. They'll say it's difficult, invoking lack of time etc. https://cotoacademy.com/how-to-say-no-in-japanese/ https://cotoacademy.com/how-to-say-no-in-japanese/
- JamesSwift 4y agoBig fan of everything Jeff has put out over the years, having found him back in the day by way of his large catalog of Ansible materials. One request: please dont advocate for stale bot :( I understand the tension between maintainers sanity and developers sanity, but there has to be a better way. It is absolutely _maddening_ as the consumer to interact with a stale-bot enabled repository. Please, just manually close the issues as 'wontfix' and link to this blog post instead.
- hu3 4y agoAgreed. Specially for small and medium activity repos. I would rather be ignored for months than have my Issue closed. Also, issues can help and be helped by others facing similar problems.
- toast0 4y agoWhen running into problems with a project, you can search closed issues too. It's not the default, but it's easy. Maybe there could be a project option to include open and stalebot closed issues.
- JamesSwift 4y agoYes, that "not the default" behavior is probably half my problem. I cant count how many days I've lost to trying to track down an issue in a project (trying to be a good citizen!), and then ultimately finding that the issue was already reported but closed by stale bot.
- deaddabe 4y agoWorse, stalebot makes it looks like the project has no issues nor known problems. Issues should be closed either with "wontfix" or let open if they detail a real bug that others may stumble upon. In the end, I agree that it takes time to do that, and who am I to dictate how people spend their time. Maybe the best solution would be to completly disable issues and PRs on Github. Still better than having to deal with stalebot. At least you know what to expect: external solicitation is not welcomed.
- DishyDev 4y agoI remember a colleague who was critical and pretty much the only person who knew how part of the business worked. He had a great analogy that for every new initiative and fresh recruit they brought into that area, it was like the organisation was hooking in another IV into him to draw more blood out. It's an image that always stuck with me to describe people in the situation Jeff found himself in.
- throwawaysleep 4y agoThis is one of the reasons I actively avoid acquiring domain and biz knowledge. You become expected to train others.
- incomingpain 4y agoI too had crohns. I too was busy saying yes as much as possible and was certainly in the final stages of burnout. I really needed to learn this lesson but alas here we are. cant say even until today ive really learnt the lesson, I just have a better work situation which doesn't use and abuse me like a tool which can be replaced. I'm obviously not the same category as Jeff; my open source projects are boring and dead. Luckily never needed surgery. Took me years to get off chemo and discover the cure to crohns.
- recursivedoubts 4y ago> but grug must to grug be true, and "no" is magic grug word. Hard say at first, especially if you nice grug and don't like disappoint people (many such grugs!) but easier over time even though shiney rock pile not as high as might otherwise be > is ok: how many shiney rock grug really need anyway? https://grugbrain.dev/#grug-on-saying-no https://grugbrain.dev/#grug-on-saying-no
- teddyh 4y agoI agree with grug, but grug was (mostly) talking about saying “no” to grug’s boss and business demands, not to users reporting issues.
- dncornholio 4y agoJust be honest to yourself and everyone. Follow this rule and you will automatically start saying no.
- ilyt 4y agoSay no to Stale issue bot
- JKCalhoun 4y agoI would be interested in the book on Crohn's — or just a discussion about it. Digestive tract issues run in the family and it seems Crohn's is this mystery disease that they have a hard time 100% diagnosing (like there's no tracer-gene or blood test that will identify it).
- bmitc 4y agoI need to read through this more thoroughly, but upon a first read, I feel I pretty strongly disagree with the approach and advice but not necessarily the sentiment. This is mainly coming from a user of open source projects who is both trying to contribute more and start projects where I'd be the maintainer. As a user, I can't think of anything more frustrating to spend hours or even days on an issue on an open source project that "welcomes" issues and contributions and then creating a detailed GitHub Issue only for it to be responded with with author's "No" and immediately closed. Just because the maintainers do not have time to fix the issue does not mean it isn't an issue! Too many times has this happened. It just means that users get a false sense of the tool's maintainability, reliability, etc. by looking at a "clean" issue listing only to find out that tons of issues still exist. How many times have you found an issue only to find several issues have already been reported, not fixed, but closed due to automated bots or maintainers just blindly closing? The issue still exists, but now its history is spread across a half dozen issue reports. This complicates what the issue actually is and contributions for it. The response to an issue of "contributions are welcome" or "you can fork it" are inappropriate because the filing of an issue is not a request to fix. It is an issue reporting mechanism. But too often, maintainers become chippy about reported issues. On another note, many maintainers will report how much of an open source developer they are on their resume or talks they give, when in reality their open source projects are just that, open source. They are often just open sourced personal fiefdoms. Which is honestly fine, if they are marketed as such, but they rarely are so. As I think about possibly open sourcing a personal project or two, I am thinking deeply about this. I think it's much better for expectations that if an open source project is going to be dictated by the maintainer, it should be explicitly stated so as to set expectations. Even then, I would not blindly close actual issues that are reported. Saying no is fine but please be honest and upfront on a repository's README. If someone says "this is open source but it's mainly a personal project and/or library and I will aggressively close issues", then that does wonders to set expectations. And I think that's the key idea. Setting expectations, upfront, is the key to effective communication.
- gautamdivgi 4y agoI don’t find anything wrong with the authors approach. I just think he should make it clear that he’s not interested in issues or PRs on the project readme or contribution guide. It’s hard to have it both ways - where you say issues and PRs are welcome but say no when someone reports or makes a contribution.
- tianqi 4y agoI remember having read a story that said (sorry I haven't bothered to re-find the source) that, among Steve Jobs' leaked emails, a large percentage of emails contained only one word: No. Interestingly, there was an email sent to him by Kim Jong Un requesting an iPod. Steve generously replied to him with two words: Hell no.
- baxtr 4y agoThat's super interesting. Can you share a link? (Now that someone is asking, maybe you bother to find it? Also, please don't say no to this...)
- shawabawa3 4y agofound a source but I don't trust it https://scoopertino.com/wikileaks-releases-140000-emails-from-steve-jobs/ https://scoopertino.com/wikileaks-releases-140000-emails-fro... edit: it's a fake news site > By now, you probably have realized that this was just a joke by Scoopertino, a website dedicated to sharing “unreal Apple news”.
- kyleyeats 4y ago"No" is so much more polite than what people do today which is just ignoring something forever.
- nonrandomstring 4y ago"No" is an important word because it's the only way you can say "yes". Imagine computers with only 1s and no zeros. Unless you can say no, you cannot wholeheartedly say yes. An offer you cannot refuse, or a question to which there is only one answer, are neither offers nor questions. Schopenhauer made the general semantic observation; in a world where everything is X, ipso facto nothing is X. Yes-men are really "nothing men".
- marcus0x62 4y ago> Saying no is hard. It's an admission you can't do something. Saying no is an admission that you won’t do something. You may or may not be able to do the thing: that’s orthogonal. By framing it in terms of ability, you internalize the no by describing it as a personal failing.
- baxtr 4y agoHow do you read "ability" into this? Can't can mean many things, like no I can't do it because I don't want to, I don't have time for this etc.
- hxugufjfjf 4y agoCan't (can not) does not imply won't (will not / don't want to), and vice versa. The words have different implications. Can't implies a lack of ability, and won't implies a lack of motivation. That's why the common statuses are "won't fix" and "can't reprodure", not "can't fix" and "won't reprocedure", even though the two latter would be interesting to see. While writing this reply I realized that able/unable might be better words to use in this context, especially if you want to specifically remove your own motivation from the equation. E.g., by saying "unable to reproduce" or "unable to prioritize" you are implying "can't" as oppposed "I don't want to".
- giaour 4y agoI definitely read "can't" in the passage you quote as expressing something like, "I can't do this because I'm too busy"
- bluetomcat 4y agoIn many work environments and cultures, it's not so easy. A single "no", even after a long row of "yes" can put you in an unfavourable position. I was once working in an outsourcing company that was onboarding developers in various short-term projects, for a usual duration between 3 to 6 months. When your project is over, they try to allocate you as a resource to another one, with a different team, different tech stack, different working hours and different work culture. I said "no" to a project that was IMO a bad match for my skills and interests, and that was the downward slope towards no further promotions, my isolation from management and my eventual departure.
- renewedrebecca 4y agoThen that work environment & culture is probably a bad fit.
- deleted 4y ago[deleted]
- axus 4y agoI feel like this is mainly an issue when you want to be the only person doing the work. Maybe ask someone else if they want to do the work, when you are too busy?
- varispeed 4y agoReminds me when working on large scale project, we have maintained strict quality control. The PR wouldn't be accepted if it had even a tiniest bit of tech debt or a hint of creating one. Less experienced developers were struggling to put the work in and our reviews have given them a ton of extra work, often the PR would look completely different from what was first raised. But the resulting code quality was great and the product had no issues whatsoever. The customer service never had to deal with problems with the project itself, just typical billing or "how to do something as I didn't bother to look into manual, please lead me" stuff. Then we had a new CTO who was unable to get the board to understand why things take long time. We got mandated to let all PRs through as long as there is reasonable amount of tests and they pass. This is where problems started to pile up. More experienced devs were now spending most of the time dealing with production bugs. Then they were quitting. Company also found a brilliant idea that it's better to hire 3 junior devs than one experienced. From there project turned into unworkable mess, nobody wants to touch. CTO got fired and most of the developers. Company then decided to outsource the whole thing and commissioned a rewrite.
- lucideer 4y ago> I also enabled the GitHub Stale Bot on most of my repos, and let me tell ya—for a lot of people that seems to be a hot-button topic. and for good reason. Reasons not stated nor addressed in this article, which I find concerning. > Despite how much some people detest the stale bot, it—along with a more easygoing attitude towards my projects—is the best burnout prevention measure I've personally taken. That's great: individual mental-health is more important. But disabling issue creation on all of your repos would've had a similar effect on burnout prevention, with all of the same benefits as stalebot & less of the drawbacks (no false sense of contribution created with users, no bridges built to be burnt). > I enabled the Stale Bot because it was an admission of this fact: Unless I specifically mark an issue as a bug or being 'planned' in my roadmap, it's just not that important to me. That's great in theory, and Jeff being a prolific & conscientious engineer, may actually work reasonably ok in practice for him. But it doesn't work this way for the vast majority of projects. For most, enabling stalebot is a measure to stave off disorganisation within the project, in which case they're not marking issues in a roadmap in any kind of timely/efficient manner nor really organising their issue queues well at all (as Jeff states here that he already is). Most issues that stalebot closes haven't even been looked at by maintainers. If you don't have the time to look at issues, ignore them. I do get that psychologically this is tricky as many chase a "Zero Inbox" type of approach to issue queue management, but take a look at any mature well-organised open source project and you'll see unaddressed issues that are years and years old. Maybe someone could invent a bot that hides ignored issues from maintainers - better maintainer filters. But as a user, I want to find those open issues & read the workarounds. I want to submit PRs to address them without having to keep track of 16 different issues opened on the same persistent problem that keeps getting closed stale. This tool might work for Jeff but if it does he's in a tiny minority & it's irresponsible to advocate its use for everyone without addressing the well-known criticisms at all.
- bouke 4y agoThis is exactly my issue with stalebot and I think it is a great disservice to the community. Closing issues without a maintainer looking at the issue is bad. I expect at least some triaging from the maintainer before the stalebot comes in and swipes the issue under the carpet.
- draw_down 4y ago
- scarface74 4y agoI rarely say no to customers in consulting and when I was working in the real world to managers or stakeholders. Instead I gave them a choice. Every project has three facets - time, cost, and budget - and framed their asks in terms of trade offs. As I’ve gotten more experienced, I can now add security, maintainability (technical people), legal risks, availability, ongoing maintenance costs, affect on future velocity, “bus factor” risks (“we don’t have time for training, documentation and knowledge transfers”), and is does the ask lead to a competitive differentiator (“does it make the beer taste better”)
- alfor 4y agoPlease, please, if you have IBS, Crohn or other immune disease try infrared light or better the sun. Especially if you spend a lot of time indoor (engineer) if you live in the north or if your condition get worse in the winter. I know someone who save his life that way. To me it clear up my winter eczema. We need infrared to get rid of inflammation. It’s scientifically proven, free, yet most people are not aware of it. https://youtu.be/5YV_iKnzDRg https://youtu.be/5YV_iKnzDRg
- alfor 4y agoIt's really frustrating to get downvoted for this. I know it sound new age and all, but it’s tested, there is research papers on it. It’s also very easy to test: two cages of mices one with infrared, the other without. Take blood sample and measure inflammation markers. Then you can correlate inflammation markers with various diseases and get an idea of the magnitude of the effect. I guess it was the same with vitamin-D, people must have think that plants use the sun, humans don’t.
- orthecreedence 4y agoI think you're getting downvoted because your comment appears to be completely off-topic from the post, and people immediately associate it with spam (especially when including a link).
- alfor 4y agoMake sense. It’s hard to share something like this and be taken seriously. The link is a doctor explaining how this work. People make the judgement in a split second.
- deleted 4y ago[deleted]
- fuckyah 4y ago[dead]
- jerrygoyal 4y agoComment section looks nice. I noticed that there's no requirement for email id. how's author preventing spam?
- geerlingguy 4y agoI'm using a service called CleanTalk, which integrates with Drupal pretty cleanly.
- rexreed 4y agoCurious on the shift to YouTube business. Is the ad revenue really that great these days for new YouTube creators? What's the real business on going YouTube semi-full time?
- geerlingguy 4y agoNot really; I'm earning less than half what I did consulting (and that on a midwestern salary... would've been much higher on the coasts). If you want to play the ad game and line up a ton of sponsors, you can make quite a bit more, but since I'm very selective with any form of sponsorship (most of my videos don't have a sponsor), that's a lot of revenue I'm leaving on the table.
- rexreed 4y agoSo is your revenue all ad revenue? How long did it take to earn? I'm curious because I'm also thinking of putting a lot of tech-oriented content on YouTube, and to make a bit on it (side hustle money), but I'm not sure what to expect. You have a lot of subscribers!
- geerlingguy 4y agoEach niche in YouTube is a bit different, the RPM is the most important thing. For tech you get maybe $2-4 per thousand views. For finance like $10. For gaming and lifestyle maybe $1-4, depending on what you talk about.
- deleted 4y ago[deleted]
- jawadch93 4y ago[dead]
- Zamicol 4y agoI've been meaning to make a web page that's a "Shrine to No", but not in the context he's speaking. From an informational perspective, "Yes" is meaningless without "No". If "yes" can be communicated, "no" needs to be a possibility (0, 1). No is fundamental to yes.
- Waterluvian 4y agoI'm part of an ongoing issue with Signal where it eats up and refuses to ever free 10+ GB of storage space on my iPhones. The Stale bot closing an issue after multiple people immediately responding, "no this is still an issue" is infuriating. I know it's hard, but if a Signal community dev said, "we hear you, this is bad, but unfortunately we're just not able to look at it right now." I'd be disappointed, but satisfied. Bonus points if they share a bit of "why". But hiding from or ignoring a problem is the worst answer.
- tootie 4y agoNo. But seriously, saying "no" makes you a jerk. In the real world, the options are never "yes" or "no". Specifically when it comes to prioritizing work in software development, the answer is pretty much always a "when" or a "who". I get asked for far more high priority work than I can accommodate. As a manager, it's easy enough for me to go find someone who has time and redirect it to them. As an IC, you have less authority, but can still ask to pass the buck. If it's a feature request or bug report, the answer is always to put it in the backlog. Just because I can't do it now doesn't mean it should never happen. It will happen when it gets to the top of the priority list. You only a reserve a "no" for when you really mean "never" or "that's a terrible idea so please don't ask again".
- justin_oaks 4y agoIf I want to contribute to an open source project is it good practice to ask the maintainer before submitting a pull request? I mean something like, "I'd like to contribute X. If I implement it, will you merge the pull request?" No answer indicates that the maintainer has no time for responses, let allow code review, so it's an implicit "No". An explicit "No" is helpful so I don't waste my time implementing something that will never be merged. A "Yes" is no guarantee, circumstances can change, but it's much better than the implicit or explicit "No". Or are there benefits to never asking?
- dagw 4y agoThe big question is do you need X personally? A lot of the time when I contribute to a project it's because I'm using the project and need the feature/bug fix for the thing I'm actually interested in. In those cases I'll just do it and then send a pull request. Some times they accept it, some times they don't, but in the mean time the thing I'm actually working on has the bug fixes and features I needed. You do however have to be prepared that you will eventually get a No, and then you have to decide if you want to maintain your own fork indefinitely or find another solution (like rewriting your feature as a standalone plugin or library that connects to the project)
- plorkyeran 4y agoThere's three general categories of unsolicited changes one might make: 1. The PR is a bug fix or feature that's critical for you, but you don't actually need upstream to merge it to use the fix yourself. 2. The PR is something quick and easy to do and if it doesn't get merged that's just no big deal. 3. The PR is a large amount of work that's entirely wasted if it doesn't get merged. For the first two, I see no reason to ask first. The third you generally should.
- Waterluvian 4y agoI generally agree with my interpretation of this article. There's important lessons there on saying no and on avoiding forms of burnout. But be very very careful not to mistake this as a solution to "I don't want to eat my vegetables." Sometimes we all have to do things we don't _want_ to do, in _some_ circumstances. If you're a contributor or author of FOSS, you are perfectly in your right to say no for any reason or no reason. But sometimes this all happens in a context where you're being paid to do a job.
- rem7 4y agoI read somewhere that “the more you say ‘no’, the more you can say ‘yes’ to the things that are important to you.” I really like that and try to stick to it.
- nayuki 4y agoSome related posts: "Open Source & Saying "No"": https://connortumbleson.com/2022/11/28/open-source-saying-no/ https://connortumbleson.com/2022/11/28/open-source-saying-no... , https://news.ycombinator.com/item?id=33771881 https://news.ycombinator.com/item?id=33771881 "Open Source Is Free As in Baby": https://danielcompton.net/dependencies https://danielcompton.net/dependencies
- linuxftw 4y agoI'm not a fan of stalebot at all. Just leave the issues open, so it's easier for a user of the project to browse the open issues and determine if they need to file a new bug, or maybe there's some info about a fix, etc. Having to browse closed issues adds a lot of overhead. If you release something and aren't planning on maintaining it or accepting contributions, and it's a somewhat popular project, at least update the README to inform others and encourage them to file an issue with a link to their active forks. Someone else might be enthusiastically maintaining it elsewhere.
- j-bos 4y agoA ship engineer I didn't know was famous for answering every question with: "The answer is no. [beat] And we'll negotiate from there." He never seemed stressed.
- aleyva 4y agoThanks for sharing-- couldn't agree more!
- jpambrun 4y agoStale bot are not okay. People spend time to write reproducible example of issue and are rewarded with annoying stale bot spam in 30 days. It could make some sense if the staleness was at least 365 days, then maybe the issue would have become irrelevant. It's also really frustrating to face an issue, search for it on the tracker and find one or more closed reports with no attempt at fixing it. Those should not be close. The project is maybe yours, but record of issues isn't. It's a shared resource.
- geerlingguy 4y agoEvery time I see an actual, reproducible bug report come across one of my repos, I immediately label it with 'bug', and the stale bot will never touch the issue. I only let it loose on all the thousands of feature requests and incomplete issues where I have no idea what the person is even asking.