Developer 2.0
Recent content on Developer 2.0
Live Last read · last published · next check
Latest posts
Part 2: CPU Profiling Deep Dive - Understanding Where Time Actually Goes
pprof quick start: profile a Go service in 10 minutes
Go libs I don't use but are popular
An overview of widely used Go libraries such as sqlmock, GORM, and gorilla/mux, with a discussion of their drawbacks in real-world applications. The post explains when these tools are helpful and when avoiding them leads to cleaner, more maintainable code.
Testing code with unpredictable or random output
Kubernestes cluster for free on OCI
How to hash and compare passwords in Go
How to gather GC metrics in NodeJS
Flattening the Package Structure
New project: ecommerce
Password policies
Memory-wall problem: cache locality in Go
Why We Should Avoid Using `else` in Programming
Writing tests in Go (business apps)
My Smart Home high-level architecture
JSON in Go
Honestly about why Go sucks (or not)
Top level logging
`replace` directive in go modules
gRPC with SSL/TLS
How to structure Go code?
HTTP context livetime
Wrapping commands in Go
Periodically restarting apps on Kubernetes
Writing custom linter in Go
Go Programming Language - book review
Extracting the business logic - the project
Refactoring for better testability
Is my interface too big?
Deep Work: Rules for Focused Success in a Distracted World
Go with some context
Never Split the Difference: Negotiating As If Your Life Depended On It
I talk to spammers. Here is what I found
From time to time, I receive an email from a scammer that says he has X million dollars/euro for me. At the very beginning, I removed those emails but at some point, I decided to answer them. Here’s what I found. Every scammer starts very typically. There’s a very reach person who’s dying or very sick. They found my email on the Internet and learned that I’ll be the person who will spend the money…
Go web frameworks
Go has plenty of different web frameworks. When you are faced with choosing a framework for the first time, it may turn out to be quite a challenge to choose the best one. This article is intended to help you choose the best one. It is full of personal judgments that you may disagree with. However, I believe you will find it most helpful.
Add header to every request in Go
Making changes to all HTTP requests can be handy. You may want to add an API key or some information about the sender like app version etc. No matter why you want to do that you have a few options to achieve the goal.
Unavailability is fine. Prepare for it
When I started my career as a software developer and published the first production application what I did was staring at logs and look for some fatal errors. It was a monolith application. Every log saying that something's wrong had to be fixed. ASAP. This approach worked for some time. However, when the scale increased, and I started building microservices, I couldn't get rid of all of them.…