Well, take a look at the dates of when Postgres was created and when SSDs become available. Better, find articles about internal algorithms, B-trees, times of operations like seeks etc. The Postgres was initially written with disk operation timings in mind, and the point is that's changing - and I haven't heard of Postgres architecture changing with that.
That blog post is very light on details can be condensed to a single line/paragraph. LSM trees are more efficient for SSDs and modern databases use them.
I don't know enough to comment yet but will go read about it.
(Not gp) I read this book more than a decade ago, when I was very inexperienced. The thing I remember the most, and I think the most valuable to me, is the idea of defining a shared domain language with the business domain experts, with a clearly defined meaning for each concept identified. For instance, what a "frozen" account exactly means, what's the difference with a "blocked" account. These are arbitrary, but must be shared among all the participants. This enables very precise and clear communication.
I think that's the core idea. The layer on top the idea that that domain language should be expressed in an isolated core layer of your code. Here lies all your business logic. On top of that, you build application layers to adapt it as necessary to interact with the outside world, through things like web pages, emails, etc. as well as infrastructure layers to talk to your database, etc.
DDD is about a lot more than just defining what it calls ‘ubiquitous language’. It helps you figure out how to constrain which concerns of the language used in one domain need to affect how other domains think about those things - through a model it calls ‘bounded contexts’. Like, in your fraud prevention context, ‘frozen accounts’ might have all sorts of nuances - there might be a legal freeze or a collections freeze on the account, with different consequences; outside the domain, though, the common concept of ‘frozen’ is all that’s needed. DDD gives you some tools for thinking about how to break your overall business down into bounded contexts that usefully encapsulate complexity, and define the relationships between those domains so you can manage the way abstractions leak between them.
No silver bullet, of course, but, like most architectural frameworks, some useful names for concepts that give you the metavocabulary for talking about how to talk about your software systems.
In highly regulated industries like banking or other highly-secure environments, it’s a gradient between an internal wiki or FAQs etc, to what you have as an example of something more expansive and explicit, to an entire book, to an entire department or business unit for more important concepts that may vary between jurisdictions or be less explicitly defined, but no less important or impactful to the running of the business or group.
I just bought a nice Asus Zenbook and first I did as soon as I received it was installing pop os. I keep my old windows notebook near by in case I need something I can't do in the Linux machine, but its use is more and more infrequent.
SignaGel is a conductive gel. It'll mostly stay in place and stays wet a lot longer than the sponges, but it is a little gross. Get it from a medical supplier rather than Amazon, where the individual tubes are massively overpriced. You might also be interested in 10-20 paste, which is a sticky conductive putty. It's a bit more expensive, but it stays put. Instead of the bands, you can also try a neoprene "swimcap" style holder.
Some of the tingling is unavoidable--the currents are driving fibers in the skin--but you can do a few things to reduce it. First, make sure there's good contact with the scalp: fully coat/saturate the electrodes and make sure they're pressed tight. The lower the impedance, the better. because the "dose" is specified in terms of current and you want to use as little voltage as possible to deliver that. Second, gradually ramp up the current instead of just switching it on/off. The sensation will diminish a bit over time anyway, so slowly increasing the current will make it more bearable. The difference between on/off and a 30 second ramp is really striking! We've used a topical anesthetic to block sensations, but it's a giant pain--it takes an hour to kick in and you need to tightly cover it too. Finally, be careful because you can burn the skin!
A great suggestion, thank you. The issue with this approach is that I have longer hair and a gel may have more difficulty bridging contact between the device and my scalp, plus it likely requires more effort to clean up. I might look into this.
