464 karma · joined April 15, 2022
I think I've heard enough of how ChatGPT is better than Google Search. I'm interested in hearing from people in the know of how Google could use its very sizable and knowledgeable resources to compete with ChatGPT.
It's quite possible the right hemisphere of the brain is subservient to the left hemisphere because the language center of the brain resides in the left hemisphere. There's some evidence that the left and right hemispheres are independent actors merely coordinating with each other via the corpus callosum [1]. In such a dynamic, it's likely that the left and right hemispheres start off as equals and play a tug of war of sorts, but eventually the right lets the left lead since the left is better able able to influence the "real physical world" because of language. Language gets you help, food (energy), sex etc. So the language center may not be constrained by embodiment but it might be optimized towards getting the most out of physical reality first?
[1] https://en.m.wikipedia.org/wiki/Split-brain
P.S. the language center is not guaranteed to be in the left hemisphere. Just a high probability as far as I'm aware.
In the context of pods dynamically spinning up and spinning down, it's bad when a pod replica can't be allocated in the cluster "predictably" but there is nothing worse than when a new pod (new deployment) fails because "Marcus the pod" drank all the water and now I have to call DevOps and wait god knows how long before they spin up a new node to guarantee a spot for the new pod.
Bin-packing is a already an np-hard problem. If you remove limits from CPU then you're adding probabilities into the mix. So, for the love of god, always use limits unless you have a very specific use case.
My only concern is how "correct" the tool or the AI is.
But I wouldn't go so far as migrating existing projects from MySQL to Postgres. Use Postgres on your new projects and let the old ones continue to use MySQL unless you had very good reasons to migrate.
However there is value in applying systems dynamics to software teams and treating humans as probabilistic variables. And instead of maximazation, one can do expectation maximization i.e. finding the average outcome. Modelling such a system is hard and intutions play more of a role here because our brains are well suited to probabilistic thinking (to a degree for simple systems).
But I can see why leadership gurus don't prefer the probabilistic dynamics. Because it involves "luck" and asking leaders to do the optimal thing i.e. sticking to the expected maximum (average outcome) isn't sexy and doesn't lead to winners and losers. Instead, in a capitalistic system, all leaders are expected to engage in risky decision making and every once in a while one leader wins, standing on the shoulders of a good software development team which also happened to be on a hot streak that quarter, whereas other leaders who didn't win are blamed for the poor performance of their equally good software development teams who happened to be in a slump that quarter.
So I'd say that introversion "in India" manifests itself by having a smaller trusted social circle, having an aversion to partying and making the most of the occasional alone time one might find.
I'm speaking mostly from personal experience. I could be terribly wrong. Now that I've moved away from India and live in Europe, my lifestyle very much resembles what someone in the west expects an introvert to have.
If SQLite had better performance for OLAP queries, there is no way I wouldn't explore it as an option for work because it's so darn easy to use. The operational or hosting or cloud costs of other OLAP database is insanely high in comparison.
P.S. It's my personal opinion and experience that most companies have only about 1TB or less of analytics data. Large OLAP databases are just a waste for such small data but currently apart from DuckDB there aren't any cheap competitors for these small use cases. Postgres and SQLite are too slow (without some additional engineering).
All I ask is a Caddy style JSON configuration format for Nginx. And don't just implement some random JSON schema either, please create a well designed schema that is extensible. Take Prometheus [1] or Alertmanager [2] as examples of well designed and extensible schemas.
Just give me some basic features first, easy HTTPS, easy reverse proxy, easy rate limiting. You can release the rest of the advanced features in your own time.
[1] https://prometheus.io/docs/prometheus/latest/configuration/c...
[2] https://prometheus.io/docs/alerting/latest/configuration/
I myself never had to do text processing but instead JSON processing and that was convenient to do in Postgres directly, and I assume it's convenient to do in SQLite given the recent advancements in SQLite's JSON capabilities.
UPDATE: I checked for "hair loss" localized to the United States on Google trends. There appears to be an upward trend after 2015. I am not drawing any conclusions, just wanted to point that out.
I am of the inattentive type so I am more prone to this reflex but I am also more mindful than most who doesn't actually go through social media at all. The reflex is most likely to just check HN or Reddit. Maybe you'll be more aware and notice this reflex in other people you're in conversation with.
The fact that I am "compelled" to look at my phone instead of staying with my thoughts is not an innocuous pattern. Why do I, with perfect predictability, prefer reaching for my phone rather than staying with my thoughts? And it's a fact that this compulsion to look at my phone exists even when I'm working on something important and not just when I'm standing in the elevator.
(My tone might be aggressive. I don't mean to offend, I just disagree).
At the moment Podman is just more work for us because I and other devs don't have years of of experience and intuitions about Podman like we have with Docker. I'd rather just focus on business problems rather than another migration.
At the end of transitive reduction, you end up with a graph with all redundant dependencies removed but functionally, it is still the same graph.
The difference is in how the Class attributes are affected i.e. the values of "A.a" and "A.b".
# obj.a += (2,) has no impact on A.a since tuples
# are immutable and copies are made.
# This is unexpected from a C/C++ intuition.
>>> print(A.a)
(1,)
# obj.b += [2,] has an indirect impact on A.b
# since lists are mutable and updates are made in place.
# This is unexpected for beginners in Python since it
# deviates from how int, str and tuples behave as "+="
# can be used for int, str, tuples and lists.
>>> print(A.b)
[1, 2]
Edit: formattingI'm curious if you see it the same way?
Basically if someone is already using Postgres as a warehouse, then they can prolong their migration to Snowflake by at least a year by using something like Neon.
I manage the data warehouse mostly alone because Postgres offers guarantees, unique constraints, triggers and relationships between columns of different tables. It does the work of two engineers. Snowflake is fast but not Postgres compatible. In order to move to Snowflake, I have to write tests and maintain them which Postgres does for me for free.
I'd stick with Postgres at least until 20TB before considering Snowflake.
2) Not entirely true. On average you may be right, but some specific items that I care about, like some good brands of milk, are actually cheaper on the app than at the store (my reference store is Rewe which is the closest to me and a bit on the expensive side).
3) If the price of items is higher as you say, then shouldn't that cover the salaries of the couriers? Also they have a guaranteed minimum wage and tips. They get a great workout since it's all based on bicycles.
4) The deliveries happen from a warehouse and not the grocery store. I assume the warehouse is optimized for deliveries and not foot fall.
On average I do pay more per week, maybe +10€, which is well worth it since I have a toddler at home and every hour is accounted for.
P.S. German cities are very compact and have decent bicycle lanes.