dagss

27 ms·

331.
by dagss 4y ago
Heatpumps are an extremely widely deployed technology by now (I have one in my house, so have everyone I know); this is an article about inventions in heat pump space, and the post is sceptical about the concept of heat pumps. Kind of like
332.
by dagss 4y ago
For typical heatpumps efficiency is a factor of temperature difference. Ground-source are efficient (COP 5) because you go from 5 degrees Celsius to perhaps 35 degree Celsius (underfloor heating or low temperature convection radiators) This
333.
by dagss 4y ago
When you move to microservices -- or rather, when you split your data across several DBs -- you sometimes end up basically reimplementing DB synchronization in business logic layers that could (sometimes, and depending on scalability con
334.
by dagss 4y ago
I think I should have avoided the word "monolith". I just meant non-microservice architectures. Microservices have their own challenges apart from network communication etc between medium sized services that yiu refer to. For inst
335.
by dagss 4y ago
Right, I agree with this. I think "monolith" in my example was a standin for "non-microservice". I am all for dividing services after technical requirements; and certainly any non-O(1) memory requirements for instance on
336.
by dagss 4y ago
"Using microservices poorly" -- this comes up a lot when I discuss microservices with people who believe in them. I think it comes close to the True Scotsman fallacy -- if microservices ended up causing a mess, the explanation is
337.
by dagss 4y ago
What I meant is: If people are working at 1/10th of their potential they would tend to get frustrated. With microservices, you make 10x as much work in such a way that the work seems meaningful and is perhaps even fullfilling. It takes
338.
by dagss 4y ago
Understaffed because with the microservices fashion you can get 100 engineers to be satisfied and think they are doing meaningful work while producing the output of 10 engineers. The industry believes the fashion is the only way to work by
339.
by dagss 4y ago
I never understood when people talk about microservices and scaling (for traffic). I thought microservices is a solution to scale development teams, not for traffic. If you have a horizontally scalable monolith, it can scale pretty much as
340.
by dagss 4y ago
We do mini-batch processing in SQL. Some hundred milliseconds latency, some hundred events consumed from to the inbound event table per iteration. Paginate through using a (Shard, EventSequenceNumber) key; writers to table synchronize/
341.
by dagss 4y ago
In mssql you have "inline tabled valued functions" which you can declare and reuse, and they are inlined and optimization happens across them. We use sqlcode [1] to get around weaknesses in deploying stored functions. Big drawback
342.
by dagss 4y ago
We use sqlcode as a more general solution to this: https://github.com/vippsas/sqlcode
343.
by dagss 4y ago
Agreed. The power of SQL is awesome. But really wish people started making better languages that compile to SQL; like it happened with JavaScript
344.
by dagss 4y ago
To use SQL (or rather, push compute to the database) well you need to think in sets, indexes, etc; the primitives you work with is rather different from the ones you usually use in C#. You need to switch mode of thought anyway. If a really
345.
by dagss 4y ago
We care A LOT about testing everything, always. We use SQL container [edit: new, freshly cloned DB for a test function in less than a second] and find it to be no problem in practice to write integration tests for our pieces of Go code that
346.
by dagss 4y ago
I'm curious about resources to learning SQL well. In our company I've done a series of teaching session (we're on about 10th hour now). It's working OK, but wish I knew of good material / blog posts to point at. I f
347.
by dagss 4y ago
It is one thing when a junior does this because they haven't learned better. It's quite another when experienced seniors ban the use of SQL features because it's not "modern" or there is an architectural principle t
348.
by dagss 4y ago
"Most organizations have shifted to organize their engineering teams by product" We have done the same. The great thing about it is locating decision makers and customer insight close to developers. The bad thing is that what is p
349.
by dagss 4y ago
Stored procedures has some advantages (fast to debug/try out a query from your service without copy+paste all the time, etc), but also disadvantages (unreadable git diffs, big bang rollouts on changes) We made this tool to get the best
350.
by dagss 4y ago
Impact on education is huge. Current style of take-home assignments will loose any educational effect. Negative in the short run; one can only hope that one can switch to new styles of education and turn it into something positive, but it&#
351.
by dagss 4y ago
Tried Norwegian (5 million or so speakers). It's doing great in it. The moment I tried something in Norwegian it just switched AND kept all the context from our previous conversation in English. It seem to speak all human languages in
352.
by dagss 4y ago
OK, re-reading your comment: Yes, I agree of course it is not super-human. People are impressed because it's able to express itself like a low-to-mediocre-skilled human, which still seems like a pretty high bar.
353.
by dagss 4y ago
About the uninspired text that's definitely tailoring. I asked for "arguments against christmas gifts" and got a lot of "correct" but bland text: "Another argument against Christmas gifts is that the commercial
354.
by dagss 4y ago
I get your point, but here is a reason I am stunned: Until now, if you ask "what makes humans different from animals" many responses could be in the line of "generating art, poetry, music, synthesise ideas".. Well, now i
355.
by dagss 4y ago
Not always, I have seen such fridges with ducts running the hot air out. Or as othees mention, the heatpump outside and gas piping. Still losses to have to cool down to 5 Celsius instead of 20 Celsius though, makes the heat pump a lot less
356.
by dagss 4y ago
1) Well assuming data is stored in the SQL as the transactional store, how do you move data safely from SQL to the eventstore? You at least need the postbox pattern. It is not clear to me that the postbox pattern is less hacky than listenin
357.
by dagss 4y ago
Not OP, but there is an approach here of using a dedicated loop worker to assign post-commit ID sequence. I.e. using the outbox pattern once, simply to assign a post-commit ID. https://github.com/vippsas/mssql-changefee
358.
by dagss 4y ago
I really like this solution and agree "bookmarks" are a lot better than outbox, but it is hard to guard against races where the reader increments the bookmark before an active transaction commits an ID at an earlier position; if
359.
by dagss 4y ago
The author says the outbox pattern should "always" be used. I agree with the goal -- one should definitely never publish an event externally before it is committed to DB! But I think using a "post-commit sequence number"
360.
by dagss 4y ago
A message queue is a database too. So the question is: Why have two copies of your data, two products to learn and monitor and operate, write boilerplate to move data between the DBs, etc.? A "message queue" comes down to being an

More ›