6:54 AM
Alright, here's the TL;DR of JIRA (other ticket managing platforms exist, I'm just familiar with JIRA, but if someone who has proper experience managing a project at this scale knows of something better, please let me know).
Basically, the idea is to organize tasks, which is rather obvious, but the exact format depends on which template you use, and there are three that could make sense.
The reason I believe this is better than issues is because it allows you to easily see all of the work being done and track progress in an aggregated display format - whereas issues are mostly just a long discussion thread of something that needs doing until it gets done, tickets let you move something between to-do, being worked on, needing code review, etc.
It's easier to explain this knowing the templates, so I'll talk about the three that would make sense (the others are all for other work; these three are for software): Kanban, Scrum, and Bug Tracking.
The Kanban board probably makes the most sense for us, and essentially there are a bunch of categories for tickets and you can create them and move them between these categories. It's best for teams that follow a continuous workflow, and it lets you add and reprioritize work as you go along so the team is always working on what is most important.
The Scrum board is probably the least sensible as it is considerably more professional (it's what my workplace uses). Essentially, you can create, plan, and run sprints, which are like mini development lifecycles between releases.
It's suitable for larger projects where you want the ability to recenter the entire project at large every now and then, and also for actual companies because it lets you schedule these sprints around releases and customer deadlines, which is something we don't really have, since we just release as we hit our own milestones.
The Bug Tracking board would make sense here too, although it's considerably simpler and honestly rather close to GitHub issues anyway. Basically, you just get a single list of things, and that's it. You can prioritize things and whatever but it's just a list of tasks.
Of course, we'll still be using GitHub issues to report bugs (and so that people outside the development team can report bugs and add feature requests / VEPs) but JIRA is a way for us to internally track progress and keep our development organized.
We don't really have strict deadlines or anything as this isn't really a hard commitment for any of us, including lyxal - it's not like we are working for Vyxal Corp. and need to meet our deadlines or we'll be fired - I just think that an organized development environment would help make the process more efficient and maybe help the code be more organized.
Anyway, ^ is a quick explanation of JIRA and my thoughts on it. Let me know what you think. My main worry is that it's too sweaty or completely excessive for something at this scale, but Vyxal is no longer a small project by any means, and we have a considerable amount of developers now.
3
Vyxal, 15 bytes
«⁽;«»⁽;»`⁽;`⁽;
Try it Online!
⁽ defines a one-byte lambda, and ; closes a non-length-specific lambda. This throws a syntax error no matter what.
The rest is to make sure it runs no matter what.
