Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
wmanley
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
91.
▲
by
wmanley
3y ago
It’s worth a try. I’d recommend buying a separate spray for your nose though.
92.
▲
by
wmanley
3y ago
I think you've misunderstood the quote. The solution that the great engineer produces is effective, but may not be efficient nor elegant if it doesn't need to be. The point is that solving the problem (and maybe stopping there)
93.
▲
by
wmanley
3y ago
Here it is: https://github.com/id-Software/Quake-2/blob/372afde46e7defc9...
94.
▲
by
wmanley
3y ago
I don’t know about quake, but in quake 2 it consisted of a big list of: else if (strcmp(cmd, “somecmd”) == 0) somecmd() I remember reading it at the time and being inspired by the simplicity of it. It didn’t need to be more
95.
▲
by
wmanley
3y ago
> It's a weird example, because it moves listener creation elsewhere, which is not always possible (e.g. consider if the goroutine would be spawning an external program instead of setting up the listener of its own). Just addressing
96.
▲
The Economist's Ukraine war-fire model
(github.com)
2 points
by
wmanley
3y ago
|
0 comments
97.
▲
by
wmanley
3y ago
> Websockets require a central broker to pass messages through when you scale past one process I believe that this is one of the big advantages of SSE vs. WebSockets. Unlike websockets, an SSE connection is just an HTTP request, just on
98.
▲
by
wmanley
3y ago
The difference between this use case and bitcoin is algorithm mobility. All bitcoin miners must use the same algorithm and get the same result for it to work. This makes it very hard (read slow) to change the algorithm, so there's ti
99.
▲
Hypermedia on Whatever You'd Like
(htmx.org)
1 points
by
wmanley
3y ago
|
0 comments
100.
▲
by
wmanley
3y ago
See also: https://david.rothlis.net/declarative-schema-migration-for-s...
101.
▲
Climate change: Fossil fuel emissions from electricity set to fall – report
(bbc.co.uk)
1 points
by
wmanley
4y ago
|
0 comments
102.
▲
by
wmanley
4y ago
I see what you mean: https://regmedia.co.uk/2021/01/05/simple_sabotage_field_manu...
103.
▲
by
wmanley
4y ago
AFAICS you're doing all your inserts in a single transaction, unlike the article. Using transactions is better for performance, but probably less representative in this specific case.
104.
▲
by
wmanley
4y ago
and the minute hand?
105.
▲
by
wmanley
4y ago
Or make plans to anger them in ways that are useful to the gaming company. As you say: hating invigorates a community
106.
▲
by
wmanley
4y ago
Very neat. I'd really like something like this for systemd units. On embedded systems you want to have confidence that any permitted ordering will result in a working system - as there'll be no-one there to restart it if not.
107.
▲
by
wmanley
4y ago
Was discussed recently here: https://news.ycombinator.com/item?id=34350749
108.
▲
by
wmanley
4y ago
Guidelines for tests that reduce maintenance burden rather than add to it: * Test the externally visible useful properties of your system, rather than implementation details. Related: don’t bother with mocks unless there’s no other way * Ke
109.
▲
by
wmanley
4y ago
I am of the opinion that the true value of TDD is that tests get written at all. I suspect that in practice the tests tend to get written at roughly the same time as the code, rather than strictly before.
110.
▲
by
wmanley
4y ago
On a related note: I think that deterministic generating something based on a git commit and then later diffing the results across commits is in general a very useful technique. Our builds work similarly. We build our software into (several
111.
▲
by
wmanley
4y ago
IMO The real value in tests is making sure you don’t break things later, rather than for getting your current code working.
112.
▲
by
wmanley
4y ago
There were other advantages to our new approach too: because all the running of the code is happening server side it is both easier and faster. Easier because you don’t need to have a complete development environment available on the machi
113.
▲
by
wmanley
4y ago
We used to use a similar approach for testing page objects in stb-tester. It was called stbt auto-selftest (it has since been removed). It would run your page objects against canned screenshots and generate a Python doctest capturing the be
114.
▲
by
wmanley
4y ago
I wrote a little bit about this a couple of years ago: https://blog.williammanley.net/2020/05/25/unlock-software-fr... gittup[1] implements part of this idea, but without the distributed bit. bazel[2] implem
115.
▲
by
wmanley
4y ago
Easier said than done. You can already have: unsafe fn new_in_place(out: &mut MaybeUninit<MyType>) But you require unsafe code both to implement it (to project MaybeUninit) and to call it. For it to be safe to call the t
116.
▲
by
wmanley
4y ago
There's some ugly hacks that may or may not help here: https://www.reddit.com/r/rust/comments/xxhp3s/perhaps_not_a_... r#box!(make_my_elem()) This crate is marked as deprecated because appa
117.
▲
by
wmanley
4y ago
I don't think it is the future - but not because of the technology. Things in the browser have proven hard to monetize, unlike app stores/steam/consoles which have been built to enable selling.
118.
▲
by
wmanley
4y ago
Something I loved about that game was that stopping didn't make you safe - if you stopped for too long the aliens would come and find you. This lead to a intense experience where you had to keep going - even when terrified - because s
119.
▲
by
wmanley
4y ago
I really like the idea of storing logs in parquet format in S3. It's something I've wanted to play with for a long time, but never have had a use-case. I'm also a big fan of Rust. I imagine you've seen apenwarr's
120.
▲
by
wmanley
4y ago
Are you using S3 Select[1]? [1]: https://aws.amazon.com/blogs/aws/s3-glacier-select/
More ›