HackerTrans
TopNewTrendsCommentsPastAskShowJobs

gunsch

no profile record

comments

gunsch
·2 tháng trước·discuss
A few months ago I was debugging a similar issue in a Go-based service layer, where frequent HTTP requests to the same domain kept making fresh TCP connections when I was expecting TCP conn reuse.

In this situation we were discarding the HTTP response without reading it before closing, which kept Go from reusing the connection. I didn't dig quite as deep as this post's author, but I imagine the same RST behavior was happening under the hood.
gunsch
·7 tháng trước·discuss
Pair programming! Get hands-on with your junior engineers and their development process. Push them to think through things and not just ask the LLM everything.
gunsch
·7 tháng trước·discuss
I hoped this might be like an externalization of g3doc. Nope.

Instead, I started reading through one of their highlighted examples --- the Go repo (https://codewiki.google/github.com/golang/go). This might be the worst high level overview of Go and its repo I've read. Mostly accurate but unhelpfully verbose, spending lots of words on trivia, and not at all making a compelling pitch for Go as a language or toolchain, how to use it, or how to work on it.
gunsch
·năm ngoái·discuss
Sure, that's advised in interviews, where you're about to make a decision on someone's livelihood, hence the importance of reducing bias. That's a completely different context than in casual conversation at a social event.
gunsch
·3 năm trước·discuss
+1. The comments bashing Closure in comparison to TypeScript feel like they're missing the timeline.

Closure brought modules, requires, compile-time type checking and optimizations to JavaScript years before TypeScript was on the scene. I wouldn't dare start a new project with Closure. But it was such a spiritual predecessor to what we have today in TypeScript, and has a special place in my heart too.
gunsch
·5 năm trước·discuss
Ad Hoc | Frontend, backend, infra / DevOps engineering | REMOTE (within USA) | Full-time | US Citizenship required Ad Hoc is trying to make federal government better by fixing its tech from the inside. We work on Healthcare.gov, VA.gov, and many other public web services, and focus on bringing product and technology best practices into government agencies. No defense or intelligence work, just civic services.

We're a remote-first company, a culture fully on Slack, a bunch of civically-minded weirdos with a strong sense of work-life balance and coworkers scattered all over the country. We look for people who are open-minded, empathetic, think of the user first, and who genuinely want to improve government services for citizens. Come help us make that happen!

I'm the Engineering Director at Ad Hoc and happy to talk with anyone who wants to learn more about Ad Hoc or generally about doing modern tech in government. Feel free to reach out to me directly (email in profile), or apply at https://adhoc.team/join/. Let's chat!