@SwiftOnSecurity wait is GitHub for the olds now? The kids onto something new?
@jaykass @SwiftOnSecurity I think the intended reading is that as a software project grows older, there are more and more barriers involved in getting a feature added. early adopters reminisce on being able to just bring up the features they wanted and see them realized. GitHub itself isn't the subject of the joke, just a software development-related property
@Eunakria @jaykass @SwiftOnSecurity True of companies too. I know people who left because they were early into a startup and burned out on the new process as the startup matures.
And, personal opinion? The new process is not only fine but important. I've worked at startups; as a general rule, they have a nasty tendency to prioritize working prototype over secure and stable (for obvious reasons) but if a company's stuck around for a decade, it's now something that users rely on and it *should* be tilting towards honoring that reliability desire (which means, yeah, we've put process in place against you reimplementing the entire database backend in Rust in an Adderall-fueled weekend, *Greg*. Get that shit reviewed).
@mtomczak @jaykass @SwiftOnSecurity I have a lot of personal scripts that I use and love to hack on, but I explicitly delimit them as "not production ready" partly because I don't want bugs in my shoddily written software to cause problems for other people, but also partly because I don't want to ruin the fun of working on hobby code with the responsibility of shipping it to actual users
@mtomczak @jaykass @SwiftOnSecurity 100%, which is why in my own projects I dedicate so much to robustness from the outset. even so, it's never possible to prepare for anything and any self-respecting software project should expect to dedicate a significant amount of its time to maintenance as it matures.
the thing that makes this all worth it is that you can always start your own project to experiment with avant-garde ideas. you can still have fun working on your own