Skip to content

Instantly share code, notes, and snippets.

there is more to life than coding

Ashish Dixit tundal45

there is more to life than coding
View GitHub Profile

I think you might benefit from a detailed study plan when you're a little further along with your studies. For now, I'd recommend following your interests, and taking a project-based approach towards learning.

Start with an idea of something you might want to build, and then make a list of all the stuff you'd need to learn to build it. Then, strip down the idea to make it a little more simple, and redo the list. Keep doing that until you have a list that's small enough to manage

Fair warning: full-scale applications tend to look like "first invent the whole world, then build your app", so you may need to come up with really simple ideas to start on. That's OK! You may also not know what you need to know until you try building things, that's OK too.

Once you have a few ideas, start reading and watching videos related to the technical tools and concepts you need. But only go just as deep into those resources as you need in order to build one small piece of a real project... you can always come back later i


Keep reading and watching videos, but cut that time down in half and use the rest of the time for exploring codebases and writing code of your own. If you do a code reading exercise, make sure you have the code open in your editor, and that you're able to interact with it via a REPL, its tests, etc.

Then from there, I'd recommend starting with very small, tiny projects. Ideally your first one should be something so simple you can do it in an hour or two.

Gradually work your way up from those tiny projects to slightly bigger ones. So start with one that takes an hour or two, then move up to one that might take 5-10 hours, then one that might take 20 hours, then 40 hours, etc. It's OK to stop at the size where you're feeling you're getting the most learning benefit.

Each time you try a new project, make it realistic if you can, but don't worry too much if you'll actually use it. The value is in having a rich context to try out ideas, not in the actual utility of whatever you build.

For each project you wor

# Grab a random gif from
# Example:
# $ gif // places a gif url on your clipboard
# $ gif -o // opens a gif url in your default browser
# $ gif chicago+bulls // places a Bulls-related gif url on your clipboard
# $ gif chicago+bulls -o // opens a Bulls-related gif url in your default browser
javan / application_controller.rb
Created Nov 30, 2013
Prevent cross-origin js requests
View application_controller.rb
class ApplicationController < ActionController::Base
before_filter :ensure_xhr
def ensure_xhr
if request.get? && request.format && (request.format.js? || request.format.json?)
head :forbidden unless request.xhr?
lsegal /
Created Nov 8, 2013
Some of my favourite research papers in formal methods & static analysis
niw / rubygems_server.rb
Created Oct 29, 2013
Running rubygems server on localhost.
View rubygems_server.rb
#!/usr/bin/env ruby
require 'webrick'
require 'rubygems'
require 'rubygems/gem_runner'
require 'rubygems/exceptions'
REPOSITORY_ROOT = File.expand_path("../", __FILE__)
# Update index
trptcolin / mavericks_upgrade
Created Oct 23, 2013
mavericks upgrade journal
View mavericks_upgrade
√ Zephyros (window manager) needs universal access:
√ gcc can’t find stdio.h (& similar) - /usr/include got blown away
xcode-select --install
√ java install got blown away & replaced with a stub that says to download java
View .vimrc
" project specific vimrcs
set exrc
set secure
sheedy /
Last active Dec 25, 2015
A list of "living" Style Guides

Style Guides

Add any links you want in this to the comments and I'll add them.



Generates styleguides from Markdown comments in CSS, SASS and LESS files using Handlebars