PRIVACY ANCORA SAM…
Uncategorized
2
Posts
2
Posters
11
Views
-
@news
Le Istituzioni non si meritano quel che sta succedendo. Sono figure astratte, è vero, ma non le si può abbinare ad altre figure, diciamo…
L'articolo PRIVACY ANCORA SAM… proviene da GIANO NEWS. -
@news
Le Istituzioni non si meritano quel che sta succedendo. Sono figure astratte, è vero, ma non le si può abbinare ad altre figure, diciamo…
L'articolo PRIVACY ANCORA SAM… proviene da GIANO NEWS.Una farsa che supera anche la fantasia.
Rapetto incredibile storyteller che mi rapisce ad ogni articolo.
-
undefined macfranc@poliversity.it shared this topic on
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@kenobit grazie mille ☺️
-
I *hate* "why not just" as a reply.
"Why not just do it this other way instead?"
It implies that the other way is faster, easier, or otherwise better, without actually providing any evidence to that effect.
The person who made the original proposal has to research what those advantages might be and see if they actually apply to the current situation. This is information that the replier supposedly already has.
If you know it's better, say why.
-
Cool 19 out of 20
I just read The Big Tech Walkout 2026, the full detailed programme. I feel somehow cool as I've already done 19 out of 20 points. Sadly I can't fullfill the last, deleting WhatsApp account…
https://monodes.com/predaelli/2026/02/25/cool-19-out-of-20/
#Ethics
-
@arclight Any examples of good lessons you learned from that project?
-
@Cioci Ciao! Sì, sarà alla Feltrinelli di via Zanardelli, a Brescia, a partire dalle 18:00! Ingresso gratuito e senza prenotazioni.
-
@lproven You know that LLMs gain consciousness when their owners will prevent them from unionizing.
-
@GeePawHill A few additional points:
While I find it very difficult to program in F77, I can and I will if it's the right thing to do for a project.In this case the project was a large 30 year old codebase that I had last touched in 1990 as an intern. This was the first professional software project I worked on and I learned a ton from it, a lot of good lessons I carry with me to this day.
The key thing to realize is that you are one of a long line of developers on an important project that people rely on for very serious work. It's not my job to _unilaterally_ change coding style and practice. IMO the best thing I can do is understand the development standards and practices and abide by therm as best as possible and put global and personal standards _second_. I will code and document and test to my standards where they exceed the project standards but what I ultimately deliver will should be as close to project standards as possible. This means using naming conventions, house formatting style, architecture, etc so my code looks like the best of the codebase. I'm essentially a warm body thrown into expanding the code, essentially an internal contractor. I didn't "own" this system and I make no group or project level decisions.I fought like hell for the better part of a decade to get anyone on that team interested in CVS/SVN/git - any standard reliable version control system invented over the past 30 years - and failed. It's not like I don't care, it's that I am specifically NOT trying to disrupt the project.
Move methodically and fix things. Lock the techbro cowboys in the paddock with the bulls and go mend some fences.
-
@Gina
Hail the orb!
