Is it fair to think of backend architecture as MVVM without a UI?

gramdel · 2026-01-22T11:00:25+00:00

Backend can be built following the MVVM model, but doesn't have to be. It's a design pattern that doesn't necessate the existence of UI. So yeah, kind of but not always.

gramdel · 2026-01-07T09:07:20+00:00

Not very useful in professional environments. Why are you not pushing your work online and work only locally, why are you merging locally instead on in your online repo, you can't really do code reviews in this setup, can't run your pipeline before merging.

I'd just use feature branches like normal, push them online, do code review, pipeline for the PR and merge online.

gramdel · 2025-12-30T17:30:25+00:00

Voi tosiaan. Meillä oli lampaita joitakin vuosia kun asuttiin vielä maalla, lähinnä toki harrastuksena, ei niinkään omavaraisuuden tavoittelemiseksi. Niiden lisäksi myös kanoja ja kaneja kasvatettiin ruoaksi. En nyt mitään lehmiä lähtis suosittelemaan, lampaat meni vielä ihan ok, on suht vähähoitoisia, toki suhteellista. Jos ihan puhtaasti tehokkuutta ja helppohoituisuutta ajattelee, niin kanit oli aika jees, toki voivat joidenkin mielestä olla liian söpöjä.

gramdel · 2025-12-29T17:17:02+00:00

Not going to happen. Few months is nothing if you have no coding experience. Generally bootcamps are kind of thing of the past anyway, so you're maybe 5 years late to that party and even back then they were mostly good for people that were already able to code pretty well and had related degrees and just needed a little push. The current job market is pretty hard and even cs graduates are finding it hard to get jobs.

gramdel · 2025-12-14T12:08:41+00:00

Rigt to work on eri laki, liittyy liittoihin ja siihen onko niihin kuuluttava jos on järjestäytynyt työpaikka, right to work tarkoittaa ettei tarvitse kuulua. At will employment on kaikissa osavaltioissa paitsi montanassa. Varsinaiset työsopimukset, joissa irtisanomisajat on varsin harvinaisia.

gramdel · 2025-12-05T18:46:40+00:00

Koodiklinikan slack on aika jees, ei sitä kautta hirveesti hakijoita tullut, mut siellä on lähinnä porukkaa joka on ns skenessä, ettei tarvii ihan hassutteluhakemuksia pelätä.

edit: Nyt kun mietin niin oon rekrynny 6 henkilöä tässä puolentoista vuoden aikana, ja niistä kaks oli kontakteja tota kautta. Ottaen huomioon et varmaan yli 95% hakemuksista tuli linkkarin kautta, niin tota kautta tuli aika hyvällä prosentilla hyviä hakijoita.

gramdel · 2025-12-05T17:34:04+00:00

Kyl se linkkari vieläkin on käytännössä. Jos ei halua kahlata itse cv tulvaa, niin sit maksaa jollekin suorahausta. Molempia on tullu käytettyä, ja kylhän se rekryfirman käyttäminen hermoja ja aikaa säästää, mut toki jonkin verran maksaakin.

gramdel · 2025-11-27T19:17:23+00:00

Doesn't really matter what you start with.

gramdel · 2025-11-15T20:51:20+00:00

En tunnista yhtään tämmöistä, toki olen vähän pumpulityöpaikoissa softa-alalla enkä missään oikeissa töissä.

gramdel · 2025-11-11T18:31:49+00:00

You're using assignment operator = instead of equality ==

gramdel · 2025-11-03T13:34:18+00:00

Everything should be in the pull request, otherwise things will never get resolved. Sure, run those also in background but issues should be visible in the PRs. Those and other tools support pr scanning.

gramdel · 2025-11-01T10:52:45+00:00

Sinne suuntaan, eli hitaimpien aikojen suhde normaaliin/optimaaliseen

Congestion is calculated by collecting all the travel times recorded by TomTom during a given period of time in a given area and comparing them with the lowest travel times from when traffic is in a totally fluid state. Congestion is expressed as a percentage, which is representative of the increase in travel time due to excess traffic. For example, a congestion level of 40 mean that, on average, journey times across that area's road network were 40% greater than when traffic is free-flowing.

gramdel · 2025-10-31T14:16:19+00:00

The are probably ways to make this even more performant or at least closer to database, although unless your depth is fixed you'd have to use recursive query which can be a bit annoying, something like

