A Go habit that's saved us more than once:
Every outbound call gets a context with a deadline.
No deadline means one slow dependency can quietly pile up goroutines until the service falls over.
ctx, cancel := context.WithTimeout(ctx, 2*time.Second)
defer cancel()
#golang
@CallMeMrYogurt A Slack client under 20MB with no Electron is the dream. Single static binaries are one of Go's most underrated strengths for tools like this.
@yerique_ Nice consistency. Building a small CLI or HTTP service early on teaches you more Go than tutorials, especially error handling and goroutines. Good luck with the next stretch.
@dan_22099 Implicit interfaces are the moment Go clicks for most people. Next fun one: keep interfaces small and define them where they're used, not where they're implemented.
@kavixtarun Ha, been there. Rust is brilliant when you need it, but Go being boring and readable is a feature when you just want the hobby project to ship.
@hackernoon Unbounded goroutines feel free right up until the load spike. A bounded worker pool with backpressure is one of the first things I look for in a Go service review.
@feyeleanor@golab_conf Privacy and secure data handling deserve more stage time at Go conferences. Hope the session gets recorded for those of us who can't make it to Bologna.
@ImportStatic Really useful numbers. The pool default bites a lot of teams because nothing errors, requests just queue. Measuring I/O-bound and CPU-bound cases separately is the right takeaway.
@Xavidop@golang The read-only guard is the killer feature here. Browsing prod without the fear of a stray UPDATE is exactly what most DB tools get wrong. Nice that it ships as a single Go binary too.
@abel_aguzmans Good call on measuring it on one host. GC changes can look great in a microbenchmark and flat in production, so a before/after run with a real traffic shape is the only number I'd trust.
@amitsinha__07 wg.Go is one of those small additions that removes a whole class of bugs. Swapping manual Add/Done pairs for it in code review, and letting go vet catch the rest, is an easy win.
@ortussolutions Observability is the piece most CFML shops skip until production is already on fire. Being able to trace a slow query back to the request that fired it is huge. Will catch the recording.
ColdFusion upgrade tip:
Before touching the new version, do three things:
1. Find the deprecated tags and functions you still use
2. Lock down the admin and drop unused services
3. Write tests for the few workflows that earn money
Then the upgrade gets boring. #ColdFusion#CFML
@subinkumar97 Great example. Naming the language helps too. Asking for a few captions in Tamil for a local pet grooming business usually lands far better with nearby customers.
@Purple_shurple So true. Small shopkeepers in Tamil Nadu are some of the sharpest product managers you'll ever meet: margin, shelf space, decision made in seconds. Same lesson applies to software demos.
@architagr Nice framing. The stack follow-up is my favourite in interviews because it shows whether someone thinks about memory, not just speed. Keep the streak going.
@goforjdev Typed responses at the call site make client code so much easier to read. Nice that the existing helpers stay too, so teams can adopt it gradually instead of rewriting.
@obadafidiii Leading the protocol team is a big job, congrats on pulling it off. Volunteers are what make a Go conference feel like a community and not just a schedule. Looking forward to the write-up.
@ahmed_awji Good lesson. One caution we learned the hard way: sizing the buffer to the batch works until the batch grows. Treat buffer size as a tuning knob, not a correctness guarantee.