beders

6 ms·

31.
by beders 1y ago
If you opt for non-human-readable wire-formats it better be because of very important reasons. Something about measuring performance and operational costs. If you need to exchange data with other systems that you don't control, a simpl
32.
by beders 1y ago
You can get basically all variations of async coding with Clojure a la carte.
33.
by beders 1y ago
They are hallucinating word finding algorithms. They are not "empathetic". There isn't even a "they". We need to do better educating people about what a chatbot is and isn't and what data was used to train it.
34.
by beders 1y ago
It is tempting, maybe a good first step, but often not expressive enough. Especially and particularly attributes/fields/properties in an enterprise solution. You want to associate various metadata - including at runtime - with a _
35.
by beders 1y ago
You need a REPL to truly read Clojure code. Could be a weakness or could be a strength. In my day to day work I consider a strength since I’m working at the REPL the whole day anyways
36.
by beders 1y ago
I always urge software architects (are they still around?) and senior engineers in charge of APIs to think very carefully about the consumers of the API. If the only consumer is your own UI, you should use a much more integrated RPC style t
37.
by beders 1y ago
I think that's a prime example showing that token prediction simply isn't good enough for correctness. It never will be. LLMs are not designed to reason about code.
38.
by beders 1y ago
I wish people would be a little bit more precise. There is no type safety. There must be data validation on the endpoint but anyone can send anything and if you rely on your front-end to send you the right data shapes and valid values wit
39.
by beders 1y ago
Zig just caught up with the practice that runs rampant in JavaScript land ;)
40.
by beders 1y ago
This is what happens when a V also wants to do the M and the C. But I would say most front-end libraries are insane: Their job is to manipulate a tree structure which is kinda slow (still?). Who would have thought that this problem has such
41.
by beders 1y ago
All correct, but remember, especially in the bay area: you always meet twice in life. So be careful burning down those bridges if meeting with HR went sideways.
42.
by beders 1y ago
if you have control over all the consumers of your API, run whatever makes you fast and keeps you safe. If you want others to play with your API: JSON here we come.
43.
by beders 1y ago
Re: HTTP Flows. As we know networks never fail, read timeouts aren't a thing and error handling is not necessary as networks never fail and read timeouts aren't a thing and error handling is not necessary as networks never fail an
44.
by beders 1y ago
#[table(name = person, public)] pub struct Person { name: String, } No, just say no. Do not conflate your relational database schema with however you treat that data in your app. You want explicit control, not ann
45.
by beders 2y ago
yeah, I wouldn't recommend trying to do this with pure Java but you could pass around method handles for that purpose. You certainly would want to use an `interface` and that means you need an object. It could be an object that has no
46.
by beders 2y ago
The issue is names. Every darn little thing in Java needs a name. If there is no good name, that's a hint that maybe you don't need a new type. Obligatory Clojure example: (defn full-name [{:keys [first-name last-name]}]
47.
by beders 2y ago
I found it quite disappointing to find a marketing piece from Nikki. It is full of general statements that are only true for a subset of solutions. Enterprise solutions in particular are vastly more complex and can't be magically made
48.
by beders 2y ago
> Whatever framework you choose will be obsolete in 5 years. Reagent was born in 2013 and still works just the same in 2025. And it adapted to React changes quite nicely. You won't have to refactor Reagent code from 10 years ago. Te
49.
by beders 2y ago
yes, I mistyped. I wanted to take the File object from writeString foo = writeString(file, "Hello world!"); g(foo);
50.
by beders 2y ago
I'm missing something on the discussion of correctness for Linear types: let file: File := openFile("test.txt"); writeString(file, "Hello, world!"); g(file); If I have any other function 'g
51.
by beders 2y ago
And here I am flinging hiccup and Reagent for years now without any major changes. Reagent has been around since 2013. They even survived the transition to functional React components without major changes. The hiccup I wrote 5 years ago i
52.
by beders 2y ago
I can only assume this comes from an observation that once your product matures, the static types become more apparent and you have a better idea how flexible your data modeling should be. i.e. we are gradually adding more runtime type-chec
53.
by beders 2y ago
That's probably the most incorrect analogy. If I have objects, I can change their state in the middle of any bookkeeping. There should be a different name for functional programming with mutable objects.
54.
by beders 2y ago
I'm surprised people think they have any kind of privacy - especially when using free services. They are not free. You pay with whatever data can be extracted from your devices and behavior. Also, there's a looong list of companie
55.
by beders 2y ago
The migration guide is massive. Threlte 8 is yet another example of how little backward compatibility matters to JS library developers and adopting such a library can be a costly endeavor. Backward compatibility is readily and easily sacrif
56.
by beders 2y ago
I think this is a valid observation and the affected apps should either add auth to resources they control - shared or not - or use an UUID to store it so names can't be guessed. This only works because the attacker knows the URL.
57.
by beders 2y ago
These are great examples of difficulties people will encounter in all popular statically typed languages sooner or later. I find the solution presented interesting but it is limited to the 3 operations mentioned. The alternative to this run
58.
by beders 2y ago
We've been down this road before many times. On adoption things are simple and clean. Then your product becomes more complicated and your requirements for data handling outgrow what a tool like mizu can offer. Then you are facing a cho
59.
by beders 2y ago
It is important to note that employing any workflow engine needs careful examination of the benefits vs. drawbacks. You will need full and complete control over workflow orchestration, restarts, deletes, logging, versioning etc. Your steps
60.
by beders 2y ago
It is a good reminder for front-end devs that security-through-obscurity is not sufficient. It never has. Reminds me of a security company that claimed they could force a watermark onto any content in their web-front-end. Turns out it was a

More ›