6 ms·
Ask HN: What habits have help you succeed as a programmer?
- onion2k 9y agoI made a conscious choice to write 'non work' code every day. It's now a habit (thanks largely to Github's contributions graph... I've got to get a little green square every day!). Sometimes it's just 5 minutes to refactor something or update a README, sometimes it's 5 hours to work on a project, but the result is the same - I spend more time writing code. This has introduced me to frameworks, libraries, patterns and algorithms that I wouldn't have been exposed to otherwise, and it's definitely making me a better developer.
- godelmachine 9y agoThat's very good :)
- naru_s 9y agoLove to try this in 2018!
- craftyguy 9y agoWhy wait until 2018? Start right now.
- mithras 9y agoGood on you, but I'm afraid that's not going to work for me with two small kids running around.
- segmondy 9y ago5-10 minutes a day?
- onion2k 9y agoA friend of mine in a similar situation is making a game with his kid - he writes code while his child is drawing sprites. They collaborate on the game mechanics, testing, etc. That works for him and (he says) it's quality time that's loads of fun. Maybe you could include your kids?
- jlengrand 9y agoThere is always time. Though I admit that with the baby now I have to get more creative. But they do have to sleep at some point don't they? :P
- nukeop 9y ago1: Keep everything as simple as possible. 2: Keep your toolchain and build process independent from the operating system and editors. 3: Don't use IDEs. 4: Have a one command automated build and run as soon as you write a basic skeleton of your project.
- axvk 9y agoWhat do you have against IDEs and what languages do you mainly write in?
- Teichopsia 9y agoNot the OP. When I started out I took a conscious decision to stay away from IDE'S. an IDE adds complexity when the main goal should be to learn to program. An IDE has a bunch of features you need to learn and understand when learning to program by itself is hard enough.
- deleted 9y ago[deleted]
- cc81 9y agoWhat language did you use?
- Teichopsia 9y agoPython.
- fiftyacorn 9y agoDelivering to your deadlines and estimates as much as possible
- EliRivers 9y agoCode without ego. You are not your code, and your code is probably not very good.
- acutesoftware 9y agoas well as the comments below, I would add 1. Get a visual prototype going as early as possible - even if its screen mockups. Your interpretation of what the client wants and what they tell you they want are often completely different, and many times they don't really know at all. Once they can see something, then requirements get a lot better. 2. Once you have a better idea on what you will be building, work out in your head how you will build it. Think about all the parts and do the bits that you haven't done before, or don't know how to do and build them FIRST. This will avoid showstoppers down the road - you may not be experienced enough to know if it's something you can't / shouldn't do, or if extra help / libraries are needed to complete the job. So once you have a clear idea on what you are building, and have done test functions to do the hard bits - then it's time to turn on the music and build the rest.
- navyad 9y agoreading code.
- tboyd47 9y agoDon't commit to anything you haven't already verified is possible
- kleer001 9y agoRead other people's working code. Figure out what they're doing and why and why you like or dislike it. Add their unique qualities to your own repertoire.