3 ms·
I've found that diving into a project and figuring out what needs to be done is the best way to get going specially if the project has zero chance of causing da
by WheelsAtLarge 3y ago
I've found that diving into a project and figuring out what needs to be done is the best way to get going specially if the project has zero chance of causing damage. Writing a text editor seems live a doable even if you decide to write it in assembler. You need to pick a project, break it down to pieces you can handle and go for it. Your job is to pick a task and decide and learn how to accomplish it. Keep in mind that you need to finish so add a deadline and be consistent. Do not fall into the trap that you can take forever to finish. If you do that,you will fail. Pick a project, copy it if you need to, and start. Keep it simple and add complexity as you move forward. So start and pick a deadline today. Stop thinking about it.
- jwindle47 3y agoYou're right. I think my biggest problem is that I always assume these crazy OSS projects were written because the author has always been this programming genius, when in reality they were just following their interests. For example, I caught myself with the proxy thinking about production scale. Who cares about production?? I just need to get going and build a single-threaded proxy that gets the job done. No need to worry about complexity, it's just for me. Hard to remember that at times though.