Skip to main content

Digilasku osa 3


Digilaskussa on jo nyt yli kaksikymmentä erilaista lomaketta. Syötekenttiä on noin 200. Yksi digilaskun onnistuneimpia osioita on näiden hallinta: syötekenttien validointi on pysynyt kohtuullisen hyvin kasassa.

Jokainen lomake on omassa luokassaan, joka perii Vaatimen Form-luokan. Laskujen, lähetteiden ja tarjousten formit perivät vielä tätä ennen abstraktin luokan, joka määrittelee näille yhteiset ominaisuudet. Lähes kaikki formit käyttävät suoraan Vaatimen datamallia, eli Java Beanit tai POJOT asetetaan suoraan formeihin. Datan tallennus onnistuu siis helposti ilman manuaalisia parsimisia, sillä formista tulee suoraan ulos ehjä objekti tietokantaan tallennettavaksi.

Formin syötekentissä käytetään useita erilaisia validaattoreita, jotka ovat myös omissa luokissaan. Syötekenttiä on yleistetty aina kun mahdollista, jotta vältytään perusvalidointien turhalta toistolta syötekentän luomisessa. Vaatimen vahvuuksia on ehdottomasti monipuolinen syötekenttien validointi.

Päädyimme toteuttamaan paljon applikaation logiikkaa tallennusnappuloihin. Suurimmaksi osin tämä toimii aika hyvin, vaikka paikoitellen rikomme räikeästi olio-ohjelmoinnin perussääntöjä, mutta toisaalta, nyt bugien lähteet on suhteellisen helppo selvittää. Elegantimpi tapa olisi tehdä itse lomakkeista funktionaalisempia, jolloin data ja sitä käsittelevät metodit olisivat samassa paikassa.
private Button getSaveButton() {
  Button save = new Button("Tallenna");
  save.addListener(new Button.ClickListener() {

   public void buttonClick(ClickEvent event) {
    PersistenceManager pm = PMF.get().getPersistenceManager();
    try {
     adminForm.commit();
     userForm.commit();
     user.setAccountId(ac.getAccountid());
     user.setUserType(DigilaskuApplication.USERTYPE_ADMIN);
     pm.makePersistent(ac);
     pm.makePersistent(user);
     NotificationFactory.showSaveMessage();
    } catch (Exception e) {

    } finally {
     pm.close();
    }

   }
  });
  return save;
 }

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

PydanticAI + evals + LiteLLM pipeline

I gave a tech talk at a Python meetup titled "Overengineering an LLM pipeline". It's based on my experiences of building production-grade stuff with LLMs I'm not sure how overengineered it actually turned out. Experimental would be a better term as it is using PydanticAI graphs library, which is in its very early stages as of writing this, although arguably already better than some of the pipeline libraries. Anyway, here is a link to it. It is a CLI poker app where you play one hand against an LLM. The LLM (theoretically) gets better with a self-correcting mechanism based on the evaluation score from another LLM. It uses the annotated past games as an additional context to potentially improve its decision-making. https://github.com/juho-y/archipylago-poker
Post a Comment
Read more

"You are a friendly breadwinner"

A recent blog post by Pete Koomen about how we still lack truly "AI-native" software got me thinking about the kinds of applications I’d like to see. As the blog post says, AI should handle the boring stuff and leave the interesting parts for me. I listed down a few tasks I've dealt with recently and wrote some system prompts for potential agentic AIs: Check that the GDPR subprocessor list is up to date. Also, ensure we have a signed data processing agreement in place with the necessary vendors. Write a summary of what you did and highlight any oddities or potentially outdated vendors. Review our product’s public-facing API. Ensure the domain objects are named consistently. Here's a link to our documentation describing the domain. Conduct a SOC 2 audit of our system and write a report with your findings. Send the report to Slack. Once you get approval, start implementing the necessary changes. These could include HR-related updates, changes to cloud infras...
Post a Comment
Read more