ryandaigle

OP here.

This is great, Peter, thank you for this perspective!

If you walked away with the impression that there were gotchas, then we have failed. While we do have specific criteria we're looking for (as we're trying to make the grading of each work sample as objective and consistent as possible), I wouldn't call those items "gotchas". It's also not the type of thing where if you miss one small item, you're disqualified. The grading allows for several missed items and is only looking for some total of all allowed points (across 33 different criteria). So while some of the items you didn't get credit for might have appeared trivial, or like a gotcha, there should be enough allowance in the process to not let one or two misses scuttle the whole effort.

Perfect candidates do not exist; just as perfect humans do not exist. Great test takers do exist though. Personally, I have never correlated good test takers with good employees or good programmers

We are totally with you re: perfect candidates. Work samples are only one part of the hiring process after all, and are meant to ensure some base level of technical ability. Others parts of the process, such as our structured interviews, are meant to flesh out some of the nuances I believe you're referring to here. We're not looking for a perfect candidate, but we are looking to understand what makes up each candidate to know if their strengths are a fit for Spreedly and if we can live with the weaknesses (and vice versa for the candidate evaluating Spreedly!).

We really do appreciate your effort, both in writing up your thoughts here, and in applying in the first place. This is how we get better at this kinda of thing!

Does this mean gists can have comment notifications again?

Add-on provisioning can fail (independent of fork). In that case fork still continues the rest of the process.

If you find it's always the same addon(s), please let us know.

How would you handle db/data sync between the apps?

Love to get your feedback on fork - ping me at: rd at heroku as you start using the tool.

The lack of search is the main reason I created http://gistedapp.herokuapp.com. Unfortunately I still find their search lacking in a few fundamental ways:

* it is (surprisingly?) case sensitive * it only searches titles, not file contents * the UI feels disconnected from the main gist area, making it unclear whether its a search of all Gists (like the previous version) or a personal search.

Fortunately, this update indicates they're paying attention to a much-used part of their product that was starting to feel neglected. At their pace of improvement I can't see these holes remaining for too long.

Now, hope they add back the ability to be notified when there's a comment on your gist (which Gisted supports)!

Just read your post, njyx. While it's solid and thorough, my first impression is that it's a bit too high-level for an audience of application developers.

Atom feed added at: http://miyagi.herokuapp.com/articles.atom

Thanks for letting the need for a feed be known!

Addressed: https://github.com/rwdaigle/adj/pull/5

Thanks for raising the issue.

http://github.com/rwdaigle/adj - but beware that the stack may be highly volatile at this stage.

Thanks for the feedback, Jesse. We're experimenting with various types of content and hear you on the general direction.

I don't want to be too narrow in these early days so I'll say we want content that will aid developers in discovering new development techniques as well as reinforcing the practice of ones they may already be aware of. I think both types of content you mention can aid in that.

I'll def read your post and follow up.

Yep, implementation is a no brainer, was just curious about the viability of RSS as medium. It appears it is not dead!

We're looking into this immediately. Thank you for raising the issue.

I was hoping people would just get that hitting enter in an input field submits the subscribe form. I'll need to make that more explicit, thanks.

Regarding submission of articles, I'd like to work with authors earlier in the writing process rather than just receive a bunch if completed work that may not be right for the site. However, even that should more transparent, I agree.

Thank you for this feedback. You're validating the general direction we were hoping to pursue. Expect to see more high level content always paired with meaningful examples and real world application.

Is Twitter of any use to you both for that purpose? @MiyagiJournal

When we look out at the world today we have trouble finding a trusted source for high-level technical content regarding application development. Miyagi is our experiment to address that need.

While initially seeded with content from within Heroku the intent is to publish and promote good ideas independent of their origin. I'd be interested in hearing 1) if you feel, as we do, of the need for such a site and 2) general interest in contributing to or reading such content.