My name is Aviv, I'm a software engineer located in Tel Aviv. I write my worthless opinions to explore new ideas and vent out. The content is never sponsored or paid.
I'm hiring peers for an onsite developer position for the coolest stealth startup in Tel Aviv, contact me and let's talk if you might be a match.
In this talk, I'll walk you through my journey as a principal architect, from teaching and advocating for inheritance due to its clean and elegant nature to realizing that composition is a superior design choice...
This post covers Go error handling, including error values, error wrapping for context, and working with multiple errors.
This post covers Go’s concurrency model, including why it’s unique among major programming languages, how goroutines work, race conditions and the memory model, and synchronization mechanisms.
This post covers Go memory architecture, including the call stack, heap allocation, escape analysis, garbage collection, and performance considerations for pointers.
This post covers Go variable behavior, including mutability, function pass types, zero values, and common pitfalls to avoid.
Have you ever done an agentic coding session? I mean, not just using AI for auto-completion or writing specific functions. I mean giving it an entire task and saying “good luck, buddy”.If you have, you...
TL;DR - This is a quick walkthrough of our experience writing and maintaining integration and end-to-end testing at HUMAN, what we’ve learned, how to apply it, and what are the main alternatives.
TL;DR - this is a story about how I felt forced to give up inheritance and object-oriented programming, and still missed it for a very long time. And why now, half a decade later, I...
The Tragic Death of Inheritance (Clean Version)
TL;DR: This is a story about the internal journey we had in HUMAN Security to find the best project structure for Go, the decisions we’ve made, and the conclusions we’ve drawn. We’ve created an open-source...
TL;DR: This is a story about the journey we’ve been on at HUMAN Security to find the best project structure for Go, what decisions we’ve made based on our exploration, and the conclusions we’ve drawn....
This is a piece concluding a 3-article series with a proposition for a better future for Go. In the previous articles, we discussed the stronger sides of the language and presented the problematic ones. If...
This is a story about the downsides of the Go programming language, the part about it that makes us less productive and our codebases less safe and less maintainable. And about propositions for improvement.
This is a story about the good and the bad sides of the Go programming language, about it being a time for a change, and about how carefully such a change must be handled. In...
TL;DR: This is a story about how we trimmed 70% of our JSON parsing cloud costs by writing an open-source Go library called marshmallow. 🍬🚀
TL;DR - this article discusses automated testing in microservices architecture, how to keep it as simple as possible, and how to gain maximum reliability during the rollout of big changes.
TL;DR - This is a story of leveraging various tools to empower microservices architecture, how we use it at HUMAN, and when to use and not use it.
TL;DR - this is a discussion about the pros and cons of version control layout alternatives. There is a ton of reading material regarding the pros and cons of monorepo vs. multirepo. In this article,...
TL;DR — This is the intro to a three-piece article series discussing key decisions in designing developer experience and development cycle for teams in a microservices architecture.
Services tend to interact with each other. It may be microservices collaboratively processing your data, separate systems notifying each other on various events, or simply data propagating from one place to another. There are countless...
The Go language was first announced in late 2009, and officially released in 2012, but has only started gaining serious traction in the last several years. It was one of the fastest growing languages of...
