groestl

11 ms·

151.
by groestl 2y ago
> When UUIDs become your bottleneck. When UUIDs become your bottleneck you'll be celebrating for picking UUIDs, because now you can move to a distributed architecture and not worry about IDs.
152.
by groestl 2y ago
If the UUID is used for external representation, now you need to join a row to get it.
153.
by groestl 2y ago
> Using completely random UUIDs is IMO the worst choice Can't say that without context. I've worked in systems where even the version bits were randomized, and for good reason (i know, technically, no UUID anymore).
154.
by groestl 2y ago
Okay, but in a live DB, typically you won't have only inserts while migrating, won't you?
155.
by groestl 2y ago
Ha? Please elaborate.
156.
by groestl 2y ago
Making companies, or individual contributors even, responsible for society's continued failing seems to distract from the real task: democratically ensuring that no profit can be made from worsening the world. Otherwise it's ratio
157.
by groestl 2y ago
I don't see how that follows. I certainly didn't feel atomized or depressed when I was part of a highly functional team. Maybe you mistook my comment for a statement on society at large? That was not my intention at all. My post i
158.
by groestl 2y ago
I don't need different perspectives if I execute a vision as efficiently and fast as possible. I need different perspectives if I want to calcify a business model (sometimes, of course, that's also worthwhile to do).
159.
by groestl 2y ago
Na, been working with similar people a lot. You can get a lot done if you understand each other easily and it does not feel like your hands are tied behind your back. As long as the premise of your business is correct (this is something tha
160.
by groestl 2y ago
It's called "Rolladen", quite popular here in Austria. https://www.rolladenplanet.de/vorbaurollladen/rollladen-stan...
161.
by groestl 2y ago
> both good and bad Not arguing against that. The first thing is to be able to steer. And then you can steer in the right direction. So I'm glad it seems we'll finally be able to steer. Now we can figure out where exactly we wa
162.
by groestl 2y ago
> and EU regulations have teeth As someone who has been involved in this journey from the beginning, essentially starting from a point akin to "fuck the EU, they're laughably ignorable" it's really interesting to read
163.
by groestl 2y ago
Large organizations don't improve by innovating. As the article mentions, they focus on sustaining the existing business model, anything that diverges from process potentially destroys the revenue source. Instead, they improve by acqui
164.
by groestl 2y ago
Drastic measures to avoid model degradation because of feedback loops ;)
165.
by groestl 2y ago
Sharing accounts is like sharing a toothbrush, that's my philosophy ;)
166.
by groestl 2y ago
That's the point.
167.
by groestl 2y ago
I did a 24 hours blood pressure monitoring once. Every 30min it would go off. I was worried I'd never fall asleep and blood pressure would not show the normal rhythm, and it absolutely felt that way, but the reading definitely showed I
168.
by groestl 2y ago
Not disagreeing. Point is, you need to know your domain, your technology, your write patterns, your downstream systems, etc to decide if a specific key scheme works to your advantage or not. All the more reason not to use natural keys, as t
169.
by groestl 2y ago
> A problem with this approach is it's not monotonical Whether or not that's bad fully depends on your platform and the number of writes you do. If you're using a massively distributed database like Datastore, Spanner etc,
170.
by groestl 2y ago
Adding to the list of comments damning this post to ensure none of my future colleagues follow this advice. > You think your surrogate key will save you? It will not. It definitely will, say my 20+ years of experience.
171.
by groestl 2y ago
But why? I don't get it. You call something. It can break. It will break. Treat it as such wrt to resources you've allocated. You can ignore error details here. At the highest level of your application (and at a few critical place
172.
by groestl 2y ago
Other programmers tend to be bad at reliably cleaning up resources such as file handles, locks etc, so I need to inspect the whole invocation tree anyways to have an understanding of what runtime implications I've summoned by invoking
173.
by groestl 2y ago
> I mean, it’s a language based around exceptions for flow control, I think the “easy to reason about” ship has sailed. Sometimes I wonder if I'm exceptionally (haha) talented as I personally find the impact of exceptions on flow co
174.
by groestl 2y ago
It's a feedback loop.
175.
by groestl 2y ago
I know only for a fact that I'm conscious ;)
176.
by groestl 2y ago
Well, Google Analytics actually forbids it's users to send PII (sure, you can't avoid communicating the IP address as part of the request).
177.
by groestl 2y ago
My servers beg to differ.
178.
by groestl 2y ago
I don't know about the legality of forging an old employee badge, but I find it amusing that apparently the forger broke, for totally no reason, the Geneva Convention protection of the Red Cross symbol, signed into law in many many cou
179.
by groestl 2y ago
I'd recommend starting at a company of 30-50. It's large enough so some processes are already there, yet small enough that your actions have impact, and you have influence on the processes. Software companies at this size have a p
180.
by groestl 2y ago
That's what I'm hinting at :)

More ›