337 karma · joined September 2, 2016
A classmate of mine, who now farms their family farm, still runs a large 4WD tractor that must be 50+ years old at this point. They have newer equipment, but the old stuff still gets used.
What I found was not great. So glad to see this idea getting a good write up.
Within a week I stopped because I could already feel pain in my kidneys. Having had a kidney stone before, and having had to pass one (thankfully small) one, I immediately stopped taking the Vitamin D since that the only lifestyle change I had made. Things subsided after that.
Should I need to take Vitamin D in the future I will be starting at a VERY SMALL dose and slowly working up. Kidney stones suck.
With Doobie you manually write your queries, and then map the results into the objects in your domain model. Nothing is generated for you. OTOH, nothing is hidden and you are free to write queries as optimized and specialized as you need. The real selling point of Doobie is a typesafe API for manipulating and combining queries, and fragments of queries, into larger wholes. This works very well when your application interfaces with a database it doesn't own.
With Slick you get access to a DSL that lets you layout how your tables look. From there Slick offers an api that let's you treat SQL tables as-if they are basically mutable collections, with Slick handling all the SQL generation itself. You also get DDL, so that you can automate db creation and upgrades. This work very well when your application owns and controls the database it is connecting to.
Both of these have diverged from that traditional ORM model. Slick bills itself as FRM, or Functional Relational Mapping. And Doobie is embedded queries on steroids.
I do not think that is accurate. The Obama administration sustained the growth from the previous administration. I do wish they had curtailed this growth, but c'est la vie.
My opinion is that virtue signalling is real, and, further, that "signalling" doesn't just have an effect on other people, it can change our own disposition.
The use of the phrase "virtue signalling" is sometimes applied in reverse, describing someone that is insufferably smug and exudes a sense of unearned moral superiority and ascribing those traits to their desire to signal their piety to others. Oddly, I find that a kindness as it means these undesirable traits have an external cause and can therefore be corrected.
Also, having only 2 Thunderbolt 3 ports seems a little light as well. I would hope to have had 4 ports at least.
Remote: Yes
Willing to relocate: No.
Technologies: Scala, Akka, http4s, cats, PostgreSQL, React, AWS
Résumé/CV: https://drive.google.com/file/d/1OJ4-OaUQCMx1W5_t3bVzg-bwrgf...
Email: _@markkegel.com
I'm looking for remote, or Dallas local, projects that are interesting and leverage Scala. Most recently I was part of a Dallas-based startup where I wrote and supported our entire tech stack. I enjoy working on hard problems and writing resilient and reliable software.
Please don't misinterpret me. The goal is to have fewer issues, not zero issues.
> Additionally versioning is needless if you have strongly typed events that get checked at compile time. Any time you need to add an abstract feature to the event architecture, the compiler would tell you what other part of the app broke as a result.
I disagree. Most type systems, especially those describing data, are really only good for checking syntactic consistency and not very good at semantic consistency. That is, it can tell if field changes from an Int to a String, but not if the content of a String field changes it's semantic, i.e. from a user id to an email address.
Lack of ability to validate content pervades wire-appropriate encodings.
That doesn't mean that session types aren't worthwhile, only that they attack the problem of safely representing one particular next-higher-level abstraction.
Session types also predicated somewhat on formal guarantees being something worthwhile. As an academic exercise I'm in favor, but in terms of having practical, working tools that I can use today that useful but lack formal guarantees, well I'd rather have good tools today rather than perfect tools never.
And that's my lament. I've yet to see good tools for building protocols.
The short story is that they valued the unlimited freedom for a single individual more than the general freedom of all individuals. In a sense, it's the finding and feeding utility monsters on the theory that that will maximize utility for society.
In this context of this article, I would prefer to version a protocol. That version subsumes the particular schema of the events used for that version of the protocol. If your protocol is well-designed then many of the assumptions of semantic versioning can be applied and relied on, so that parts of your system can speak an older version compatibly with a parts that speak a slightly newer version.
I really wish there was more support in the major ecosystems for creating protocols and a less obsessive focus on message encodings. Oh well.