dagss

28 ms·

361.
by dagss 4y ago
This is my favorite kind of schema -- do not UPDATE Person.Name, instead INSERT into PersonNameChange. With the right indexes and lateral joins/cross applies you can make the aggregate you need when you query instead of when you write.
362.
by dagss 4y ago
Well, even if WE do not have 64TB tables (where one need low latency for the entire table), I believe there are plenty of other mature NoSQL offerings out there? Whether you go to the other cloud vendors or self host. Cosmos is at best unfi
363.
by dagss 4y ago
We migrated to Azure SQL Hyperscale and are very happy about that.
364.
by dagss 4y ago
This rhymes with my overall impression of Cosmos. It took us a while to see through the smokescreen because when talking to Microsoft support and representatives it is the Best Thing Ever and they sound so confident about it. But it really
365.
by dagss 4y ago
I love SQL and use it as much as I can, but it is not a good storage format for storing gigabytes of floating point numbers that you want to do linear algebra on with routines written in Fortran or assembly, ideally without having to copy t
366.
by dagss 4y ago
We do something similar, but in 2), instead of using the outbox pattern, we make use (in several different settings) of integers that are guaranteed to increment in commit order, then each consumer can track where their cursor is on the fee
367.
by dagss 4y ago
I have seen lots of code where the author did not understand DB transactions (at all!), without idempotency even if it was critical, test suites that call getters and setters for coverage stats but without any actual assertions; those kind
368.
by dagss 4y ago
Isn't this like replying to a thread and clicking "Also post to channel" in Slack?
369.
by dagss 4y ago
Not sure why you added /s; .. SQL is in many ways exactly lile JavaScript. The only way to run your code where it needs to run, but with some things to be desired language wise. I wish more languages compiling to SQL were more common.
370.
by dagss 4y ago
It is not also gas, also less hydropower available than usual in Norway, Switzerland etc. due to unfortunate climate/weather past year. There is genuine energy shortage not only an issue of setting the right price.
371.
by dagss 4y ago
Entering and awakening from a coma comes pretty close...
372.
by dagss 4y ago
Electric vehicles use a lot less energy in total in the supply chain than gasoline cars (extracting and refining and transporting oil uses a lot of energy too, some of it electricity). So electric vehicles reduces the energy required. Longe
373.
by dagss 4y ago
I still disagree about your main point. Even the existence of software controlled lock features is not something that most people will even know about. I would say this stuff is "arcane knowledge for geeks", not "prudent assu
374.
by dagss 4y ago
I disagree with "it's a reasonable assumption that it might become locked again in the future". Unless this was very explicitly explained by Tesla to first customer. The default assumption is going to be "they were out o
375.
by dagss 4y ago
If only 10% of your work is thrown away consider yourself very lucky, I would think of that would be a minimum number in the industry... Myself I not too long ago did a 6 month crunch with the rest of my team on a product that was cancelled
376.
by dagss 4y ago
Here in Norway Torx is everywhere, almost all new screws and bits. It is like Torx is USB 3.0 and everything else is "legacy". Torx just works. Never an issue (except smallest bit size TX10 can wear out quickly). I guess disadvant
377.
by dagss 4y ago
Very interesting. In my domain of backend business rule + SQL development I think a perfect programming language would combine ideas from "Out of the tar pit" with event sourcing. So perhaps something in sort of the same direction
378.
by dagss 4y ago
FWIW I think the database is an integral part of one's service, and should often be included in unit tests (depending on the size of the unit of course). E.g. if you have CRUDObject and want to test GET and PUT of that...and that is th
379.
by dagss 4y ago
Total emissions of 100% is made up contributions of 1%+1%+1%+... By that logic there exists nothing that can help climate change...even if we are causing it. A bit like saying "shooting this one plane down out of 1000 enemy planes does
380.
by dagss 4y ago
The 25x number already includes this effect. Methane is much much more potent than CO2, but since it breaks down rapidly then over the course of a 100 years the average effect is 25x. So: if you first say "25x" then you cannot say
381.
by dagss 4y ago
2 things: A common error about CH4 is misunderstanding half-life vs CO2e calculations. The half life is 10 years but that does not make it a non-problem; a commonly used number is that CH4 is 25 more potent that CO2 -- but that number 25x i
382.
by dagss 4y ago
This proposal was 12 bytes and the feature that it is 16 chars in base64. UUID is more than 16 chars in base64.
383.
by dagss 4y ago
I agree that SQL vs git is not a perfectly solved problem, but I would argue that NoSQL vs git is an even harder problem where the state of the DATA does not necessarily match what your current code says -- you need to remember/comment
384.
by dagss 4y ago
YES! It is a shame one feels one has to fix organizational and coordination issues by introducing network barriers incidental to the real problems. I cannot wait for microservices to become unfashionable for cases where they are not solving
385.
by dagss 4y ago
We have a team to manage our Azure k8s. Blue/green clusters, switching traffic between clusters to be able to upgrade k8s, etc Definitely a lot of work.
386.
by dagss 4y ago
I meant in the context of 2-3 years before a rewrite I guess. Code with bugs can just sink your team in the first months after hitting production..
387.
by dagss 4y ago
A huge issue with the statefile IMO is storing secrets and API keys. We try to make sure EVERYTHING is done through service identities (Azure). No secrets in deploy scripts or resources. Terraform will happily generate and store passwords a
388.
by dagss 4y ago
Buggy code can be a real timesink for startups...the failures often cannot be ignored too long, they just sit and mature and compound some interest before they have to be fixed anyway. And writing bug free/low bug code is about experie
389.
by dagss 4y ago
PS I think microservices excel in making people FEEL productive (doing work that is not directly benefiting the company). I have personal experience with the same product built twice, once as a monolith by a small team that worked really we
390.
by dagss 4y ago
Microservices gets owned by different teams, teams get cemented, politics get in the way of refactoring. Game over. Sure, if you are a single team working on 10 microservices you can probably refactor with abandon without spending 70% of yo

More ›