Nice presentation, thanks for sharing!
Favorite quote: "your product should be cutting edge, not your tech"
How GitHub No Longer Works
31–40 of 139 posts
Re: How GitHub No Longer Works
#32I love almost eveything GitHub does, and the way they do them. I'm a GitHub fanboy. There it is. I had a similar crush on Google, maybe 6-7 years ago, they lost me somewhere on the road.
Back in college around '08 my friend and I always used to joke that Google would buy a startup or company, then make their product free and better.
That doesn't seem to happen much anymore.
Re: How GitHub No Longer Works
#33I've found it interesting how many people in the Bay Area, particularly veterans of the 90s boom, discount a lot of the ideas pushed by GitHub and 37signals. Anedotally, one of the common responses whenever I reference either company is, "Yeah, but how big is [GitHub|37signals], really?" It's actually somewhat surprising to me how consistently I've encountered this response (so consistent, it feels as if it was distr…
> I've found it interesting how many people in the Bay Area, particularly veterans of the 90s boom, discount a lot of the ideas pushed by GitHub and 37signals
Then you can imagine how many people outside of the Bay area do the same thing. I've worked at places where I (stupidly) suggested some of their principles as solutions to systemic problems that came up, assuming that everyone would be on the same page (I mean their ideas just make sense right?) ... no way. I've gotten laughed out of the room a couple of times, wised up and am now resigned to the fact that unless I start my own company or join the founding core of a startup, I'll never get to apply those kinds of ideas unless I work in the Bay
Re: How GitHub No Longer Works
#34That guy knows how to make good looking slides.
Re: How GitHub No Longer Works
#35I love almost eveything GitHub does, and the way they do them. I'm a GitHub fanboy. There it is. I had a similar crush on Google, maybe 6-7 years ago, they lost me somewhere on the road.
I think they lost a lot of us as soon as the G+ train started rolling.
The problems Google has have nothing to do with Facebook being better, or G+ being empty or whatever. Facebook is terrible.
Re: How GitHub No Longer Works
#36Earlier quoted context omitted.
I think they lost a lot of us as soon as the G+ train started rolling.
The problems Google has have nothing to do with Facebook being better, or G+ being empty or whatever. Facebook is terrible.
And G+ is worse because the thing with Facebook...I'm never FORCED to reveal my Facebook identity on the open web. G+ doesn't really give me that option.
Re: How GitHub No Longer Works
#37Wow, I'm taking notes on the slide design. Looking forward to the video.
Re: How GitHub No Longer Works
#38Seems like 20% of that slide deck is about chat rooms... GitHub still uses Campfire for chat? I tried Campfire and Hipchat a couple years ago, neither stuck. Not sure why, maybe poor offline notifications and logging? Or maybe our team didn't have enough timezone overlap or things to chat about? Hard to say. Is strong chat as important to Github as Zach implies?
Absolutely. As I mentioned, we have 150+ rooms that we chill in, and most of our day-to-day work practices are tied into chat. Mention someone's name in a room they're not present in and we send push notifications to their phone and desktop- works great to pull people in as needed, without needing to distract them with the noise of being in the room 24/7. Our ops team is particularly in deep with chat. Instead of sil…
Great post Zach!
Tom Preson Warner, GitHubs founder and CEO (and creator of TOML[1]), also gave a very good overview of how GitHub works: http://www.youtube.com/watch?feature=player_detailpage&v=Ms-...
Tim Berglund recently talked in details about the PRPs and the product development process: http://www.infoq.com/interviews/berglund-product-owners
Re: How GitHub No Longer Works
#39Earlier quoted context omitted.
>> staging servers so non-technical staff can check the work of "their" developers Surely staging servers have some other benefits? Maybe some teams consider running code on the production setup for the first time to be risky to their customers? Perhaps some teams have encountered differences between dev laptops and production servers, which run on different OS/memory/etc. combinations?
Short-lived staging environments (eg, a temporary clone of a production environment) certainly have a place, such as when making architectural changes, but these kinds of changes are generally not happening on a regular basis if you are making incremental changes and doing continuous deployment. I'm sure that there are companies that have a valid engineering need for perpetual staging environments rather than feature…
I'm a dev at a company and I pushed for us to have a staging environment _and_ QA. When I started at my current job, it was common practice to edit code in production, and there was no testing (automated, QA, anything).
In our case, having a staging server (which is really a prod server since it's used for some internal stuff) gives us a chance to check a few things:
1. The installer still installs everything properly. 2. The main website works 3. Web services work
We don't have any hard and fast rules about how long things sit on staging, but having a staging system is useful.
So there you have it, a staging environment driven by engineering.
Re: How GitHub No Longer Works
#40Earlier quoted context omitted.
Short-lived staging environments (eg, a temporary clone of a production environment) certainly have a place, such as when making architectural changes, but these kinds of changes are generally not happening on a regular basis if you are making incremental changes and doing continuous deployment. I'm sure that there are companies that have a valid engineering need for perpetual staging environments rather than feature…
You honestly can't think of good engineering reasons not to push new code directly into production?
too busy crushing it to use a staging server
sorry you aren't a technical coder
you probably even file bugs instead of just monkey-patching it in production like a real man
(srcub)