@mgattozzi@hachyderm.io
@mgattozzi@hachyderm.io avatar

mgattozzi

@mgattozzi@hachyderm.io

'A bad programmer' according to the Orange Site, he/him. DMs open. Always open to chat.

This profile is from a federated server and may be incomplete. Browse more on the original instance.

fasterthanlime, to random
@fasterthanlime@hachyderm.io avatar

I’m excited about all of these, since the borrow checker is at the core of Rust.

I am holding my breath for Polonius, so please don’t let me run out of oxygen 🫥

https://smallcultfollowing.com/babysteps/blog/2024/06/02/the-borrow-checker-within/

mgattozzi,
@mgattozzi@hachyderm.io avatar

@fasterthanlime I'm just not expecting anything to ship for another like 4 years maybe

mgattozzi,
@mgattozzi@hachyderm.io avatar

@fasterthanlime same. We can't be singers without em

fasterthanlime, (edited ) to random
@fasterthanlime@hachyderm.io avatar

Re: Microsoft Recall

mgattozzi,
@mgattozzi@hachyderm.io avatar

@fasterthanlime shipped as is, until the EU gets involved many many months later to say the opt out feature isn't good enough because "open my settings after the install with no clear disable this feature" button isn't good enough. The change will only then be made in the EU. Satya will continue to harp on about security being a number one priority.

mhoye, to random
@mhoye@mastodon.social avatar

Tired: This meeting could have been an email.

Wired: This startup could have been a spreadsheet.

mgattozzi,
@mgattozzi@hachyderm.io avatar
mgattozzi,
@mgattozzi@hachyderm.io avatar

@hazelweakly @mhoye they really should. It's so simple and elegant and actually makes sense.

hazelweakly, to random
@hazelweakly@hachyderm.io avatar
mgattozzi,
@mgattozzi@hachyderm.io avatar

@hazelweakly "We have to do what the big companies do because they're the ones essentially controlling the spec and also what if I do become webscale?" My developer in CompSci your app does 200 req/s you can afford to be correct and slow.

hazelweakly, to random
@hazelweakly@hachyderm.io avatar

Love "mandatory training" course questions.

"HEY, bobby has cancer and really hates cake with frosting. Should you give him a cake with frosting?

[ yes ] [ no ]"

hmm, wonder what the answer is

mgattozzi,
@mgattozzi@hachyderm.io avatar

@hazelweakly back when I was in the army the saving grace for some of the critical mandatory online trainings needed to advance in rank to like SGT, was that some of the courses were old, like pre SPA, beginning of the Iraq war, and you could only run them in IE, old and allowed you to access the tests via URL params if you were smart enough. Turned some like 4 to 8 hours courses into a 30 minute test only one

mgattozzi,
@mgattozzi@hachyderm.io avatar

@hazelweakly they also had my training installing Windows XP on a computer in the year of Luigi 2014 which was on contract life support and they were just switching to windows 7 slowly and windows 10 was either out or just around the corner. 8 definitely existed.

fasterthanlime, to random
@fasterthanlime@hachyderm.io avatar

Although I've known about it for years it's just now going click in my brain how big of a hack the syn crate is and how much I dislike it 🙃

https://lib.rs/crates/syn

mgattozzi,
@mgattozzi@hachyderm.io avatar

@fasterthanlime because of the author of the syn crate specifically which is bad for 10 different reasons

mgattozzi,
@mgattozzi@hachyderm.io avatar

@fasterthanlime the non apology really ticked me off

fasterthanlime, to random
@fasterthanlime@hachyderm.io avatar

re offline Rust: everything in crate docs, or rustdoc (the cargo manual, incl. unstable features, etc.) you can take with, but, for example, neither serde_derive nor serde_macros actual documents container/field attributes.

reading proc macro sources in anger is no fun!

mgattozzi,
@mgattozzi@hachyderm.io avatar

@fasterthanlime I don't see why not. It just takes in a stream of tokens and outputs a stream of tokens.

mgattozzi,
@mgattozzi@hachyderm.io avatar

@fasterthanlime hmmm I wonder if like a static variable is shared across invocations of the macro or not. I'm leaning towards not, but you know, who's to stop you from commiting crimes and bincoding data to disk to be read by a later invocation.

mgattozzi,
@mgattozzi@hachyderm.io avatar

@fasterthanlime damn. They really out here like:

  • do crimes
  • fast builds
  • the code you actually want

Pick 2

mgattozzi, to random
@mgattozzi@hachyderm.io avatar

Tired: Closing issues with "won't fix"
Wired: Closing issues with "THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT."

