Explore >> Select a destination
|
You are here 
|
nickhayden.com | ||
| | | | |
rohan.ga
|
|
| | | | | Recently I have been working on what I guess is called an LLM agent, but it's more just building more ergonomic tools for myself to use LLMs in my life. The code base keeps growing, and I use it to help write itself. What I have noticed is that the patterns I have applied for making code more intelligible to LLMs also apply to making code more intelligible for humans. I think the reason for this is that LLMs can only successfully hold so many details in their context window, and we can only hold so many details in our mind. | |
| | | | |
blog.gougousis.net
|
|
| | | | | ||
| | | | |
vladikk.com
|
|
| | | | | Let's do a little experiment: try to explain the gist of Domain-Driven Design to someone who has no clue about it. This, especially doing it succinctly, is not easy. Heck, I struggle with it myself. Bounded contexts, entities, domain events, value objects, domains, aggregates, repositories... where do you even start? To find the order in the apparent chaos, I want to analyze the DDD methodology from a rather unusual perspective - by applying Domain-Driven Design to Domain-Driven Design itself. After all, this methodology is intended to deal with complex domains, isn't it? | |
| | | | |
cassidoo.co
|
|
| | | Today is the 100th Jumblie puzzle day! | ||
