10 ms·
Beware offers of “help” with your projects
- jrm415 4y agoSometimes my 5 year old wants to build her block tower just the way she wants, and she says no thank you if someone offers to help. Other times she accepts help and then the tower takes a different form. Both ways are OK.
- lars-b2018 4y agoThis article talks about two main things. Accepting "help" applies more broadly than engineering or software. And I agree with his overall goals of his project..I believe the same. We get trapped into this bigger and better and more complicated stacks and the hardware resources required, but you can reach a lot of folks with simplicity and the basics.
- Alupis 4y agoThis mostly sounds like the project owner doesn't have experience, or perhaps more importantly time, to manage the project and 3rd party contributions. Nothing is wrong with that, of course - but the framing here, I take issue with. Placing the codebase on GitHub would allow folks to work and make contributions in the form of a Pull Request, which the OP can reject with explanation if it does not go in the direction they desire. They can even setup a roadmap and tickets (issues) to help guide eager-to-help offers. For anyone wanting to take the project in a direction OP doesn't want - they can fork it and do just that. So no, don't beware of offers to "help" - be aware of your time commitments and that not everyone's goals will always align with yours. That's just how open source works...
- travisjungroth 4y agoYou can have the experience and time to do something and choose not to.
- Alupis 4y agoThat is perfectly fine - but then don't write a blog post warning people about free offers for "help". Just instead say you're not interested in doing OSS and want to keep the project private. You're not obligated to do anything.
- re-thc 4y ago> which the OP can reject with explanation if it does not go in the direction they desire. Often that alone - going through pull requests is time consuming enough to drain you.
- dndn1 4y agoWhat I read sounds like the project owner can clearly articulate the projects purpose (a point about free speech and big tech v lightness and about enabling). And the proposed contributions are reasonably contrary to them as he sees it. Experience, time... I think the response in this case was perfectly reasonable so I don't know how to remark on this. Hosting the code (someplace) and discussing issues may be separate good suggestions, all in the context of the projects purpose.
- UncleEntity 4y agoI think the confusion is coming from it being a social network which requires them to ask people for “help” to prove out their ideas — you can’t have a network without users. Having people helping to prove the idea is one small step away from having people helping to implement the idea and, IMHO, is where the confusion is coming from. They want to implement the idea without help but can’t because the idea itself can’t work without help and helpful people are, unfortunately, helpful. Totally wrong message being learned here.
- ojbyrne 4y agoBy the point of “It is being so wrapped up in yourself and your own goals that you cannot accept the fact that your goals are not more important that those of everyone around you.” I couldn’t help but think of the expression “Pot…Kettle…Black.” I think most Engineering Managers know that doubling the number of engineers doesn’t double the speed of development, but you have the accept that sacrifice to actually get things to market.
- burnished 4y agoIf you think there was hypocrisy then I think you lost the thread - the point is not accepting help from people who are more interested in their own vision of the project than yours (as the originator of that project). Hence why they don't accept offers of volunteer help.
- travisjungroth 4y agoThe author is not being hypocritical. They can accept that their goals are not more important than the person emailing them. But (in the author’s view) their goals are incompatible. This project can only achieve one set of goals. If they try for both, it’s likely neither. So, the project goes as-is. I can think that my hunger isn’t more important than my family’s, but if someone offers to help eat the sandwich I just made reply “go make your own”.
- guhcampos 4y agoThe author is not being hypocritical, just arrogant.
- SoftTalker 4y agoWell, it's their project.
- guhcampos 4y agoGranted. But then why write the passive-aggressive blog post and post it on Hackernews? Just say no. Done deal.
- wvenable 4y agoI recently forked a project to make some significant changes to make it more useful for my needs. The direction I took the fork is different from needs of the original author. My version is definitely much more useful for other people but wouldn't be any help to the goals of original project. But I'm very thankful that the original author just posted his code to Github to make this possible.
- ivraatiems 4y agoYeah, I'm confused as to why the author wouldn't make their source code available with a message that says "I am not looking to accept pull requests or help with this project, but I'm providing the code in case it's useful to anyone in their own pursuits." That seems like it would make everyone happy, wouldn't it?
- Waterluvian 4y agoGitHub surely has a way to simply disable both Issues and PRs right? Clone it. Fork it. Star it. That’s it.
- arp242 4y agoYou can disable issues but not PRs. People faux-disable it by opening a PR with "don't open PRs" or set up a bot to comment on PRs.
- internetter 4y agoHaha, you'd think. You can disable issues, but not pull requests, which has been a pain point for the last... forever[0]. Best you can do is setup workflows to automatically close and lock every pull request (and optionally, add an exception for a single pull request that says in all caps "DO NOT OPEN PULL REQUESTS"). It's as painful as it sounds. [0]: https://github.com/github/dmca/pulls https://github.com/github/dmca/pulls
- airtonix 4y ago[dead]
- deleted 4y ago[deleted]
- pella 4y agorelated: https://macwright.com/sites/polite.technology/preview https://macwright.com/sites/polite.technology/preview """ Responding to feature requests Once a project achieves a certain level of success, it will have users, and those users will have additional demands of the project in the form of feature requests. Experienced and empathetic users will state their feature requests precisely and kindly, but others will use an unfriendly tone or imprecise language that doesn't lend itself to a solution. The maintainer does not owe their time to anyone The maintainer must treat everyone with respect Ignoring the first principle will lead to burnout: there are unlimited features to be requested and limited time to implement them. The sense of obligation quickly becomes an emotional burden. Ignoring the second principle will damage the project and reduce its chances of ever attracting additional contributors, which is the only way to succeed in the long term. 1.) Maintainers are the keepers of the project principles 2.) The goal of the software. 3.) The scope that defines problems that the software will try to fix and those it will not. 4.) The style of the project: which programming practices are used, which language. 5. The culture by which the project is managed. 6. Maintainers approve of changes to the software by these principles, and also manage discourse and which other contributors are allowed. """
- joshribakoff 4y agoThe author seems to propose it is impossible for large teams to be productive. They even go so far as to claim most potential team mates have malice intent to “sabotage the project”. Amazon is an example of an organization that does this well (i used to work there). Small teams are responsible for their own project(s). Project(s) can be composed to form higher level project(s). It’s certainly not impossible, and id rather put in effort to manage team(s) than to place an increasingly insurmountable amount of pressure on myself. Perhaps the reason the author’s project has “few users” is that there are competing alternatives that have authors who understand how to leverage team work to deliver more value to users, and users go where they perceive value. Also, if you worked for an organization that actually hired (and retained) people with malice intent, i dont think team size was the real issue. In that sense i do agree with the author that you should screen anyone and ensure your goals align before agreeing to invest time in trying to work together. If someone is offering to add a feature you dont think fits in the project, i have a hard time characterizing that as “malice intent”, though!
- foobar1962 4y ago> The author seems to propose it is impossible for large teams to be productive. Not productive, efficient.
- RajT88 4y agoThis story sounds quite a lot like a few experiences I had. Years ago (more than I'd like to admit), I took to playing Travian with friends and coworkers. Travian is an RTS, where 'Realtime' really means 'Real-Time'! If you attack the town next to you, just a few squares away, it can take 5 hours for your troops to arrive and the battle to ensue. It was the perfect game; you could play it casually, in between stuff at work during the day, or on break, or in the evening. My friends started getting really into it and spending a lot more time on it. I did not want to spend more time playing it, but it was a fun game. The makers of Travian did something interesting, though - they would dump one database table with city data every night for people to do interesting things with. My friends were using a bunch of these tools already, but I perceived some opportunity to build tools which didn't yet exist - like a tool which let you discover inactive accounts to pillage. I starting building more and more tools, eventually starting to write a bot to play the game for me, by automatically raiding inactive accounts and automatically building up my current towns to avoid appearing inactive. My goal in doing this wasn't to play the game per se, but to learn and get better at programming. So I made the mistake of mentioning all this to another friend who was playing Travian. He was interested. I told him if I ever finished, he could try out the bot, but in the meantime he could use the rest of my tools. Well, he got impatient waiting for the bot (which btw, I never finished, but I did learn some cool stuff from the experience). He decided he was going to 'help' me, by group calling me with another programmer friend of his who first of all quizzed me on how I was building it, and telling me I was doing it the wrong way and that I needed to use different languages, frameworks, messaging layers, etc. Yeah, so now that I am way further in my career, that guy was dead wrong and an idiot who was trying to overcomplicate everything. But the point was - he didn't want to help, he wanted to stroke his own ego by fixing (or as the case may be, fucking up) some other idiot's project. This actually really strained my relationship with my friend. Huge dick move, and one that took me a long time to forgive him for. Stay out of my personal projects! To me, it felt along the lines of hearing about an argument with my wife, and then unbidden forcing me to take a call with a relationship coach who told me I was a bad husband.
- asdfman123 4y ago> he didn't want to help, he wanted to stroke his own ego by fixing (or as the case may be, fucking up) some other idiot's project Maybe that’s just the way he approaches problems. Not necessarily helpful to you, maybe legitimately annoying, but why assume the worst?
- guhcampos 4y ago> "My primary goal for Xnet is to prove that--contrary to everything everyone else says--one does not need a huge, expensive server on a super-fast Internet connection to host a social network with tens of thousands of users" I don't think "everyone else" believes that. In fact I believe a "social network with tens of thousands of users" can probably be served off a bash script running on a Raspberry pi over SQLite.
- EarlKing 4y agoI mean, that basically describes a telnetable bulletin board system, and those definitely run off an RPi. This is a common problem with tech-adjacent types: believing that technology is the solution to all problems, including social ones. If someone isn't using your preferred social networking solution, the problem isn't necessarily that you're not using the latest whizbang language and hardware....... maybe you just haven't given them anything to do on your network. Put another way: the telephone arguably didn't catch on as a utility with obvious use until after the 1878 Tariffville Crash[1]. If you want to start a new network, you need a social nucleation point... whether that's you writing interesting stories, composing music, making artwork, whatever... SOMETHING that people can participate in and interact with in some fashion. Without that you've just got a communications device with no one in particular to reach for any reason. -- [1] https://en.wikipedia.org/wiki/1878_Tariffville_train_crash https://en.wikipedia.org/wiki/1878_Tariffville_train_crash
- thimkerbell 4y agoIt is good that the writer could discern that his and the would-be helper's goals were not aligned. I wonder what the best ways of discovering (and perhaps verifying) alignment-or-not could be.
- andrewstuart 4y agoSoftware projects need a "Director" - much like a Film Director. This person has ultimate control over what the software should be. I'm always surprised to find software that is a really cohesive and appears to be the implementation of a clean and consistent vision, because software projects have so many people pulling it in so many directions. This is, IMO, why MacOS is such a simple and clean and consistent implementation and Windows is just spaghetti soup. I don't know the truth of how these projects are run but I imagine at Apple there is someone at the top with a really clear vision of what MacOS should be.
- chrisjharris 4y agoI'm sure that somebody has thought this through more fully than myself, but the impression I have is that for software, the benevolent dictator model works best. Python and Javascript occupy adjacent places in the programming language firmament, but the Python language (with van Rossum having fairly tight control over it), although bloating somewhat over time, has still ended up quite a lot more elegant than Javascript.
- UncleEntity 4y agoIronically, Guido got dethroned precisely because python became too popular and “you can’t please all of the people all of the time” so he just walked away. Now they have committee meetings to decide if an idea is good enough to form a committee to discuss if a committee should be formed to discuss the idea — though, probably not exactly like that…
- scrollaway 4y agoModern python is not more elegant than modern JS, I disagree (I’ve been coding in both for over 15 years). Python has a good degree of elegance to it, and it does have less warts due to its less stringent backwards compatibility requirements. But JS is very elegant, and better at it than python thanks to python’s shitty lambdas vs js anonymous functions.
- yakshaving_jgt 4y ago
- LastTrain 4y agoAm I missing something? There is no lesson learned here. No offer of help was accepted and nothing went wrong. Why beware? He hasn't even tried it. Hell I can't even really parse if there ever was an offer to help, just some suggestions.
- proxiful-wash 4y agoI don't think you are. Not sure why I am reading this either.
- taneq 4y agoThat's basically what the article is saying, though, isn't it? The author wasn't deceived by an offer and didn't suffer a setback, they're just commenting on the fact that offers of help always carry some kind of cost. In this case the cost was compromising on their goals for the project. It goes in the same basket as any other unsolicited opinion on the internet, including this one.
- LastTrain 4y agoExcept he has no idea what the costs would have been, and neither do we, because it never happened.
- thrawa8387336 4y agoExcept he does have an idea. Some people don't need a summary from a double-blind randomized decade-long experiment to know things
- 1lint 4y agoThe author wasn't deceived, in fact no one even tried to deceive him. Rather, a guy offering to help clearly communicated his intentions, so that the author was able to make an informed decision to decline that help. From the very limited information presented, it's not clear to me why the author would judge this offer to be a selfish act, or why this anecdote would support his conclusion to "beware offers of help".
- pengaru 4y agoSuch projects have phases of development. If too many people get involved too early, you easily create a "too many cooks in the kitchen" situation. But once the long-term architecture is largely defined and implemented, there's usually enough inertia and established compartmentalization of modules that more developers can participate without ruining the soup.
- paulcole 4y agoDon’t you also have to be a little bit narcissistic to say, “You can help build this thing but only as long as you adhere to my vision.”
- internetter 4y agoNo? They're not forcing, or even encouraging, people to help them. People just... Want to. It's not narcissistic to say "Oh... Well I was planning to work on this myself, you can help if you want, but I have my own vision that I don't want to diverge from"
- fsckboy 4y agoit's not narcissistic to say "You can help build this thing but only as long as you adhere to this vision.” it would be narcissistic to say "...and this vision is MY vision, nobody else has a vision like mine" which I don't hear the author saying
- qingcharles 4y agoNow I want to see the unnamed social network.
- dankwizard 4y agoOP created wt.social
- account42 4y ago> The non-toxic social network The tone of TFA doesn't make that likely. > Welcome to a place where advertisers don’t call the shots. > Where your data isn’t packaged up and sold. > Where you – not algorithms – decide what you see. > Where you can directly edit misleading content. Sounds pretty bad. > Where bad actors are kicked out and kept out. Strong echo chamber vibes. > Where you actually like spending time. > Welcome to social media the way it should be. > Welcome to WT.Social. > Register [to even be able to see any of it at all] Yeah I can see why this would not catch on.
- anarchogeek 4y agoThis is terrible anti-social advice. Getting projects to work is about organizing people to work together. Unless your DJB, software is a team sport. If it is a one person project it will fail. Now when somebody offers to help, be welcoming because it's amazing. But also remember that most of the time their desire to help won't translate in to something useful. That's ok, eventually people will show up who are helpful. Keep being open. Also, what the hell is somebody doing making a social network if they don't like people.... WTF!?
- antoineMoPa 4y agoLooks like we don't have any evidence of success of this project. Having other people help your project might be bad for your ego, but it's also a great way to grow as a developer.
- nailer 4y agoI think the way engineers help open source projects is to send a PR. ‘Offering to help’ without contributing anything seems somewhat suspicious.
- account42 4y agoOn the contrary, the right way is to ask first before making large changes that might not even be wanted. For obvious fixes sure, shoot first. For anything more complex it is inconsiderate to put the maintainer into a position where they have to choose between comprimising their project or hurting your feelings.
- nailer 4y agoOh definitely, don’t send a large change as a first PR. We are in agreement there.
- calcsam 4y agoOr OP could post it on GitHub with integration tests around eg memory footprint. There’s a mindset shift between “senior engineer” and “tech lead” that OP seems to be struggling with…
- GVIrish 4y agoI think the author is taking a bit of the wrong lesson from his experience. One of the challenges of coordinating a group of people is getting everyone to buy into the same vision. Fact is that other people see the world differently and may have different goals. Here the author is attributing that to narcissism and maliciousness when most of the time it isn't that. So yes, as you add more people it gets more challenging to get everyone rowing in the same direction. This is why setting a clear direction and clear communication is key, but the increase in communication overhead as the team grows is always going to be difficult. In this case, as others have said, he could've just open-sourced his code so the people who had a different idea were free to run with it.
- asdfman123 4y agoYou don’t have to learn and grow if other people are Bad
- alextalks 4y agoJust a tip: don't forget the nearly 50-year old book The Mythical Man-Month. It may have some lessons!
- omoikane 4y agoDefinitely read Mythical Man-Month, which describes how adding more people may delay a project due to communication overhead ("why did the Tower of Babel fail?"). I was thinking this article would be an example of that, but actually while Mythical Man-Month mostly assumes that new team members would share the same visions and goals, this article takes a more adversarial view where new team members are assumed to come with their own agenda. I believe it's a form of cookie licking[1]. [1] https://devblogs.microsoft.com/oldnewthing/20091201-00/?p=15843 https://devblogs.microsoft.com/oldnewthing/20091201-00/?p=15...
- asdfman123 4y agoIt’s not narcissism. Don’t use terms you’ve researched on Wikipedia to diagnose other people. If that’s narcissism, then what’s creating a project that is the unique extension of your own values? I’ll answer: both are legitimate ways to approach the world, that may involve an acceptable and perhaps at times level of selfishness. Sometimes things don’t work with other people because you don’t see things the same way. They are not Wrong and Bad.
- satisfice 4y agoI like that I can scan down the comments on HN and usually find one that says what I wanted to say. Damn straight. It's not narcissism to have ideas and be excited about them and to suggest that a team or a founder pursue those ideas, whether or not that jibes with someone else's original vision. The OP doesn't tell us what the reaction was of the person who offered him help, when he re-explained his vision. Was the reaction something like "oh, okay, I didn't realize you felt so strongly about that?" Was it "I'm a narcissist and I don't care what you want?" I think the OP might be a little insecure about negotiating with other people-- which is fine-- but what not fine is to turn that into universal advice for other people about not talking to strangers.
- asdfman123 4y agoI read it clearly as someone who does not want to work with other people and deal with their bs. That’s fine, I get it. But at least be mature about that and own it. There’s a reason why there’s a profession in software—management—that often exclusively involves dealing with other people. In fact, good management is critical to the success of any large project. But it’s not an easy job.
- jasmer 4y agoThis is literally why git exists. I wouldn't say 'beware', rather, just say 'fork it and have fun'. Obviously you have to be a bit selective over who can contribute to a small project.
- 1lint 4y agoAnyone have a link to the post the author referenced here? "A couple of weeks ago, someone else <posted> his desire to help code Xnet, and he included his vision of the direction it should go" (emphasis added) The way this story was presented makes me curious to see the dialog (if there was any) between the author and the guy who offered to help.
- rob74 4y ago> Something I have noticed is that the more people join a project, the more it begins to go off the rails, and the less productive each member of the team becomes. [...] many of the newcomers spend the bulk of their time, if not actually sabotaging the project, doing the next best thing. They do their best to drive the project in the wrong direction. In so doing, they waste the valuable time of everyone around them who is forced to clean up the messes they leave behind. These are intelligent people, so I do not believe they are incapable of understanding the vision that caused the project to be born. I think, rather, they just don't care. Some call this "not being a team player", but I call it narcissism. Er... reading this, I would rather suspect the author of "not being a team player". Of course, if other developers find your project interesting and want to contribute, they may have their own features and use cases in mind that don't necessarily overlap with what you have planned, which doesn't however mean that it has to be a "wrong direction". As the owner of the project, you are free to accept their contributions or not, and they are free to fork the project and take it into another direction if you don't like that direction.
- atoav 4y agoI agree that this passage says more about the author than about any fundamental law of organization. It is true however that there is more organizational overhead if you have two people working on a thing than if you have one doing it solo. But that is a problem that can be solved, e.g. by dividing responsibilities very clearly or by having clearly defined procedures that guarantee a decent handover. I have also experienced people that do better, more accurate and resonable work when they work together with someone else, because they will anticipate the other seeing their code. The quoted passage tells me one thing: If you invite people to work on your project, no matter if it is a film, a garden party or a software product, the right casting is crucial. Don't invite people that won't understand the thing you're doing, and if you absolutely have to make sure there is something in it for them when they do their own job well and see your thing succeeding — but the crucial thing is, you should always know what is in it for the other person. As someone who has been on a number of amateur film sets where nobody got paid the ones that really sucked where the ones where the initiator treated everybody like dumb paid labour that should just do as they were told, pushing people that might have cared into actively sabotaging the project. If you want people to care about your project it is your task to find people who do and it is your task to keep them there, if they are needed for the project. And very often that means not doing it 100% dictator-style, but letting people play and evolve within their own domain. From what I have seen the results of allowing this outshine micromanaging dictators nearly all of the times.
- bestest 4y agoNow I'm going to be the one and say that this was written by an AI. Because it doesn't make any sense at all.
- ozim 4y agoWhen it comes to new employees he is right. We just have one that is quitting. Guy is smart of course but he could not understand refactoring all code he touches is not what we hired him for. If you make 10-20 pages long PR with spelling corrections or renaming variables where functionality company asked you for is 5% then problem is you not understanding there will be 2 or more developers having to read that.
- phendrenad2 3y agoWow, good job! Most places I've worked that guy gets promoted for being "so productive".
- bawolff 4y agoThe mythical man-month is just as true (or even more true) of open source than closed. Just because something is open source doesn't mean it has to be a free for all.
- RheingoldRiver 4y agoAs a maintainer (and product owner/pm) of OSS, I somewhat disagree with the OP. Beware of your over-attachment to a project that others are willing to contribute their ideas, time, and energy to. You are not an oracle; nor are you the only user of your product. Other people have better ideas than you do sometimes, especially when they're your users. Give them latitude to take the project in ways you disagree with, even vehemently. Your project will be better for it, and you'll learn something along the way.
- mellosouls 4y agoBlinkered and badly-written take on Open Source, and - to a larger extent - team work in general. Obviously there are potentially problems with any development model but if you don't have the skill or motivation to be a maintainer in the open or work in good faith without ego within a team, that's cool - but maybe don't assume everybody has the same limitations as you in that regard.
- lofaszvanitt 4y agoEveryone cares about himself and everyone wants the limelight for himself. Divide and rule works perfectly in an egocentered environment. Especially for the work for free, beg for money, fork for yourself os ecosystem.
- mrtweetyhack 4y ago[dead]
- caporaltito 4y agoTru dat.
- gtirloni 4y agoNot much wisdom from this article besides "keep other out, they don't understand your vision".
- 0dayz 4y agoI'll admit I was going into this thinking it was a warning against some kind of hostile takeover ig said project. Instead it just reminded me of yanderedevs excuse of not allowing tiny build help him finish yandere simulator, which was very similar to this.
- jasoneckert 4y agoIn this case, the help offered didn't align to the project owner's vision and wasn't accepted as a result. However, that doesn't mean that offers of help should always be ignored - they can often lead to improvements, opportunities, and welcome collaborations.
- graderjs 4y agoThe GitHub block function, your friend, is.
- osigurdson 4y agoLinus was able to do it. We all benefit from the fact that Linus is a jerk that knows what he is doing and cares about the result.
- jdthedisciple 4y agoI've been finding myself less and less inclined to read semi-long articles so here is Kagi's summary: The author warns against accepting help from people who are not genuinely interested in helping further the goals of a project. While the offers may seem helpful, these people often waste time driving the project in the wrong direction to suit their own goals. They do not care about the original vision of the project, but instead want the project owner to help them. This was evident when someone offered to help scale up the author's social network, Xnet, without understanding that the author's goals were the opposite - to prove a social network can run on a tiny, low-power server. While scaling up Xnet may have been fun, it was not the purpose of the project. Therefore, the author advises to be wary of offers of "help" and sometimes it is best to do the project yourself.
- sharkbird2 4y agoThe author claims that people's offering of help is not true help since it's for selfish reasons. I would like to argue that this is natural and necessary to some extent. People are motivated by what benefits them personally. All your relationships, pretty much everything you do, has a selfish aspect to it. You're not in a relationship with someone because you're being kind towards them, you're in a relationship because it benefits you, and hopefully it's mutually beneficial. So, you need to let people be just a little bit selfish, because you need them to be motivated. Without people working for the sake of personal motivation, open source wouldn't work.
- AbrahamParangi 4y agoSort of off topic but I’ve noticed that when push comes to shove a lot of people are very resistant to the notion that the road to hell is paved with good intentions. The implication being: just because you have good intentions, or because you feel the positivity in your heart, doesn’t mean you’re actually doing good. “But surely”, we all think, “that applies to other people, not me. I would know.”
- projektfu 4y agoI think this is why I often push help offers away in other things. If someone wants to help, they may be more experienced and willing to teach. That'd be great. If I was doing an electronics project and an EE found the idea interesting and wanted to help me get it done, fantastic. I'm not trained in that. However, for many things either I have an idiosyncratic way of doing things or the offer comes from someone who needs me to teach them a lot to meaningfully help. My business bookkeeping is one of those things. Teaching people to do it is stressful and painful, and then I have to worry about the mistakes they make, as opposed to the ones I make. This author adds a third case, where your project inspires them but they want to take some ownership of the design. Either they don't understand your idiosyncratic approach or they are more comfortable with their own patterns. However, it will be clear that there will be a lot of friction and that's bad for friendships. I think there's an implicit fourth case, where the offer is coming from a person who doesn't really know how to help but wants to get involved in something they think is cool. These are the people who mix up their terminology in their rants on your forum about how your working software could be much better done. Finally, there's the people you enjoy teaching, where it's rewarding to include them in your journey. Maybe it's good to consider that possibility from time to time.
- costco 3y agoI think the author is a little cynical. As someone with a handful of small open source projects, I know exactly what he is talking about but I wouldn't say it's driven by narcissism. It's mostly just people new to programming trying to contribute and usually learn something through the process of contributing. You can always just tell them they are free to fork your project, this may offend them but if you do it politely and explain that you do not feel like investing that much time in the project or that their changes are too complicated then they will understand.
- phendrenad2 3y agoIf you have a vision, and you make something noteworthy, people will show up with different visions, and try to take your project in a different direction. This happens when you found a company. The most dangerous employee to the life of the company is employee #2. This is why YCombinator doesn't like solo founders, and wants a more stable two-person team with a shared vision for the company. The third employee you hire is much less dangerous because they can be overruled by the majority (without even threatening to fire them). Also note that wasn't an open-source project, so there's always the threat that someone will steal your code and your hard work. Don't allow someone to see your code unless you're ready to open-source it, or you have enough money to pay for a lawyer if the person steals your code. (I know the concept of software ownership is anathema to most of the HN crowd, but hopefully this makes it through the downvoters to reach its intended lurker audience).