kukkeliskuu

8 ms·

61.
by kukkeliskuu 9mo ago
Has somebody written an analysis why Qt really sucks? It would be great to have a spec for a GOOD cross-platform (desktop) UI framework. It might be also possible to create a reference implementation of that spec on top of Qt.
62.
by kukkeliskuu 9mo ago
Many of my enterprise customers face the microservice hairball problem. Adoption of microservices has been "too succesful". There may be 200-400 microservices, and ownership may be lacking. The number is typically growing fast, be
63.
by kukkeliskuu 9mo ago
What do you think is the bottleneck?
64.
by kukkeliskuu 10mo ago
>The mobile app wasn't complex (literally only does the things outlined above) and I've done enough mobile development and graphics/computer vision development before that the stack and concepts involved weren't compl
65.
by kukkeliskuu 10mo ago
For example, I just got: "I've identified the core issue - one of the table cells is evaluating to None, causing the "Unknown flowable type" error. This requires further debugging to identify which specific cell is probl
66.
by kukkeliskuu 10mo ago
What I meant by "not treating LLM as senior" is that the disillusionment phase culminates in an a-ha moment which could be described a "LLM is not a senior developer". This a-ha moment is not intellectual, but emotional.
67.
by kukkeliskuu 10mo ago
> I realized the Claude version had a threading issue waiting to happen that was explicitly warned against in the docs of the api calls it was using. I am reading between the lines here, trying genuinely to be helpful, so forgive me if I
68.
by kukkeliskuu 10mo ago
My question was misleading. For me Claude Code appears sometimes to stop too often at a random point instead to ask instead of keeping going. I guess that is the point of the linked article that Codex works differently in this regard.
69.
by kukkeliskuu 10mo ago
How do you get it to stop to ask you something sometimes when it is doing its thing?
70.
by kukkeliskuu 10mo ago
> It was so impressed with its new performance it started adding > rocket ship emojis to the output summary. I laughed more at this than I probably should have, out of recognition.
71.
by kukkeliskuu 10mo ago
> This is step 3 of “draw the rest of the owl” :-) Fair enough :-) This reminds me about pigeon research by Skinner. Skinner placed hungry pigeons in a "Skinner box" and a mechanism delivered food pellets at fixed, non-continge
72.
by kukkeliskuu 10mo ago
For me, it has gone through stages. Initially I was astounded by the results. Then I wrote a large feature (ad pacing) on a site using LLMs. I learned the LLMs did not really understand what they were doing. The algorithm (PID controller) i
73.
by kukkeliskuu 10mo ago
I think this is similar in other fields, and appears to be related to your self-esteem. Some junior (and sometimes even senior) developers may have hard time accepting improvements on their design and code. If you are identified with your c
74.
by kukkeliskuu 11mo ago
> You can give them a consistent snapshot quite easily. How would you do that in a standard event sourcing system where data originates from multiple sources?
75.
by kukkeliskuu 11mo ago
That is a fair point, although I believe that misleading name is contributing to the confusion.
76.
by kukkeliskuu 11mo ago
Having worked as the lead architect for bank core payment systems, multiple bank scenario is a special case that is way too complex for the purpose of these discussions. It is a multi-layered processes that ultimately makes it very probable
77.
by kukkeliskuu 11mo ago
I know. That is why it is useful way to think about it, because it both is true and makes you think.
78.
by kukkeliskuu 11mo ago
It might arise from necessity, but what I see in practice that even senior developers deprioritize consistency on platforms and backends apparently just because the scalability and performance is so fashionable. That pushes the hard problem
79.
by kukkeliskuu 11mo ago
It is highly relevant in many contexts. I see in my work all the time that developers building frontends on top of microservices believe that because the system is called "eventually consistent", they can ignore consistency issues
80.
by kukkeliskuu 11mo ago
Branches, commits and merges are the means how people manually resolve conflicts so that a single repository can be used to see a state where revision steps forward in perfect lockstep. In many branching strategies this consistent state is
81.
by kukkeliskuu 11mo ago
Both of your statements are true. But in practice we are rarely interested in single writes when we talk about consistency, but the consistency of multiple writes ("transactions") to multiple systems such as microservices. It is d
82.
by kukkeliskuu 11mo ago
I have no beef with the academic, careful definitions, although I dislike the practice where academics redefine colloquial terms more formally. That actually causes more, not less confusion. I was talking about the colloquial use of the ter
83.
by kukkeliskuu 11mo ago
"... with your reasoning no complex system is ever consistent with ongoing changes. From the perspective of one of many concurrent writers outside of the database there’s no consistency they observe." That was kind of my point. We
84.
by kukkeliskuu 11mo ago
I have worked with core systems in several financial institutions, as well as built several event sourcing production systems used as the core platform. One of these event sourcing systems was actually providing real consistency guarantees.
85.
by kukkeliskuu 11mo ago
Yes, I agree. I don't really believe we can change the terminology. But maybe we can get some people to at least think about the consistency model when using the term.
86.
by kukkeliskuu 11mo ago
I was not trying to "define" eventually consistent, but to point out that people typically use the term quite loosely, for example when referring to the state of the system-of-systems of multiple microservices or event sourcing. T
87.
by kukkeliskuu 11mo ago
My point was kind of tongue-in-cheek. Like the other comment suggests, I was talking about how people actually use the term "eventually consistent" for example to refer to system-of-systems of multiple microservices or event sourc
88.
by kukkeliskuu 11mo ago
Your example is too simple to show the problem with the "eventual consistency" as people use the term in real life. Let's say you have two systems, one containing customers (A) and other containing contracts for the customers
89.
by kukkeliskuu 11mo ago
I think we should stop calling these systems eventually consistent. They are actually never consistent. If the system is complex enough and there are always incoming changes, there is never a point in time in these "eventually consiste
90.
by kukkeliskuu 11mo ago
My feeling about GitHub Pages is that it is not unreasonable just to forget about the site. For any cheap shared hosting I would psychologically feel the need to monitor the site somehow, periodically check that the credit card works etc. F

More ›