ajsharma

Yes, I think of them as blogs. New engineers can read along and see the evolution of thoughts and design decisions.

Wow, I love this idea. I'm curious how you have that structured within the code base. Is it literally a platform folder and a business folder?

At Goldbely, our solution has been to have a single GitHub repo that's just for issues and use tags to highlight the actual code repos involved.

Works pretty well, if a little awkward at first.

Great read. What's more, I found out that my company's codebase was still using the broken 3.3.2 version (code fix in the works).

Love it when reading HN pays off immediately like that :)

We're using https://geekbot.io at Goldbely to organize this.

Handy to have the Slack bot remind us in the morning so no one forgets.

Reminds me of FOMO bot by Thoughtbot https://github.com/thoughtbot/FOMObot

What kind of development do you do and how old/big is the codebase?

Wealthfront article mentioned (i think) https://blog.wealthfront.com/college-vs-retirement-savings-s...

If Otto's Appfile mimics Heroku's app.json file (https://devcenter.heroku.com/articles/heroku-button#creating...), that'd be a huge win to me in having more sustainable Rails open source projects.

I do appreciate when tools/libraries take the time to explain the problem and how they differ from their competition. Especially in cases like this, where it's an underlying architecture difference.

The various Rake servers (Puma, Unicorn, etc.) have also done a great job of this.

> some of the design decisions simply didn’t make sense for our security model

I'm curious what decisions those are. We use heaven and it's worked well.

This seems like a good way of creating stand up reports that no one will read, except maybe management.

I've always thought of stand ups as a self-management tool and a short period of forced communication.

Wikipedia says "the structure of the meeting is meant to promote follow-up conversation, as well as to identify issues before they become too problematic" which having it as an asynchronous discussion seems to prevent.

Awesome, thanks :)

I dont suppose you have a tool that does this? I've been pondering building one, but I'd rather just skip to the part where I can start complaining about my service :p

Yeah, this is pretty much the behavior that I want to see from open source maintainers: make decisions and build conventions but be open to having your mind convinced of alternatives.

Last time I tried to get Induction working, it refused to load any of my databases :/

I use atmos/heaven for a similar functionality. It's nice because it ensures that the master branch on Github has gone through out automated tests and that whoever is deploying is deploying exactly the code from Github and not some strange variant locally.

I like the content, but I wish it was a blog so that I could simply follow the RSS feed.

Literally, your ideas are intriguing to me and I wish to subscribe to your newsletter.

How are you using Hubot to do this? Are you using a particular plugin?

This is the first I've heard of restify, but it seems like a useful framework for the main focus of most Node developers I know, which is to replace an API rather than a web application.

You won me over immediately with the fox in a lab coat

Looks like some other people are seeing it too http://developer.linkedin.com/forum/has-authentication-url-c...

I'd have posted too, but their login is broken http://developer.linkedin.com/user/login

Apparently, the highest trending ruby project for the last month is a Python project? https://github.com/trending?l=ruby&since=monthly

You should be, I'm probably going to steal the idea for all my front-end teams :)

Came across this UI kit a while back. I like their solution of a glossary page to show all classes in use: http://ink.sapo.pt/glossary

My dad taught me that delegation is about trusting that the work will be done better than if I had done it myself. Not always because of the lack of skill, but sometimes because of the lack of time. Hiring out of frustration due to pack of time can lead to poor choices, and a difficultly in working with the new hire