prospero

5 ms·

1.
by prospero 1y ago
My point is that the creator/user dichotomy exists at every level of software.
2.
by prospero 1y ago
Show me a software developer who isn’t an end user for someone else’s code.
3.
Complexity as Entropy(explaining.software)
2 points by prospero 2y ago|0 comments
4.
by prospero 2y ago
Here’s one in Java: https://github.com/lacuna/bifurcan/blob/master/src/io/lacuna...
5.
The Sudoku Affair(explaining.software)
153 points by prospero 2y ago|43 comments
6.
State and Trace(explaining.software)
1 points by prospero 2y ago|0 comments
7.
Structuralism(explaining.software)
2 points by prospero 2y ago|0 comments
8.
Senior Developer Agents(explaining.software)
1 points by prospero 2y ago|0 comments
9.
Senior Developer Agents(explaining.software)
3 points by prospero 2y ago|0 comments
10.
Platforms Need New Building Blocks(junctionlabs.io)
11 points by prospero 2y ago|0 comments
11.
The Death of the Architect(explaining.software)
5 points by prospero 2y ago|1 comments
12.
Making things better(explaining.software)
2 points by prospero 2y ago|0 comments
13.
Intent and Implication(explaining.software)
3 points by prospero 2y ago|0 comments
14.
Structures as Paths(explaining.software)
3 points by prospero 2y ago|0 comments
15.
Decoupling in Depth(explaining.software)
4 points by prospero 2y ago|1 comments
16.
by prospero 2y ago
Yes, and that is used as an example for the general point: a network transparent API doesn’t help us understand the network when it inevitably fails.
17.
by prospero 2y ago
The point is that an interface should help you to both ignore and understand the underlying implementation. I'm not sure I understand your point about data and transport, since most interfaces (e.g. names) don't touch the netwo
18.
The Simplicity of a Limb(explaining.software)
1 points by prospero 2y ago|0 comments
19.
The Simplicity of a Fractal(explaining.software)
3 points by prospero 2y ago|0 comments
20.
Coupling as Co-Explanation(explaining.software)
1 points by prospero 2y ago|0 comments
21.
Explaining Software Design: A Brief Introduction(explaining.software)
2 points by prospero 2y ago|0 comments
22.
Sense and Structure: Towards a Textual Analysis of Software(youtube.com)
1 points by prospero 4y ago|0 comments
23.
Designing a Framework for Conversational Interfaces(microsoft.com)
2 points by prospero 5y ago|0 comments
24.
Designing a Framework for Conversational Interfaces(microsoft.com)
11 points by prospero 5y ago|0 comments
25.
by prospero 6y ago
It's very plausible that these techniques could be used to fix the output of a CSG library that uses floating point math, but I'm not sure what the specifics would look like. If anyone has ideas in that vein, I'd be very int
26.
by prospero 6y ago
Hi, author here. I looked into that side of things, but CGAL only offers exact precision implementations for lines and circular arcs. The fact that Bézier curves are left as an exercise for the reader is further proof of the disconnect betw
27.
Better Geometry Through Graph Theory (2018)(ideolalia.com)
161 points by prospero 6y ago|33 comments
28.
by prospero 8y ago
By forcing the GC to run in between tests, basically. The README for the benchmarking tool describes it in more detail: https://github.com/hugoduncan/criterium .
29.
by prospero 8y ago
I tried to include these, but it wasn’t immediately obvious how to construct them from outside Scala without CanBuildFrom. If anyone wants to open a PR or even provide a few hints, I’d be happy to update the benchmarks.
30.
by prospero 8y ago
Guava’s “immutable” collections are effectively read-only indices, and do not support efficient updates.

More ›