Skip to main content

Digilasku osa 4

Digilasku on tehty täysin asiakkaan toiveiden mukaiseksi. Saimme asiakkaalta listan halutuista ominaisuuksista jotka priorisoimme. Lähdimme implementoimaan järjestelmää hyvin lyhyen (varmaankin noin kahden tunnin) suunnittelun jälkeen. Tarkoituksena oli scrum-tyyliin demota järjestelmää usein ja hakea siten lopullista muotoa.

Homma ei aivan haluamallamme tavalla sujunut. Kesälomien takia pääsimme näyttämään järjestelmää vain muutaman kerran kolmen kuukauden aikana. Tämä vaikutti järjestelmään varmasti paljon. Käyttäjäpalautteen puutteen takia jouduimme arvailemaan toteutuksessa jonkin verran. Jotkut arvauksista osui oikeaan, toiset väärään.

Käyttäjäkokemusten puuttuessa, teimme järjestelmän sisään oman osion, jossa käyttäjä voi kertoa parannusehdotuksista ja bugeista käytön ohessa. Tästä on ollut huomattavaa hyötyä, sillä olemme saaneet tätä kautta merkittävän osan bugiraporteista ja parannusehdotuksista. Asiakkaan mukaan kynnys yhteydenottoon on merkittävästi pienempi, koska raportointi aiheuttaa vain vähän lisävaivaa. Vaikka osa raporteista on ollut hieman lyhyitä, ovat ne parempia kuin ei mitään.

Comments

Post a Comment

Popular posts from this blog

I'm not a passionate developer

A family friend of mine is an airlane pilot. A dream job for most, right? As a child, I certainly thought so. Now that I can have grown-up talks with him, I have discovered a more accurate description of his profession. He says that the truth about the job is that it is boring. To me, that is not that surprising. Airplanes are cool and all, but when you are in the middle of the Atlantic sitting next to the colleague you have been talking to past five years, how stimulating can that be? When he says the job is boring, it is not a bad kind of boring. It is a very specific boring. The "boring" you would want as a passenger. Uneventful.  Yet, he loves his job. According to him, an experienced pilot is most pleased when each and every tiny thing in the flight plan - goes according to plan. Passengers in the cabin of an expert pilot sit in the comfort of not even noticing who is flying. As someone employed in a field where being boring is not exactly in high demand, this sounds pro...
Post a Comment
Read more

RocksDB data recovery

I recently needed to do some maintenance on a RocksDB key-value store. The task was simple enough, just delete some keys as the db served as a cache and did not contain any permanent data. I used the RocksDB cli administration tool ldb to erase the keys. After running a key scan with it, I got this error Failed: Corruption: Snappy not supported or corrupted Snappy compressed block contents So a damaged database. Fortunately, there's a tool to fix it, and after running it, I had access to the db via the admin tool. All the data was lost though. Adding and removing keys worked fine but all the old keys were gone. It turned out that the corrupted data was all the data there was. The recovery tool made a backup folder, and I recovered the data by taking the files from the backup folder and manually changing the CURRENT file to point to the old MANIFEST file which is apparently how RocksDB knows which sst (table) files to use. I could not access the data with the admin tool, ...
Post a Comment
Read more

Making dashboards more usable for LLMs

I’ve been looking into agentic workflows to act as an operations assistant for the SaaS I'm working on. A big part of that work is getting the assistant to make sense of all the alert and monitoring data that pours in every day. Passing a bunch of raw time-series data to an LLM generally doesn’t work that well. You need to tell the LLM to aggregate the data and give it the means to do so. Using aggregates will often lead to better insights from the LLM. This is a well-known fact to anyone who has tinkered with this (at least at the time of writing this). Humans, of course, like to build visualizations and dashboards to solve this issue (yes, yes, dashboards are often useless, but complaining about that is another blog post). LLMs can analyze them as well and in fact are pretty good at that, so the aggregate can be something both humans and LLMs can digest. I’ve been tinkering with the idea of appending some LLM-only content to a dashboard—for example, additional context, specific d...
Post a Comment
Read more