tychoish (sam)
@tychoish
Followers
829
Following
3K
Media
136
Statuses
12K
Writer. Brooklyn. Coffee. Databases. Engineering, (Common Lisp, Go, Emacs, Arch Linux), @GlareDB. Shape Note Singing. Queer (he/him).
Eastern Time
Joined February 2007
I'm here less these days, but you can hit me up on telegram https://t.co/iaLwnopgJA I've also made this telegram channel where I've been putting the things that I'd otherwise put here: https://t.co/0Vqt2Q0mXS Blog announcements will continue.
1
0
2
I'd like someone to make a rust library (Go would also be interesting) that would make it easy a binary shebangable.
0
0
0
the working definition of "how big is big data" has to be whatever the maximum EBS volume size is.
3
0
2
Want to build a @getdbt pipeline that can seamlessly connect across different data sources? You can do that with GlareDB! Check out the video for a preview, this repo for an example ( https://t.co/YK3cSfPhne), & this post for a step-by-step walkthrough ( https://t.co/8W83tLFbdW).
0
1
1
I'm sure the novelty will wane, but I've been getting a lot of kicks out of referring to the last 20 years or so of Apache Foundation as "the hadoop cinematic universe."
0
0
4
Look, I wrote a thing!
Ever wonder how to get the most out of your database? In our latest blog post we dive into what makes databases fast and what you can do, for any database at any scale, to get the best query performance you can. https://t.co/p31hfj1PsV
0
0
2
Hot take: the reason why Star Trek (mostly) and The Culture (almost entirely) don't have money is because they're liberal fantasies, not socialist/communist (materialist) fantasies.
0
0
0
I think we should have common language about "read (past tense) bugs" which are bugs you discover when reading code rather than by observing incorrect behavior or semantics.
1
0
1
This feature was, soup-to-nuts, all my work, but I don't think I'm entirely off base when I say, it's pretty cool.
https://t.co/2HSpe1QNGA 'In v0.8.0, we added a few features to GlareDB to support what I've been thinking of as "workload sharding." This grew out of work we were doing internally using GlareDB; since we found this pattern useful, we thought you might as well.' Check out our
0
0
2
I realize that this was 10+ years ago, but--and perhaps this is one of the reasons I keep doing this--it feels like I I've only just begun.
0
0
0
the messages are fine, good even, but I feel generationally out of places. it's not even warranted because I really started doing this software thing in 2009-2016, which is too late for being this weird.
1
0
0
I kind of cringe at the fact that I open issues on open source repos like someone who just read karl fogel's book.
1
0
0
Wouldn't it be cool if there were a google-keep style "shared task list" or just collab notes editing (so something not quite https://t.co/8fnym6SgbD, which is good but different)
0
0
0
... not just the data problems we have today, but the future that we all will exist in. The great thing about the future is that it's still mutable: in addition to building things, we shape the future by giving an actor a little black box to pull out of his pocket and talk into.
0
0
0
so I've been really keen to work on these posts about how we, @GlareDB, have been thinking about the future that we're building, because I think it's important that we take this really cool thing that we're building and make sure that it (and the world) is ready for...
1
0
0
... this isn't to say that any particular problem with crypto would be solved by having had better science fiction writers, but it sure wouldn't have made things worse.]
1
0
0
[aside, I think one of the things that the crypto space fell apart on, was that they built a really exciting database and then, rather than write some killer SF stories, they literally picked the first textbook example of how you use a database (bank account management)...
1
0
0
I admit that data analyitics is not as exciting as spaceships and aliens, but I definitely spend a lot of time talking with people and saying "but what if we didn't have to do that at all" about ETL or heavy weight distributed systems problems.
1
0
0