3 ms·
Not in any order: Learn to do more than just write software. In fact, learning how to minimize source code is a good start (really source code is bad like cros
by ericHosick 15y ago
Not in any order:
Learn to do more than just write software. In fact, learning how to minimize source code is a good start (really source code is bad like crossing streams bad).
Learn how to read and leverage off of existing, hopefully open source, resources.
Learn how to design away problems instead of coding a solution for them.
Learn to keep things simple.
Learn to design/mockup and get feedback (UX, etc.) on your solutions before coding them.
Did I mention the try not to write code part?
- yijinsei 15y agoEmm... but why not write codes? I think, for example, code down algorithm is both good to understand the practical side of comp sci as well as a better way to remember algorithm.
- ericHosick 15y agoEvery time you write code you have to/should: Define requirements for it, define tests for it, continually run regression tests, design it, implement it, debug it, peer review it, etc. All of this is done to solve some problem in a specific domain. That is a lot of work when all you want to do is add some small feature to your overall software solution. In software development communities, people are now able to pull from the works of others and build on it. Let's take the Rails community as an example. Many of the features I need in a software program have already been written and available for me. I need an SMS system? Done for me already. User authentication? Done. Persistence? Done. One way of becoming a good software developer is to become better at taking existing solutions and integrating them into your final software solution. This should involve as little source code as possible.