Posts Archive

Working in JIRA I came across a new feature today, “Smart Replies”:

How absolutely ridiculous.

We use written communication in place of talking to each other. Using LLM’s to write those messages for you is the equivalent of having a robot by your side talking instead of you.

This new feature in JIRA is akin to that robot having a button that you can press so it says something. And by “encouraging your team to respond to work more often” we expect people to just push the “speak” button repeatedly. Somehow Atlassian labels this idiocy “collaboration”.

I’ve used the Starship prompt for a while now, and really like the extensive info it provides out of the box. However, I was missing the layout I had when I used the Tide prompt. So I did spend some time configuring and I’m fairly happy with the result.

Next step is to get it more Powerline‘y, but that will have to wait for another day.

The config is as follows:

I’ve created a Capacitor app that wraps the website I built a few years back - https://www.v-sanger.se. It is available in the nordic countries in Google Play. I will make it available for iOS - if I ever get a Mac.

It was an interesting endeavour creating an app - there are so many hoops to jump through to get an app published.

The original words introduced by the agile movement have lost their meaning, and I believe we need new ones.

I was recently in a situation where I wanted to tell my client that they would improve their software delivery if they focused on value delivered rather than features produced. Also, it would be a good idea if teams were responsible for delivering software rather than having individual contributions coordinated by a project manager.

Well, it lasted 18 months, but I’ve changed Linux distro again. I really thought I had settled on Fedora KDE - I really liked it.

The whole point to running Fedora was that I didn’t have to fix much with the OS, it just worked - until it didn’t. I have two main computers, a Framework laptop, and a stationary desktop computer, and they both got the same problem at the same time - the screen turned black after login if using Wayland, and I couldn’t find a way to fix it. Xorg worked decently, but both computers required re-installation. But the the whole point of running Fedora was that I shouldn’t have to deal with things like this. It should be noted that I was still on Fedora 40, and 41 had been out for three months.

The Problem

When I write tests in Java, I find it tedious to manually create objects and setting attributes. Code easily turns out like this:

var foo = new Foo("Satellite", 1000, true);
var bar = new Bar("Edward", "Scissorhands", List.of(foo));
// do stuff
assertEquals(foo, bar.findByName("Satellite"));

Here we’re first creating a Foo, which is then added to a Bar. We then test that we can find the Foo when we ask the Bar to search for it.

A year and half ago I ended a two year experiment using Windows as my daily driver OS. In short, I felt WSL had too many wrinkles that annoyed me. I switched back to Linux and it was like coming home after being away for too long.

Since then I’ve tried a number of distros and desktop environments, and I believe I have finally settled on Fedora KDE Plasma Desktop Edition. Getting there took some time though, I tried a number of alternatives, and this is my condensed experience:

As part of a larger overhaul, I recently redid the navigation for this site and switched the CSS framework from Semantic UI to Bulma. The main reasons are that I find Bulma requires simpler HTML, and that it has no included JavaScript dependencies. JavaScript is needed for some features though, one of them being the burger menu.

Bulma has a navbar component that automatically adapts to touchscreen devices by hiding the navbar-menu item. It also supplies a burger menu item, navbar-burger, that is shown when the navbar-menu is hidden.

I’m running Intellij inside Ubuntu on WSL 2, and today I had problems connecting to a database. It would connect randomly and then quickly lose connection. It turns out that the problem was with the way that IntelliJ stores passwords. When running in Linux, IntelliJ uses the Gnome Keyring, which I did not have running. The quick solution to the problem was to switch IntelliJ’s password save setting to “Never”.

During the Christmas break, I have installed and set up Windows on my Lenovo X1 Extreme laptop. That might sound slightly stupid as it came installed with Windows, but as with every other non-Mac laptop I’ve owned/used over the last 20 years, I wiped the disk and installed Linux on it. Now it was the other way around.

I now do development on Ubuntu using Windows Terminal, editing in VS Code on Windows or IntelliJ in Ubuntu using X410.