Top all-time · #7005
Ilija Eftimov
Personal blog · ieftimov.comprogrammingcareer
Ilija Eftimov's personal blog at ieftimov.com covers programming and career. Since 2016, 11 different Hacker News readers have linked it 26 times, most often “Conditional HTTP GET: The fastest requests need no response body”. The last post was in 2022, but the archive is still widely read.
Documenting my experiences and learnings, with the goal of helping other software engineers on their journey
Most-linked posts?
- Conditional HTTP GET: The fastest requests need no response body3 people · 3 mentions · first linked 2021-06-02
- When and Why to Use Least Frequently Used (LFU) Cache with Golang Implementation2 people · 2 mentions · first linked 2019-03-01
- Understanding bytes in Go by building a TCP protocol2 people · 2 mentions · first linked 2020-04-14
- Make resilient Go servers using timeouts, deadlines and context cancellation2 people · 2 mentions · first linked 2020-01-07
What Hacker News says?
https://ieftimov.com Started it back at the end of 2014. I have been maintaining a twice-a-month publishing schedule (roughly) for the past two years. In the past year and a bit I've been focused on writing about backend topics from a Go angle. Usually the posts are +3K words, with relevant code examples, explaining a deep technical topic. I always try to I take the reader from first principles and build the knowled…
Comment linking /post/golang-datastructures-trees/
on “Ask HN: What is your blog and why should I read it?”Submitted Deep dive in CORS: History, how it works, and best practices as a story · 387 points
HN discussionSubmitted Make resilient Go servers using timeouts, deadlines and context cancellation as a story · 229 points
HN discussionSubmitted Conditional HTTP GET: The fastest requests need no response body as a story · 9 points
HN discussionSubmitted Identify and Escalate Risks: A Practical Framework for Software Engineers as a story · 4 points
HN discussionSubmitted Creating and testing gRPC server interceptors in Ruby as a story · 4 points
HN discussionSubmitted Understanding bytes in Go by building a TCP protocol as a story · 4 points
HN discussionSubmitted The practicality of designing and describing your APIs as a story · 4 points
HN discussionSubmitted Ditch old tools and habits for the golden tools of your new company as a story · 3 points
HN discussionSubmitted How to Make the Step Up from Intermediate to Senior Engineer as a story · 3 points
HN discussionSubmitted Understanding bytes in Go by building a TCP protocol as a story · 3 points
HN discussionSubmitted Resilient Go net/HTTP servers using timeouts, deadlines and context cancellation as a story · 3 points
HN discussionSubmitted Tutorial: Predict diabetes using k-NN from scratch and using scikit-learn as a story · 2 points
HN discussionSubmitted How to Make Reviewers Love Your Big Pull Requests as a story · 2 points
HN discussionSubmitted Conditional HTTP Get as a story · 2 points
HN discussionSubmitted Conditional HTTP GET: The fastest requests need no response body as a story · 2 points
HN discussionSubmitted Four Steps to Daemonize Your Go Programs as a story · 2 points
HN discussionSubmitted When and Why to Use Least Frequently Used (LFU) Cache with Golang Implementation as a story · 2 points
HN discussionSubmitted Understanding why and how to add idempotent requests to your APIs as a story · 2 points
HN discussionSubmitted Testing in Go: Clean Tests Using T.Cleanup as a story · 1 points
HN discussionSubmitted Golang: When and Why to Use a Least Frequently Used (LFU) Cache as a story · 1 points
HN discussionSubmitted Should working with legacy be awful? as a story · 1 points
HN discussion
