turtles3

7 ms·

31.
by turtles3 3y ago
Can you elaborate on why you don't like ClickUp? I've been long in search of a Jira replacement (haven't we all) and the only one that I'm seriously considering is ClickUp. Are there any show stoppers you've seen in
32.
by turtles3 3y ago
But you still need an external->internal lookup, so doesn't that mean you still need an index on the fully random id?
33.
by turtles3 3y ago
IIRC projects only group resources under the same account. API keys are still account-wide, so projects provide no isolation there. There is a other mechanism DO has to allow multiple accounts under one billing context (I think it might be
34.
by turtles3 3y ago
The lack of ACLs or comparable permissions is by far the biggest thing that prevents me from recommending DO for production workloads. This kind of thing is absolutely essential. You can't even separate dev resources from prod resource
35.
by turtles3 3y ago
I thought they had the same deal as DO - control plane is free and you pay for nodes at the standard rate. Have I missed something? I am considering moving our DO to ovh mainly because DO lacks fine grained IAM
36.
by turtles3 3y ago
Unironically this? It might violate gdpr to get consent for the purposes of maps but then use it in more contexts. I guess they might include all purposes when the user is asked, and at that point it boils down to whether the user is being
37.
by turtles3 3y ago
I think it is also important to acknowledge that there are things innodb does better than Postgres, eg. For most workloads an undo log is a far better data structure than implementing MVCC by duplicating rows. Autovacuum and vacuum can be a
38.
by turtles3 3y ago
This sounds very much in the spirit of Grzegorz Brzęczyszczykiewicz[0] [0] https://m.youtube.com/watch?v=AfKZclMWS1U
39.
by turtles3 3y ago
Arguably they weren't 'business minded' if that was the outcome. I know what you mean, but at the same time understanding what the technical members of the team do and how they get that work done is an essential part of succe
40.
by turtles3 3y ago
Some men just want to watch the world burn.
41.
by turtles3 3y ago
That is a very specific use case, and might only be a small subset of your actual data. If you don't have these specific requirements (eg. CRUD apps), you can save yourself a lot of unnecessary headaches by defaulting to MySQL. My main
42.
by turtles3 3y ago
Unpopular opinion: if you're skimping on ops/DBA resources (as you may need to do in a startup), then MySQL is a better default. By all means use postgres if your use case demands it, but personally I find the ops story for MySQL
43.
by turtles3 3y ago
I find the opposite wrt. refactoring - that is to say integration tests are _more_ robust to refactoring than unit tests, and that's one of the reasons I strongly prefer them. Unit tests are deeply coupled to the internal structure of
44.
by turtles3 3y ago
Does AI really speed up projects by 10x? In my experience, tools like copilot help with the smaller things, but it's bigger things that really matter in a project. For example, the right database schema or the right architecture I coul
45.
by turtles3 3y ago
If you take unlimited in its most literal meaning then no, you can't provide unlimited anything. However, I think there's a difference between saying you provide unlimited storage, and a SaaS tier supporting 'unlimited'
46.
by turtles3 3y ago
I'll add that C# also has using statements that dispose the object when the current scope exits (including if it exits due to an exception) this significantly cuts down on ugliness .
47.
by turtles3 3y ago
> Additionally, there are folks using SpiceDB today by replicating denormalized checks back into their database (e.g. Postgres) or search index (e.g. Elastic) so that you can filter them natively. This is the combination of the aforement
48.
by turtles3 3y ago
This, especially when you combine it with pagination, filtering and ordering requirements. Zanzibar implementations (eg. Spicedb, keto etc) offer functionality for listing resources accessible to a given principal, but as far as I can see n
49.
by turtles3 3y ago
This is a 'guns don't kill people' argument, which historically has been a bit more complicated than that. Humans are not context-free actors independent of their environment - our environment shapes us. And the argument here
50.
by turtles3 3y ago
Completely agree with this approach - recently I find that most of the tests I write are so-called 'integration' tests. I find these tests not only get more code coverage for fewer tests, but they more closely represent the real o
51.
by turtles3 3y ago
> Merge squash works every time. Unless you've already started a follow-up branch before the first gets merged (eg. Waiting for QA, PO review etc.) Then you at minimum will need to rebase your second branch after the first is merged
52.
by turtles3 3y ago
Are there any payment processors you can recommend, especially re. fraud protection? We have started out with stripe (because the API is so damn convenient), but HN has so many stories like this were seriously reconsidering that choice. It&
53.
by turtles3 3y ago
However, the same thing could be achieved with closed source models. There's nothing to stop an LLM being made available to run on prem under a restrictive license. It would really be no different to ye olde desktop software - keeping
54.
by turtles3 3y ago
This may be irrational but it's something that worries me about using postgres in production. Sure as a developer I love all the features, but the fact that the query planner can suddenly decide on a radically different (and incredibly
55.
by turtles3 3y ago
>It will quack like self consciousness but is not actually self conscious. But isn't this the point of the Turing test? Since we cannot determine otherwise, if something exhibits all of the outward observable behaviour of consciousn
56.
by turtles3 4y ago
Presumably the article is meaning two CPU sockets, rather than two cores?
57.
by turtles3 4y ago
I don't think it's as simple as that - we have higher level languages that protect us from trivial security issues like buffer overruns, but that's a net good. There is no advantage we would gain in security from rolling that
58.
by turtles3 4y ago
I think the root of the issue is not that we need imperative languages for configuring cluster workloads - declarative state as an API contract between clients of the cluster and the cluster itself is a good thing. The reconciliation model