fasterthanlime, to random
@fasterthanlime@hachyderm.io avatar

I've reached the "steam-iron my green screen to get the wrinkles off" stage of video production

send help

mgattozzi,
@mgattozzi@hachyderm.io avatar

@fasterthanlime at least you're not at the part where you're buying dedicated hardware to do the chroma keying for you or whatever yet

mgattozzi,
@mgattozzi@hachyderm.io avatar

@fasterthanlime I'll see you in a few months where your demand for quality sends you ever further down the rabbit hole then!

mgattozzi, to random
@mgattozzi@hachyderm.io avatar

I've noticed a weird trend where people who aren't engineers but interact with them such as Recruiters all capitalize Rust as RUST and I have no idea why.

ekuber, to random
@ekuber@hachyderm.io avatar

Every time there's a CVE affecting some fundamental part of modern computing that Rust provides a dot-release for, it seems multiple publications find out first from the Rust blog and publish titles implying that Rust is the only affected thing. It's not only mildly annoying hearing the echos of "har, har, I thought it was 'safe'", it does a complete disservice to anyone that doesn't use Rust because they won't find out they have to update or mitigate the issue too!

mgattozzi,
@mgattozzi@hachyderm.io avatar

@ekuber it says it affects other languages right under the title, but I get it being hard to spot

skade, to random
@skade@hachyderm.io avatar

GitHub, but with microtransactions. Every ticket 10c, comment 1c.

mgattozzi,
@mgattozzi@hachyderm.io avatar

@skade every push is 5c and every force push is 10c

mgattozzi,
@mgattozzi@hachyderm.io avatar

@fasterthanlime @skade because GitHub already punishes us in the pr review process when we force push 😞

hazelweakly, to random
@hazelweakly@hachyderm.io avatar

Core competencies are something I think about a lot. I love to dig into what makes companies or ecosystems or social groups tick. Especially when that core competency enables what they do:

McDonald's, for example, is a real estate company that happens to make burgers.

Walmart is a shipping logistics company that also sells things.

What other examples can you think of where the core competency of the company is such that the "thing" a company does falls out naturally as a consequence?

mgattozzi,
@mgattozzi@hachyderm.io avatar

@hazelweakly Apple core competency is hardware and vendor lock in. They also sometimes do software, but mainly they run a marketplace

hazelweakly, to random
@hazelweakly@hachyderm.io avatar

I love explaining complicated subjects in a quippy way that isn't necessarily wrong. For example:

Kubernetes is 20 while-true loops in a trench coat pretending to be a container orchestration platform.

What are your favorite quippy ways to explain a complicated topic? It could be anything! I'm just curious what y'all have :)

mgattozzi,
@mgattozzi@hachyderm.io avatar

@hazelweakly async rust is just 3 synchronous functions in a trench coat

mgattozzi, to random
@mgattozzi@hachyderm.io avatar

After almost 9 years of Rust I've come to the conclusion that it's not just the way we write errors that's bad, it's also that Result guides us towards bad error handling and ? Makes it worse (handle my error? No just chuck it up the stack) I just need to write a post soon huh

I also think thiserror and anyhow are detrimental to good error handling as well and I'm guilty of doing this. The easy way to write error handling is the bad way to write good robust tools and programs

mgattozzi,
@mgattozzi@hachyderm.io avatar

Also God forbid you want to return multiple failures to handle all at once, while processing say a list of things that could succeed

b0rk, (edited ) to random
@b0rk@jvns.ca avatar

let's imagine you're resolving this merge conflict (in screenshot).

You've forgotten which code comes from your current branch and which one comes from the "other" branch. How do you figure it out? Do you:

  1. remember what the "top" and "bottom" parts correspond to from past merge conflicts?
  2. remember what HEAD means?
  3. read the last line of the merge conflict?
  4. run something like git show main or git diff mybranch..main to see the diff?
  5. enable diff3
  6. something else?
mgattozzi,
@mgattozzi@hachyderm.io avatar

@LucasWerkmeister @b0rk in the future you can run git checkout --conflict diff3 the/file of you have this issue

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • mdbf
  • InstantRegret
  • ethstaker
  • magazineikmin
  • GTA5RPClips
  • rosin
  • modclub
  • Youngstown
  • ngwrru68w68
  • slotface
  • osvaldo12
  • kavyap
  • DreamBathrooms
  • Leos
  • thenastyranch
  • everett
  • cubers
  • cisconetworking
  • normalnudes
  • Durango
  • anitta
  • khanakhh
  • tacticalgear
  • tester
  • provamag3
  • megavids
  • lostlight
  • All magazines