351–360 of 1001 posts
> I know I work at GitHub so that might sound heretical, but I promise it’s not controversial for me to say it. Very few people internally believe that PRs and issues are ideal primitives for the future of engineering. And there are a lots of us inside the machine exploring what comes next. From GitHub's Staff Research Engineer https://maggieappleton.com/zero-alignment/
Earlier quoted context omitted.
Sure it does. Users who continually push for the right features, stress test things (under normal circumstances), demonstrate uses of the platform that could be baked in by default, etc. are all highly valuable to everyone. And the social aspect matters too, even if GitHub really isn't a "social coding" site anymore. If great people doing OSS stuff are all on various GitHub projects, that encourages more good people…
> Users who continually push for the right features, stress test things (under normal circumstances), demonstrate uses of the platform that could be baked in by default, etc. are all highly valuable to everyone That's the job of GitHub's product and engineering teams, not the users.
I know this is ridiculously dramatic, but its the truth: I actually cried writing this blog post (tears hit my keyboard, I'm embarrassed to say). Nobody should cry over a SaaS, of all things. But GitHub has meant so much more to me than that (all laid out in the post). I have an unhealthy relationship with it. Its given me so much and I'm so thankful for it. But, it's not what it used to be. I don't know. We've been…
Hi there! Longtime fan and hubber here. It's okay to have emotions. I have similar emotions. I'm GitHub User 22723 which is effectively the same as you (considering there's ~180m GH accounts nowadays) My version of your post reads differently: "GitHub only gets better if people who give a shit stick around to make it better" Walking away would be easy. I felt that way when I left Heroku ~six years ago. I left that jo…
I know this is ridiculously dramatic, but its the truth: I actually cried writing this blog post (tears hit my keyboard, I'm embarrassed to say). Nobody should cry over a SaaS, of all things. But GitHub has meant so much more to me than that (all laid out in the post). I have an unhealthy relationship with it. Its given me so much and I'm so thankful for it. But, it's not what it used to be. I don't know. We've been…
Thank you for your hard work.
Earlier quoted context omitted.
Sure it does. Users who continually push for the right features, stress test things (under normal circumstances), demonstrate uses of the platform that could be baked in by default, etc. are all highly valuable to everyone. And the social aspect matters too, even if GitHub really isn't a "social coding" site anymore. If great people doing OSS stuff are all on various GitHub projects, that encourages more good people…
> Users who continually push for the right features, stress test things (under normal circumstances), demonstrate uses of the platform that could be baked in by default, etc. are all highly valuable to everyone That's the job of GitHub's product and engineering teams, not the users.
Earlier quoted context omitted.
Some years ago I wondered how long will it take them to go they way sourceforge went. Once you grow too much without a proper leader, you will fall :(.
Sourceforge died in a very different way though. Bundling spyware/crapware in install packages for open source software was a serious breach of trust, and was pretty much the direct reason for mass migration to Github. Github is failing on the technical side, but they at least mostly have their brand value intact. I think it will still take quite a lot for a mass migration of the same scale to happen.
Earlier quoted context omitted.
What? React has nothing to do with current state of affairs. In fact, React on GitHub currently exists in mere islands, i.e. in Projects and recently in Pull Requests. Most of the frontend is still Web Components[1] paired with Turbo[2] for hot reloading. GitHub is still as slow even with JavaScript disabled, try it yourself. Backend just serves stuff really slow. In fact, there is an alternative GitHub frontend (no…
Pull Requests is the thing that was wacky in the UI yesterday, coincidence or not? I have no idea. Yesterday we saw PR pages that displayed no error, just displayed wrong info. I would have preferred to get an error page than outdated or empty lists. I was guessing this was related to the React migration but I don't really know.
Like, what user-hostile intention was the reasoning behind that? I am literally imagining a product manager smoking a cigar and laughing at the RUM session replays of me losing my shit.
Earlier quoted context omitted.
If anyone reading this is curious of their own, you can go to https://api.github.com/users/YOUR_USERNAME_HERE and fetch it. My ID is just over 10,000. Crazy to think of the journey that I've had in computing since I signed up for GitHub.
I was late to the party: 457,207 Created at 2010-10-27T23:42:22Z. 16 years! What a wild ride. I used to use bitbucket a ton back then. I loved it. https://api.github.com/users/steveadams
> I know I work at GitHub so that might sound heretical, but I promise it’s not controversial for me to say it. Very few people internally believe that PRs and issues are ideal primitives for the future of engineering. And there are a lots of us inside the machine exploring what comes next. From GitHub's Staff Research Engineer https://maggieappleton.com/zero-alignment/
Github released that split PR beta, so sounds like they are still thinking about the future which is moving towards small manageable PRs which are part of a parent ticket. That's a solid way to dealing with AI codegen bloat.