i appreciate the way you took the feedback. i saw the domain name and immediately knew the content and context. the article did not disappoint. i come from a heavy mssql background with some postgres sprinkled in, but my current company is migrating our mssql fleet to pg and it’s nice to have a technical foundation and article to be able to truly understand and pass the differences and similarities then how the two platforms handle workload. Traditionally it’s just been multiple sides, mercilessly criticizing each other for their deficiencies, but each platform has its own strengths and its own gaps. I’m excited to be a part of this migration, and I appreciate technical articles such as this that help me articulate the broader challenges to both our executive level levels, and our developers.

edit: syntax. voice to text was liberal with the comma abuse

HyperCard was a revelation to me in high school. it piqued such an interest in technology for me that i fully pivoted from exploring civil engineering to computer sciences.

> happy to stop the freebies we give other nations.

but indignant when other nations return in kind.

one of the things that i noticed in a recent trip to austin is that the waymo vehicles were far more assertive and quick than the human drivers so maybe that has been addressed.

so happy to see Sapiens in there. what an obtuse read. here's a fun "if books could kill" episode on this work of pseudoscience https://podbay.fm/p/if-books-could-kill/e/1763632800

I am constantly so suprised to see this sentiment posted everywhere I see this book mentioned, when the book perfectly mirrored everything I learned in both my physical and cultural anthropolgy 101 courses in college (this was before Sapiens publication).

Seems to me that a reasonable reader should already assume that not all points of debate in the antropolgical literature can be expounded on in a book like this and that you can always find experts who will of course debate what constitutes a fair read of the subject matter. But in my experience the theories and histories laid out in Sapiens matches pretty squarly with what is taught at University at an undergraduate level. And isn't that pretty much what readers of this book expect?

Maybe I should check out that episode to see, but I am wondering if anyone else feels this way?

I'm not sure about Sapiens although I am aware of the popular criticism of it, I'm not informed enough to comment on it specifically. But I do take everything that particular podcast says with a mine of salt.

this isn't purely laundering blame. it is frustrating for the infrastructure/operations side is that the dev teams routinely kick the can down to them instead of documenting the performance/reliability weak points. in this case, when someone complains about the performance of the site, both dev and qa should have documented artifacts that explain this potential. as an infrastructure and reliability person, i am happy to support this effort with my own analysis. i am less inclined to support the dev team that just says, "hey, i delivered what they asked for, it's up to you to make it functional."

> From the perspective of the devs, they expect that the infrastructure can handle what the business wanted. If you have a problem you really should punch up, not down.

this belittles the intelligence of the dev team. they should know better. it's like validating saying "i really thought i could pour vodka in the fuel tank of this porsche and everything would function correctly. must be porsche's fault."

this still undersells the developers' intelligence and presses the metaphor a bit too far. if the implication is that the developers are unaware of (or do not have access to) infrastructure capabilities, that's seems like a procedural failure (communication, education, information, etc). i wouldnt expect developers to know everything, but i'd expect them to be curious about how their work will interact with the goal, at large.

yeah. ignorantia juris non excusat applies to both the speed limit and passive data theft

i want to love datagrip but it big, slow, memory-hungry, and presents an unfamiliar paradigm to me over against most tools i've used for admin tasks. other than this last issue, do you have any suggestions for streamlining the experience?

I already use several development tools from JetBrains, so it made sense to streamline everything since I'm familiar with their terminology and UI.

I recommend going with DBeaver if you're only using it for admin tasks and small queries. It's probably your best option for a free, lightweight client. Another strong alternative I keep reading about is TablePlus, but I don't have any personal experience with it.

the data types were introduced with SQL Server 7 (1998) so i’m not sure it’s accurate to state that it’s considered as the new thing.

UTF-8 was introduced in SQL Server 2019:

https://learn.microsoft.com/en-us/sql/sql-server/what-s-new-...

thanks. now i see the point that the poster was making.

i love this blend of storytelling and sharing.