amw-zero

11 ms·

121.
by amw-zero 3y ago
This is my favorite CS paper of all time. Reason being, it distills multiple different areas of CS down to one idea: state machines. Now I'm frequently able to map a complex idea down to a state machine, which makes all kinds of proble
122.
by amw-zero 3y ago
I think you should be able to read a 9 page paper. But here is a summary: https://ratfactor.com/papers/naur1 .
123.
by amw-zero 3y ago
For every person that says this, there's 5 people that say the opposite.
124.
by amw-zero 3y ago
I'm very happy to see continued investment into mutable value semantics. When I was writing Swift, it felt absolutely magical to have most of the guarantees of functional programming without the performance penalty and intermittent awk
125.
by amw-zero 3y ago
It’s not abandoned though. They turned it into office and retail space, and you can go there and just walk around and hang out for the day.
126.
by amw-zero 3y ago
Documentation: "is any communicable material that is used to describe, explain or instruct regarding some attributes of an object, system or procedure, such as its parts, assembly, installation, maintenance and use." That's a
127.
by amw-zero 3y ago
Can you look at which fields are required to make a value of type `Generic`, `GenericV2`, etc.?
128.
by amw-zero 3y ago
What would you call the ability of a type to communicate information such as the range of values that can be passed into a function?
129.
by amw-zero 3y ago
A perfect example of the limits of HTML rendering. It works for a large class of applications, but it's not the end of the line in terms of all UI.
130.
by amw-zero 3y ago
Well, "constraint" is a very abstract word. What you're describing are still constraints, they're just complex constraints. The type vs. no type argument is basically: what's the cutoff line for constraints that are
131.
by amw-zero 3y ago
I agree with the premise - type-level logic is still just logic, so why not unify the syntax? There's a specification / model checking system called TLA+. This is exactly how you specify types - just as predicates in the same logi
132.
by amw-zero 3y ago
That doesn’t seem like a fair characterization in all cases.
133.
by amw-zero 3y ago
You’ve invented lisp. The issue with meta programming is that it’s too powerful, in the sense that the transformations can’t be statically checked for typing rules.
134.
by amw-zero 3y ago
The pros of any type-level logic all boil down to automatically enforcing something that you want to be enforced. The key word being _automatically_. This can be frustrating in the moment sometimes, but other times a type can do two really
135.
by amw-zero 3y ago
I think that’s a major simplification of what’s going on in software development. Alan Kay invented OO, and everyone says the same thing about OO - that it’s over complicated and slows down development. And then everyone replies with, “well
136.
by amw-zero 3y ago
> & aims to avoid side effects by using pure functions I think this has always been an incorrect framing. Functional programming does not _avoid_ side effects purposefully. It simply doesn't have them without explicitly modeling
137.
by amw-zero 3y ago
Predicting the future is hard. People said this same thing about cryptocurrencies, no?
138.
by amw-zero 3y ago
The whole idea of machine learning / AI is to build functionality indirectly though, i.e. to build a system which evolves into another system over time. They are inherently meta-systems, so it does make sense to think of them different
139.
by amw-zero 3y ago
You just described science, and why you don't believe in science.
140.
by amw-zero 4y ago
Exactly. As in, the documentation doesn't actually stay in sync.
141.
by amw-zero 4y ago
You said: "Going slower today means we can go faster tomorrow". So I guess, relative to yesterday?
142.
by amw-zero 4y ago
Have you ever measured this alleged speedup when "tomorrow" comes?
143.
by amw-zero 4y ago
Sounds like an architecture decision record. Here's an example ADR template: https://github.com/joelparkerhenderson/architecture-decision... .
144.
by amw-zero 4y ago
What ways have you found for keeping the documentation in sync across frequent changes?
145.
by amw-zero 4y ago
Why does there need to be a successor to Heroku?
146.
by amw-zero 4y ago
There's not much of a choice if your company doesn't make money. Not paying employee paychecks also affects their engagement.
147.
by amw-zero 4y ago
Postgres is good
148.
by amw-zero 4y ago
> It can be a much simpler approach to building an application This is not related to hypermedia, this is related to server-rendering vs. client-rendering. Everyone knows that server-rendering saves on some code and JS. This is a tradeof
149.
by amw-zero 4y ago
No we're not, HATEOAS is a design pattern that no one uses. People use the web because it made self-publishing on the internet (which already existed) slightly easier.
150.
by amw-zero 4y ago
The only actual benefit I've ever been able to come up with for HATEOAS / "true" REST, is that it allows servers to evolve independently from clients. As in, you can change endpoints under the hood, but as long as the na

More ›