blocks|key|541299|text|几乎任何开发方法都可以在单独的环境中工作，除了那些明确需要团队的开发方法(例如并行编程)。但即便如此，你也可以通过建立一些想象中的朋友/队友或发展成多重人格障碍来绕过这一问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|541300|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Just about any development methodology will work in a solo environment except for those that explicitly require a team (such as side-by-side programming). But even then you could get around that by just creating some imaginary friends/teammates or developing a multiple personality disorder.

blocks|key|2454064|text|即使作为一个单独的开发人员，您也可以使用适用于大型开发团队的方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2454065|2454066|编写规范。|unordered-list-item|2454067|布局UML.|2454068|进行纸笔UI+design.|2454069|Hallway测试:如果您预计会有很多人，请询问妈妈它是否易于使用。|2454070|同行评审:您可以与其他个人和最新的代码建立特别评审团队，依此类推...|2454071|<>F215>|2454072|我一直在独立开发，这些实践使我与自己的工作保持一致，并为我的老板提供了一个很好的资源，让他们知道我做了什么以及我已经走了多远。他们让我一直走在正轨上！|2454073|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|X|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|Y|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|Z|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|10|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|11|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|S|$]]

Even as a solo developer you can use methodologies applied to large development teams.

<ul>
<li>Write a Spec.</li>
<li>Layout a UML.</li>
<li>Do pencil-and-paper UI design.</li>
<li>Hallway testing: If your expect a large crowd, ask Mom if it's easy to use.</li>
<li>Peer review: You can build ad-hoc review teams with other solo developers.</li>
<li>Keep an up to date schedule.</li>
<li>and so on...</li>
</ul>

I solo develop all the time, and these practices keep me in line with my own work and give my bosses a great resource to know what I've done and how far along I am. And they keep me on track, to boot!

blocks|key|3678003|text|脑海中浮现出橡皮鸭方法论：http://lists.ethernal.org/oldarchives/cantlug-0211/msg00174.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3678004|entityMap|0|LINK|mutability|MUTABLE|url|http://lists.ethernal.org/oldarchives/cantlug-0211/msg00174.html^0|D|1S|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

The rubber duck methodology comes to mind:
<a href="http://lists.ethernal.org/oldarchives/cantlug-0211/msg00174.html" rel="noreferrer">http://lists.ethernal.org/oldarchives/cantlug-0211/msg00174.html</a>

blocks|key|541398|text|许多敏捷技术单独工作效果很好：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|541399|541400|User访谈和故事:如果你不知道你的用户想要什么，为什么你的软件是useful?|unordered-list-item|offset|length|style|BOLD|541401|A+simple+spec：，或者仅仅是一个使命宣言。“让人们向他们的订户列表广播短消息。”“使用in-degree对internet搜索结果排序。”“让人们协作回答编程问题。”Whatever.|541402|A严格有序的待办事项列表:帮助您避免淹没在thoughts.|541403|Tangents日志中:一个好的待办事项列表有一个“待办事项”部分，这样您就不会纠结于您不打算做的事情，并保持在目标上。当您独自工作时，这一点非常重要，因为没有人会告诉您“不！不要在Java中重新发明动态类型！回到项目中去吧。”注意事项清单对this.|541404|Test-driven开发的帮助：编写测试迫使您考虑最终结果，而不是陷入实现细节的泥潭。无论如何，你都会陷入足够的泥潭；不需要让它发布：让你自己坚持到最后期限。“到周五，我们将有一个功能完整的版本，其中包括用户故事1-4。它不会连接到网络，也不会将数据保存到磁盘上，但XYZ..."|541405|User测试：会让你的朋友定期查看你在做什么--可能是每月一次，也可能是每周一次，这取决于你有多少朋友以及你想喂他们多少啤酒/披萨。”在使用软件时，密切关注他们所说的、所做的和所想的。|541406|541407|而其他看起来只在大项目中有意义的事情可能会有很大帮助：|541408|git控件：+Install+git。这很简单。使用它。不要纠结于it.|541409|Off-site备份：Y‘’know。如果发生房屋火灾或floods.|541410|
|541411|A博客：，但只有在发布时才允许在那里写。;)还可以帮助您在产品发货前为其建立受众。|541412|541413|希望这能有所帮助！在大型项目中单独编程可能非常令人望而生畏。|541414|entityMap^0|0|0|0|14|0|0|2Q|0|0|U|0|0|3I|0|0|3X|0|0|2K|0|0|0|R|0|0|6|0|0|B|0|0|0|4|0|0|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1B|8|@$F|1C|G|1D|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|1E|8|@$F|1F|G|1G|H|I]]|9|@]|A|$]]|$1|L|3|M|5|E|7|1H|8|@$F|1I|G|1J|H|I]]|9|@]|A|$]]|$1|N|3|O|5|E|7|1K|8|@$F|1L|G|1M|H|I]]|9|@]|A|$]]|$1|P|3|Q|5|E|7|1N|8|@$F|1O|G|1P|H|I]]|9|@]|A|$]]|$1|R|3|S|5|E|7|1Q|8|@$F|1R|G|1S|H|I]]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1U|8|@$F|1V|G|1W|H|I]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1X|8|@$F|1Y|G|1Z|H|I]]|9|@]|A|$]]|$1|Y|3|Z|5|E|7|20|8|@$F|21|G|22|H|I]]|9|@]|A|$]]|$1|10|3|11|5|6|7|23|8|@]|9|@]|A|$]]|$1|12|3|13|5|E|7|24|8|@$F|25|G|26|H|I]]|9|@]|A|$]]|$1|14|3|-4|5|6|7|27|8|@]|9|@]|A|$]]|$1|15|3|16|5|6|7|28|8|@]|9|@]|A|$]]|$1|17|3|-4|5|6|7|29|8|@]|9|@]|A|$]]]|18|$]]

