so you put up a front?
Kissaki
joined 1 year ago
I've tried out Linear (only peeked into it) and it's the perfect contrast of performance against Jira.
I feel like Jira is not enabling me to use Jira either.
The UI and UX is shit. Performance is shit. It's not only about configuration.
Jira Server is the on-premise Jira, right?
We had to change to Jira Cloud. (Vendor lock-in, mainly because of time-tracking appendix tools of that.) It's horrendeous. UI and UX is horrendeous. The DOM is horrendeous. Performance is horrendeous.
My CSS Hacks to fix the UI to a degree I can reasonably work with it are a lot more work now with the generated DOM class and ids. Sometimes they at least have test IDs which can be used.
Some things, like the board component quick filter, are not even available anymore.
The interactivity functionality is irritating and annoying most of the time.
The browser extension we use further fucking up doesn't help either of course.
Don't even get me started on Confluence. Which can't even find pages when I type the exact page title, or ranks them low. And editing tables is a hassle beyond belief now that responsive tables (self-sizing) are gone. It's wasteful on space too of course, with huge spacing.
Be bold and make changes. Document what you find out, what is outdated, what is missing.
Take ownership. If there's nobody that oversees overall structure, be the one to do so - at least where you're touching it or are being bothered by it.
Diatraxis gives some great insight and considerations input into writing and structuring documentation. Namely how different target audiences and doc use cases require different forms and detail levels of guidance.
My company's internal doc/guidance also links to https://www.writethedocs.org/guide/ which seems like a good source.
Blazor is incredibly versatile in terms of where and how you run it. The UI is in HTML and CSS, the generated runtime bindings in JavaScript, but you can code the backend as well as frontend logic in C# / .NET / Razor template files.
It can render on the server or client, even work offline with WebAssembly and Service Worker, and dynamically switch between or combine them.
You can also integrate it into Windows Forms, WPF, or multi-platform .NET MAUI with Webview2, which will render "as a website" while still binding and integrating into other platform UI and code.
Your goals of "neat little GUI" and "as portable as possible" may very well be opposing each other.
Main questions are what do you have (technologies); what are you constraints, and what do you need. Different tech has different UI tech. Overall, most GUI programming is a hassle or mess.
If you want to dip your toes, use the tech you like, and look for simple GUI techs first. Don't try to do everything/all platforms at once first.
I'm still waiting for better Windows Git Auth integration in GitButler. I don't want to enter my key password for each remote action (fetch or push).
sounds like a skin disease.”
I mean… it does occasionally make my skin crawl
If Markdown formatting is enough for you, I would look into using a static site generator, like Hugo or Jekyll.
If you want to keep your existing content as static files but same website skeleton and layout instead of copying and editing files you'll copy one and create the layout template. Then content and new posts and pages can be generated from Markdown files. If you set up CI they won't need to run Hugo or what you're using, only push the Markdown files to your Git repository.
Whatever you want to do primarily depends on: Your formatting, styling, functionality, and interfacing needs for the editor, and what you're willing to use or invest for setup.
Hugo runs from a single binary. The source layout is reasonable. With a single layout the folder structure doesn't have to be complex.
I'm not very familiar with alternative [Markdown] static site generators.
I'm thankful I am full stack and can do my stuff across borders. I hate the interfaces, waiting for stuff, or being hindered by dissatisfactory (to me anyway) stuff from them. So I'm glad when I have control over the entire stack - from talking to the customer to running production.
Anything I don't have control over - most if it doesn't get done, the rest can be okay or bothersome.
I hate that I don't see what the admin set up and does on the infrastructure. It makes it harder to assess issues and potential issues and how they could correlate with infrastructure changes and activities..