eandre

34 ms·

91.
by eandre 6y ago
I don't think they're the same, but I do think low-code has become synonymous with incredibly special-purpose tools that barely resemble programming. We've been building Encore [1] to improve on this. It's a backend fram
92.
by eandre 6y ago
Awesome! I have lots of fond memories from the days of writing World of Warcraft addons (CTMod, CT_RaidAssist, ...). Great to see the community is still going.
93.
by eandre 6y ago
Thanks, it's back up now.
94.
by eandre 6y ago
Unfortunately not – this is what building modern cloud based software is like! This software complexity crisis is what we're trying to fix with Encore [1], if you're interested. [1] https://encore.dev
95.
Git clone over gRPC(encore.dev)
3 points by eandre 6y ago|0 comments
96.
by eandre 6y ago
I've been working on something that might be interesting to you [1]. It gives you the full flexibility of a programming language while removing all the boilerplate surrounding your business logic through static analysis. Have a look at
97.
by eandre 7y ago
Thanks, that means a lot! Unlike other offerings the focus is really on the development experience, hence the focus on ease-of-use and simplicity as you say. The goal is to provide a best-in-class developer experience; the serverless part i
98.
by eandre 7y ago
Great article. Working on my own startup ( https://encore.dev ) I also feel the urge to measure my progress in terms of output, not outcomes. I have to constantly remind myself that what matters is the outcome. Focus on producing
99.
by eandre 7y ago
I can really recommend "How to Take Smart Notes" [1] by Sönke Ahrens. It's made a real difference for me. Ignore the self help-sounding title and give it a chance. [1] https://www.goodreads.com/book/show
100.
by eandre 7y ago
Wow, this looks great! Will check it out immediately tomorrow morning!
101.
by eandre 7y ago
I think the confusion comes from that not everybody thinks of "passing data to the database layer" as an output, but only an input to the next layer. If you think of this input as an output from the previous layer, then your advic
102.
Service-Oriented Architecture Tradeoffs(encore.dev)
2 points by eandre 7y ago|0 comments
103.
by eandre 7y ago
That's a reasonable point. Maybe I should update the post to guard it with a mutex to discourage newcomers from doing something subtle. Thanks for the feedback!
104.
Advanced Concurrency Patterns in Go(encore.dev)
5 points by eandre 7y ago|2 comments
105.
The Blank Page(encore.dev)
1 points by eandre 7y ago|0 comments
106.
by eandre 7y ago
I agree with the article and am facing the same challenges in my own startup: how much, and what, to open source? It's a platform that offers a simpler way of building serverless backends [1], and so it's naturally targeting devel
107.
by eandre 7y ago
Good point, I didn't necessarily mean simpler primitives but rather "higher-order" primitives. We need to move to a higher level of abstraction on top of a new layer of primitives (even if those primitives themselves are more
108.
by eandre 7y ago
This article is conflating the benefits of a particular way of doing implementation, and JWT as an implementation of that approach to authentication. That's dangerous because it n discourages people from thinking carefully about the se
109.
by eandre 7y ago
I agree! But isn't that the beauty in abstractions? If you are using an unmaintained file system with a CVE, the beauty of the POSIX interface means you can just migrate to another file systems and basically all applications would just
110.
by eandre 7y ago
I agree that the parts are needed and the complexity essential. What I mean is that we need higher-order primitives that abstract away and shield us from the conplexity. Just like we don't need to spend time crafting TCP packets by han
111.
by eandre 7y ago
I used TailwindCSS which I can highly recommend, but the design and components were all custom made by myself :)
112.
by eandre 7y ago
I share Nelson's belief that we can conquer the rampant complexity in modern software applications. I'm generally in favor of the approach he's advocating for -- working to understand the layers of the stack rather than treat
113.
by eandre 7y ago
That was a quite interesting read; I hadn't heard that analogy before. It's a shame the formatting of the page really makes it difficult to engage with the content.
114.
by eandre 7y ago
That's the Baader-Meinhof phenomenon talking [1] :) [1] https://science.howstuffworks.com/life/inside-the-mind/human...
115.
Writing a Reliability Strategy (2019)(lethain.com)
2 points by eandre 7y ago|0 comments
116.
by eandre 7y ago
This is certainly true, but it strikes me that the solution must be a move towards simpler primitives so that managing a cloud-based piece of software doesn't require so many moving parts.
117.
by eandre 7y ago
I really appreciate the approach of building something simple (in user experience but also in implementation). These days it's so easy to get sucked in and end up spending months setting up Kubernetes clusters and the "that won&#x
118.
by eandre 7y ago
Liste looks great! I've been looking around for a better tool to aid in note-taking after all the posts around this space over the last few weeks. Will keep an eye on it and good luck with the launch. How did you decide to start a comp
119.
by eandre 7y ago
This is good advice. I've been working on a side project for almost a year now [1]. It's a constant struggle with the pressure to reach a certain amount of users or impact, when at the end of the day I've just been building i
120.
by eandre 7y ago
I believe this is what Roam[1] is kind of built for, whether they intended it or not. I haven't used it but was inspired to take another look at it after this article. [1] https://roamresearch.com/

More ›