ivan-pesenti
181 posts
ivan-pesenti
@ossandev
Hi! I'm an Italian guy who codes and plays football. Glad for what I've got and happy with people. Looking for software engineering challenges 😵
Bergamo Katılım Kasım 2020
567 Takip Edilen105 Takipçiler
Never use panic is a common oversimplified advice. It works 99% of the time, but you should understand where to apply it and where to skip the advice. I think @func25 explain it here very well.
Phuong Le@func25
A lot of Go devs get taught a fake rule: never use panic. The advice is simple but it is also lazy. Panic is just a sharp tool that needs to be used correctly. The real advice is do not use panic for normal failure, use it when the program has reached a state that should not exist and cannot be handled in a sane way. If your code can recover, return an error. If your code is - broken, - your assumptions are false, - startup cannot continue, Basically, this can't be happen, if this happen, my data is corrupted, my application is not in correct state, etc. Then failing hard is cleaner than pretending everything is fine. Bad error handling is often worse than no error handling. People wrap impossible states in polite-looking error returns and push the mess upward, so now every caller has to act like a broken invariant is just another routine case. That makes code noisier and less honest. So a well-placed panic can say something important: this is not business logic, this is a bug, a bad configuration, or a state the program was never designed to survive. We do use panic in our codebase to catch corrupted state early: #L142" target="_blank" rel="nofollow noopener">github.com/VictoriaMetric…
English
🤯 Ever tried running a Windows app like Robocopy on Linux?
Read the full adventure in the blog post!
dev.to/ossan/have-you…
English
ivan-pesenti retweetledi
I work with @jespinog and his depth of knowledge is wonderful. Love that he's taking up writing and sharing his experience widely.
Jesús Espino@jespinog
I'm launching today a project that I've been thinking about the last 10 years. A blog about software internals. If you want to know more take a look to the welcome post (or the other 2 that are already published) internals-for-interns.com/posts/welcome/
English
ivan-pesenti retweetledi
🔧 Curious about gVisor’s netstack?
Join @daniel1paulus for “Leverage Google gVisor for a userspace network stack in pure Go” — from TCP state to WireGuard, all in user space.
🕑 11:30 AM
📍Leonardo Room
#golang #golab2025
English
ivan-pesenti retweetledi
👏 Applause for Jesús Espino! His deep dive into Go’s select gave us a whole new appreciation for concurrency under the hood.
#golang #golab2025 @espinog
English
ivan-pesenti retweetledi
👏 Thanks to Konrad Reiche for “Writing Better Go: Lessons from 10 Code Reviews”. A great reminder that code reviews are more than nitpicks — they’re a path to clearer, pragmatic Go. 🚀
#golang #golab2025 @konradreiche
English
ivan-pesenti retweetledi
👏 Great insights from @ossandev on optimizing Go apps. Performance isn’t just a nice-to-have — it’s what makes you stand out as a developer. 🚀
#golang #golab2025
English
ivan-pesenti retweetledi
Your Go app is slow, memory-hungry, or OOM-ing?
@ossandev shows how to read metrics, find bottlenecks, and fix performance issues — before it’s too late.
🚀 Become a 10x Developer with Go Performance Optimization
#golang #golab2025
English
Please check out my last blog post about Go, Docker, Integration tests, and testcontainers-go
dev.to/ossan/the-retu…
English
I've just released my last blog post about Docker, Graphite and Go!
Please, check it out ☺️
dev.to/ossan/take-it-…
@golang @Docker
English
Don't miss the session I gave at the Come to Code event two months ago. You'll find amazing content regarding #tests and #go.
Comments, feedback, shares are always welcome!
youtu.be/qesTI2C2tNg
YouTube
English
@MoniOnlyoneday @golab_conf Thank you bro for your support! Looking forward to meeting you again 😘
English
@golab_conf @ossandev congrats @ossandev! I look forward to seeing it on the @golab_conf YouTube channel!!
English
ivan-pesenti retweetledi
#GoLab2024 may have ended, but we’re still reminiscing about those wonderful moments. 😍
Who remembers Ivan Pesenti’s talk on "Swiss knife for Go debugging with VSCode"? 🛠️✨
🙏 Thank you, Ivan, for sharing your expertise!
#GoLang #TechCommunity @ossandev
English
@golab_conf it's been an honor and a joy to be on your stage. Surely, it's been an unforgettable moment for me 😍
English
@pradumna_saraf I really enjoyed the reading of it 😁
Thanks for sharing it
English
ivan-pesenti retweetledi
The new blog is up!
Learn how to rate-limit a Golang API using Redis:
dev.to/pradumnasaraf/…
English
ivan-pesenti retweetledi
🚨 New Article Alert! 🚨
Just published Angular Signals: From Zero to Hero on @ThePracticalDev! 🎉
Check it out, and let me know your thoughts! 🛠️
👉 dev.to/soumayaerradi/…
English
@golab_conf Thanks for having me, folks 🤗🤗
Cannot wait to be there 🚀
English
ivan-pesenti retweetledi
Struggling with #GoLang debugging in #VSCode? 🔍
Ivan Pesenti shows how to master launch.json and Delve debugger at #GoLab2024!
From basic setup to advanced customization: level up your debugging game with this practical session! 🐹 🛠️
👉 golab.io/speakers/pesen…
@ossandev
English
"Leverage Your Test Suite With testcontainers-go & docker-compose" by @PesentiIvan #DEVCommunity dev.to/ossan/leverage…
English