Git Product home page Git Product logo

ama's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ama's Issues

How do you manage your time?

How do you manage your time?

  1. Do you pick projects or does someone pick them for your (thinking of GitHub-specific stuff here)?
  2. Do you report on said projects to someone specifically or just to your team? Is it constant (campfire)? Is it formal?
  3. Do you say what you're working on – specifically – to other people?

I'm curious how you organize the spread of information through small teams and through GitHub as a whole. I recently had a discussion with my own team because they rely heavily on IM and email for communication. I believe this approach dulls people to what should be important (email) or urgent (IM), and it fuels an urge for meetings to discuss casual topics because it effectively forces one-to-one communication on everything, or worse, emails to all.

I just followed you on twitter, and I need you to know something...

I am going to stalk you. I don't mean it in a weird way. I mean it in a very normal, everyday, staring through your window, hanging out on a tree in your front yard, way.

No but seriously, stalk.

Ok, just kidding, but seriously - I love octodex.github.com, and I never really knew who to tell that to. Did you have anything to do with that?

On a side note, stalk.

How do you handle priorities?

What I understand so far is this. You don't have priorities and you don't have deadlines. But what gets done is gauged on "is something important" and the important things are generally known to everyone. So to dive in a little deeper here....

HOW is something determine to be important and by who?

HOW are things generally known to everyone to be important? What occurs that makes the devs think it should be taken care of?

Just trying to get a better understand of this organizational void I see.

Hi! What about testing in github?

What is Your CI?
Do You have manual testing?
Just wanna know about Your "every developer push to production" deployment strategy. How GitHub assured that there are no errors in code? Link to blog post I haven`t seen (any blog post about that) accepted=)

How can I affect hourless days in my office?

So, I'm interested(as are my coworkers, I think) about how we could start to affect the Boss and our managers toward more flexible or hourless days. We all work on salary basis as is, some of us have commutes lasting nearly an hour. I personally have gotten used to starting my day at ≈ 8am, but I know some of my coworkers would love the opportunity to come-and-go and just be responsible for their own shit. A few specific questions include:

  • How do you handle one employe being blocked by another (What if the end of my day is the beginning of yours?)
  • How would you handle a metric to know what to charge or how long something would take? Is "3 good days or 2 bad ones and 2 good ones" expected and acceptable?
  • How do you keep people accountable before it's too late? Is the only way of managing this kind of workforce by hiring managers to review and lord over everything your employee's do, every day?
  • How do the managers handle necessary face time with an employee who's schedule is the opposite(or, conflicting) of their own?

Keeping in mind that we take on projects, and so far have not developed any of our own. The hourless work day seems very feasible in a business where you upkeep and iterate on a single product and those product's owners are the employee's, but what about when clients are constantly communicating with managers and things are being delegated/iterated throughout the day based on client feedback or client-project realizations?

Thanks for any elaboration on not only how GitHub works, but, more so how to affect those changes in an existing organization.

WTF do you actually do and how can I do it also?

Two part question, and by that I mean two questions:

  1. Pretty much everything I've seen from you is off-topic/side-projecty/hilarious. What is your actual function at GitHub? Which things were you hired to work on and which current features are you responsible for?
  2. Working at GitHub sounds like a fucking dream, both for the environment and because there are few products/sites I love and use so much. The primary focus of my life is getting better at programming (primarily Ruby and JavaScript). How do I know when I'm a good enough programmer to try to get hired there? How do I even know if I'd be a good fit, were I to be appropriately skilled?
  3. I said TWO questions. Pay attention!

Two questions

  1. If you weren't working at GitHub, where else would you love to work?
  2. In the song "Itsy Bitsy Teenie Weenie Yellow Polka Dot Bikini", which is yellow, the bikini or the polka dots?

What does GitHub use to deploy?

I know GitHub uses Hubot to begin deploys, I was wondering what is actually used in the back end for deploying, is it just Capistrano, or do you guys use something else?

upstream visual cue for Mac GitHub

Hey, had a thought: how about a handy dandy visual cue for git upstream changes for Mac GitHub? I'm discovering just how handy it is to fork projects and yet rather than remembering to yank down upstream changes, it would be nice to have a visual cue on each project that has the upstream added and a prompt to git fetch upstream.

Heck, while we're at it, perhaps have an option to add an upstream from the UI, but the visual cue alone would be super handy.

A Day at Github

Can you description a working day at Github? What time did people normally get in? How are features officially decided/approved? I'm sure anyone can't just write whatever they want. I also notice you guys work pretty late sometimes, is this due to too much fun or working hard or BOTH. Also, are you guys hiring more devs?

By the way, I love your screencasts. I hope there are more to come! Sorry for the ass load of questions. Just curious. :)

How do you live without a product manager?

So.. with the everyone does everything and everyone does whatever mentality who is driving the product? Who has the vision? Who turns the bad ideas down? etc etc..

Admittedly you are a developer company making tools for developers so I believe the landscape is different than with a company who is making products for say the medical industry.

From what I understand so far a lot of this comes from the designers. But what if what one designer wants is not a direction the "company" wants?

How do you measure productivity?

I just read your article "Hours are bullshit". I agree - for now however hours were the only measurable thing that we can bill.

Do you have an idea what should replace hours? What kind of metric should we use to measure productivity?

How newbie learn github to use github?

There are two types of people in this world: Geeks and non-geeks.

I am the non-geeks, who raised as non-geeks but few years back, found peace in the world of the internet and making my path blindly into the Geeks world.

Basically my current learning flow is just start toying and experimenting with projects (I was forking, watching and i don't know what else I was doing/destroying) instead of "researching" and waste more time.

I have to be honest, it gets "nowhere". I learn some stuffs, but with the time I put in, i think I am lost most of the time.

My question is: How would you do it if you were a beginner/newbie that's toying and experimenting github?

What would be your self-help resources, instead of doing things like what I am doing right now, asking you question and hope that someone can share their experiences and insights.

I thank you for your time and concern.

How long do you spend programming everyday?

And by programming I mean including writing little throwaway things as well as actual "production" code. Also do you have any specific "will not write code" hours/times to just get away from it all and refresh?

Github/github organization

How is github currently organized? One rails app with different rack applications like sinatra and whatever else tossed in and mounted at different routes? Can we get a post about how things are organized and what you use and how? Bonus nachos for pictured of the file structure and anything else (I like unicorns).

Feature Workflow and Task/Issue Management

Hey Zach—

After reading your Working at Github series, I've come up with a question of task management. You've said that hours are bullshit. I've got curious, what do you guys use for managing tasks? Do you set estimations? What's you feature workflow, from understanding the need of a feature to delivering it?

It would be awesome to hear a little bit about it.

Best,
@bai

Want to grab lunch?

Feel free to say no... but I think you're cool and my office is near GitHub's

Zach, what is your Creativity tonic?

I would love to hear what other things you are interested in - writing, painting, music, working out and so on. The reason I ask is I wonder if you have any suggestions for sparking Creativity.

How do you test?

I'm really interested in learning more with regards to how Github tests, specifically from the perspective of the Rails/Ruby code you ship. For instance:

  • Are you doing unit, functional and integration testing?
  • Any particular frameworks being used to support this effort?
  • How are you testing client side effects, interactions, etc.?

Thanks!

How does github deal with code internally?

Does github use an organization? If so, how are pull requests managed? Do you fork the repo as yourself and then do a pull request from a branch on that fork or is there some other way it can be done?

-- cwebber

Your Workspace

After seeing the software you use in #21, what does your work desk look like? (Picture?)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.