HNHacker News
TopNewBestAskShowJobs

jipiboily

89 karma · joined March 22, 2011

More on http://jipiboily.com/.
submissionscomments
jipiboily··on Dawn, a Docker based PaaS in Ruby
How does it compare to another PaaS in Ruby: https://github.com/tombh/peas ?

Just curious :)

jipiboily··on Version control: best practices
We use Fourchette (https://github.com/jipiboily/fourchette), which means we have a Heroku fork of our QA env for each GitHub PR.

Also, once something is on develop/staging, it is about to be shipped. If there is any bug in there, they are they should be fixed ASAP.

As we grow, we might have to do things differently, we'll see, but this works really well for us right now. :)

jipiboily··on Version control: best practices
Commits with unrelated changes should be multiple commits.
jipiboily··on Version control: best practices
For #1, we use Fourchette (https://github.com/jipiboily/fourchette), which means we have a Heroku fork of our QA env for each GitHub PR.

For merges to master, we submit other pull requests that we call "Release: ...". We can then see if CI and Rainforest tests are passing, if all is green, then we merge! :)

jipiboily··on Version control: best practices
Just an FYI, with this model, we still do multiple deploys each and every day :)

There might be a point where this won't work for us anymore, it's always time to change.

Also, this is not because a branching model works for a team that it will for all teams and projects.

Like any in-house, process the branching model will evolve with the team and it's requirements to be efficient.

jipiboily··on Version control: best practices
Good point! Force push should be avoided at all cost on origin. I think mercurial now has that as a feature!!!

Also, I prefer merge over rebase.

jipiboily··on Version control: best practices
We don't squash and we just use plain merges. It gives the real version of what happened. This is what I personally prefer.
jipiboily··on Version control: best practices
Yes, totally! We picked some examples quickly just to demonstrate that people can do better "lol", "fix" or "meh". There is still room for improvements and we have better ones, too.
jipiboily··on Version control: best practices
I agree it useful, but it's more useful overtime than anything, on the short term, issue numbers are not really useful. You are right, those examples were not our best ones ;)
jipiboily··on Show HN: OverLook.io – Get your non-technical friends involved in QA and Testing
It might feel similar, but they don't take care of the testing itself which is a major pain point. My 2 cents :)
jipiboily··on OnePlus One – $299 CyanogenMod 'killer' smartphone
Source for that?
jipiboily··on Show HN: Kiwichat – group chat of people who are within 1 mile
You could always pivot to a chat for people from New Zealand with that name :)
jipiboily··on Ask HN: Who is hiring? (April 2014)
Come join us, we do do awesome and fun stuff! :)
jipiboily··on Readmill shuts down, team joins Dropbox
What? Another service I start to use and shutdowns just a few days later...sad!

That's a problem with free services, and sometimes even with some paid services.

← PreviousPage 3 of 3