Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
roblaszczak
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
Show HN: Watermill v1.2 – building event-driven applications the easy way in Go
(threedots.tech)
2 points
by
roblaszczak
4y ago
|
0 comments
32.
▲
What will drive computer performance after Moore’s Law? [pdf]
(microsoft.com)
2 points
by
roblaszczak
4y ago
|
0 comments
33.
▲
The Go libraries that never failed us
(threedots.tech)
4 points
by
roblaszczak
4y ago
|
0 comments
34.
▲
by
roblaszczak
4y ago
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're ready to share our idea that we t
35.
▲
Show HN: Learn Go by building real-life projects in your terminal and IDE
(threedots.tech)
19 points
by
roblaszczak
4y ago
|
1 comments
36.
▲
The best Go framework: no framework?
(threedots.tech)
205 points
by
roblaszczak
4y ago
|
177 comments
37.
▲
by
roblaszczak
4y ago
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're ready to share our idea that we t
38.
▲
Show HN: A Platform to learn Go by building projects in your terminal and IDE
(threedots.tech)
1 points
by
roblaszczak
4y ago
|
1 comments
39.
▲
Increasing Cohesion in Go with Generic Decorators
(threedots.tech)
1 points
by
roblaszczak
4y ago
|
0 comments
40.
▲
Show HN: Auto-Generated C4 Architecture Diagrams in Go
(threedots.tech)
2 points
by
roblaszczak
5y ago
|
1 comments
41.
▲
Auto-Generated C4 Architecture Diagrams in Go
(threedots.tech)
3 points
by
roblaszczak
5y ago
|
0 comments
42.
▲
Common Anti-Patterns in Go Web Applications
(threedots.tech)
4 points
by
roblaszczak
5y ago
|
0 comments
43.
▲
by
roblaszczak
5y ago
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 encapsulated and separated from the doma
44.
▲
by
roblaszczak
5y ago
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 monoliths. In the first blog article I was even
45.
▲
Software Dark Ages
(threedots.tech)
83 points
by
roblaszczak
5y ago
|
89 comments
46.
▲
Software Dark Ages
(threedots.tech)
6 points
by
roblaszczak
5y ago
|
3 comments
47.
▲
by
roblaszczak
5y ago
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.
48.
▲
by
roblaszczak
5y ago
Pleasure is all mine!
49.
▲
by
roblaszczak
5y ago
> 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 that before doing such movement, company
50.
▲
by
roblaszczak
5y ago
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 can be productive within a week . It
51.
▲
by
roblaszczak
5y ago
> 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 around the lack of generics by making most g
52.
▲
by
roblaszczak
5y ago
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.
53.
▲
Show HN: We wrote a book about building business applications in Go
(threedots.tech)
269 points
by
roblaszczak
5y ago
|
168 comments
54.
▲
by
roblaszczak
5y ago
> 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 have an option and know that we can do it
55.
▲
by
roblaszczak
5y ago
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 this part of the system something will
56.
▲
Show HN: Exactly-once delivery counter using Watermill messaging library
(github.com)
18 points
by
roblaszczak
5y ago
|
9 comments
57.
▲
by
roblaszczak
5y ago
This is also what Google suggests: > Please associate your commit with your google.com email unless: - You have a history of contributing to the repo under a different email before your employment at Google Source: https://ope
58.
▲
Combining DDD, CQRS, and Clean Architecture by Refactoring a Go Project
(threedots.tech)
5 points
by
roblaszczak
6y ago
|
0 comments
59.
▲
Basic CQRS by refactoring a Go project
(threedots.tech)
4 points
by
roblaszczak
6y ago
|
0 comments
60.
▲
Clean Architecture by refactoring a Go project
(threedots.tech)
1 points
by
roblaszczak
6y ago
|
0 comments
More ›