Nitro
103 posts

Nitro
@_nitro_dev
React Developer, loves to do full stack development. Learning golang, soon a Gopher #js #golang #fullstack #reactjs
Hindupur Katılım Ekim 2023
72 Takip Edilen7 Takipçiler

How to pass the Leetcode interview (without getting lucky).
One of the best things you can do to become good at Leetcode is to study patterns and do mock interviews.
I created a powerful template to help you systematically approach Leetcode interviews.
To get it for FREE, just:
1. Follow me @systemdesignone
2. Like & Reply "Leetcode"
Then I'll DM you the details.

English
Nitro retweetledi

@MattJamesBoyle I was just kidding dude!! But will surely contribute, and it is in my plans for this year...
English

@_nitro_dev If you had contributed to the community I would have considered it :) you gotta give to receive.
English

@_nitro_dev You can store only the request ID in the context and then create a new logger at the start of every handler
English

I am trying to setup zap logger for my server. I am taking the logger as a dependency to my handler. And i want to add request-id into my logging so that it identifies the request uniquely. But i am struggling with it. Following is my code setup.
go.dev/play/p/3eBRzke…
English

@tebeka github.com/ortin779/priva… this is what i was doing. But i felt it is not a good practice to store non request scoped values in context.
English

@_nitro_dev See gist.github.com/tebeka/5c4ee20… (with slog, but same idea)
English

@_nitro_dev @tebeka @goinggodotnet What’s up with it?
That package name being called ctx was confusing because it’s usually a variable name for context.Context.
English

@matryer @tebeka @goinggodotnet I tried modifying the logger in the middleware, as the middleware runs for every request it was adding again and again to my logger instance.
As i think mote about it, i feel i should store the logger in the request context itself. But is it a good practice
English

@matryer @tebeka @goinggodotnet github.com/ortin779/priva…
This is my repo. I want to log every request with a unique id, and i want to have that id to be present in the logger for the entire life cycle of the request. I am taking the logger as an argument to my handler. Unable find an example for this.
English

@tebeka Firstly thanks a lot for putting up one of the best go lang course! I just completed the Practical Go Foundations on @ardanlabs . I now feel more confident about the core concepts of the language. Really appreaciate ur efforts and the curriculum design. Thanks
English

@ardanlabs do we have any support groups for the courses you folks offer?? In case of any doubt what should we do??
English
Nitro retweetledi

(RTs appreciated!)
As we get closer to the release of #golang 1.23, I have started preparing a free video course on the most important changes being introduced that you need to be aware of.
Join the waitlist here to be notified as I add videos!
bytesizego.com/go-1-23-in-23-…
English