Many agile techniques work great solo:

<ul>
<li>User interviews and stories: If you don't know what your users want, why would your software be useful?</li>
<li>A simple spec: Or even just be a mission statement. "Let people broadcast short messages to their subscriber lists." "Use in-degree to sort internet search results." "Let people collaboratively answer programming questions." Whatever.</li>
<li>A strictly-ordered todo list: Helpful to keep you from drowning in thoughts.</li>
<li>Tangents log: A good to-do list has a "to-don't" component, so you don't obsess over things you aren't going to do (yet).</li>
<li>YAGNI: Stay on target. This is very important when working by yourself, because no one is there to tell you "No! Don't reinvent dynamic typing in Java! Get back to the project." To-don't lists help with this.</li>
<li>Test-driven development: Writing tests forces you to think about the end result, rather than getting bogged down in implementation details. You'll get bogged down enough anyway; no need to make it worse.</li>
<li>Frequent releases: Make yourself stick to deadlines. "We'll have a feature-complete version that includes user stories 1-4 by Friday. It won't connect to the network or save data to disk, but XYZ..."</li>
<li>User testing: Have your buddies look at what you're making on a decently frequent schedule -- maybe once a month, maybe every week, depending on how many friends you have and how much beer/pizza you want to feed them. Pay very close attention to what they say and do and think when using the software.</li>
</ul>

And other things that only seem like they make sense in big projects can help a lot:

<ul>
<li>Source control: Install git. It's bone simple. Use it. Don't obsess over it.</li>
<li>Off-site backups: Y'know. In case of house fires or floods.</li>
<li>A blog: But you're only allowed to write there when a release comes out. ;) Also helps you build an audience for your product before it even ships.</li>
</ul>

Hope this helps! Solo programming on a large project can be very daunting.

blocks|key|549898|text|按照此堆栈溢出问题中的说明进行操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|549899|549900|+What+Tools/Techniques+can+benefit+a+solo+developer?|blockquote|offset|length|549901|549902|549903|还有。使用源代码管理。你不会相信我有多少次在个人项目上被它咬了。|style|BOLD|549904|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/59561/what-tools-techniques-can-benefit-a-solo-developer^0|0|0|1|1F|0|0|0|0|3|7|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|X|8|@]|9|@$F|Y|G|Z|1|10]]|A|$]]|$1|H|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|13|8|@$F|14|G|15|L|M]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

Follow what is laid out in this Stack Overflow question:

<blockquote>
 <a href="https://stackoverflow.com/questions/59561/what-tools-techniques-can-benefit-a-solo-developer">What Tools/Techniques can benefit a solo developer?</a>
</blockquote>

Also. Use Source Control. You wouldn't believe how many times I've been bitten by that on personal projects.

