adamkl

21 ms·

151.
by adamkl 6y ago
I don't have as much experience working with Nest.js as you do, but I can see some validity in some of the things you mention. Nest.js tries to have "answers" for everything (i.e. CQRS, MQTT, Kafka, etc., etc., etc), but I do
152.
by adamkl 6y ago
Its true that, by default, you use a Class when wiring up the DI container because as you guessed, the interfaces are erased during transpilation. You can still achieve the loose coupling of DI by using custom providers [0]. Basically, this
153.
by adamkl 6y ago
Nest.js is a great framework, with excellent documentation, but it can be quite heavy weight (from a coding and concepts perspective) and alienating to JavaScript devs without a background in C#/Java. Its basically Spring/.Net MVC
154.
by adamkl 6y ago
I agree that it doesn't have to be a trade-off, but that mindset might explain why there is less focus on creating one-click installers. An example would be Clojure's newish approach to managing projects via the CLI and deps.edn.
155.
by adamkl 6y ago
I've posted this quote before, but it might help explain why making Clojure easier to get into maybe hasn't been a priority for Hickey et al. So we need players. I would rant here, but I won't. But look at this guitar player
156.
The Evergreen Cache(medium.com)
2 points by adamkl 6y ago|0 comments
157.
Unlocking Data-Driven Systems(youtube.com)
2 points by adamkl 6y ago|0 comments
158.
Luigi Micro Front End Framework(luigi-project.io)
2 points by adamkl 7y ago|0 comments
159.
by adamkl 7y ago
the API is literally a query language for the DB No, SQL is literally a query language for the DB. The API is the contract you define for how people with interact with your application. While some people may choose to model this aft
160.
by adamkl 7y ago
I think this looks very cool, but this quote concerns me: If you’re into laziness and magic (who isn’t?) Magic is great until you run into an edge case, or try to do anything complicated. Then it tends to bite you in the ass. I can s
161.
by adamkl 7y ago
I always hesitate to model an externally facing API to match the underlying database schema because you end up coupling consumers of the API to its internal implementation. Mind you, I'm coming from an enterprise background where syste
162.
by adamkl 7y ago
True. I actually thought about the same 'if' special form when formulating my response (I've been playing a lot with Clojure lately, and your other_function looks a lot like a functional conditional when compared to an if&#x2
163.
by adamkl 7y ago
The premise is not that there are no dependencies of any sort, or that you aren't allowed to pass complex structures from one to the other. Its more about splitting logic (and by logic, he is referring to code with multiple, branching
164.
by adamkl 7y ago
I came across an article a few weeks ago [1] that distils the idea of this architecture into a very simple pattern, stratified design, or the “Integration Operation Segregation Principal”: “A function either integrates or operates, it eithe
165.
by adamkl 7y ago
It’s all about the right tool for the job. I always push this approach when developing applications, but I work in large enterprise where performance often isn’t critical, but applications can live on for _decades_. Should you use this appr
166.
by adamkl 7y ago
Rich Hickey has a pretty interesting take on this very topic where he compares programming languages to instruments, and how instruments aren’t for beginners. How it takes work to become good at playing an instrument, and how that isn’t a b
167.
The Integration Operation Segregation Principle (IOSP)(medium.com)
3 points by adamkl 7y ago|0 comments
168.
by adamkl 7y ago
A interesting article that presents a very functional approach to design without mentioning functional programming. I've been trying to get more people adopt this approach ever since watching this talk by Gary Bernhardt a while ago. [1
169.
Stratified Design over Layered Design(medium.com)
9 points by adamkl 7y ago|2 comments
170.
by adamkl 7y ago
React wrapper doesn’t do much, and it is very easy to port to other UI frameworks. Here’s a follow-up post with a gist of what the React integration looks like. https://news.ycombinator.com/item?id=22294087
171.
by adamkl 7y ago
https://news.ycombinator.com/item?id=22294087
172.
by adamkl 7y ago
We keep things very simple. Maybe that will have to change as the code base grows, but for now it works and it easy to grok. On start of the application we create singletons of our state machine backed services, and manage the dependencies
173.
by adamkl 7y ago
From my view point, we “shoe-horned” a React UI into a well-established pattern for building an application. I guess it depends on the vintage of the developer. I would argue that Redux is an idiosyncratic technique for state management, an
174.
by adamkl 7y ago
Just xState. Each machine is responsible it’s own piece of the global state pie by using its internal `context`. This allows a similar approach to redux’s actions and reducers (or events and `assign` for xState), but each machine can focus
175.
by adamkl 7y ago
To manage state in our React application, we have a "service layer", just like you’d see in a server side application, only these are based on state machines (reactive services based on RxJS observables works as well). We also cre
176.
The Clojure Mindshare(groundedsage.dev)
4 points by adamkl 7y ago|0 comments
177.
by adamkl 7y ago
This sounds very similar to what we've been doing with XState[1] and React. We have a "service layer" for React made up of state-machine-based services (although reactive services based on RxJS observables works as well). We
178.
by adamkl 7y ago
If you are flying solo, then sure, I can see the appeal, but for most(?) of us, that hand-tailored language needs to be learned by everyone you work with, and anyone who might need to work on your codebase in the future. And it’s unlikely t
179.
by adamkl 7y ago
Yes! Yes! Yes! I've been preaching this approach ever since watching Gary Bernhardt's talk on "Boundaries" [1]. Splitting conditional logic from dependencies makes code so much easier to test. If you can do that, there&#
180.
by adamkl 7y ago
The issue that I find with JavaScript (which I use on a daily basis) is that it has become a "kitchen-sink" language. Every time it gets new additions to "close the gap" with some other language, it gains more ways to do

More ›