Spent half a day adding a testing framework and a bunch of tests to a legacy code base. Merged it and started with some refactoring needed in order to do an upgrade. Tests already prevented me from pushing 2 bugs to production. No user suffered in the process. No developer suffered from having to review 2 extra hot fix PRs. I didn’t suffer from having to deploy 2 extra times.
I'm very excited about my new job here in Belgium :)
I'm glad that @mntmn reflected why I'm excited about the MNT Reform (birdsite link): https://twitter.com/mntmn/status/1260245367712555008
> here is the response i just gave to a question submitted via Crowd Supply. i think it's still not clear to everyone that this product is designed to outlive our company, should we fail.
🤘Killswitch Engage 🤘
SourceHut + Plan 9 = ❤
the number one question i’m getting about Reform is: “how is real world performance? what can you do with it?” i’m working on an article/videos adressing this.
i would like to know your expectations / which apps and tools you need to work.
paul klingberg did some amazing rendering and animation work on MNT Reform for us. here are some more juicy perspectives: https://www.behance.net/gallery/96804715/MNT-Reform
A great shout-out to user mappu04 who identified the roadblock that made us look bad in previous run!
The worst-case results for huge repos still a known open issue, potentially resolved by caching in coming gitea release.
NOW OUR CALL FOR CONTRIBUTION: If you agree with us that accessibility is important, and would like to help resolving the accessibility issues tagged in the report: please have a look and consider a pull request!
Software developer • Latino 🇬🇹 • expat 🇧🇪
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!