On my team, is has been used to prevent developers from pushing code straight to production without being tested first. After some of those updates caused high impact bugs.
It ensures someone else has moved the card to the next status (or, that automated tests have passed and moved it to the next status by automation)
You can permission who can move to what status.
As a random dev, I personally wouldn’t recommend it unless there are legal requirements for such separation (or your org has lawyers that think such requirement exists)
Mark Zuckerberg attempted to sue native Hawaiians to force them into selling him their land near his compound and bunker under a shell company. He dropped the lawsuits after getting exposed with media coverage, and it is suspected he silently funded a native to buy the land for him. Truly villainous stuff. Never forget.
Will there be a way to make custom “apps” or “plugins”? Even just feeding it dynamic text to display on certain inputs or commands. Or are we stuck with the 6 features it comes with?
You are right. Nextjs has been terrible in my experience. And some junior developers are reaching for it for any and every project they start, even internal tools that don’t need server side rendering. I spent 2 days implementing auth middleware that clients and server side. Something that would have taken me 2 hours using a SPA. 2 days figuring out cryptic error messages and fight the client vs server model. Ended up having to convert to vite SPA
I wish this opinion was more widespread. The amount of time I have wasted building API + SPA when just sending HTML back and forth would have been entirely sufficient must be ridiculous
If it is one person doing both it is bad enough but if you now need two teams collaborating on some stupid form to do crud that only 5 people will ever use you have lost all velocity
The only reason I would use something like LINQPad is for the syntax tree and semantic analysis support, for compiler extensions. With a name like RoslynPad, seems funny that such a feature would be missing from that "alternative"
It uses a new Roslyn API to dump SyntaxTree and IOperation's starting at a specific span of source code IIRC, and it shipped in one of the minor version after .NET 8.0.0 release, it took me a bit to get it working upon its release but by this time you should have the necessary SDK, though the relevant extension version may still be marked as pre-release hence my suggestion.
I messed with it a little more before going to bed. The prerelease version changed the error and at least felt like it was closer. But I also found there was a new SDK release in the last few days that I have not upgraded yet.
