lipinho

lipinho

@lpnh.io

solve et coagula

168 followers245 following627 posts

refactoring can be tricky… at some point, the more abstraction you add, the more your code starts to look like the one you were trying to replace

lipinho reposted

#rustlang hot take: We should rename .unwrap() to .or_panic(). (And .expect() to .or_panic_with().) "Unwrap" is a terrible name for the panicking function, especially since we also have things like .unwrap_or() and .unwrap_or_default() which never panic.

lipinho reposted

“We adopted #rustlang for its security and are seeing a 1000x reduction in memory safety vulnerability density ... with Rust changes having a 4x lower rollback rate and spending 25% less time in code review, the safer path is now also the faster one.” security.googleblog.com/2025/11/rust...

security.googleblog.comRust in Android: move fast and fix thingsPosted by Jeff Vander Stoep, Android Last year, we wrote about why a memory safety strategy that focuses on vulnerability prevention in ...

não façam igual eu amigos, ouçam o Dr. Áuzio

Portal Drauzio@drauziovarella.bsky.social

Cerca de metade dos corredores amadores desenvolvem uma lesão por ano. Mas é possível evitar isso. No terceiro vídeo da série sobre corrida e treinos, o dr. Drauzio Varella explica como.

lipinho reposted

só hoje fui perceber que esse >8 do git commit é uma tesoura kkkkkk # ------------------------ >8 ------------------------ # Do not modify or remove the line above. # Everything below it will be ignored.