Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
vkhorikov
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
Short-term vs. long-term perspective in software development
(enterprisecraftsmanship.com)
1 points
by
vkhorikov
9y ago
|
0 comments
32.
▲
by
vkhorikov
9y ago
It's not a matter of giving up, it's a calculated choice. True, the path you described is good, and if I wouldn't have any other options, I would gladly take it. However, I do have other options, and they are more effective,
33.
▲
by
vkhorikov
9y ago
Actually, we figured the Youtubers thing pretty quickly, I just didn't emphasize this stage in the blog. We did try to reach out to them for about a month. With no luck. Only one more or less famous Youtuber posted a video about the ga
34.
▲
by
vkhorikov
9y ago
Wow, that's a hell of a suggestion. All on point! Where were you when I was still developing the game
35.
▲
A story about how I tried to get into game development and failed
(enterprisecraftsmanship.com)
2 points
by
vkhorikov
9y ago
|
0 comments
36.
▲
A story about how I tried to get into game development and failed
(enterprisecraftsmanship.com)
1 points
by
vkhorikov
9y ago
|
0 comments
37.
▲
Temporal coupling and Immutability
(enterprisecraftsmanship.com)
1 points
by
vkhorikov
10y ago
|
0 comments
38.
▲
Error handling: Exception or Result?
(enterprisecraftsmanship.com)
2 points
by
vkhorikov
10y ago
|
0 comments
39.
▲
OOP, FP, and object-relational impedance mismatch
(enterprisecraftsmanship.com)
3 points
by
vkhorikov
10y ago
|
0 comments
40.
▲
Complete mock elimination. Practical example
(enterprisecraftsmanship.com)
2 points
by
vkhorikov
10y ago
|
0 comments
41.
▲
by
vkhorikov
10y ago
I do agree with this one.
42.
▲
by
vkhorikov
10y ago
Coupling is an important concept but I think this concern can be mitigated by following the DRY principle. That is, if you have only one function that knows about the object’s internal structure (“couples” to it, so to speak), it doesn’t re
43.
▲
Law of Demeter and immutability
(enterprisecraftsmanship.com)
9 points
by
vkhorikov
10y ago
|
1 comments
44.
▲
Styles of unit testing
(enterprisecraftsmanship.com)
2 points
by
vkhorikov
10y ago
|
0 comments
45.
▲
Growing Object-Oriented Software, Guided by Tests Without Mocks
(enterprisecraftsmanship.com)
4 points
by
vkhorikov
10y ago
|
0 comments
46.
▲
Unit tests value proposition
(enterprisecraftsmanship.com)
1 points
by
vkhorikov
10y ago
|
0 comments
47.
▲
What is functional programming?
(enterprisecraftsmanship.com)
2 points
by
vkhorikov
11y ago
|
0 comments
48.
▲
3 ways of achieving code correctness
(enterprisecraftsmanship.com)
2 points
by
vkhorikov
11y ago
|
0 comments
49.
▲
Entity vs. Value Object: the ultimate list of differences
(enterprisecraftsmanship.com)
2 points
by
vkhorikov
11y ago
|
0 comments
50.
▲
by
vkhorikov
11y ago
What city in Russia? Moscow? Also, shouldn't the cost of the flight eat up the difference?
51.
▲
Early exit is a tail call optimization of procedural languages
(enterprisecraftsmanship.com)
93 points
by
vkhorikov
11y ago
|
49 comments
52.
▲
Do you need an ORM?
(enterprisecraftsmanship.com)
1 points
by
vkhorikov
11y ago
|
0 comments
53.
▲
Domain-centric vs. data-centric approaches to software development
(enterprisecraftsmanship.com)
2 points
by
vkhorikov
11y ago
|
0 comments
54.
▲
by
vkhorikov
11y ago
I agree with your performance concerns. In fact, I state them in the end of the article pretty much the same way you did it in your comment.
55.
▲
Is SQL a good place for business logic?
(enterprisecraftsmanship.com)
3 points
by
vkhorikov
11y ago
|
3 comments
56.
▲
SQL vs. NoSQL: you do want to have a relational storage by default
(enterprisecraftsmanship.com)
16 points
by
vkhorikov
11y ago
|
2 comments
57.
▲
Why following software design best practices decreases code complexity
(enterprisecraftsmanship.com)
3 points
by
vkhorikov
11y ago
|
0 comments
58.
▲
Stages of competence: 2 ways of learning
(enterprisecraftsmanship.com)
1 points
by
vkhorikov
11y ago
|
0 comments
59.
▲
Making implicit assumptions explicit
(enterprisecraftsmanship.com)
1 points
by
vkhorikov
11y ago
|
0 comments
60.
▲
by
vkhorikov
11y ago
You are right, inheritance is perfectly applicable to the example from the article, basically because the example is very simple. The idea is that in more complex scenarios the best practice is to prefer composition over inheritance because
More ›