If you think JIRA is bad, you haven't been around long enough to see just how bad some systems can get.

But I like JIRA. Maybe I'm part of the problem. At my last job we started with JIRA and moved to Azure DevOps, which was not as good I think. Although, it was about when it launched and I have to give MS credit for doing a lot of major development while I noticed it.

Of course, the systems work best if they are allowed to integrate properly with your CI/CD and version control system. Azure DevOps didn't have wiki (at least at the time we used it) so we still had Confluence. And Mercurial although we were slowly switching to git. So we lost all integration.

Now I am working with Apple Radar, and that's a whole different world of both some interesting features but a whole lot of less interesting attributes...

But the problem even in the places that do use JIRA is that if it gets out into the hands of a large organization they are going to mess it up and customize it into something crazy, unless you're really lucky. Same is true about almost every off-the-shelf system.

And if you ever feel uncertain, you could always try bugzilla. I never really used it directly, so I guess I can't speak about it... But I never could get over the looks.

A tool I set up for a team to use almost 20 years ago now is Trac. It's the first system I used that combined wiki, source control (SVN at the time), and issue tracking all at once. I'm not even sure Atlassian existed at the time or maybe it was just JIRA. Looks like it still exists (https://trac.edgewall.org/). It was easy to set up and had a really nice plugin system (it's a Python-based tool). Never really took off and I didn't see it used anywhere else.

What's weird is the number of years I've been around and it's odd how a "new feature" comes along and something had it years ago. More surprisingly is when a new system comes out and you lose some really valuable feature and everyone likes the shiny stuff they sort of forget about what they lost...

I remember everyone flipped out about Remote Desktop coming out for Windows like who's ever done that before. Then all the UNIX guys in the room went what about X Windows that came out in the 80s?

So I disappear from Acc for months at a time then come out with an old guy post every once in awhile. So here it is. I guess I didn't realize I've made it to old guy rambling age till now .

C++ and D getting some nice enhancements. I'm excited for the future.

C++20 added modules. Finally. The end of the insane, 70's era concept of using a PREPROCESSOR to include multiple files together with all the bugs, forward declarations, and slow file access that included.

D just added in beta, the 'musthave' (IIRC) keyword which fires off a compiler error if you don't check the return value of a function. So now, we can have compiler statically verified return checks. Imagine how many hundreds of posts on Allegro have been the result of people not checking return values. I've long told people, "error checking should not be opt in". If you're depending on people to do the right thing... in order to not do the wrong thing you're in for a bad time with sleepy and distracted programmers.

The future of code is zerocode (or at least that's what's Microsoft & Co are trying to sell now. Yes, it was a trap !)

Have you tried Go, Rust, Ruby, WebAssembly ? Or just jump into the wagon and do some embedded stuff in ARM (C/C++ mainly) :-)

Does anyone learn asm anymore?

EDIT : Changed learnt to learn.

I've noticed it. I've been having trouble logging in too.

Yep, all the time! Sometimes takes an age to load, sometimes doesn’t load at all, seems really hit and miss. Logging in via my iPhone only seems to work if I enable auto login.

Hey, spit and bailing twine can only do so much. One of these days ML is going to reveal Allegro.cc 3.0. Any day now. Soon.....

"One of these posts, is not like the other"

Congrats!