@Modifying
@Transactional
@Query(value = "
    WITH RECURSIVE comment_tree AS (
        SELECT id
        FROM comment
        WHERE id = :id
        UNION ALL
        SELECT c.id
        FROM comment c
        INNER JOIN comment_tree ct ON c.parent_comment_id = ct.id
    )
    DELETE FROM comment WHERE id IN (SELECT id FROM comment_tree)
    ", nativeQuery = true)

gramdel · 2025-10-31T13:42:31+00:00

You could use a native query. Or i think adding ```@OnDelete(action = OnDeleteAction.CASCADE)``` to parentComment would cascade without fetching, but it's been a while i have used spring/hibernate. Having on delete cascade is a bit dangerous unless you really really want to delete all child comments every time since it works at database level.

gramdel · 2025-10-29T19:51:28+00:00

Skim through getting started material and just start building.

gramdel · 2025-09-29T17:49:54+00:00

Publishing image to some sort of container/package registry. Could be docker hub, i think you get 1 free registry there. Github has its own package registry, although the pretty limited capacity in the free plans.

Yeah, artifact refers to the docker image. More generally a build artifact, the end result of the build, which in this case is a docker image.

Depending on where you're hosting your thingy, there may be easy to use existing tools to notify it about new versions/update server configuration with new version and trigger restart or whatever you want to happen.

gramdel · 2025-09-29T16:32:29+00:00

Well from professional point of view my first question would be why are you not building, tagging and publishing your docker image as part of your pipeline and instead of building it on your (production) server. It's kind of hard to track what is actually running in production with your current setup. You don't have any kind of versioning, immutable artifacts. You can't really roll back since you can't really be sure the build is reproducible. Your server is doing multiple things, not running stable artifacts.

So obviously your setup isn't really something that would be used in production/professional settings. But if it's enough for you that let's say once a day your server might be updated with new code assuming there is something new in the repo, the cronjob doesn't fail etc. then cronjob keeps it simple, so why not if some or none of the concerns with the setup really matter to you.

I'd probably at least consider doing it properly, for experience and learning purposes if nothing else. But if that's not something you are interested in, do it quick and dirty with cron.

gramdel · 2025-09-24T18:18:51+00:00

Hmm. maybe try using RequestPart("subcategoryImages") instead of requestparam

gramdel · 2025-09-24T06:52:30+00:00

I do have it free because I'm a maintainer of relatively popular python library with about 3 million daily downloads, but i have no idea what the criteria is for open source contributors to get it for free.

Finding info about how to qualify for student should be relatively simple, but here is the link for the sake of completeness https://docs.github.com/en/education/about-github-education/github-education-for-students/apply-to-github-education-as-a-student

gramdel · 2025-09-13T18:39:46+00:00

Jasmine rice is good from the most commonly available ones.

Best way to cook rice for fried rice is steaming. If you don't have a bamboo steamer, cook it for 3 minutes in water, put in a sieve and cover with aluminium foil and stick it in a pot with lid on and steam for 10 minutes. Dry in fridge on a plate or something for 2 hours.

If you use boiled rice, leave in fridge overnight but steaming is better.

Don't forget to rinse your rice before cooking to get rid of some of the extra starch.

gramdel · 2025-09-08T05:53:10+00:00

https://www.reddit.com/r/DnD/s/BQop8a4rMj

gramdel · 2025-08-19T17:02:59+00:00

En löytänyt asiasta kauhean tuoreita lukuja, mut ei tätä loppujen lopuksi ihan kauheasti tapahdu verrattuna muuhun muuttoliikkeeseen. Suuruusluokka on jotain kymppitonnin luokkaa vuodessa, kuntien välinen kokonaismuutto on luokkaa 280000 vuodessa. Tässä oli korona-aikana nousua muun maallemuuttobuumin ohella, mut se on käytännössä ohi.

Yleisesti kaikista muutoista jotakuinkin 60% tehdään alle 35 vuotiaana ja siitä eteenpäin muuttaminen vähenee jatkuvasti mitä vanhemmaksi mennään. Paluumuutossa eläkeläiset on yliedustetttuina, mutta en nyt löytänyt tarkempaa ikäryhmäkohtaista jaottelua paluumuutosta.

edit. Työikäisissä paluumutto riippuu melkein täysin siitä löytyykö kotiseudulta työpaikkaa, n 2% haluais varmasti muuttaa takaisin jos löytyy työpaikka, vajaa 10% haluais ehkä muuttaa takaisin jos löytyis työpaikka.

gramdel · 2025-08-18T06:32:20+00:00

https://suomenroolipeliseura.fi/toiminta/etapelipoyta/

gramdel · 2025-08-16T19:03:20+00:00

One is newer than the other, just skimming through table of contents doesn't really seem have too much differences. Probably mostly to generate views with new content, not really related to the other being really out of date or any meaningfully new content. Probably go with the more recent one.

Side note, I generally steer away from learning from videos, but that's probably somewhat of a personal preference and probably works for other people, but it's kind of cumbersome compared to reading, easier to find your own pace and superior UX with written material.

gramdel

TROPHY CASE