mzaks

5 ms·

1.
Me and ClaudeCode swapped Zed's storage layer for Dagr(mzaks.medium.com)
1 points by mzaks 16d ago|0 comments
2.
Let's talk about structured logging(medium.com)
1 points by mzaks 17d ago|0 comments
3.
We swapped Zed's storage layer for Dagr(gist.github.com)
2 points by mzaks 18d ago|0 comments
4.
Show HN: Untapped potential of fixed-size buffers(mzaks.medium.com)
1 points by mzaks 21d ago|0 comments
5.
by mzaks 4y ago
Not a data structure, but a nice concept for very fast search on immutable pre sorted array, eytzinger order. I did some experiments, it is about 2-3x faster then binary search. https://medium.com/swlh/binary-search-vs-
6.
by mzaks 6y ago
True, I guess it all boils down to ease of use (convenience). You can build a system which accepts schema + data and build dash boards and data relevant relevant processing + optimisations, but that results in a much more complex system wit
7.
by mzaks 6y ago
If you need a language support for FlexBuffers please create an issue on GitHub repo. I ported it already to Swift, C#, Dart, Python, JS (is in review). If I am familiar with the language you need, it will take me just a couple of days to p
8.
by mzaks 6y ago
One use case where schema-less is the way to go, when you provide the infrastructure, but have no „ownership“ of data it will be used for. E.g. you build a logging or analytics tool where customers can send arbitrary data. Or a document dat
9.
by mzaks 6y ago
You forgot Python and C# :). Plus a Unity3D specific version, which is battle tested in a game with more than half a million downloads ;).
10.
Alternative way of building reactive, testable, easy to evolve apps with Flutter(medium.com)
1 points by mzaks 7y ago|0 comments
11.
LIDL – Interface Definition Language for AWS Lambda(medium.com)
4 points by mzaks 8y ago|0 comments
12.
Extending JSON with key paths(medium.com)
1 points by mzaks 8y ago|0 comments
13.
Why I hate code challenges(hackernoon.com)
4 points by mzaks 8y ago|0 comments
14.
by mzaks 10y ago
The good thing about any narrative, it resonates with different people on different levels. The blog post is in deed titled "10,000 times faster Swift". I though it will be a catchy title even though 6 seconds to 0.35 ms is not fa
15.
by mzaks 10y ago
I was suspicious, I just could not put my finger on it :) for i in 0..<iterations { let result = flatuseStruct(outputData, start:i) assert(result == 8644311666 + Int(i)) total2 = total2 + UInt64(result) } this r
16.
by mzaks 10y ago
This makes sense! Changed the iteration to: for i in 0..<iterations { let result = flatuseStruct(outputData, start:i) assert(result == 8644311666 + Int(i)) total2 = total2 + UInt64(result) } now result is around
17.
by mzaks 10y ago
Performance test run on Travis CI in a virtual machine https://travis-ci.org/mzaks/FlatBuffersSwift function called for decode+use+dealloc https://github.com/mzaks/FlatBuffersSwift/blob/m
18.
by mzaks 10y ago
I Updated the run bench function https://gist.github.com/mzaks/e3a2dc7ccdfc2397bc26c55eb6dc8a... the output is now: Eager run ================================= 1557 ms encode 264 ms decode 34 ms use 206 m