...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Child pages (Children Display) |
---|
Table of contents
Table of Contents |
---|
Child pages
Child pages (Children Display) |
---|
Related pages
- Being Productive / Time Management / Fighting Procrastination
- Games in which you program ← The idea here is to use these games to figure out how to program more quickly.
- Beginner Programming Resources (Programming)
...
- Rest / breaks
- Get enough sleep.
- This is just like when I was taking the LSAT.
- Mike Krieger talks about this.
- Take naps if you're feeling tired.
- Bryton also brought this up; he doesn't try to work when he's tired.
- If you slept well, try to start coding as soon as you wake up in the morning, before you do anything else.
- Reason: I find that I'm "freshest" as soon as I wake up, and that if I delay in starting to code, I can end up procrastinating for hours.
- Get enough sleep.
- Equipment
- Have your monitors oriented vertically.
- Rec'd by Andy.
- Use multiple monitors.
- Andy used two.
- Have your monitors oriented vertically.
- Get psyched up / motivated / set the mood
- Videos that I've watched that have gotten me psyched up to start coding
- Put on some good music
- Notch
- Search Google for 'site:https://twitter.com/notch/status/ music'
- He apparently has a soundcloud account where he (at least) posts clips of songs he's created, but a quick search on Google didn't lead me to it.
- Songs I know for sure he was listening to while coding:
- Boys Noize - Kontact Me - "This is the music I will listen to all day on repeat while I code"
- He doesn't explicitly say he was working while listening to these:
- µ-Ziq - Grape Nut Beats Pt.1 - "Too lazy to change playlist, but music not to listen to during a headache", "Oh wow, I totally forgot this wonderful piece of music exists"
- Kid606 - Ecstasy Motherfucker - "Too lazy to change playlist, but music not to listen to during a headache"
- Ventolin (the song by Aphex Twin?) - "Too lazy to change playlist, but music not to listen to during a headache"
- Autechre - Second Bad Vilbel - "Too lazy to change playlist, but music not to listen to during a headache"
- A custom song he created named 'calm4.ogg' - "[the song] wasn't made for the music [for Minecraft], it was just a test song I put in there to try the mp3 loading."
- DOG BLOOD - Next Order - "dog blood is amazing beyond words. The combination of Alex's old school and Sonny's crowd is incredible."
- IDM (Intelligent Dance Music?) - "I got into electronic music via IDM."
- Dense & Pika (artist) - "I'm a full-on Dense & Pika fanboy now. This is almost as intense as my Knife Party era."
- Knife Party (artist) - "I'm a full-on Dense & Pika fanboy now. This is almost as intense as my Knife Party era."
- Boards of Canada - Music Has the Right to Children (album) - "Music Has the Right to Children is a masterpiece that seems to get better for each passing year."
- Artists that were recommended to him:
- Pig & Dan, Nicole Moudaber, Kaiserdisco, Stephan Bodzin, Sasha Carassi, Paul Kalkbrenner, GoldFFinch, Eekkoo - "Into techno? Check out [...]"
- di.fm/electro
- Source: https://news.ycombinator.com/item?id=3811332 "He's listening to http://www.di.fm/, specifically the Electro House stream."
- Someone in the HN thread rec's the "A State of Trance" sets that you can d/l here (the red links): http://www.teamliquid.net/forum/general/316887-music-a-state-of-trance-550
- Source: https://news.ycombinator.com/item?id=3811332 "He's listening to http://www.di.fm/, specifically the Electro House stream."
- Pieter Levels
- YouTube - Panda Mix Show ← This is Pieter's previous project.
- YouTube - hurfyd - Pieter sub'd to this channel
- PlayMyInbox.com - Demo ← This is a list of songs from Pieter's inbox (Source)
- I forget which coder I saw post this on his twitter: https://soundcloud.com/benzi
- Zach Adams (random coder) - https://zach-adams.com/2014/05/music-to-listen-to-while-coding/
- Notch
- While coding
- Starting
- It's normal to feel overwhelmed by the size of the task in front of you
- "98% of dev is just pretending you're not overwhelmed with the massive amount of work left to do"
- Before starting on a task, set a limit on how much time you're willing to allocate to it
- Examples
- I wanted my flask app to autoreload when I made changes, but I didn't want to waste hours on it, so next to the task I wrote "10" (meaning "spend 10 minutes on this"), and then I wrote the actual time range I should use (ie "10:13 - 10:23"). I ended up finishing the task in under a minute, which was a pleasant surprise, but I think knowing about the limit I'd placed helped me to not waste any time.
- In one of the links below a guy describes how Notch cut a feature after spending 40 minutes on it because he realized it could end up taking up a lot more time. So he may not have thought of a time limit before he started on it, but he had some sense of the big picture.
- Examples
- Don't overthink it!
- It's normal to feel overwhelmed by the size of the task in front of you
- Coding-related
- Use keyboard shortcuts instead of the mouse
- http://luigimontanez.com/2010/mouseless-monday-1-vimium-google-chrome/
- Related page: Vimium
- Cody does this.
- Andy also does this.
- Yang also does this.
- Use keyboard shortcuts instead of the mouse
- Dealing with being stuck
- Debug efficiently.
- When asking for help, consider phrasing your question in this form: "I wanted to do X, so I wrote <some-code>. I expected to see Y when I ran this code, but instead I saw Z. What am I missing?" (Source)
1. What makes you say your code isn't working?
2. What did you expect your code to do and why?
3. What did your code do instead and how do you know?
- Listing And Testing (Hidden) Assumptions - most bugs are caused by the assumptions we didn't realize we were making, ranging from the forehead-slapping (e.g., "My code is free of typos") to the more fundamental (e.g., "I understand how this-or-that component works and I'm using it correctly.")
- When asking for help, consider phrasing your question in this form: "I wanted to do X, so I wrote <some-code>. I expected to see Y when I ran this code, but instead I saw Z. What am I missing?" (Source)
- Figure out what's making you feel confused, and attack that issue
- Examples
- 2015.12.06 - I was procrastinating for hours, staring at my screen, and then eventually I realized that what was holding me back was that I didn't have a clear folder structure for organizing my code, and so I wasn't sure where I should be putting my code. After a few minutes clearing up what the folder structure should be I was back in business.
- Examples
- Have a friend you can ask for help.
- Mark Zuckerberg
- Get the quote where he says he learned most of what he knows from his friends rather than from books.
- TypicalProgrammer
- He said something to me like "I always had someone more experienced to pull me out of the weeds."
John Collison (of Stripe)
- https://web.archive.org/web/20090819010430/http://transatlanticitinerant.wordpress.com/2007/07/
Yesterday I had a problem with Seaside linking to a stylesheet multiple times (don’t ask). After 15 minutes I gave up and decided to ask Patrick. He wasn’t on MSN and I was about to email him asking him to when I realised I prod him onto MSN a lot – the time I spend sending him emails to go on is an inefficiency. I decided to write a script to be able to poke members of the Auctomatic team from the command line. After 15 minutes of debugging (I could have sworn it was chomp that takes off trailing new newlines. Maybe I was just hungry) it was finally working and at my shell I simply had to enter:
$ poke p
Of course, emailing him would have just taken 10 seconds more so I’ll have to do a lot of poking before I can chalk this up as a saving
- https://web.archive.org/web/20090819010430/http://transatlanticitinerant.wordpress.com/2007/07/
- Mark Zuckerberg
- Debug efficiently.
- Don't waste time stressing about how little time you have left.
- This is surprisingly similar to when I was studying for the LSAT. I'm noticing the same feeling of "stay concentrated and try not to panic" that I had when I was doing LSAT sections.
- Starting
- Food / drink / drugs
- Eat high-quality food.
- This is just like when I was taking the LSAT: Protein (fish / chicken), carbs (broccoli / peas), and fat (cheese / almonds)
- Alcohol
- Mark Zuckerberg
- “9:48pm. I’m a little intoxicated, not gonna lie. (...) It’s taking a few tries to compile the script…another Beck’s is in order.“ (Source)
- http://www.nathanwailes.com/blog/alcohol-may-reduce-anxiety-while-programming/
- Another article mentions that he'd had a fight earlier that day with his girlfriend.
- “9:48pm. I’m a little intoxicated, not gonna lie. (...) It’s taking a few tries to compile the script…another Beck’s is in order.“ (Source)
- Mark Zuckerberg
- Caffeine
- Chung is a big advocate of espresso
- John Collison (of Stripe)
- "My attack on bugs and lameness in the app was fuelled by adrenaline and ridiculously strong coffee, tea and sugared Red Bull." (Source)
- Eat high-quality food.
Stuff I Learn While Going Through the USACO Puzzles:
- If you're having trouble with a certain task, see if you can break it into smaller pieces. This is one of the most useful things I've gotten practice with from these puzzles. It's kind of cliche advice, but if you're staring at something for half an hour and can't figure out how to get it working, you NEED to have the thought/motivation to try hard to break it up.
- If you're having trouble with a certain task, see if you can describe / write out how you would do it in the real world, without a computer. This helped when I was trying to write a function that would convert from base 10 to another base. If you get too bogged down in how to execute things in the programming language it can make it harder to brainstorm.
- Be OK with having your first version be ugly / sloppy. You can always go back over and smooth things over later. Trying to make everything perfect the first time around often makes it take LONGER to get to a great version.
- Don't get too sucked into a particular way of doing things if it's hard to execute. Be willing to look for easier methods. On one puzzle I had the idea that I could use a fancy way of doing things, but it was so hard to figure out how to execute my idea that I burnt out and stopped working on the problems for a month or two.
- It's extremely important to have a compiler set up so that you can quickly compile your code and see what happens. You should NOT try to figure out how to create the program without ever running your code. This held me up for literally 10 months with the USACO puzzles: I was having trouble learning all the C / C++ code necessary to do certain things so that I could create an entire program and hand it to the USACO website to compile, when I should have just been typing stuff up, handing it to my own compiler, and seeing what happened. I should have been starting with the most simple part of the puzzle and incrementally getting more complicated, just like that Stanford professor recommended in his Python class at Google.
Articles
- 2016.08.16 - Gamasutra - Programming principles from the early days of id Software
- 2011.03.19 - Robin Wilson - Want to write some code? Get away from your computer!
...
- https://sites.google.com/site/steveyegge2/practicing-programming
- https://danluu.com/programming-blogs/
- https://byorgey.wordpress.com/2009/01/12/abstraction-intuition-and-the-monad-tutorial-fallacy/
- https://github.com/tarmstrong/longcv/blob/master/bio.md
- http://blog.nullspace.io/ticket-to-ride.html
- https://danluu.com/learning-to-program/
Quora - How do programmers code quickly?
http://www.quora.com/How-do-programmers-code-quickly?share=1
Quote:Jesse Farmer:
- They know how to use their keyboards to do work. Keyboards are way faster than mice once you know how to use them. They're also more amenable to muscle memory. Are you clicking around to open new files? When I'm coding I barely touch my mouse.
- They are good typists. I probably type around 80 WPM on average and 100-120 WPM if I'm focusing on my typing, for example. Go practice! I like http://play.typeracer.com/ and https://typing.io/.
- They know how to use their tools, especially on the command-line. Ctrl+R for reverse search, Ctrl+A/E for beginning/end of lines, <Tab> for autocompleting filenames, etc. These become muscle memory after a point.
- They are very good at debugging and are likely to isolate, identify, and resolve a bug 100x quicker than a beginner. This isn't just because they "know more." Oftentimes they know just as much as you, but have a more disciplined approach to finding the source of unexpected problems.
- They have a better sense of where to look for information and aren't afraid to navigate through manpages or even source code to understand how some other system is behaving. If I'm having trouble with a poorly-documented Ruby gem, for example, I'll often look at the gem's source code to see if I can make sense of what's going wrong. I'd say 90% of the time this is quicker than Google.
Regarding debugging, I wrote a blog post (Teaching Novice Programmers How to Debug Their Code) that outlines how to teach people to be better debuggers.