1. What is this dead sea scroll business?
    Some middle east awareness project?
    No. No. No, not how it's pronounced at all. Think "Just" + "Describe". Or "Prescribe", if that's your thing.
  2. Is this a serious thing?
    No. Not going to freak if some classroom jumps on it en masse, but having spent no effort towards spreading the word, there is no expectation for such a drawing.
  3. ...okay, because I don't think anyone knows about this.
    For the briefest of moments there was some consideration about putting some serious effort into promoting it as a real thing. But due to other obligations, it appeared best to work on it in this manner to perhaps provide benefit for someone else down the line.
  4. Who is behind this project? At times it sounds like just one person, at other times you speak in the collective.
    Mostly one person. Friends offer occasional support, but we're all too busy with our own jobs and lives. And when it gets later into the night, that one person ends up getting disjointed into several personalities from bouts of sleep deprivation.
  5. You're going to make everything just available open source?
    To an extent. Once the "event" is completed, that will mean the final product, a deliverable and fully functioning app, will have been finished and deployed. While that won't by any means be a bare-bones shell of a project (in fact, it'll be quite feature-loaded), there are some aspects which will get built afterwards, particularly with separately existing code written for specific features, that likely won't be shared.
  6. Are you actually going to do some design or is this just a Bootstrap-fest?
    There may have been a point where Bootstrap was novel enough that it was conceivable to take a product to launch with just the default themes. Now Bootstrap is far too prevalent to even consider that a legitimate effort. Even if there wasn't such a wide usage of the framework, the intent is to focus on the things that I can speed through while deferring the less urgent (but I don't mean to downplay the importance of good design here) design tasks for when there is leisure, or a break is warranted from the coding.
  7. Maybe it'd be better for you to not handle the design at all. I don't believe programmers should get involved in those things.
    I agree. While I never considered myself a programmer and considered myself more a web designer than a developer for most of my career, and while I do have considerable exposure to the field of graphic design, that exposure is what reveals my own weaknesses. I might be super confident about being able to come up with some really great designs, but for me that entails 10+ hours minimum, maybe much much longer to get through the research/planning. For the same level of quality, a professional graphic designer may need just 30 minutes. I do enjoy the design/aesthetic aspects of the trade, but one thing is certain: I have to push it off until the end, or I'd risk getting too caught up in fruitless endeavors.
  8. If your goal is to demonstrate an example of the complete process, don't you have to present the case that you are qualified?
    I never imagined that would become some big issue. If the changesets I push out show patterns and habits that you don't agree with, for one I'd love a discussion on it, but more importantly, I don't claim or believe I demonstrate some exemplary code. There are plenty people who can demonstrate those things. This project is meant as an illustration of the longer process of development.
  9. Still not sold.
    That's okay. While there's some language throughout the project which makes it sound very public-facing, it's primarily becoming a personal motivational tool. In addition to having a documented process for the future, it provides me a blog which I've lacked for a long time, and in a way it can be a point of interest for a potential employer who likes the notion of getting a different glimpse of a candidate than he can through the conventional methods (GitHub, LinkedIn, Resume, Cover Letter).
  10. The final product is pretty much going to be what you built before?
    I was very proud of that accomplishment, launching a full app like that despite what is now plainly evident was a woefully lacking understanding of the pieces involved. I do intend to implement most or all of the features that used to exist, and likely in more efficient, easier ways that I've learned over the years, but I'm thinking that perhaps I'll try narrowing down its focus to see if a developer-targeted blog platform might be a fun direction to take it in.
  11. *Perking up* What would that entail?
    Code syntax markups (naturally), StackOverflow, GitHub, Gist integration, submission of code from your editor/IDE to an API endpoint which stores your code fragments privately until you come ready to compose a post and then piece together a rich text that interweaves images, code, videos. I'm just talking, here; I haven't really thought much on this. I only mention it because I felt a strong need for such a thing, and naturally I'll be building some tools to that end anyway, at the least for myself.