in reply to Re: Time for an application portfolio
in thread Time for an application portfolio

There are a couple of advantages in putting my portfolio onto a website:

Alex / talexb / Toronto

Thanks PJ. We owe you so much. Groklaw -- RIP -- 2003 to 2013.

  • Comment on Re^2: Time for an application portfolio

Replies are listed 'Best First'.
Re^3: Time for an application portfolio
by Your Mother (Archbishop) on Jul 29, 2015 at 15:58 UTC

    Your reasons and approach are right on. You will get hired this way and be a better dev for the process. As you have found, deployment is often harder than development and begins to impose a healthy parsimony on both.

Re^3: Time for an application portfolio
by tangent (Parson) on Jul 29, 2015 at 16:22 UTC
    I'll gain the experience of how to get it running on a shared web host (I'm working on this now, and so far, it's not trivial).
    Do let us know how you get on - I also have shared hosting on Pair but was under the impression that you could not run persistent processes.

      I'll write more in a later post, but for now, it's just running as a regular CGI. :( This is probably the worst way to take advantage of Mojo; I'd love to run a long-running daemon instead, but that approach is almost certainly out of the question. :)

      Alex / talexb / Toronto

      Thanks PJ. We owe you so much. Groklaw -- RIP -- 2003 to 2013.

Re^3: Time for an application portfolio
by Anonymous Monk on Jul 29, 2015 at 15:36 UTC

    Well, if you ever need a demo video of your Paradox database utility made in RealVideo format and pushed across the PointCast network to its subscribers, you now know the man for the job.