back
user profile
roblaszczak
371karma·83submissions·January 8, 2018
recent activity (83 total)
comment
Hey HN! I'm Robert, and I'm one of the authors. With my friend Miłosz, we've been working on a way for experienced developers to grasp Go quickly. After long evenings and weekends, we…
comment
Hey HN! I'm Robert, and I'm one of the authors. With my friend Miłosz, we've been working on a way for experienced developers to grasp Go quickly. After long evenings and weekends, we…
comment
If new hardware or technology is totally changing your solution - it's a bad sign. It depends a lot on the domain on which you are working on. In places where I worked, such big changes could be …
comment
You are right - I'm using it as as shorthand. It's referring to the "typical" monolith architecture perception. I'm actually a big fan of modular, properly implemented monolit…
comment
Also as the context, most of these companies where PHP, Python, Ruby or NodeJS. In that case migration to Go had a lot of clearly visible benefits.
comment
Pleasure is all mine!
comment
> You're missing one key question in your list: "How much (time/money) will it cost and what will be the gain?" I guess it depends on the situation of the company. But I guess t…
comment
The good news is that Go have very little entry point. Thanks to that you can hire people, who are working in other technologies and are interested in learning something new. From my experience they c…
comment
> While protocols in Go are great (one of the very many breaths of fresh air that Go provided), operations on data structures without generics does not seem like a good time. Does everyone get arou…
comment
Hey, unfortunately our e-mail automation is a bit slow. It should arrive to your mailbox within couple minutes :) I'll add information to subscribe confirmation page about the delay.
comment
> In my experience, it's easier to reason about and build systems when idempotency is an application level concern. This is exactly what we are doing in my company :) But it’s always good to h…
comment
Exactly-once delivery is covering processing in this scenario. Because of that it is not covered in tests and schemas.
REST endpoint was just added to create entire use case. But you are right, if in…