mrkeen

42 ms·

961.
by mrkeen 2y ago
> Then it argues that tail call optimisation is bad! I didn't think I'd find this, so I went digging. Sure enough: The disadvantage of tail recursion is that it requires rearranging your recursive function so that the last
962.
by mrkeen 2y ago
> What does secure attachment to reality look like? It means feeling safe to experience whatever arises. It means trusting that reality is fundamentally reliable. In other words, up is up and down is down. Water is not wine. Reality do
963.
by mrkeen 2y ago
> The conventional explanation for what’s freezing young adults in place is that they can’t afford to grow up, given rising inflation and ballooning housing costs. Yet this doesn’t quite explain what’s going on. > Median wages for ful
964.
by mrkeen 2y ago
Try once again to make small inroads into frontend. I took another look at the Android SDK (and holy crap...) So now I'm bouncing around the web looking at various ways I can use my android phone to interact with backend code I've
965.
by mrkeen 2y ago
I don't know of any way to replicate data ("solve the underlying problem") aside from a replicated log. It's like git solving the problem without commits, or banking solving the problem without transactions.
966.
by mrkeen 2y ago
I'm not sure what counts as the "first 25 years", but Dining Philosophers is from 1965.
967.
by mrkeen 2y ago
Here's a DSL example https://copilot-language.github.io/
968.
by mrkeen 2y ago
I read "just sync the data" as naively doing reads over here and writes over there, and hoping that the two sources of truth don't diverge. Queues and event processing are a necessity to do it right.
969.
by mrkeen 2y ago
> Replace "database mocks" with ANY <X> distributed API service calls in your execution flow and ... so far so good - you're inviting the comparison of "use a real database" to "use a real X", whe
970.
by mrkeen 2y ago
Yep, I keep the dead events around, for when the constraints behave incorrectly. I also keep the live events around, in case there isn't a constraint exception, but something else goes wrong - upstream/user error causing deletion,
971.
by mrkeen 2y ago
> with a mock you have to explicitly specify "when called with this return that". Riiiight, no I've always hated that Mockito way of doing things. I find wrapping a hashmap avoids the need for explicit when-this-then-that
972.
by mrkeen 2y ago
My coworkers call it "data integrity". At best it's a local maximum for consistency. Right now it's how we reject true facts about the business. Our partner bank tells us a customer deactivated? Our database says &qu
973.
by mrkeen 2y ago
My take is that your business logic shouldn't know about your storage tech. (Like, dependency inversion 101 right?) > Still, using an in-memory db is way better than mocking, the tests are not coupled to the implementation details&
974.
by mrkeen 2y ago
Two points: 1) The subtle issues with constraint violations, default values and indexes are part of the RDBMS, not the testing strategy. The article suggests stepping on these rakes in test so that you hopefully don't step on them in
975.
by mrkeen 2y ago
CQRS is great, (but I've not heard it linked to DDD before this article.) If you have an SQL schema and your domain is money, some numbnuts is going to get the rounding wrong, accidentally calculate with floating point, forget to store
976.
by mrkeen 2y ago
Good example of a bad abstraction. If you're speaking the language (or "abstraction") of sets, you should see certain terminology: union, intersection, disjunction. These words are not part of the Java Set interface.
977.
by mrkeen 2y ago
It might not give enough examples to show you how to do something right, but I think it's enough to warn against doing something wrong, namely introducing an indirection that doesn't provide any of the benefits of abstraction. My
978.
by mrkeen 2y ago
It starts with a strong point that abstraction is not indirection, but then slips back into using the terms interchangeably.
979.
by mrkeen 2y ago
Why rob a bank when you can pickpocket a guy walking into the bank instead? Anyway Linux has 62.7% share of servers https://en.m.wikipedia.org/wiki/Usage_share_of_operating_sys...
980.
by mrkeen 2y ago
Yeah but they're a statistical anomaly in the field. For every example of encapsulated state, there's probably 9 more examples of global state which is called encapsulated. And what is managed state? I can think of two examples t
981.
by mrkeen 2y ago
> Stop re-inventing. You don't need NoSQL. I need somewhere for my objects to live. Objects are not relations. Scattering their data across five tables, to fit the relational model, so I can later JOIN them together again, has to
982.
by mrkeen 2y ago
[flagged]
983.
by mrkeen 2y ago
See join points: https://dl.acm.org/doi/pdf/10.1145/3062341.3062380
984.
by mrkeen 2y ago
Can you not move to c99?
985.
by mrkeen 2y ago
Python 2, Python 3? Types or no types?
986.
by mrkeen 2y ago
Weird, I read that between the lines of parent's post. Of course local reasoning precludes global effects.
987.
by mrkeen 2y ago
I think the 'Layered Architecture' section is all over the place. There are a lot of terms thrown around with pretty loose definitions - in this article and others. I had to look up "layered architecture" to see what ot
988.
by mrkeen 2y ago
The comment was reaffirming immutability's benefits, against the previous comment which said traditional packaging provides a better tradeoff.
989.
by mrkeen 2y ago
I've been doing mostly backend dev, and watching from the sidelines as buzzwords come and go: vmware, virtualbox, puppet, vagrant, ansible, zookeeper, mesos, docker-compose, chef, etcd, docker-swarm, terraform, helm. I don't know
990.
by mrkeen 2y ago
> Pointers are literally 64bit ints... And converting them to an index is extremely quick if you want to store an offset instead when serialising. This implies serialisation/deserialisation passes, so you can't really let bigge

More ›