7

Always Stick to One Task at a Time

Whenever I’m trying to learn how to do new stuff, or if I have a project where I’d have to figure out how to do a lot of things, I try to just pick a particular task and attack that.

Often times in programming, you’ll hold a lot of context in your head depending on what you’re working on, so it’s best to focus on one thing and try to get it done. There are a lot of ways you can tackle a single problem, so a lot of things will depend on what solution you end up choosing. For example, if you’re trying to build a CMS website that build websites where it will deploy things to each user, you could organize a site where it’s a big giant app where everyone has a specific subdomain, or you can make it so that each individual subdomain is a separate instance of your app with configuration changes. There are pros and cons to each approach, so this is where the judgment comes in and why some people say programming is an art, since you constantly have to weigh different tradeoffs.

Comments
  • 1
    "Top down" Vs " Bottom up" have their pros and cons. I like to start at the component level, it takes ages to work out what a "component" actually is. My first step is usually to define the components first then work out implementation details. I have yet to see a universal definition of component. IMHO, there isn't one as it is project specific.
Add Comment