Nikita retweetledi
Nikita
135 posts
Nikita
@nikitakuchur
Software Developer at @GoLandIDE. Just posting my thoughts on random topics.
Munich, Bavaria Katılım Ağustos 2017
58 Takip Edilen38 Takipçiler
@nikitakuchur Took me a day! Was honestly in a time crunch so I had no choice but to finish it that day really lol
English
Here's a track I made for an animated film! This is one of my favorite works so far hehe.
Rts appreciated!
#composer #filmscoring
English
Recently I added "ASCII rendering" to my side side side project. It's a classic tiled turn-based roguelike.
That's my dream project. I work on it whenever I get tired of my main projects, so its development is very slow.
#ScreenshotSaturday #gamedev #indiegame #godot
English
Nikita retweetledi
This was one of the coolest projects I’ve had the chance to work on. Really glad it’s finally available for Go developers!
GoLand, a JetBrains IDE@GoLandIDE
Profiling in #Golang just became easier with GoLand. Now you can capture and view CPU, heap, allocs, mutex, block, and goroutine profiles in a few clicks right in your IDE, without having to remember a single line of code or command. Read more about our new profiling tool 👇 blog.jetbrains.com/go/2026/05/20/…
English
Nikita retweetledi
Nikita retweetledi
Definitely no attack surface in here. Totally Reliable™ and Secure™. Trust me, they had Claude review it. It passed the tests that Claude wrote!
English
Nikita retweetledi
Get ready for a party! 🥳
📅 February 19, 4:00 pm GMT
📍 Online (Live)
Together with @ohmypy and @alextrending, we’ll be celebrating the release of Go 1.26! Expect technical insights, hands-on demos, open discussion, and a few surprises along the way!
Register now 👇 jb.gg/og8812
English
@gurusalih @GoLandIDE That's true - golangci-lint is a great tool, and it includes a couple of linters, such as bodyclose and sqlclosecheck, that can catch some resource leaks. However, it only helps in simple scenarios, which is not ideal.
English
@GoLandIDE golangci-lint already handles it #bodyclose" target="_blank" rel="nofollow noopener">golangci-lint.run/docs/linters/c…
English
What is the main issue?
The response body is never closed - and the app breaks under load. Even if you don’t read the body, you must still close it. Leaving the body open keeps the connection busy, and sooner or later the pool will be exhausted… taking production down with it.
GoLand, a JetBrains IDE@GoLandIDE
The code works… but something isn’t being handled. What’s missing? And what might happen in prod? Drop your guess below 👇
English
@GoLandIDE 1. Time out
2. Not closing the response body
3. Hope in the handler or somewhere else it validates the url. Otherwise end up with SSRF
English
The code works… but something isn’t being handled.
What’s missing? And what might happen in prod? Drop your guess below 👇
English