trueno

my org has snowflake as its data warehouse analytics space. for whatever reason analysts were given free reign to built streamlit in snowflake tools and the emoji hellscape is truly unbelievable

yo this is actually some really fire reading. i had to read it twice then go back and read the original that he's responding to here. i feel full of wonder right now seeing people who are this deep into compsci debating merits in the marketplace of ideas, there's just so much going on globally with computing that i never even get to see. super fascinating to read about the different constraints at play here even the global socioeconomic ones and how they apply to the chip world in general. it sounds like risc-v's real play is democratizing access to the entire embedded stack

yeah it's definitely confusing messaging i can't imagine being a community contributor there and saying "ok im gonna help implement this thing that they just described as not a good fit for their thing". i think being under resourced or whatever or just not having anyone on the team that would be able to pull this off is a fine thing to be forward about, but it gets confusing because they kinda frame it like it's the wrong thing to do then leave the door open for someone else to do it. if they didn't beat around the bush perhaps they'd have encryption on this already.

I was hanging around during the bootstrap era. It was fine, no i think theres some blend of where UI/UX/marketing that were way overblown that really blitzed all sites into looking the same. Every component framework or helper framework under the sun is barely doing anything different. Shadcn, daisyui, tailwind, all of that.. it's all customizable but people aren't interested in making something fresh and new using bootstrap/daisyui/shadcn/whatever, the components aren't the problem. Anyone could if they took the time and effort put together something pretty unique using any of these, but they don't. Outta the box yeah they are particularly bland (flat buttons and rounded everything literally sucks I'm so tired of it), but it's _what_ the page is and how it's arranged that is reeking with sameness / pointlessness / enshittification. And that abomination is... landing pages. These pages are fkn awful. Career UX/UI folks will defend them, and this just feels like they smoked too much of their own shenanigans.

Every SaaS under the sun, hell half the things here that end up with some sort of VC backing... the first thing they do is spin up a nothingburger landing page that says a whole lot of jack diddly squat that all have a familiar feel where everything's centered, there's meaningless bulletpoints and info cards, but no real meat or information that describes what you're after... that feeling = "how do i beat gd level 1 (this landing page) so i can find what im looking for" and yeah. This has bled into documentation spaces as well, somehow rendering documentation (the thing that is supposed to help you get oriented) feel like you can't actually find what you're looking for.

UX/UI in the past decade was blown way out of proportion and I can't help but feel like it's been shaped by way too many imperfect half theories / stupid market research and is way too heavily influenced by marketing and adspace to be taken seriously. In general there is certainly a taste for what makes a good UX and that to me is typically a blend of utility and looks-cool. But without any utility everything feels like a goddamn waste of time & I'm mostly assured that websites that sport pages like this have way too many financial strings attached driving their every move. They all try to drive you towards filling out a sales inquiry form. It's ironic and hilarious that a lot of times if I want to learn about some platform or product, the last place I can reliably go to is their own website. These days you just gotta go digging, ask claude to go collect a bunch of user feedback from around the net or something.

their reply in that issue:

"We don’t plan to implement this directly, as it is designed for test initially, we do not recommend using RustDesk with a public IP alone, that's also why direct ip access is turned off by default.

For security and privacy, we strongly advise using it in combination with a VPN—the VPN tunnel already provides end-to-end encryption, so additional encryption within RustDesk is unnecessary in that setup.

That said, we welcome community contributions! Many users express interest or share feedback—but very few take the next step and submit a pull request. If you’re able to help, your PR would be greatly appreciated! "

yeah ive read so many takes on how people survive compaction amnesia ive wired up my own "protocols" that are okay, have used things like beads, am okay burning a buttload of context right at the beginning of a post-compaction just to get up to speed and oriented.. but i still end up with a decent amount of sprawl and lately the writing style of claude has just gotten so dense and nonsensical that my eyes are starting to glaze over.

this seems to be the fate with all the big grand 'god' projects people are doing with AI. super epic omega knowledge bases, super epic omega personal platforms, etc. I don't think enough people admit that whatever they're working on has evolved into something they don't fully understand.

any recs?

i see. appreciate the reply this was concise and just what i needed

ive not paid any attention to this space much, is deepseek referring to paid-sub service like claude/gemini/etc ? or is this local llm

i was more or less testing to see how complete of an answer it could come up by scanning the whole semantic graph so i threw questions at it that spanned multiple books

damn it good point

jealous. i've had tinnitus ever since i had memories. my literal earliest memories are laying down when i was put down for a nap and vividly paying attention to the sound. dunno if i was born with it or had some crazy ear infection or what but ive just given up that anything can be done. i'm fortunate it's not all bad but i can't sleep without a fan. i sometimes get sad that i genuinely don't know what no sound is like. i've never experienced true silence :/ when im super tired i get some weird auditory effects like the tinnitus sound gets super choppy almost like a rumbly gating flutter like the tubes deep in my ear are spazzing out as im drifting off to sleep. im probably gonna die idk

i threw the entire sanderson cosmere into a RAG graph sorta deal just to see how it would do if i questioned an mcp server for it about a universe i know decently well. it was actually astoundingly good. was able to find easter eggs acrossed different books and answer dumb questions like "why is kaladin emo"

on the scroll note, the top background had a seizure while i was scrolling down

this looks prettttttty slick i might dive in later.

are people using these things but isolating agents to some sort of containerization individually or do you have like one big dev env ? probably time i get around to sorting a better dev container strategy just to isolate agents here but trying to think of the best way to set this up locally.

holy yikes

I mean I'm all for everything collapsing into sql. SQL all the things. Not really against it, I'd just rather not-AI write the challenges they were up against. It seems like these are all very behind-the-scenes scaling issues they faced, so it'd be cool to hear from them. Redis has great qualities, I don't use it often but I've also for years now understood why Redis was put in front of these use cases to handle them. Complexity be damned generally you're trying to enforce a first come first served or some level of idempotent behavior, so if sqls doing that now then hell yeah. It's just super off-putting to try and upend an important design pattern with an AI written article.

I've done multiple large scale implementations with shopify paired with many flavors of order managmeent systems as well as competing offerings in the space. The only one i haven't touched that i'd like to get my feet wet with is commerce tools.

I really just disagreed with the assessment that redis is not good enough for the job for a reservation system. I use sql database all the time, I prefer them. But I'm seeing a claude written article here that seems to heel turn on a proven technology, it would at most be insightful if there was human content in here from actual engineers at shopify who want to vouch for and explain the challenges they were up against with redis rather than just expect me to take claudes word for it. Anyone who's been dabbling with AI knows damn well that you can convince claude to write up a dissertation on any hill you want to die on.

so this is interesting to me, im in retail i work closely with platforms ive used shopify ive used magento ive used smaller players ive helped implement various pieces of all of them.

and i was excited to get some insight, then i realized that this whole thing was written by AI and im going to guess the idea and implementation were probably very AI driven.

> The solution: SKIP LOCKED > Core idea: one row per unit, bounded by design

cool, thanks claude.

Now I'm wondering what the engineering culture is even like at shopify.

Here's the thing. I like databases, I think there's a lot of shit in this space that went and smoked a shit ton their own good stuff to come up with these pure event driven designs that lock you into event workflows with no isolation and remove the ability to do broader bulk-functions.. and then do something even stupider and say "all you need for the interface is graphql" and such service/platform doesn't give you any other way to reconcile or do reporting for your org you have to warehouse from graphql.. this is crap. So seeing a headline where shopify says they want to kinda get behind a unified database strat behind the scenes even if it's not necessarily customer facing, like that's good imo. SQL is many decades of relational algebra that makes insane computations acrossed vast sets of data pure magic and one of the best query dml interfaces of all time.

..however i dont even agree with the claim their making here that redis isnt the tech for a reservation system. redis when used correctly feels like an insanely awesome way to do a reservation system, i lurv redis for stuff like that.

I'm just gonna go forward with the assumption that current and future shopify updates are pure vibeslop. I already hate their data interfaces, but compared to other saas offerings i appreciate that they do have bulk-features.

Literally cannot take this guy seriously, this guy, Sam Altman.. these dudes are memes

i've attempted signing up for this thing like multiple times over the years and i've never had luck trying to game their free tier. based on all the other comments it sounds like you're SOL at this point none available or people on 4/24 are getting downgraded. maybe i'll try again sometime but i haven't seen any recent success stories

ive lived etl and elt eras. i would never, ever go back to etl. having your business logic baked into ssis or some god forsaken piece of software was truly awful. being stuck in the rigidity of the integration or package that transformed the data in flight until some poor underpaid engineer is whipped to go make a change to it and it breaks the whole package... having to migrate legacy stuff and pick through an ssis pack age only to find no one remembers why logic is the way that it is makes me wanna find a ledge. etl was a terrible paradigm. maybe people see it through rose tinted glasses because "usable data" was what landed. servicing and scaling over a thousand etl pipelines is the worst ball torture ever, trust me. for the most part i dont think anyone needs to care much about the how/why with data lakes, a competent data strategy involves taking landed elt data and transforming it into usable reporting/integration data that becomes self service. at my last org the whole damn data lake concept freed one small subset of IT that focused on data needs and transformed the organization: all business units could finally hire their own sql analysts because data was consolidated in a warehouse and was being synchronized from many systems and applications and the all those dreams of self-serve reporting came alive. it was a monumental organizational step that changed the face of the org forever.

not much of a dbt nerd myself but sql is at least a language analysts understand, so if they go peep dynamic tables / materialized views on whats transforming the data they can get a wrangle on it. this requires no expertise in file movement and threading and surrounding whatever, the business nerds can stay business nerding and influence and at some orgs have the latitude to control the materialization logic without needing to be an engineer. it's a much better fit since analysts tend to be closer to business needs.

i dont mind blasting data in blob storage. theres a couple use cases where the "lake" thing works out, extending a postgres db to read the same data store via pglake (or duckdb + ducklake) is actually pretty slick. i build some apps that also have report pages that do some pretty heavy analytics. powerbi is effectively dead to me now.

where i think it all went wrong is literally just nomenclature. such stupid namings in the space, self importance galore. datalake is already dumb, theres ten trillion more terribly named things in the "data engineering" space, and this was an era that was largely swamped by linkedin/medium/enshittification (we got snowflake astroturfing their own subreddit trying to get people to pay for their dumb cortex ai) so data engineering is really hard to take seriously sometimes. not to mention the existence of what i consider blip in history saas services like fivetran (still not sure how these guys are still in business). it was a career step towards software for me, but looking back it is a pretty funny space shrouded in too many services and licensing. one finds it hard not to champion for postgres, duckdb, etc.

with that said, data lakes have been ridiculously effective at my last org. moving engineering full time into real time replication lords and having a whole warehouse full of everything you can possibly need enabled even greater heights for us. integrations got to just delta system vs system and true them up on 1-5 minute schedules with literally just a job that runs a select from some view which does the delta compare. doesnt sound like much but when you work at one of those dumb orgs that pays for like 75 different platforms, suddenly it started only taking us days to onboard and wire in a whole platform into the fold at the org and build out middlewares, it's actually hilarious. all of that is possible because of data lakes for the most part, though we didn't always do the "lake" thing and just materialized stuff into tables. being able to make live reporting from just about every system and bring data together acrossed many systems actually insulates us from hemmorhaging way too much money on stupid shit like salesforce and a new erp. you get to buy best in class platforms for whatever function and then your erp is just.. a damn multipage app. all that was possible with our datalake constantly having data dumped into it and going thru the infamous and inevitable end game pipeline: the road to reporting

feel like its mostly sports journalists at least in the US. pro athletes and journalists need to gtfo. everyone i knew in real life used to be on twitter. theres like one dude left, and he's just there for basketball. total graveyard on a lot of fronts. even a lot of corporate accounts that really wanted to be in the know are just auto posting graveyards now

lmao that's actually so good

microsoft those dudes are hilarious this decade plus old github request is the only one i've ever gotten email alerts for it just made me lmao more each and every year. someone dropped a cake on its tenth birthday https://github.com/microsoft/vscode/issues/519#issuecomment-...

we've been calling it meatware at work.

i just like dont read peoples md files they send me from claude anymore

theres gonna be a lot more at this rate. everyones tribalistic preferences about how web frameworks should be made... is never going to get solved. now everyone can just spend a week of their claude max plan making whatever framework they want. ive done it like twice now in the past year just for shits and giggles, it is fun but i wont pretend like i know where any of this is going, i think a hybrid of ssr and a blend of "the client should do some work" is probably the prevailing strats that will scale. something like aggrid is a very performant js datatable so i personally am not inclined to try and reinvent that from the backend, rather a backend has full coverage over its api surface but largely just sets/configures/sends data to but lets aggrid do what aggrid does. component models and diffing changes and all of that though and sending lil dom updates... shouldve never been purely on the front end to begin with. front end runtimes are about to get way smaller.

my favorite part of using whatever this weird ssr hybrid landscape ive been in is just not using graphql lol. i can just rawdog sql now for most things like the lords of data intended. its fantastic

claudes still claude. still as load-bearing as ever. the ladies have no idea how absolutely right i am every day

just ran this article that ran a cve through gptzero.. through gptzero

-GPTZero AI Detection

-Model 4.8b

-We are moderately confident this text is a mix of AI and human

-63/88 Sentences likely AI generated