Set Lofty Goals, but Break Them Down Into Achievable Pieces.
Uncategorized
1
Posts
1
Posters
3
Views
-
Set Lofty Goals, but Break Them Down Into Achievable Pieces.
-
undefined stefano_zan@mastodon.uno shared this topic on
Gli ultimi otto messaggi ricevuti dalla Federazione
-
This is all possible because we had a healthy commons and so that's the reward for building a healthy commons: enclosure by billionaires who are promising the end of everyone's ability to make a living in a creative field. If that really will come to pass, we'd have been better off if we never shared anything on the internet and that really hurts.
-
Cavolo sono anni e anni che porto ogni giorno il pranzo a lavoro in una Balenciaga e non lo sapevo.
Vedi che alla fine sono davvero una influencer.
#quisièpersoicapo
-
C4
Fino al 1992 sembrò che di Sistemi Aperti si sarebbe riusciti ad occuparsene
C'era una rivista dedicata, del Gruppo Editoriale Jackson, che l'anno dopo cessò di esistere
C'erano lavori in corso sugli standard di riferimento, presidiati da governativi USA, IBM e consulenti Inglesi, che finirono nel nulla perché le funzionalità richieste comprendevano la possibilità di rendere anche LE PERSONE INTEROPERABILI in un Open System Environment
C'era la OLIVETTI
Ora non c'è ....
-
❗ Un nuovo Caravaggio entra nel patrimonio pubblico italiano.
✅ Il Ritratto di Monsignor Maffeo Barberini è stato acquistato dallo Stato per 30 milioni di euro e sarà esposto stabilmente a Palazzo Barberini a Roma.
#Caravaggio #PalazzoBarberini #storiadellarte #arteitaliana #museiitaliani #patrimonioculturale #Roma #barocco #capolavori #arte
➡️ I dettagli su Storie & Archeostorie: https://wp.me/p7tSpZ-cBF
-
Vespa?
Qualcuno ha detto Vespa?
-
@aeva i hear you. i've been an open source contributor for decades and closed my github because i don't want to feed the machine, and it feels like a betrayal of my own principles but so does knowingly giving everything away to the slop hopper
-
I was ambivalent about my code going into training sets, but now for a variety of exciting reasons I am no longer ambivalent. So here's the conflict: the only way I can think of to realistically prevent it from ever going into the plagiarism machine is to simply never make the source available. There we go. That's the crisis of faith.
-
ok genuine crisis of faith here. I've got two games I've been working on, both are intended to be fully open source. One is nearly ready for a public release, the other is probably realistically a year or two out. I feel it is important for the source to be available for the former is probably not yet part of any training sets because it only has 17 stars on github, but I'm assuming it probably is already.
The latter is largely not online at all, because I simply haven't built it yet...
