Readit News> a factory that forgot what it’s building. Features ship, bugs creep back in, and the codebase becomes an archaeological dig of short-term fixes and forgotten context.
That's tangential to tickets.
We always had tickets to some extent, but our current process involves organized feature planning, design tickets, implementation tickets, and review.
That has imposed a lot more structure, but it's also resulted in a lot less work. Developers know what the priorities are, know what the scope of work is, they know they'll get reviewed.
Issues the article talks about such as short term technical debt being accepted are tangential. If a problem comes up, it's documented and then a decision is made on when to address it. If it's serious, that could be immediately, and if not, it may be put aside until it's encapsulated in other work, such as a refactor or redesign.
Tickets drastically improve context by telling the story of what they're about, connecting to commits, and connecting to merge requests. The code becomes a series of narratives.
> “Yeah, good thought, but just stick to the ticket for now.”
That's bad management. Good management will say "Good thought, make a new ticket for it so we can hear what's on your mind and evaluate it."
> Ask why the feature matters? You’re overstepping.
Ask why the feature matters and you're a good dev!
But before we had this level of structure at my organization, sometimes the devs would override the stakeholder's explicit wishes without informing them!
Now with tickets there's an opportunity for dialog and a paper trail on decisions.
> Suggest a refactor while in the code? Not in scope.
This one is tricky as I just told a dev not to do a refactor this week. The reason was the refactor was tangential to the feature, which was already late to deliver. Instead, a ticket was made and we'll evaluate the decision to refactor next week.
> Improve naming, extract duplication, or add a helpful comment? That’s gold plating now.
Those aren't gold plating, they're part of code quality checks that go into reviews.
The tickets aren't the issue here any more than one might complain about a specific programming language being the problem. The core issue is the environment, and specifically of management. Before I had tickets, developers worked on what they wanted to work on
It might make sense to provide some system for figuring out how to create the budget, and then how to track your expenses against it.
In my mind the simplest form of budgeting is so-called "Envelope Accounting", where you have physical envelopes full of money where you pull money out when you spend it.
There are electronic envelope accounting systems which retain the simplicity.
I'm a bit unsure of how this system works, where it differs, etc.
In summary, I'd love to see:
1. An explanation of how to construct a budget using your system.
2. An explanation of how to compare your spending to your budget? (bonus points if I can use my existing plain text accounting system, or at least a csv file)
3. An explanation of how to track my budget over time.
I agree this was a terrible move on the ADL's part, and there have been others, but you're essentially labeling the oldest anti-hate group "fascist" because you disagree with one statement they made.
This dismisses any concerns they raise, or if someone else says the same as them, then they too must be pro-facist.
Dead Comment
They also position things in such a way that implies antisemitic things, such as saying that Zionism is only 200 years old, or discussing the Israel wars only or primarily through an Arab lens.
These biases around Jewish topics are small individually but large in aggregate, especially in how they present Jews and Jewish topics.
Multiple Jewish and civil rights organizations have done a more comprehensive job at discussing this, even organizations who don't usually agree on things. While they talk about "anti-Israel bias" Wikipedia articles on or mentioning Zionism (80% of Jews are Zionist) are IMHO just as, if not more damaging, and demonstrate the issue.
Most importantly though, talk to the Jews in your life about this. They will tell you.
https://www.worldjewishcongress.org/en/news/wikipedia-entrie...
https://www.jpost.com/diaspora/article-846563
https://cameraoncampus.org/blog/seven-tactics-wikipedia-edit...
https://www.adl.org/resources/report/editing-hate-how-anti-i...
https://www.standwithus.com/post/it-s-time-to-correct-wikipe...
https://www.piratewires.com/p/how-wikipedia-s-pro-hamas-edit...
I'm working on a solution to the effects of this isolation, but it's not ready for a big announcement.
https://github.com/epicenter-so/epicenter/issues/669
I did manually download the models and associated them, which are great but then the audio didn't work. On the browser version, it never asks me for permission for an audio device, and on the native version, it makes a file of 0 length and then complains it can't read the contents.
My read is that the project looks very interesting, and I'd love a FLOSS replacement for Aqua Voice, but this software isn't ready for everyday use yet, at least not on Linux.
I'd love to help somehow, whether that's a donation or experimenting if you point me to somewhere.