blocks|key|2454153|text|这是这样的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2454154|http://en.wikipedia.org/wiki/Personal_Software_Process|offset|length|2454155|可能是杀伤力太强了|2454156|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1I|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

There's this: 

<a href="http://en.wikipedia.org/wiki/Personal_Software_Process" rel="nofollow noreferrer">http://en.wikipedia.org/wiki/Personal_Software_Process</a>

It's probably overkill

blocks|key|3678044|text|问题更多的是你对什么感到满意，以及你希望解决什么问题。大多数方法都是由单人开发人员在某些时候使用的(结对编程是一个值得注意的例外)。问题是你实际上是一个人，还是一个人在工作？我发现，有一些人可以让我从他们那里获得灵感，这是非常宝贵的。此外，让别人看你的代码(同行评审)是发现你不能“看到”的问题的好方法。所以同意Aiden+Bell所说的“在你的oen上编程是不酷的”。我会尝试连接到一个社区(就像这样)，在那里你可以从别人那里学到一些想法。然后，你需要以这样一种方式构建你的方法，当你发出一个想法时，允许中断。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3678045|这有意义吗？为什么你一个人编程？|3678046|Pat+O|3678047|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The issue is more a question of what you are comfortable with and what problems you hope to solve. Most methodologies are used by a solo developer at some point (pair programming is a notable exception). The issue is are you actually alone, or just working by yourself? I have found that it is invaluable to have people I can bounce ideas off of. Furthermore having someone else to look at you code (peer review) is a great way to find issues that you just cannot "see". So to agree with Aiden Bell "Programming on your oen is uncool."
I would try and connect to a community (like SO) where you can bounce ideas off of others. Then you need to build your methodology in such a way as to allow for interruptions when you send an idea out.

Does that make sense? Why are you programming alone?

Pat O

blocks|key|5791328|text|不是真正的官方方法，但我做了很多单独的开发(独立顾问和ISV)，下面是我发现的重要事情：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5791329|5791330|找到一个在线组织(如oisv.com)来分享想法和想法|unordered-list-item|offset|length|5791331|确保您花时间与现实世界中的实际人员互动|5791332|设置项目目标、截止日期和时间来做适当的前期设计和项目规划|5791333|留出的工作时间是坚持下去<代码>H211<代码>H112不要工作太多而过度劳累<代码>H213<代码>H114没有什么是十全十美的，所以努力编写可以工作的好代码，而不是perfection|5791334|Get一些非编程爱好<代码>H217<代码>F218|5791335|5791336|entityMap|0|LINK|mutability|MUTABLE|url|http://www.oisv.com/^0|0|0|A|8|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|10|8|@]|9|@$F|11|G|12|1|13]]|A|$]]|$1|H|3|I|5|E|7|14|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|15|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|16|8|@]|9|@]|A|$]]|$1|N|3|O|5|E|7|17|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

Not really an official methodology, but I have done a lot of solo development (independent consultant and ISV), and here are the things I have found to be important:

<ul>
<li>Find an online organization (like
<a href="http://www.oisv.com" rel="nofollow noreferrer">oisv.com</a>) to share thoughts and
ideas</li>
<li>Make sure you take time to interact
with actual people in the real world</li>
<li>Set project goals, deadlines, and
milestones</li>
<li>Take time to do appropriate up-front
design and project planning</li>
<li>Set aside working hours are stick to
them</li>
<li>Don't work too much and burn yourself
out</li>
<li>Nothing is ever perfect, so strive
for good code that works, not
perfection</li>
<li>Get some non-programming hobbies</li>
</ul>

blocks|key|3678198|text|这与其说是一种方法，不如说是一种技巧。当你在调试的时候，向自己大声解释错误，就像你试图向同事解释一样。这感觉很愚蠢，但强迫自己大声说出问题往往会揭示出问题所在。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3678199|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This is more of trick than a methodology. When you're debugging, explain the bugs out loud to yourself as though you were trying to explain it to a co-worker. It feels silly, but forcing yourself to articulate the problem out loud often reveals what the problem is.

What are some solo developer programming methodologies for smaller projects?

What are some solo developer programming methodologies?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

对于较小的项目，一些单独的开发人员编程方法是什么？

问一些单独开发人员的编程方法是什么？
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问一些单独开发人员的编程方法是什么？EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问一些单独开发人员的编程方法是什么？
EN